Capture the published site, not the Designer

Use the live custom domain or published webflow.io address. A Designer link represents an editing workspace, not the public HTML the converter reads. Start with one page to review the layout, then capture the public site when that preview is usable.

List important landing pages and CMS item URLs before the capture. Compare that list with FNJ's report afterwards. A linked page or sitemap entry can be discovered, but an unlinked, unpublished or restricted page cannot be assumed to be included.

Move CMS content and interactions deliberately

A captured CMS item becomes a static page. Changing its content in Webflow later will not update the HTML download. Decide whether you need occasional file edits or a new CMS publishing workflow before switching traffic.

Test dropdowns, navigation and animated sections on the exported preview. Webflow scripts can remain external. If you need the site to work independently of Webflow, inspect those dependencies and replace the interactions that still require them.

Reconnect forms and ecommerce before launch

Keep an inventory of every form action and purchase link. Visible fields and buttons are not a form inbox or an order-processing system. Connect each action to your chosen service and test the entire journey, including confirmation pages.

Publish first on a temporary URL in your own hosting account. Check direct visits to CMS paths, images and fonts, and mobile navigation before pointing your domain at the static site.

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 Webflow launch checklist

Open each captured CMS item URL and confirm its content is present; collection data will not update automatically.
Submit a test form and complete a test checkout on the new host before moving your domain.
Check interactions and animations with the original Webflow site closed; external Webflow scripts may still be required.

Is this a Webflow Designer project export?

No. FNJ captures the published page output. You receive editable HTML and assets, not a Designer project, Webflow CMS database or account configuration.

Export Webflow to HTML: CMS, interactions and hosting guide