Discover public pages from site links and the sitemap.
Example: https://your-site.mystrikingly.com
Strikingly store, memberships, forms, and platform widgets may still need the original service. Next.js export is in development.
What a Strikingly HTML export includes
Paste a public Strikingly address to create a static copy of pages FNJ can discover. The exported markup can be edited and hosted elsewhere, but platform widgets are separate from the visible page HTML.
How to convert a Strikingly site to HTML
- 01 / Paste a public URL
Use a published Strikingly 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
Review every section at mobile width as well as desktop. Check navigation, forms, embedded media and any store or membership widget. Keep or replace the service behind each widget before using the static page in production.
Strikingly 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:
- Use the published Strikingly URL and test section navigation after capture.
- Inspect mobile spacing, embedded media and any platform widgets in the preview.
- Submit test forms and exercise store or membership actions through their new services.
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 →Strikingly to HTML: export and hosting FAQ
- Can FNJ capture a private Strikingly site?
- No. The converter reads only pages published for visitors at the URL you provide.
- Do Strikingly widgets become standalone code?
- Not automatically. Widgets may still call Strikingly or third parties, and their hosted data and actions need their own integration.
- Does a Strikingly HTML capture keep membership access rules?
- No. Public page HTML does not transfer authentication or membership permissions. Keep or implement a membership service before publishing restricted content elsewhere.
- Can I edit the Strikingly 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 Strikingly do not automatically sync.
- Can I host the Strikingly 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 Strikingly 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 Strikingly HTML
Host your Strikingly HTML export on Cloudflare
Deploy Strikingly HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Strikingly HTML code to GitHub
Put your Strikingly 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 Strikingly 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