Skip to content
Resources

Diagnosis answer

How do you know a migration caused ranking loss?

A direct answer for separating migration-caused ranking loss from algorithm changes, seasonality, tracking gaps, or normal volatility.

Short answer

A migration is the likely cause when the drop starts shortly after launch, affects URLs or templates that changed, and lines up with redirect, canonical, sitemap, metadata, structured data, internal-link, rendering, or tracking changes. Do not assume the migration caused every drop, but do not wait weeks before checking the technical signals.

Look for timing: launch date, DNS cutover, redirect deployment, sitemap submission, and first Google recrawl.

Look for scope: one template, one folder, product/category pages, blog posts, or the whole domain.

Look for signal changes: old URLs not redirected, new URLs not indexed, canonicals pointing elsewhere, missing metadata, or thinner rendered HTML.

Migration loss vs other explanations

OptionWhat it coversRisk to watch
Migration-caused lossDrop aligns with launch and clusters around changed URLs, templates, redirects, canonicals, or sitemap entries.Usually fixable faster if evidence is captured before Google recrawls the broken state for weeks.
Algorithm or SERP shiftCompetitors move at the same time and unchanged pages drop without technical signal changes.Requires SERP and content analysis, not only redirect or code fixes.
Tracking or reporting gapGA4, GTM, consent, or tag firing changed while GSC impressions remain stable.Can hide real leads or create a false traffic-drop panic.

Evidence to collect before deciding

  1. 1GSC Performance by page and query for 28 days before and after launch.
  2. 2GSC Pages report, Sitemaps report, Crawl Stats, and URL Inspection samples for priority URLs.
  3. 3Old crawl, new crawl, redirect map QA, sitemap export, canonical export, and rendered HTML samples.
  4. 4GA4 landing pages, lead events, source/medium split, and tag firing checks.
  5. 5SERP checks for a small set of priority queries to see whether the entire SERP shifted.

Official source checks

Google traffic-drop debuggingUse this to compare drop patterns before blaming the migration, an update, or seasonality.Search Console URL InspectionUse this for URL-level indexing, canonical, sitemap, and live-test details.Google site move guidanceUse this when the diagnosis involves URL changes, redirects, and move monitoring.

Need the answer applied to your site?

SEOParity turns the crawl, Search Console, redirect, canonical, sitemap, schema, and analytics evidence into a developer-ready fix list.

Related SEOParity pages

Traffic dropped after redesignUse this when you need the full 72-hour diagnostic sequence.Pages deindexed after migrationUse this when indexed page count or priority URLs disappeared.