Fixing a Ranking Drop That Will Not Recover After a Migration
Some turbulence after a migration is normal while search engines recrawl and process the move. The worry starts when positions and clicks stay down, or keep sliding, long after the new site has settled. At that point waiting is not a plan.
This guide is a diagnostic checklist for owners and developers who need to find out why: how to measure the loss properly, how to tell a migration fault from an unrelated algorithm change, and which technical and content differences between the old and new site most often explain a drop that refuses to recover.
Turbulence or a real problem?
Google's documentation on site moves says that rankings can fluctuate while a move is processed and that large sites take longer. It does not give a timetable, and neither will this guide, because the time depends on site size, how often the site is crawled and how much changed at once. What you can judge is the shape of the curve.
| Pattern in the data | Likely meaning |
|---|---|
| A dip soon after launch, then a steady climb back | Normal processing. Keep monitoring, fix what the audit finds. |
| A dip that levels off lower than before and stays there | Something was lost in the move: pages, content, links or signals. |
| A continuing slide | An active fault, such as a crawl block, server errors or redirects failing. |
| A loss concentrated in one section | A template, URL pattern or redirect rule specific to that section. |
| A site-wide loss that began days after launch, not on launch day | Possibly an unrelated algorithm update. Check before assuming. |
The Site Migration Audit tracks ranking shifts alongside lost URLs, redirect coverage, indexing, structured data and internal links, which helps you connect the pages that lost ground with a specific technical finding.
Measuring the loss properly
A drop measured badly leads to the wrong fix. A few rules keep the comparison honest:
- Compare equal periods. Use the Performance report's compare option with the same number of days before and after launch, and also compare with the same weeks last year if your business is seasonal.
- Combine properties for a domain change. After a move to a new domain, old-domain clicks fall while new-domain clicks rise. Add them together before deciding how much was really lost.
- Look at clicks and positions by query. A drop in impressions with stable positions can simply mean fewer people searched. A drop in positions for queries you used to win is the real loss.
- Exclude branded queries. Searches for your own name usually survive any migration and can hide losses on everything else.
- Map old pages to new ones. Join the old page export with your redirect map so you can compare each old page's clicks with its new equivalent's clicks.
old_url,new_url,clicks_before,clicks_after,change,section,audit_finding
/services/boiler-repair/,/heating/boiler-repair/,640,210,-67%,heating,content shorter
/services/boiler-service/,/heating/boiler-servicing/,420,390,-7%,heating,
/blog/radiator-bleeding/,/advice/bleed-a-radiator/,880,120,-86%,advice,redirect to /advice/
/contact/,/contact/,300,295,-2%,core,The table above is fictional, but the shape is typical: most pages are roughly flat and a handful account for the loss. Those are the pages to investigate first.
Causes that have nothing to do with the move
A migration is the obvious suspect, so it gets blamed for everything. Before you change anything, rule out:
- Core or other ranking updates. The Google Search Status Dashboard lists confirmed ranking updates with start and end dates. If a site-wide loss lines up with one, the cause may be how your content is assessed rather than the move itself.
- Tracking changes. A new site often means a new analytics tag, a new consent banner or a missing tag on some templates. If analytics shows a drop and Search Console does not, the problem is measurement.
- Seasonality and demand. Compare with the same period last year.
- Search results changes. New features such as AI Overviews or more ads can reduce clicks without any change in position.
- Competitors. Another site may have improved at the same time. Check whether specific competitors moved up on the queries you lost.
The migration causes behind lasting losses
Redirects that do not carry the page across
Redirects to the home page or a broad category, redirect chains, and old URLs that never got a redirect are the most common reasons a specific page's rankings do not transfer. Test the old URLs of your losing pages individually.
Content that did not make the move
New templates frequently shorten or restructure pages: introductory text removed from category pages, FAQ sections dropped, specification tables turned into images, headings changed, or product descriptions replaced with a manufacturer's text. If a page ranked because it answered a question well, and the new version answers it less well, rankings follow.
Titles and headings rewritten
A redesign often introduces a new title pattern for every page. A title that once contained the exact phrase people searched for may now lead with the brand, or be cut short.
Internal links diluted
Pages that were linked from the main navigation or from many articles on the old site may now sit several clicks deep, or be linked only through redirects. Internal links tell search engines which pages matter most on your site.
Signals that went missing
Structured data, hreflang for international sites, canonical tags and image alt text all tend to drop out when templates change. Each has its own guide in the Migration Audit Fixes hub.
A slower or less stable site
If the new platform is heavier, pages may load more slowly or shift about as they load. Page experience is one of many signals, so it rarely explains a large drop alone, but a new site that times out for crawlers or returns intermittent errors can.
The fix, step by step
Step 1
Measure the loss like for like
In the Search Console Performance report compare equal periods before and after launch, and the same weeks last year if trade is seasonal. For a domain change, add old and new property clicks together. Exclude branded queries, then export pages and queries. Join the old page export to your redirect map so every old page sits on one row beside its new equivalent with clicks before and after.
Step 2
Rule out causes outside the migration
Check the Google Search Status Dashboard for ranking updates that overlap your loss, confirm that the analytics tag and consent banner fire on every template, and compare demand with the previous year. Look at whether positions fell or only clicks and impressions. If the loss starts on launch day and is concentrated in pages that changed, the migration is the likely cause and the rest of this checklist applies.
Step 3
Split the loss by section and template
Add a section and template column to the spreadsheet and total the change for each. A loss that sits almost entirely in one section, such as product pages or the blog, points to a rule or template specific to it. Sort the losing pages by clicks lost and pick the top twenty as a working sample. Check them against the ranking shifts and other findings in the Site Migration Audit.
Step 4
Test the redirects for the losing pages
Request each old URL in the sample and record every hop and the final status. Each should reach its closest new equivalent in one step and end in a 200. Correct any that land on the home page, a broad category, a 404 or a chain. Also check that the new page's canonical tag names itself, and that internal links and the sitemap use the final address rather than an address that redirects.
Step 5
Compare old and new versions of the losing pages
Open each old page from your pre-migration crawl, a saved copy or the Wayback Machine beside its new version. Compare the title, main heading, body text, images and alt text, FAQs, tables, structured data and the links pointing to it. Note every difference. Restore the information that answered searchers' questions and the phrasing of titles that matched their queries, without padding pages with extra words.
Step 6
Check crawling, rendering and speed on the new site
Open the Crawl stats report in Search Console settings and look for rising response times, server errors or a drop in crawl requests since launch. Run URL Inspection with the live test on losing pages and check that the rendered HTML contains the main content and links. Review field data for Core Web Vitals: good means LCP within 2.5 seconds, INP within 200 milliseconds and CLS within 0.1.
Step 7
Change one thing at a time and record it
Fix the most likely cause for the biggest losing group first, note the date and the change in a log, and annotate it in analytics. Wait long enough for the affected pages to be recrawled before judging the result. Changing titles, content, templates and redirects all in one go makes it impossible to tell what helped. Re-run the Site Migration Audit after each round of fixes.
Links from other websites
Redirects pass the value of external links to your new pages, but updating the most important links at the source removes a hop and protects you if a redirect is ever lost. Use the Search Console links report or a backlink tool to list the sites that link to you most, and ask the owners of the most valuable ones, such as trade associations, suppliers, local directories and your own social profiles, to update the address. Update anything you control directly: your Google Business Profile, social media bios, email signatures and printed QR codes that point to old paths.
Things that do not help
- Reverting the whole migration. Moving back usually creates a second migration with its own disruption. Fix the faults on the new site unless it is fundamentally broken.
- Repeated indexing requests. Requesting indexing for the same page many times does not make it rank.
- Mass rewriting in a panic. Rewriting every page at once destroys your ability to measure what worked and can remove the content that was ranking.
- Switching redirects between 301 and 302. Google treats both as passing signals, so swapping codes will not trigger recovery. Use permanent redirects because they state the move clearly, then leave them alone.
- Buying links to compensate. Paid links intended to manipulate rankings break Google's spam policies and can lead to a manual action.
1. How long should I wait before worrying about a ranking drop after migration?
Google does not publish a fixed period, and the right answer depends on the size of the site and how much changed. Instead of waiting for a date, watch the shape of the data. A dip followed by steady improvement suggests normal processing. A loss that flattens out lower than before, or continues to slide, suggests something was lost in the move and should be investigated straight away rather than left to see whether it fixes itself.
2. How can I tell whether a drop is the migration or a Google update?
Check the dates. The Google Search Status Dashboard lists confirmed ranking updates with their start and end dates. A loss that begins on launch day and is concentrated in pages whose URLs, templates or content changed points to the migration. A loss that begins later, lines up with an update and affects pages that did not change points to the update. Sometimes both happen at once, which makes careful segmenting even more important.
3. Why did only some pages lose rankings after the migration?
Because the causes are usually specific to a template, URL pattern or redirect rule. If product pages lost ground while articles did not, compare the product template before and after, test how old product URLs redirect, and check whether descriptions or reviews were dropped. A loss confined to a group of pages is good news in one sense: it normally has a single cause that can be found and fixed for the whole group at once.
4. Does a 302 redirect stop rankings from transferring?
Not in Google's systems, which treat temporary and permanent redirects alike as passing signals. A 302 by itself is unlikely to explain a lasting ranking loss. Permanent 301 or 308 redirects are still the right choice for a migration because they state clearly that the move is permanent and are read the same way by other search engines. Look instead at where each redirect lands and whether the destination matches the old page.
5. Should I change my new page titles back to the old ones?
Compare them first. If the old title contained the phrase people searched for and the new one dropped it, restoring that wording is a sensible, low-risk fix. If the new title is simply different but still describes the page clearly, changing it back is unlikely to help much. Make title changes for a group of pages at a time, note the date, and watch the queries for those pages before changing anything else.
6. Can page speed on the new site cause a ranking drop?
It can contribute, but page experience is one of many signals and rarely explains a large drop alone. A bigger risk is a new host that responds slowly or with errors when crawlers visit, because Google then crawls less and processes the move more slowly. Check the Crawl stats report in Search Console for response times and errors, and look at field Core Web Vitals data for the templates that lost the most traffic.
7. Should I undo the migration if rankings have not recovered?
Rarely. Moving back is a second migration with its own redirects, recrawling and disruption, and it does not restore the old situation exactly. In most cases the loss comes from specific faults such as missing redirects, thinner content or broken signals, which can be fixed on the new site. Consider reverting only if the new platform itself is fundamentally unable to serve the pages properly, and plan it as carefully as the first move.
The Site Migration Audit compares your pre-migration crawl with the live site, finds lost URLs, validates redirects, tracks ranking shifts, checks indexing and structured data, and audits internal links.
Open Migration Audit Fixes →