Website Migration SEO: Why Traffic Drops After a Redesign or Move, and How to Get It Back
A new design, a new platform or a new domain goes live, and within a few weeks Google traffic is down. Some of that dip is normal and comes back by itself. The rest is something Google relied on that did not make the move. This page shows how to tell the two apart in Search Console, and the seven things that most often get lost, in the order I check them.
Why does traffic drop after a website migration? Either Google is still swapping old URLs for new ones, which is expected and temporary, or something was lost in the move: old URLs with no redirect, content that now needs JavaScript to appear, dropped internal links, rewritten titles, staging settings left switched on, an outdated sitemap, or pages removed without anyone checking what they earned.
The test is in Search Console. If the old URLs are losing impressions while the new ones gain them, Google is still processing the move. If total impressions keep falling and the new URLs never pick up what the old ones had, something was lost, and waiting will not bring it back.
- Google says a medium-sized site can take a few weeks or more before its new URLs replace the old ones in results, and larger sites longer.
- Google asks for redirects to stay in place generally at least 1 year, so signals and links from other sites can move across.
- From January 2022 to October 2026 a confirmed Google update was rolling out on 518 of 1,765 days, so a launch often lands inside one by coincidence.
From Google’s site move guidance (checked 13 November 2026) and our dataset of every confirmed Google update.
Step 1: make sure the migration is the cause
A launch date and a drop date that sit close together feel like proof. They are not. Rule out two other explanations before you touch anything.
Tracking moved with the site, or it did not. Redesigns drop analytics tags more often than they drop rankings. A new theme without the tag, a new cookie banner that blocks it until consent, a tag manager container that was never added to the new templates. Open Search Console Performance and your analytics for the same dates. If Search Console clicks held and only analytics fell, Google did nothing. Fix the tag and stop there.
A Google update was rolling out at the same time. With an update live on roughly three days in ten, this happens often. Write down the first day Search Console clicks fell below their normal range and stayed there, then check it:
Know the day your traffic fell? The Google update matcher checks it against every confirmed Google update since November 2021.
If the date sits inside an update window, look at which pages fell. A migration problem follows what changed: one template, one section, the URLs that were renamed. An update tends to follow content type across the whole site, including pages the migration never touched. If pages you did not change fell just as hard, the migration is probably not the main cause.
Step 2: a normal dip, or a real loss?
Google says to expect ranking fluctuations while it recrawls a moved site. The dip is real but temporary, because every old URL has to be visited, followed through its redirect, and replaced in the index by the new one. That happens one URL at a time, not all at once.
You can watch it happen. In Search Console Performance, open the Pages tab and compare four weeks after launch with four weeks before.
Old URLs lose impressions, the matching new URLs gain them, and the two roughly add up to what the old page had. The total may dip for a while, then recover as more URLs swap over.
Old URLs lose impressions and nothing on the new site picks them up. Or the new URLs appear and sit at lower positions than the old ones held. Or total impressions keep sliding week after week instead of levelling off.
For a domain move the comparison spans two Search Console properties. Verify both the old and the new domain, including the www and non-www versions, and read them side by side.
Do not wait out the second pattern. A redirect that was never set up will not appear on its own, and every month an old URL returns an error, more of what it earned fades.
Step 3: rebuild the list of what you had
Everything after this step is a comparison, so you need the old site on paper first. You almost always have more of it than you think.
- Search Console keeps 16 months of data. Set the date range to the three months before launch, open the Pages tab, and export it. That is your list of URLs that earned clicks, ranked by how much each one mattered.
- The old sitemap, if anyone kept a copy or it is still on the old server.
- Web archives. The Wayback Machine usually holds snapshots of the main pages, which shows you what the old titles, text and links looked like.
- Links from other sites. The Links report in Search Console lists your most-linked pages. Those are the URLs where a missing redirect costs the most.
Put the exported URLs in a spreadsheet with one column for the new URL each should now point to. That sheet is the backbone of every check below.
Step 4: the seven things Google most often loses
Work through these in order. The first two are the most common and the quickest to prove.
Test every URL in your sheet. Each old page should return a single permanent redirect to its closest new match. Three failures show up again and again: old URLs that now return a 404, many old URLs all sent to the homepage, and redirects that hop several times before landing. Google says sending many old URLs to one unrelated page such as the homepage may be treated as a soft 404, and that chains should ideally be no more than 3 hops and fewer than 5. Permanent redirects do not lose PageRank, so a correct redirect is not a compromise.
In Search Console: Pages report: “Not found (404)” and “Soft 404” rising after launch, and URL Inspection on an old address showing where it ends up.
The new site was built on a staging server that was told to stay out of Google, and the instruction came along at launch: a noindex tag on every page, a robots.txt that blocks the whole site, or canonical tags that still point at the staging address.
In Search Console: Pages report: “Excluded by noindex tag” or “Blocked by robots.txt” climbing across every page type, or “Alternate page with proper canonical tag” on pages that should be indexed.
The page looks the same in a browser, but text that used to sit in the HTML is now loaded by script, put behind tabs, or cut down to fit a tidier design. Google can render JavaScript, but anything that fails to render, or loads only after a click, is content Google may not see.
How to check: URL Inspection, then “View crawled page” on a top page. Compare that HTML with the archived old version. Missing paragraphs are missing for Google too.
A slimmer menu, a footer with fewer links, no more related posts or breadcrumbs. Pages that lose their internal links are not removed, they just slide slowly, which is why this one gets blamed on everything else.
How to check: For your ten most important pages, count the links pointing to them from the old site (archive) and from the new one. Any page that went from many to few is a candidate.
New platforms often generate titles from a pattern: page name, then site name, the same on every page. Hand-written titles that matched what people search for are gone, and some pages lose their main heading altogether.
In Search Console: Queries for the page are the same, but its average position fell. Compare the old title in the archive with what Google shows now.
A sitemap that still lists the old URLs, or none at all, slows down how fast Google finds the new pages. On multilingual sites, hreflang tags that point to old addresses break the link between language versions.
In Search Console: Sitemaps report: submitted URLs that redirect or return errors, or a sitemap that has not been read since launch.
Someone decided an old blog post, a location page or a product range was not worth moving. Often that was right. Sometimes the page brought in a fifth of the site’s search traffic and nobody looked before cutting it.
How to check: In your sheet, mark every old URL with no new match, and add up the clicks those pages had. That number is traffic you chose to give up, and it will not come back without the page.
If the domain changed too
A domain move needs everything above plus three things of its own:
- Use the Change of Address tool in Search Console, on the old property. Google says it is needed only when moving from one domain or subdomain to another, not for a redesign on the same domain.
- Redirect every version of the old domain: http and https, www and non-www, each straight to the matching new URL.
- Keep the old domain registered and the redirects running. Google’s guidance is generally at least a year, and longer if people still reach you through old links. Letting the old domain lapse removes the redirects and hands its links to whoever buys it next.
On 27 August 2026 seorevive.in moved from Hostinger to Vercel. No URLs changed, so it was the simplest kind of migration there is. I still checked it the same way.
All 43 URLs in the sitemap returned 200 on the new host. www and http each redirected once, straight to the matching https page. The new host also served a copy of the site on its own preview address, and that copy needed a noindex rule scoped to that address only, so it would stay out of Google without the rule touching seorevive.in. That last one is the staging trap from card 2 above, and it takes a one-line mistake to put it on the live site instead.
What not to do while you diagnose
- Do not roll back to the old site in a panic. Rolling back is a second migration, with all the same risks, on top of the first. Sometimes it is the right call. Decide it with the evidence, not on day ten.
- Do not remove redirects because traffic has “settled”. They are still carrying links from other sites to your new pages.
- Do not send every unmatched URL to the homepage to make the 404 count go down. Google may treat those as soft 404s anyway, and visitors land somewhere useless.
- Do not start another redesign to fix it. A third version of the site hides which change mattered.
Migrating soon? Check these before launch
Almost everything above can be caught before go-live, when it costs an afternoon instead of months of traffic.
- Export the Search Console Pages report for the last three months and build the redirect sheet from it, before launch, not after.
- On staging, open the top twenty old URLs through the redirect rules and confirm each lands on its match in one hop.
- Make a list of what to switch off at launch: the staging noindex, the robots.txt block, any password protection. Then check it on the live site within the hour.
- Compare the HTML of five key pages, old against new, for text, headings, title, canonical and internal links.
- Submit the new sitemap on launch day and check the Pages report every few days for the first month.
The checklist
- ☐ Search Console clicks compared with analytics for the same dates
- ☐ Drop date written down and checked against every update’s full rollout window
- ☐ Pages tab: old URLs losing impressions, and new URLs picking them up or not
- ☐ Old URL list rebuilt from Search Console, the old sitemap and web archives
- ☐ Every old URL tested: one permanent redirect to its closest match
- ☐ No noindex, robots.txt block or staging canonical left on the live site
- ☐ Crawled HTML of top pages compared with the archived old versions
- ☐ Internal links to the ten most important pages counted, old against new
- ☐ Titles and headings on top pages compared with the old ones
- ☐ New sitemap submitted, old URLs out of it, hreflang updated
- ☐ Clicks from removed pages added up
- ☐ Domain move only: Change of Address submitted, all old versions redirected, old domain kept
When you do not need me
- It has been less than a few weeks since launch and the Pages tab shows old URLs handing their impressions to new ones. Wait and watch.
- The drop lines up with a Google update and pages you never touched fell just as hard. That is an update problem, not a migration one, and the core update guide is the better place to start.
- The lost traffic came from pages you removed on purpose and you are happy without them.
- Your developer can run the checklist above. Most of it is an afternoon for someone who knows the site.
Where people get stuck is when several of these overlap: a launch inside an update window, with a few redirects missing and a template that changed every title. Then it is hard to say which one cost the traffic, and fixing them in the wrong order wastes weeks. That is the part worth paying for.
Related reading
- Site migration recovery: how I compare the old site with the new one, and prices
- WordPress traffic drop: six checks, including the settings a redesign often breaks
- Shopify traffic drop: the same checks for a store
- How long Google recovery takes, by type of drop
- The Google update calendar and statistics
- Google Search Central: site moves with URL changes: the primary source
- Google Search Central: moving hosts without changing URLs