Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

SEO › Troubleshooting

Organic Traffic Drop After Site Migration

Why organic traffic fell after a site migration and how to recover: missing redirects, chains, blocked staging rules, lost content, and canonicals.
Troubleshootingintermediate8 min readUpdated

First, confirm the loss and where it sits

Before touching the redirects, check whether search traffic really fell or whether only the measurement changed. Compare clicks in Search Console (GSC) with sessions in analytics for the same period. If Search Console clicks held steady while analytics shows a cliff, the tag is the problem, not the rankings. If both fell, the loss is real.

Then split the performance report by page. Old URLs should lose clicks while new URLs gain them; the two lines should roughly mirror each other as Google processes the move. Pages where the old URL lost and no new URL picked up the traffic are the ones to investigate first. Export the top old landing pages from the pre-launch baseline and request each one: note the status code, every hop in the redirect chain, the final URL and whether that final page carries the same content. The page indexing report for the new property, and the old property if it was a domain change, shows whether new URLs are being indexed or excluded. Sudden drops on a site that did not move belong to the sibling page on rankings that dropped suddenly.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
Old landing pages return a not-found error, or land on the home pageRequest each top old URL; compare the destination with the original pageOld URLs not redirected or redirected to the wrong pageMap each old URL to its exact equivalent with a permanent redirect
Old URLs reach the right page only after several hops, or never arriveTrace the full redirect path for a sampleRedirect chains and loopsPoint every old URL straight at its final destination in one hop
New pages are crawled but excluded, or not crawled at allURL inspection; robots.txt on the live host; meta robots and headersStaging noindex or robots.txt rules carried to productionRemove the staging rules from production and request recrawl
Redirects work but the new pages rank lower than the old ones didCompare old and new copies: body text, headings, internal inlinksContent, headings or internal links lost in the redesignRestore the missing content and the internal links that pointed at it
Google indexes old URLs or the wrong locale after the moveCanonical tags and hreflang annotations on the new pagesCanonicals and hreflang still pointing at old URLsUpdate canonicals and every hreflang set to the new addresses
Analytics sessions fall but Search Console clicks do notTag presence on each new template; real-time view while browsingAnalytics tag missing on the new siteAdd the tag to every template and annotate the data gap

Fix, verify and prevent each cause

Redirect gaps and wrong destinations

Google's site move documentation describes mapping every old URL to its new equivalent with permanent server-side redirects. Pages that lost the most usually had external links, so a missing redirect throws away that Backlink value as well as the ranking. A catch-all redirect to the home page is little better than none.

Fix: compare the old URL list from crawls, analytics, Search Console and server logs against the redirect rules, and add exact one-to-one redirects for every gap.

Verify: each old URL in the baseline returns a permanent redirect to a page with matching content.

Prevent: build the map from every source of old URLs, not only the CMS export, as the redirect map section of the site migrations guide describes.

Chains and loops

Layered rules (http to https, then old path to new path, then trailing slash) can turn one redirect into several hops, and conflicting rules can loop. Each extra hop slows visitors and crawlers alike, and a loop never resolves at all, so the destination is never reached.

Fix: flatten the rules so each old URL resolves to its final destination in a single hop, and update older redirects from previous migrations to point at the new final URLs too.

Verify: a crawl of the old URL list reports one hop per URL and no loops.

Prevent: keep a single redirect table and test it in full before launch, with the checks listed for staging in site migrations. Where Search Console reports redirect errors or a growing list of redirected addresses, the page on page with redirect in Search Console sorts the expected entries from the ones that need work.

Staging blocks that went live

A staging site is usually protected with a disallow-all robots.txt, a site-wide noindex or a password, and any of them can travel to production with the release. Google's robots.txt introduction explains that a disallow stops crawling, so neither new content nor a noindex removal can be seen.

Fix: remove the staging rules from production immediately, check both HTML and HTTP headers for robots directives, and request recrawling of key pages.

Verify: URL inspection shows the new pages as crawlable and indexable, and the indexed count of the new site rises.

Prevent: make directive checks a launch-day gate, using the controls described in crawling and indexing.

A redesign often shortens copy, merges pages, renames headings and replaces rich navigation with a minimal menu. Redirects then send authority to pages that no longer answer the queries, or to pages the site barely links.

Fix: compare old and new versions of each losing page; restore the sections, headings and specification tables that answered queries; rebuild the contextual links and navigation paths that used to point at it.

Verify: a crawl shows inlink counts close to the old site for priority pages, and their query impressions recover after recrawl.

Prevent: benchmark internal links per priority page before a redesign and keep them in the acceptance criteria, using the audit method in the internal linking guide.

Canonicals and hreflang naming old addresses

Templates sometimes keep a hard-coded host or path, so the new pages declare the old URLs as canonical, and international sites can carry hreflang sets that still reference the old locale paths. Google then receives conflicting instructions: the redirect says one thing and the Canonical Tag says another.

Fix: generate canonicals and hreflang from the live URL scheme, and update every alternate in every set.

Verify: URL inspection shows Google selecting the new URL as canonical, and the international targeting reports show no errors for missing return links.

Prevent: review annotations on staging with the checks in the hreflang guide, which also covers how hreflang interacts with redirects.

The analytics tag fell off

New templates are built from scratch, and the tag that lived in the old theme's header may not have been carried over to every one of them. The result looks like a traffic collapse that Search Console does not confirm.

Fix: add the tag to every template, or deploy it through a tag manager container loaded on all pages, and check consent settings behave as before.

Verify: browse each template while watching the real-time report, and compare daily sessions with Search Console clicks again.

Prevent: include tagging in the migration test plan, using the analytics setup checklist, and annotate the gap in reports so nobody compares broken days with normal ones.

Prevention: the next migration

The best recovery is the one you never need. Take a full baseline before the next migration: every indexable URL, its clicks, its links and its internal inlinks. Change as little as possible at once; a domain move, a redesign and a content rewrite are three projects. Test redirects, directives, canonicals, hreflang and tagging on staging against the baseline list, and repeat the same tests on production the hour after launch. Watch the old and new URLs side by side in Search Console daily for the first weeks, keep the old domain registered and redirecting, and use the Change of Address tool when the domain itself changes, as Google's site move documentation describes. When the migration was part of a rename and enquiries fell as well as organic traffic, the diagnosis of results that fell after a rebrand sets the redirects beside the other causes a new name brings, from old-name searches to listings and email.

Illustrative example — not a real result

A travel agency's redesign and domain change

A tour operator moves from an old domain to a new brand domain and redesigns at the same time. Four weeks later, organic sessions are down 55%, but Search Console clicks are down only 20%. Two causes overlap. The booking and blog templates, which carry 30% of landing pages, have no analytics tag. And of the 600 old URLs with external links, 140 redirect to the new home page because the destination guides were merged. The team tags the missing templates, recreates 90 of the merged guides, and remaps the other 50 to the nearest remaining guide. Three months after launch, clicks are back within 5% of the baseline.

For the next move, size the stakes in advance with the site migration guide to the SEO traffic estimator, which sets the baseline that monitoring should use.

Ordinary releases after the migration carry the same risks on a smaller scale, and SEO checks for staging and releases turns the launch-day tests into a routine for every deployment.

Common mistakes

Launching a domain change, redesign and rewrite on the same day. Removing old redirects once traffic seems to recover. Judging the migration on analytics sessions without checking Search Console. Redirecting everything that has no obvious match to the home page.

Frequently asked questions

Is some traffic loss after a migration normal?

Short fluctuations are common while Google recrawls and processes the redirects, especially on large sites. A loss that persists or concentrates on particular sections is not normal and usually traces back to redirects, directives, content changes or tracking.

How long should old redirects stay in place?

Keep them for the long term. Google's site move documentation recommends keeping redirects in place for a long period, and external links to the old URLs rarely get updated, so removing redirects later throws that value away.

Can I undo a migration that went wrong?

Rolling back is possible but creates a second migration with its own risks. It is usually faster to fix the specific problems, missing redirects, staging rules or lost content, than to reverse the whole move.

Terms used on this page

Where this page is used

Also related

Sources

  1. Site moves with URL changes — Google Search Central
  2. Redirects and Google Search — Google Search Central
  3. Robots.txt introduction and guide — Google Search Central

Related