TRAFFIC & RANKINGS · FIELD GUIDE
SEO traffic dropped after a migration: trace old to new
Compare the old and new URL sets together before declaring lost demand. Verify that important old URLs reach relevant new destinations, then inspect the new pages’ responses, canonicals and indexing directives. A migration date is a lead, not proof of one cause.
Preserve a pre-migration reference
Keep exports of important pages, clicks and queries from a comparable completed period. Save the launch date and the old-to-new mapping. If the hostname changed, account for both Search Console properties; traffic disappearing from the old property may partly reappear on the new one.
Illustrative case: /features/alerts becomes /seo-alerts. Follow the old URL to its new destination and compare their combined search history. Looking only at the old path would report a loss even if visitors now land on the intended replacement.
Test redirects by value, then by template
Start with URLs that previously brought meaningful traffic, then sample each template. Follow each chain to its final status and content. A redirect to the homepage is not necessarily a relevant replacement. Fix loops, missing destinations and avoidable chains in the mapping layer.
- Old important URLs reach the closest relevant new pages.
- Final pages return useful 200 content.
- Internal links use final URLs rather than old redirect sources.
- New canonicals and sitemap entries agree with the mapping.
Check for staging settings in production
Inspect robots.txt, robots meta, X-Robots-Tag and authentication behavior. Review shared templates before changing isolated pages. Also compare page titles and visible content: a working route that lost its main content is not a successful migration from a search user’s perspective.
Separate expected movement from unresolved loss
Track important old/new page pairs and completed dates. Compare unaffected sections where possible. Search processing can take time, but do not use that uncertainty to ignore confirmed errors. Conversely, do not promise a fixed recovery date after repairing a redirect.
A useful incident record distinguishes “redirect mapping fixed today” from “Google has recrawled the new page” and “clicks recovered in later comparable periods”. Each is a different observation with its own timestamp.
Keep the migration under observation
Verify fixes through fresh public responses, update your sitemap and follow normal Search Console site-move guidance where applicable. Retain the URL mapping and decisions for future checks. SEO Orbiter can monitor selected important pages and search changes, but a large migration still requires a complete redirect and crawl audit.
Continue the investigation
- Organic traffic dropped: what to check first
- Canonical and noindex: different signals, different checks
- Sitemap errors: separate fetching from URL quality
Primary references
These references describe Google’s reporting and crawling behavior. The worked examples above are illustrative, not customer results.