Capture published Tilda pages

Paste the live tilda.ws or custom-domain address. Begin with a page that represents the site's main layout, then use site scope for discoverable public routes. Private project links and unpublished pages cannot be captured.

Compare the report with a list of important pages. Keep a separate record of campaign landing pages that are not linked from the main navigation so missing public URLs can be handled explicitly.

Review Zero Block and motion at each width

Check alignment, font rendering and image positioning on desktop and phone. Zero Block layouts and animated elements deserve interaction testing; a matching still image does not establish that every transition works.

Inspect scripts and media requests that still use the original service. Retain dependencies only when they fit your migration plan, and replace missing or unreliable interactions before treating the export as production-ready.

Reconnect forms, CRM and store actions

Confirm where every form submits and what happens after success. HTML can include fields and validation markup without providing message delivery or a CRM database. Connect your intended service and send a test submission.

Test store and payment actions separately from the page layout. Publish a temporary deployment, check route loads and responsive behavior, then switch your domain after the new services and pages are working.

Edit, deploy and protect your search URLs

Keep the downloaded HTML, CSS and assets together. Store a copy in your own GitHub repository to track changes; a repository is source storage, so configuring a deployment is a separate step. You can publish static files to your own Cloudflare account or another compatible static host.

For changes through an AI agent, connect it to FNJ MCP and give it the intended site and a specific task. Review the draft and its preview before publishing. Use the agent prompt library for content, links and CMS tasks, and the deployment guide for the next steps.

Keep existing page paths when practical. Map changed URLs to their closest replacements with permanent redirects. Check titles, descriptions, canonical URLs and internal links on the final domain, then submit its sitemap in Search Console. These checks help search engines find the replacement pages; they do not guarantee unchanged rankings.

Google Search Central: moving a site with URL changes

Your Tilda launch checklist

Compare Zero Block layouts and animation behavior with the live Tilda page.
Check whether fonts and media still request files from Tilda after deployment.
Submit a form and complete a store test using your replacement CRM or checkout.

Can I import the exported HTML back into the Tilda editor?

FNJ generates editable page files, not a Tilda project format. Maintain the exported HTML and CSS in your code workflow rather than expecting editor round-trip support.

Export Tilda to HTML: Zero Block, forms and migration checks