How to migrate from WordPress to Framer without losing SEO, traffic, or leads

1. Start with an inventory, not a redesign

Before designing or building anything, create a complete picture of the existing website.

Crawl the WordPress site and collect every public URL you can find. Do not rely only on the main navigation: older landing pages, campaign pages, resources, author archives, partner pages, and unlinked content may still receive traffic or backlinks.

For each URL, record:

• Page title and current URL
• Page type and template
• Organic traffic and conversions
• Backlinks or referral traffic
• Indexing status
• Proposed action
• New destination URL
• Redirect requirement

Use several sources together: a crawler, the WordPress page and post lists, the XML sitemap, Google Analytics, and Google Search Console. No single source will reveal the whole site.

This inventory becomes the source of truth for design, content migration, redirects, QA, and launch.

2. Separate the website into page types

Not every WordPress page should be handled in the same way. Group the inventory into practical categories:

• Core static pages, such as Home, About, Pricing, and Contact
• Product and service pages
• CMS content, such as blog posts, case studies, resources, and authors
• Campaign and paid landing pages
• Legal and compliance pages
• Partner, event, and legacy pages
• Utility pages, including thank-you pages and form confirmation pages

This classification helps define the Framer architecture. Static pages can be rebuilt directly, while repeatable content should usually become Framer CMS collections. It also reveals which parts of the migration can be automated and which require manual work.

3. Choose what to migrate, redirect, or retire

For every existing URL, choose one of three outcomes.

Migrate: Keep the page when it remains strategically relevant, receives meaningful traffic, earns backlinks, supports a campaign, or contributes to conversions.

Redirect: If the old page is no longer needed but has traffic, links, or search visibility, redirect it to the closest relevant page on the new site.

Retire: Remove pages only when they have no meaningful value and no suitable replacement. A retired URL should return a deliberate status rather than redirecting every obsolete page to the homepage.

Traffic should inform the decision, but it should not make the decision alone. A low-traffic page may still be essential for sales enablement, compliance, customer onboarding, or an active campaign. The migration team can prepare the data, but business owners should confirm what still matters.

4. Preserve URLs wherever possible

Changing a CMS does not require changing every URL.

If an important WordPress page already has a clear, useful slug, keep it in Framer. Preserving the URL reduces the number of redirects, limits risk, and makes it easier for search engines and users to understand that the page still exists.

Before changing a URL, ask whether the new structure creates a meaningful long-term improvement. Cosmetic consistency alone is rarely worth the migration risk.

When a URL must change, map the old address directly to the most relevant new page. Avoid redirect chains such as old URL to temporary URL to final URL. Each old URL should point to its final destination in one step.

5. Build the redirect map before launch

Redirects are part of the migration architecture, not a launch-day cleanup task.

Create a redirect sheet with at least these columns:

Framer supports redirects in Site Settings. Test every rule in the production environment and confirm that it returns the expected status and destination. Pay special attention to trailing slashes, capitalization, query parameters, and old WordPress category structures.

6. Export and review WordPress content

WordPress provides a native export tool for posts, pages, comments, custom fields, categories, and tags. Treat that export as a content source and backup, not as a guaranteed one-click Framer import.

WordPress installations vary widely. Page builders, plugins, shortcodes, custom fields, and embedded blocks can store content in ways that do not map cleanly to Framer. Review the exported data before deciding how to migrate it.

For smaller sites, manual migration may be faster and cleaner. For larger CMS libraries, prepare structured CSV files that match the destination collections. A migration script can help when the content is consistent, but automation should always be followed by visual and editorial QA.

Do not assume that copying text is enough. Check images, alt text, captions, internal links, author data, publication dates, embeds, downloads, and SEO fields.

7. Map WordPress content to Framer CMS

Design the Framer CMS model before importing content.

For each collection, define the fields the new templates actually need. A blog collection might include:

• Title
• Slug
• Excerpt
• Cover image and alt text
• Author reference
• Publication date
• Category or topic
• Rich text content
• SEO title and description
• Social sharing image
• Canonical URL, if needed

Keep the model purposeful. Recreating every historical WordPress field can carry old complexity into the new system. At the same time, removing fields without auditing their use may break filters, templates, structured data, or integrations.

Import a small sample first. Test long titles, missing images, complex rich text, duplicate slugs, and unusual embeds before migrating the full library.

8. Preserve SEO metadata

A page can look identical after migration and still lose important search information.

For every indexable page, review:

• Page title
• Meta description
• URL and canonical URL
• H1 and heading hierarchy
• Image alt text
• Open Graph title, description, and image
• Structured data
• Indexing directives
• Internal links

Framer can generate a sitemap and provides page-level SEO settings, but these still need to be configured correctly. Confirm that every intended public page appears in the sitemap and that private, duplicate, staging, or utility pages are excluded from search where appropriate.

Also review `robots.txt`. It controls crawler access, but it is not a reliable method for removing an already indexed page from search results. Use the correct page-level indexing settings for that purpose.

9. Be careful with staging and indexing

Staging environments should not compete with the live website in search.

While the Framer site is being built, prevent staging pages from being indexed. Before launch, remove any temporary restrictions from the production domain and verify that important pages are crawlable.

This sounds basic, but it is one of the easiest migration mistakes to make: a team blocks indexing during development and forgets to reverse the setting at launch.

10. Use a phased migration for larger sites

For a small marketing site, a single launch may be reasonable. For a large site with many CMS pages, active campaigns, or complex integrations, a phased migration can reduce risk.

Framer supports page-by-page migration through reverse proxy hosting. This can allow selected paths to be served from Framer while the rest of the website remains on the existing platform.

A phased approach can help teams:

• Launch priority pages earlier
• Validate analytics and conversion flows in production
• Migrate CMS content in manageable batches
• Compare performance before moving the whole site
• Reduce the impact of unexpected issues

However, phased migrations add routing and operational complexity. Define who owns the domain, proxy configuration, publishing process, and rollback plan before starting.

11. Reconnect forms, tracking, and conversions

Forms are not just interface elements. They often connect to CRM fields, lead routing, notifications, scheduling tools, attribution, and automation.

Map every important conversion path, including:

• Demo and contact forms
• HubSpot forms and workflows
• Chili Piper or other scheduling flows
• Newsletter subscriptions
• Gated resources
• Event registrations
• Thank-you pages
• Hidden fields and campaign parameters

Visible services can usually be identified during the technical audit. What often requires client input is the hidden logic: internal routing rules, lead qualification, lifecycle updates, notifications, and workflows that cannot be understood from the public page alone.

Before launch, submit test leads through every critical form. Confirm that the data reaches the correct system, required fields are preserved, notifications are sent, scheduling works, and conversion events are recorded.

12. Keep analytics clean during the move

Reinstall analytics intentionally instead of copying every historical script into the new site.

Create a tracking inventory that covers:

• Google Analytics 4
• Google Tag Manager
• Ad platform pixels
• Consent and cookie tools
• CRM tracking
• Heatmaps or session recording
• Custom conversion events

Framer supports Google Analytics and Google Tag Manager, but adding the container is only the first step. Confirm that page views, form submissions, CTA clicks, and campaign parameters work as expected.

Preserve event names where possible so reporting remains comparable before and after launch. Annotate the migration date in reporting tools and avoid changing the platform, URL structure, tracking taxonomy, and conversion definitions simultaneously unless the project requires it.

13. Run a full pre-launch QA

The final review should cover more than visual accuracy.

Check:

• Desktop, tablet, and mobile layouts
• Navigation, footer, and all key links
• CMS templates and edge cases
• Forms and CRM delivery
• Scheduling and automation flows
• Redirects and 404 behavior
• Titles, descriptions, canonicals, and social previews
• Sitemap, indexing settings, and `robots.txt`
• Analytics and conversion events
• Cookie consent behavior
• Performance and image loading
• Accessibility basics, including keyboard navigation and alt text

Run a crawl of the staging or preview site and compare it with the migration inventory. This catches missing pages, broken internal links, duplicate metadata, and unexpected indexable URLs before they reach production.

14. Launch carefully

Before changing DNS or routing, prepare a launch plan with named owners, a maintenance window, and a rollback path.

At launch:

1. Publish the final Framer version.
2. Connect the production domain or update the routing configuration.
3. Verify SSL and both root and `www` domain behavior.
4. Test priority pages and conversion flows.
5. Run the redirect checks.
6. Confirm analytics in real time.
7. Verify the sitemap and submit it in Google Search Console.
8. Crawl the live site for errors.

Do not delete the WordPress site immediately. Keep a recoverable backup until the new site, redirects, content, and integrations have been validated in production.

15. Monitor SEO for 30 to 90 days

Launch is the beginning of the monitoring period, not the end of the migration.

Track:

• Organic traffic and conversions
• Indexed page count
• Search impressions, clicks, and average position
• 404 errors and redirect failures
• Pages discovered but not indexed
• Changes in top landing pages
• Form submissions and lead quality

Some fluctuation is normal after a migration. Investigate sustained drops at the page or template level. Common causes include missing redirects, changed internal links, accidental `noindex` settings, lost metadata, rendering problems, and content that was shortened or removed during redesign.

Avoid making broad SEO changes immediately after launch unless they solve a confirmed issue. A stable migration gives you a clean baseline for future optimization.

WordPress to Framer migration checklist

Before the build

• Crawl the WordPress site
• Export WordPress content
• Collect GA4 and Search Console data
• Identify backlinks and high-value landing pages
• Classify page types
• Decide what to migrate, redirect, or retire
• Define Framer CMS collections
• Map forms, analytics, and integrations

Before launch

• Preserve important URLs
• Prepare and test redirects
• Migrate SEO metadata and structured data
• QA CMS content and internal links
• Test every critical conversion flow
• Validate analytics and consent tools
• Check sitemap, indexing, canonicals, and `robots.txt`
• Crawl the complete staging site
• Prepare a backup and rollback plan

After launch

• Crawl the production site
• Submit the new sitemap
• Monitor Search Console and analytics
• Fix 404s and redirect issues
• Compare traffic and conversions with the pre-launch baseline
• Keep the old WordPress installation recoverable during validation

Final thought

The safest WordPress-to-Framer migration is not the one with the fewest old pages. It is the one where every page, URL, integration, and search signal has an intentional destination.

If SEO preservation is a priority, migrate first and optimize second. Once the new site is stable, indexed, and accurately measured, you can improve the content and structure with much greater confidence.

Official resources

• Framer: Migrate a site page by page‍
• Framer: Set up redirects to maintain SEO ranking
• Framer: WordPress to Framer guide
• Framer: Set up Google Analytics
• Framer: Add Google Tag Manager
• Framer: Access the sitemap.xml file
• Framer: Access the robots.txt file
• WordPress: Tools Export screen
• Google Search Central: Site moves with URL changes
• Google Search Central: Redirects and Google Search