Do not migrate the design and abandon the authority.

If the old WordPress site has rankings, backlinks, or branded search equity, the migration needs a preservation plan before anyone rebuilds the pages.

Before design starts

Create the inventory first. The old site may look tired, but it may also contain the exact URLs, backlinks, service pages, and local signals that keep the business findable.

• Crawl every indexable URL.
• Export top organic landing pages from Search Console.
• Identify pages with backlinks, conversions, or local relevance.
• Capture current titles, descriptions, canonicals, H1s, and schema.
• Flag thin or obsolete pages for consolidation instead of deletion.

Before launch

The new Framer site should launch with a migration packet, not a hope. Every important old URL needs a destination and every important new page needs machine-readable context.

• Map old URLs to new URLs with 301 redirects.
• Preserve or improve metadata on priority pages.
• Publish sitemap.xml, robots.txt, and llms.txt.
• Validate JSON-LD for service, organization, article, FAQ, and breadcrumb pages.
• Check internal links and canonical URLs.
• Run a pre-launch crawl and a post-launch crawl.

After launch

Search and AI systems need time to process changes. The first month is for monitoring, correction, and proof that the move preserved the signal.

• Watch 404s and redirect chains.
• Submit sitemap in Search Console.
• Check branded and service-query rankings.
• Run a Mythos audit or monitor rerun 30 days later.
• Update comparison and FAQ pages based on buyer questions.

Next step

Built in Framer? Run the free Framer AEO Gap Check to see whether ChatGPT, Claude, and Gemini can explain the company behind the site.

Framer-aware resources

• Framer AEO Gap Check — Built or migrated a site in Framer? Run a free Mythos proof to see whether ChatGPT, Claude, and Gemini can explain, cite, and compare your company.
• Framer AEO Scanner vs Mythos — Compare Framer's AEO Scanner with Mythos: a quick site scan versus a founder-reviewed AI visibility audit across ChatGPT, Claude, and Gemini.
• Is Framer Good for AI Search Visibility? — Framer can support strong SEO and AI-readable site structure, but visibility depends on content clarity, schema, citations, and whether AI engines actually cite you.
• How to Add llms.txt and Schema to a Framer Site — A practical guide to llms.txt, JSON-LD schema, metadata, and AI-readable structure for Framer sites.
• Framer vs WordPress for SEO and AI Visibility — Compare Framer and WordPress for SEO, AEO, security, publishing workflows, schema, redirects, and authority preservation.
• Aegis vs Framer: Website Builder vs Authority Rebuild — Compare Framer's website-building platform with Aegis, the authority rebuild layer for preserving SEO, routes, schema, redirects, and AI-readable source signals.
• Framer vs Custom React Site for Authority — Compare Framer and custom React/static sites for SEO, AI visibility, publishing control, schema, redirects, performance, and authority maintenance.
• Framer SEO Audit Checklist for ChatGPT, Claude, and Gemini — A Framer SEO and AEO checklist for teams that want their site to be clear to Google, ChatGPT, Claude, Gemini, and other answer engines.
• The Framer AI Visibility Checklist — A practical Framer AI visibility checklist covering llms.txt, JSON-LD, metadata, service pages, comparison pages, citations, and Mythos proof testing.

Download the Framer AI Visibility Checklist.