Discover public pages from site links and the sitemap.
Example: https://your-site.weebly.com
Weebly or Square commerce, forms, and platform widgets need separate integrations. Next.js export is in development.
What a Weebly HTML export includes
FNJ captures visitor-facing Weebly pages and reachable assets. It also handles published routes ending in .html, which some Weebly sites use. The result is a static site, not a Weebly editor project.
How to convert a Weebly site to HTML
- 01 / Paste a public URL
Use a published Weebly page you own or are allowed to convert. A private project link cannot be captured.
- 02 / Choose the scope
Capture one page, or discover linked public pages and pages exposed in the site's sitemap. Review the capture report for omissions.
- 03 / Preview and export
Check the HTML preview, then edit, download or deploy the captured files according to your FNJ access.
What FNJ captures
FNJ saves public page markup and accessible styles, images and other assets. You can capture one page or let it discover linked public pages. Uncopied assets and external scripts may still load from the original service.
Before you publish
After capture, click through the exported navigation and confirm that .html page links resolve on your target host. Check forms and Square-powered store actions separately; their data and payment services are outside the exported files.
Weebly migration checks
A static export captures public pages, not the builder account or its hosted workflows. Check these before directing visitors to the new host:
- 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.
Keep your pages findable after the move
Keep important URLs and page titles where possible. If a path changes, redirect its old URL to the matching new page. Review canonical URLs and your sitemap on the final domain, then check indexing and crawl errors in Search Console. The export cannot guarantee that a search ranking will stay the same.
Follow the edit and deployment guide →Weebly to HTML: export and hosting FAQ
- Will my Weebly .html page URLs still work?
- FNJ writes captured .html routes as files rather than treating them as folder names. Test each route on the host you choose before switching traffic.
- Is my Square store exported?
- No. Public product pages may be captured visually, but inventory, payments and orders require Square or another commerce backend.
- 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.
- Can I edit the Weebly HTML and CSS after downloading?
- Yes. The captured HTML, CSS and accessible assets are editable files. Work in your code editor or use supported FNJ MCP tools with a connected agent. The export is a snapshot; changes made later in Weebly do not automatically sync.
- Can I host the Weebly HTML export on Cloudflare?
- You can deploy the static files to your own Cloudflare account or another compatible static host. Preview every page and reconnect hosted forms, payments and other services first. A GitHub repository can hold the source files; pushing code is separate from configuring its hosting.
- Is the Weebly converter free or does it need an account?
- Converting requires a signed-in FNJ account and the access shown in current FNJ pricing. You can read this guide without signing in. Check the pricing page for current purchase terms; no builder subscription or private account access is used to fetch public pages.
Need the next step? Connect your agent through MCP, copy a site editing prompt, or check current FNJ pricing.
Where to take your Weebly HTML
Host your Weebly HTML export on Cloudflare
Deploy Weebly HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Weebly HTML code to GitHub
Put your Weebly HTML export in your own GitHub repository. Choose the right files, review the fnj-export branch and plan updates and hosting.
Follow the workflow →Make your Weebly export work for you
Practical guides for editing the captured HTML, reconnecting services and checking the result before launch.
Edit with MCP →
Connect an agent to FNJ MCP, inspect the correct route, change content and review the draft before publishing.
Reconnect forms →
Audit form actions, connect your own submission service and verify delivery, validation and error feedback after moving hosts.
CMS & content →
Separate captured article pages from the original CMS, inventory content and choose a tested publishing workflow for future updates.
URLs & SEO →
Map old and new routes, check canonical tags and metadata, test redirects and review indexability on the final domain.
Mobile layout →
Compare narrow and wide previews, fix overflow and navigation, and verify touch, keyboard and reduced-motion behavior.
Images & fonts →
Find failed asset requests, correct relative paths, inspect external dependencies and preserve typography on the new host.
Export troubleshooting →
Separate URL access errors, capture limits, missing content and deployment problems using a small reproducible conversion.
Explore related converters