BlogPlaybook

How to leave Framer without losing your Google rankings or AI citations

Benjamin Libor8 min read

To leave Framer without losing rankings or AI citations, keep every URL that works, send every URL you change to its new home with a permanent redirect, and carry over each page's title, description, social image and language versions before the switch. Then record which of your pages Google and AI answers rely on today, so you can check them first after launch. Search engines and AI assistants know your site by its addresses, and most of the damage in a migration comes from addresses that quietly stop working.

In short

  • Most traffic lost in a website move comes from broken or changed URLs, not from the new platform itself.
  • Keep the same URL for every page and CMS item wherever you can, and give every changed one a permanent (301) redirect.
  • Carry over titles, descriptions, social images, hreflang and structured data, and improve the structured data while you're at it.
  • Record which pages rank, get clicks and get cited in AI answers before the move, and check those pages first afterwards.
  • Expect some movement for a few weeks while search engines and AI crawlers re-read the site; watch it, don't panic.

What actually goes wrong in a migration?

A move from Framer to a custom-code site is a rebuild: Framer has no built-in export of a published site to a code project, so the pages are rebuilt, usually with an AI tool like Claude Code doing most of the work. A rebuild is a good moment to improve the site, and also the moment small details get lost.

The usual problems, in the order we see them:

  1. URLs change without redirects. A blog that lived at /blog/post-name moves to /articles/post-name, and every link, bookmark and search result now ends in a 404.
  2. CMS items lose their slugs. Content exported as CSV gets new slugs generated from titles, so the old addresses vanish one by one.
  3. Metadata doesn't come across. Titles fall back to the site name, descriptions disappear, social images go blank.
  4. Language versions get confused. The new site uses different language paths, and the alternate links between them point to nowhere.
  5. The new site blocks crawlers. A staging setting that told search engines not to index the site goes live with it.

Every one of these is easy to prevent and slow to notice afterwards. The rest of this playbook is how to prevent them.

Before the move: what to record

You can only protect what you know you have. Before anyone builds anything, make three lists.

Every URL

Export the full list of addresses: every static page and every CMS item's page. Framer's published sitemap (usually at /sitemap.xml on your domain) is a good starting point, and Search Console's pages report fills in anything the sitemap misses. Add the old URLs that already redirect, because those redirects have to survive the move too.

What brings visitors

From Search Console, export the pages with clicks over the last few months and the queries that bring them. From your analytics, note the pages that bring sign-ups or demo requests. These are the pages you check by hand on launch day.

What AI answers cite

This is the list most migrations forget. Ask ChatGPT, Perplexity, Gemini and Google's AI Mode the questions your buyers ask, and note which of your pages they cite. A comparison page or a pricing page that AI answers lean on deserves the same care as your best-ranking article. How assistants choose those pages is in how ChatGPT decides which pages to cite.

How should you handle URLs?

Keep the address if you can. Redirect it if you can't. Never let it 404.

The rule is simple, and it holds for every page and CMS item.

  • Keep the same paths. A code framework like Astro lets you choose any URL structure, so there's rarely a reason to change it. If Framer used /blog/post-name, keep it.
  • Keep the CMS slugs. When you turn Framer's CMS export into content files, use the existing slug column as each file's name or slug field, not a new slug made from the title.
  • Redirect what changes. Use a permanent (301) redirect from each old address to the single most relevant new page, never a blanket redirect of everything to the home page.
  • Keep old redirects. If Framer already redirected old addresses, carry those rules over and point them straight at the final address, so nobody goes through two hops.
  • Decide on trailing slashes once. Pick one form (with or without the slash at the end) and redirect the other, so each page has one address.

On a code site, redirects usually live in one file the host reads, or in a CMS screen that writes that file. Either way, check the file into the repository so it has a history.

Which on-page details must carry over?

For every page and every CMS item, these should arrive on the new site exactly or better:

DetailWhere it lives in FramerWhat to check on the new site
TitlePage or CMS item SEO settingsSame text, no site-name-only fallbacks
DescriptionPage or CMS item SEO settingsPresent on every page, 140 to 160 characters
Social imagePage or CMS item settingsShows in link previews
Canonical URLSet by FramerPoints to the page's own final address
Language versionsFramer's localisationhreflang links between every pair, in both directions
HeadingsYour layoutOne h1 per page, then h2 and h3 in order
Alt textImage settingsEvery meaningful image described

A useful habit: have the AI tool that builds the pages fill these from the old site's HTML as it goes, and generate a report of any page missing one. Reading the old page is quicker than retyping.

Should you add structured data during the move?

Yes, this is the one place the move should leave you better off. On Framer, structured data is custom code added page by page, so it's often missing. On a code site it comes from templates: every article gets Article data, every FAQ block gets FAQPage data, the home page gets Organization data, without anyone adding it by hand. What each type does, and what it doesn't, is in structured data for AI search.

The same goes for the files AI crawlers read. Decide your rules for crawlers like GPTBot, ClaudeBot and PerplexityBot in robots.txt rather than inheriting a default, and read AI crawlers explained before you choose.

Launch day: the checks in order

Run these in the first hour after switching the domain, and fix anything before moving on to the next.

  1. Open the robots.txt on the live domain and make sure it doesn't block the whole site.
  2. View the source of the home page and check there's no noindex left over from staging.
  3. Open ten of the most important old URLs from your list. Each should load or redirect in one hop.
  4. Run every old URL from your list through a redirect checker and sort by status: anything that returns 404 gets a redirect today.
  5. Check a few CMS items in each collection: title, description, social image and the page itself.
  6. Submit the new sitemap in Search Console and request indexing for the key pages.
  7. Check analytics and the cookie banner fire on the new site, so you can measure what happens next.

After the move: what to watch

For the next few weeks, compare against the lists you made before the move.

  • Search Console: clicks and impressions for the pages that earned them, and the pages report for anything newly marked as not found.
  • AI answers: ask the same questions as before and see whether the same pages are cited, and whether any answer now cites a 404 or an old address.
  • AI crawlers: server or host logs show whether GPTBot, ClaudeBot and others are fetching the new pages, and which ones they miss.

Some movement is normal while search engines re-read the site. A drop that lasts, or a page that falls out entirely, almost always traces back to a URL or metadata problem you can find in the lists.

Questions people ask

Will moving off Framer hurt my SEO?

It doesn't have to. Rankings fall in a migration mostly when URLs change without redirects or metadata goes missing. Keep your URLs, redirect the ones you change and carry over titles, descriptions and structured data, and the move can leave you in a better position.

How do I redirect old Framer URLs on a code site?

Most hosts read a redirects file in the repository, with one line per old and new address. List every old URL first, then add a permanent (301) redirect for each one that changes, pointing at the most relevant new page.

Can I keep my Framer CMS URLs when I move?

Yes. Export each collection as CSV and use the existing slug for each item on the new site. As long as the collection's path and the slug stay the same, the address does too.

Do AI assistants notice when a website changes platform?

They notice the pages, not the platform. If a page they cite keeps its address and content, nothing changes for them. If the address breaks, answers may keep citing the old URL until their sources are refreshed, which is why redirects matter for AI answers as well as for Google.

How long does it take for rankings to settle after a migration?

It varies by site and by how much changed. Expect some movement for a few weeks while search engines re-crawl the site. Watch the pages you listed before the move, and treat a lasting drop on one page as a bug to find.

Written by Benjamin Libor, founder, echo.

Something wrong or out of date? Write to hello@echo-aeo.com and we'll fix it.

See what AI says about your brand.

Free, in about a minute.