How to move a website to Framer without losing your SEO
A step-by-step plan for migrating a client site to Framer while keeping its rankings, links and search traffic intact.

Moving a client from WordPress, Webflow or an old custom build to Framer is one of the most common projects we see. The design part is usually the easy bit. The risky part is the switch itself: old URLs stop working, pages lose their titles and descriptions, and a site that ranked well for years can drop in search within weeks of a beautiful relaunch.
None of that is caused by Framer. It is caused by skipping the boring migration work. Here is the process we use so that a new Framer site keeps the search traffic the old one earned, and ideally grows it.
Take an inventory before you design anything
Before the first frame, export a list of every URL on the current site. The sitemap is the fastest source (usually at /sitemap.xml), but also check the client's analytics and Google Search Console for pages that get traffic but are missing from the sitemap. Old blog posts and landing pages from past campaigns often hide there.
Put everything in a spreadsheet with these columns:
- Old URL
- Monthly visits and clicks from search (from analytics and Search Console)
- Current page title and meta description
- Backlinks, if the client has an SEO tool that shows them
- Decision: keep, merge or remove
- New URL on the Framer site
This sheet becomes the single source of truth for the whole migration. It also gives the client a clear view of what is changing, which avoids awkward questions after launch.
Keep URLs the same wherever you can
The safest redirect is the one you never need. If a page lives at /services/branding today, build it at the same path in Framer. Framer lets you set the path of every page and CMS collection, so in most cases you can match the old structure exactly.
Blog posts are where structures usually differ. If the old site used /2023/05/post-name and you want /blog/post-name, that is fine, but every one of those posts will need a redirect. Decide this early, because it affects how you set up the CMS collection.
Set up redirects for everything that moves
For every row in your sheet where the old and new URLs differ, you need a permanent (301) redirect. Framer's site settings include a redirects section where you add each old path and its new destination. Where whole groups of URLs follow the same pattern, a wildcard rule saves you from adding hundreds of lines by hand.
A few rules we follow:
- Redirect each old page to its closest new equivalent, not to the homepage. Sending everything home throws away the relevance the old page had.
- Pages you remove with no equivalent can redirect to the parent section, for example an old service page to /services.
- Avoid chains. If an old URL already redirected somewhere, point it straight to the final new page.
- Test every redirect after launch. A spreadsheet of fifty paths takes ten minutes to click through.
Carry the metadata over, then improve it
Titles and meta descriptions are often left blank on new builds because they are not visible in the design. Copy them from your inventory into each Framer page's SEO settings first, so nothing regresses. Then improve the weak ones: titles under about 60 characters that say what the page is, and descriptions that read like a reason to click.
For CMS content, map the old SEO fields to CMS fields and connect them to the collection page's title and description. That way every blog post or case study keeps its own metadata instead of inheriting one generic line.
While you are there, set Open Graph images. They do not affect rankings directly, but they make shared links look intentional, which helps clicks.
Do not lose the content that ranks
A redesign is a tempting moment to cut copy. Be careful with pages that bring in search traffic. If a service page ranks because of a detailed 800-word section, replacing it with three short lines and an icon grid will cost you. You can redesign how the content looks without removing what it says.
Rule of thumb: on pages that already earn search traffic, change the design freely and change the words carefully.
The same goes for headings. Keep a single clear h1 on each page and keep the key phrases the page ranked for in its headings and opening paragraph.
Launch day checklist
When you connect the domain and publish, work through this list in the same session:
- Confirm the site loads on both the root domain and the www version, and that one redirects to the other.
- Check that HTTPS works on every page.
- Open the new /sitemap.xml that Framer generates and make sure the pages you expect are in it.
- Make sure no pages you want indexed are set to be hidden from search engines in their page settings.
- Click through your redirect list and confirm each one lands on the right page.
- Submit the new sitemap in Google Search Console.
Watch the first four weeks
Some movement in rankings after a migration is normal while search engines recrawl the site. What you are looking for is anything that does not recover. Check Search Console weekly for a month:
- The pages report, for new "not found" errors. Each one is a missing redirect.
- The performance report, comparing clicks for your top ten pages before and after launch.
- Core Web Vitals, to make sure heavy animations or large images did not slow down key pages.
Fix 404s as soon as they appear. Most post-launch traffic drops we have seen came from a handful of old URLs that nobody redirected.
Make it part of your offer
If you build Framer sites for clients, write this process into your proposal as its own line item. Clients who have been burned by a relaunch before will value it, and it protects you from blame if traffic dips for reasons outside the project.
A migration done this way takes a day or two of extra work. In exchange, the client gets a faster, easier-to-edit site that keeps the search traffic they already paid for, and you get a launch you do not have to explain later.


