Founder of Goodspeed
An SEO migration strategy is the plan that decides which pages you keep, merge or drop, how every old URL maps to a new one, and how you prove the new site sends search engines the same signals as the old one. Most ranking loss after a replatform comes from avoidable mistakes: missing redirects, thinner content, broken internal links and lost technical tags. A careful plan reduces that risk, but some temporary movement after launch is normal and should be expected.
Who can do this for you?
Goodspeed, a Framer Enterprise partner, runs migrations as a fixed product. We audit your current site first, sign off a redirect map with you before anything moves, launch with zero downtime in about five weeks, then monitor rankings, redirects and indexing for 30 days after launch. Migrations start from $10,000. See our Migration service.
What actually causes ranking loss
Search engines do not penalise a site for changing platform. What they react to is change in the signals they had already learned about your pages. When a website migration loses traffic, the cause is almost always one of a short list of things, and almost all of them are visible before launch if you look.
Old URLs that return 404s. Every backlink and bookmark pointing at them stops passing value, and the page drops out of the index.
Redirects to the wrong place. Sending dozens of old articles to the homepage is usually treated like a 404, because the destination does not answer the same query.
Thinner pages. A redesign that cuts copy, collapses FAQs into accordions that never render, or drops supporting sections changes what the page is about.
Lost internal links. New navigation and footers often link to fewer pages, so deeper pages lose the internal authority that kept them ranking.
Missing technical tags. Titles, meta descriptions, canonicals, hreflang and structured data that lived in a plugin or theme do not move by themselves.
Indexing accidents. A staging noindex tag or a blocking robots.txt that ships to production.
Notice what is not on the list: the platform itself. Replatforming is a risk because it touches every one of these signals at once, not because the new platform is worse at SEO. The strategy is about controlling how much changes at the same moment.
Decide what to keep, merge or drop
Before anyone designs a page, build an inventory of every URL the current site has. Pull from three sources, because each one misses something: a full crawl, your XML sitemap, and the pages that received clicks, impressions or backlinks in Search Console and your link tool over the last 12 months. A proper website audit at this stage is the cheapest insurance in the whole project.
Then give every URL a decision:
Keep. Pages with traffic, rankings, conversions or meaningful backlinks. These move across with their content intact.
Merge. Several thin or overlapping pages competing for the same query. Combine them into one stronger page and redirect the others to it.
Drop. Pages with no traffic, no links and no business purpose, such as expired campaign pages or tag archives. Redirect them only if a genuinely relevant page exists; otherwise let them return a 410 or 404.
Be conservative. A migration is a bad moment for an aggressive content prune, because if traffic moves afterwards you will not know whether the platform, the prune or the redirects caused it. If you want to restructure your blog or CMS collections, plan it with the same care as the page move. Our CMS migration guide covers how to map collections and fields without losing content.
Choose a URL strategy
The safest URL is the one that does not change. If your new platform can reproduce the existing path for a page, keep it, and you have removed that page from the risk register entirely.
Sometimes changing URLs is the right call: messy legacy paths, a blog that lives under a date folder, or a section you are restructuring anyway. When that happens, follow three rules.
Change URLs once. Do the restructure during the migration, not a few months later, so search engines process one set of changes rather than two.
Keep the slug where you can. Moving /blog/post-name to /articles/post-name is far easier to map and audit than rewriting every slug.
Do not change the domain at the same time unless you have to. A domain change, a platform change and a URL restructure in one launch stacks three risks together.
Platform constraints matter here. Each source platform has its own URL habits, from WordPress category bases to Webflow collection folders. Our guides to moving from WordPress to Framer and moving from Webflow to Framer cover the specific patterns to watch for.
Redirect mapping principles
The redirect map is the single most important document in any replatforming project. It is a spreadsheet with one row per old URL, its new destination and the status code, and it should be signed off before content moves. Google's own guidance on site moves with URL changes is built around the same idea.
The principles
One to one wherever possible. Each old URL goes to the single new page that best answers the same intent, not to a category or the homepage.
Permanent redirects. Use 301 (or 308) redirects for permanent moves. Temporary 302s send a mixed signal about which URL should be indexed.
No chains. If an old page already redirected somewhere, point the original URL straight at the final destination. Every extra hop slows crawling and adds a point of failure.
No loops. Test that no destination redirects back to a source.
Cover the variants. Trailing slashes, uppercase paths, http and www versions, and common query string URLs that picked up backlinks.
Keep them in place. Leave redirects live for at least a year, and in practice for as long as old links still point at them.
Then update internal links to point at the new URLs directly. Redirects protect external links; your own navigation should never rely on them.
Content and technical parity
Parity means the new page tells search engines at least as much as the old one did. Check it page by page for everything you marked Keep, before launch, on staging.
Content parity
The same core copy, headings and answers, or better. Redesigns often trim body text that was doing the ranking.
Titles and meta descriptions carried over, or deliberately rewritten.
Images moved with their alt text, and FAQs rendered as real text on the page.
Internal links from the page to related pages, at a similar depth.
Technical parity
Canonicals. Every indexable page has a self-referencing canonical on the new domain, with no leftover canonicals pointing at staging or old URLs.
Hreflang. If you serve multiple regions or languages, every alternate is mapped to the new URLs and the tags are reciprocal.
Structured data. Organisation, article, FAQ, product and breadcrumb schema markup recreated and validated, since it often lived in a plugin.
Sitemaps. A new XML sitemap that lists only final, indexable, 200 status URLs.
Robots. Robots.txt and meta robots checked on the live domain, so nothing blocks pages you want indexed and the staging noindex is gone.
Analytics and tags. Your tag manager, analytics and CRM scripts firing on the new pages, so you can actually measure the outcome.
Measurement plan and launch
You cannot judge a migration without a baseline. Before launch, record the numbers you will compare against:
Clicks and impressions by page from Search Console, for at least the last three months.
Positions for a tracked set of priority queries, split by country if you sell in more than one market.
Indexed page count, organic conversions and the top landing pages from analytics.
On launch day, switch DNS, then immediately crawl the old URL list against the live site to confirm every row returns the expected redirect and every destination returns 200. Submit the new sitemap in Search Console, and use the Change of Address tool if the domain changed. The SEO migration checklist breaks the launch into individual checks.
Launching in stages also lowers risk. Zen Educate, a Series B edtech working across the UK and US, moved to Framer page by page with zero downtime. Their CMS was rebuilt as four content hubs, and GTM, Zoho, Heap and Hotjar kept working through the move, so measurement never went dark. Afterwards the team ran 10x more growth experiments. Read the Zen Educate case study.
Normal movement versus a real problem
Some fluctuation after a migration is expected. Search engines have to recrawl old URLs, follow the redirects and reprocess the new pages. Google notes that a medium-sized site can take a few weeks for most pages to move in its index, and larger sites longer.
Usually normal
Rankings for individual pages moving up and down for a few weeks.
Old URLs still appearing in search results for a while, then being replaced.
A short dip in impressions that recovers as new URLs are indexed.
Usually a real problem
A sharp, sitewide drop in impressions in the first days, which often points to a robots or noindex mistake.
Specific pages or whole sections losing traffic while the rest holds, which usually means missing redirects or lost content.
Rising 404 or soft 404 counts in Search Console, or redirected pages reported as not indexed.
A decline that is still getting worse after several weeks rather than flattening out.
Check Search Console daily in the first fortnight, then weekly. Compare page groups against your baseline rather than the whole site, because a sitewide average can hide one section that has broken. For the full end to end process, see our ultimate guide to migrating to Framer.
Plan the migration before you design it
A safe replatform comes down to a few disciplined decisions made early: an inventory of every URL, a clear keep, merge or drop call for each, one to one permanent redirects with no chains, page by page parity checks, and a baseline to measure against. None of it guarantees rankings, but it removes the avoidable causes of loss and gives you the evidence to tell normal movement from a real problem.
If you would rather have a team run it, our website migration service starts with an audit and a signed-off redirect map, launches with zero downtime, and includes 30 days of post-launch monitoring.
Written By
Founder of Goodspeed
Share this article
