Keep an inventory of .html page URLs

Use the published weebly.com or custom-domain address. Record important pages and their exact paths, including .html endings. Start with one page, then compare the full-site report with your inventory.

FNJ writes captured .html routes as files. After deployment, open those addresses directly and refresh them. Navigation alone is not enough to verify routing: a host can serve the homepage correctly while a nested file path returns an error.

Separate public content from Square services

A captured product page may display its original content without including inventory or order management. Keep Square or connect another commerce backend for cart, payments and purchase handling.

Check form actions and menu links. Decide whether each still relies on the original Weebly domain, and test replacement endpoints on the deployed version. File ownership does not recreate the platform's hosted services.

Test the final host before switching traffic

Review fonts, images, mobile navigation and links to legacy page paths. If a path must change, create a redirect to its closest replacement rather than sending every old page to the homepage.

Complete a test form submission and the appropriate commerce test flow. Keep the original site available while validating the preview, then update the domain and recheck important URLs on the final address.

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

Open every exported .html path directly on the target host, not only through navigation.
Check images and menu links after moving to your own domain.
Test contact forms and Square checkout separately; their backends are not in the HTML files.

What should I check for Weebly pages ending in .html?

Open each exported .html URL directly on your chosen host and reload it. FNJ writes these routes as files, but your hosting configuration must still serve their paths correctly.

Export Weebly to HTML: page URLs, forms and Square commerce