FNJ / URLs & SEO
Preserve URLs and SEO when moving an exported site
Map old and new routes, check canonical tags and metadata, test redirects and review indexability on the final domain.
Start with the outcome
A migration plan that keeps useful page addresses and identifies any changed ones. Metadata and redirects help search engines understand the move, but neither an export nor a new host guarantees that rankings stay the same.
Choose your original builder below. The task is shared, but the dependencies, URL structure and missing features to check depend on the platform. Each guide includes a reviewed platform note, a full procedure and a prompt you can adapt for your agent.
Choose your website builder
Framer / URLs & SEO
Preserve URLs and SEO when moving an exported site
For Framer, compare CMS slugs and collection detail paths as well as the homepage. The deployed domain should own its canonical URLs. Keep equivalent article routes or map changed ones explicitly, and review redirects through the final hostname before removing the original hosted site.
Read the guide →Webflow / URLs & SEO
Preserve URLs and SEO when moving an exported site
Review Webflow collection folders and item slugs, not just static page names. Some old links may target the webflow.io address while others use a custom domain. Normalize your internal links and canonical URLs for the chosen final hostname and test each changed collection path through its relevant redirect.
Read the guide →Gamma / URLs & SEO
Preserve URLs and SEO when moving an exported site
Separate Gamma card anchors from actual page URLs in your migration map. An in-page section ID is not a new crawlable article route. Preserve useful anchor targets when editing cards, and give independently published pages their own titles and canonical URLs on the final host.
Read the guide →systeme.io / URLs & SEO
Preserve URLs and SEO when moving an exported site
Map funnel step addresses and confirmation paths before moving hosts. Preserve campaign query strings where your services need them, and check that a redirect does not send a purchaser to a generic marketing page. Canonicalize public content pages thoughtfully; private transaction and member flows have different requirements.
Read the guide →Carrd / URLs & SEO
Preserve URLs and SEO when moving an exported site
For Carrd, preserve section IDs used by existing links and ads. An anchor such as #contact does not create another HTML page or sitemap entry. If you introduce separate pages, give them real routes and update navigation intentionally while retaining useful landing-page anchors.
Read the guide →Duda / URLs & SEO
Preserve URLs and SEO when moving an exported site
Use the published Duda custom-domain paths as your route baseline. A capture block or omitted page should be fixed or explicitly replaced before DNS changes. Redirecting a missing business page to the homepage hides the gap from a casual menu test but does not preserve its content.
Read the guide →Elementor / URLs & SEO
Preserve URLs and SEO when moving an exported site
Audit WordPress permalinks, category links and article pagination alongside Elementor landing pages. If you remove archive or search functionality, provide an honest navigation replacement instead of publishing empty copied shells. Map changed article paths specifically and review canonical tags inherited from the old WordPress origin.
Read the guide →Squarespace / URLs & SEO
Preserve URLs and SEO when moving an exported site
Check Squarespace article and gallery slugs plus any scheduling or store destinations that remain external. Preserve public article paths where possible and separate deliberate external service links from stale internal links. A new domain canonical should identify the corresponding article, not collapse the whole blog to one URL.
Read the guide →Strikingly / URLs & SEO
Preserve URLs and SEO when moving an exported site
Keep section anchors used in Strikingly navigation and inventory any additional public paths. Member and store links may intentionally stay external. Update only the links that should become local, and do not create sitemap entries for page sections that have no independent URL path.
Read the guide →Tilda / URLs & SEO
Preserve URLs and SEO when moving an exported site
Tilda campaign pages may be absent from main navigation but still receive traffic through old URLs. Include those authorized public paths in the migration inventory. Preserve useful section anchors and map any renamed landing pages explicitly, keeping tracking and form destinations distinct from canonical content URLs.
Read the guide →Weebly / URLs & SEO
Preserve URLs and SEO when moving an exported site
Record legacy .html paths and test their behavior on the chosen host. Cloudflare Pages may normalize HTML files to extensionless URLs, so inspect response headers and final canonicals rather than assuming the visible filename is the public URL. Use the actual served path consistently in links and the sitemap.
Read the guide →Wix / URLs & SEO
Preserve URLs and SEO when moving an exported site
Wix pages that depend on scripts must contain usable content in the replacement, not only matching URLs. Inventory item and category paths before changing hosts. If the capture misses the main content, repairing canonical tags alone cannot make it an equivalent page; rebuild or retain the original until it is usable.
Read the guide →What a completed task should demonstrate
- Important old paths reach the intended equivalent content.
- Canonical tags and sitemap URLs use the final public domain.
- Published pages are indexable and return the intended status.