Confirm the published URL is accessible

Use the live address visitors open, preferably the site's published custom domain if available. FNJ cannot fetch a private editor workspace or bypass access controls. If the host blocks capture, the error is a migration constraint to resolve first.

Convert one accessible page before attempting the entire site. Check headings, images and layout in the preview, then compare the full-site report with an inventory of the public pages you need.

Audit responsive content and widgets

Open the result at desktop and phone widths. Review navigation, responsive sections, image crops and widgets that display different content across devices. Do not infer mobile parity from a desktop preview.

Appointments, stores and forms need services behind them. Record each widget's original destination and whether it still calls Duda or another provider. Keep working external integrations or rebuild them before visitors rely on the new site.

Validate the replacement site on a temporary domain

Submit a form, make a test booking through the chosen service and follow every important CTA. Check direct visits to nested pages and reloads, not just navigation from the homepage.

Move the domain after the exported version is usable for the site's actual customers. A small brochure site and a booking-heavy business need different launch checks even when their page designs look similar.

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

If Duda returns a capture block, try its published custom domain; FNJ cannot bypass access controls.
Compare responsive sections and images at desktop and mobile widths.
Book a test appointment and submit a test form through replacement services before changing DNS.

Can FNJ bypass a Duda capture block?

No. Use a publicly accessible published address and review the reported error. FNJ does not bypass passwords or platform access restrictions.

Export Duda to HTML: capture checks and migration planning