Domain Migration Indexing Issues: A Practical Recovery Plan
A practical, evidence-led plan for diagnosing old-domain canonical selections and new-page exclusions after a website rebrand or domain move.
· 14 min read
A finance publisher reported moving about 2,200 pages to a new domain on August 12, 2026, briefly retaining rankings before impressions fell and the new-domain indexed count reportedly dropped from roughly 1,900 pages to around 300. For teams facing domain migration indexing issues, this guide provides a way to distinguish conflicting migration signals from an indexing-selection or content-quality reassessment before making another sitewide change.
The reported case originated in an r/SEO discussion. The publisher said it had implemented one-to-one 301 redirects, a Google Search Console Change of Address, self-referential canonicals, and new XML sitemaps. It later found that, for some URLs inspected in Search Console, Google had selected old-domain URLs as canonicals while corresponding new URLs were excluded as “Crawled - currently not indexed.”
That is a serious pattern worth investigating, but it does not prove one universal cause. Google’s systems consider redirects, canonicals, duplicate clustering, page accessibility, internal links, content, and other signals. A sound recovery process documents what is observable, changes one cause at a time where possible, and avoids treating a single community report as a Google requirement.
Read the reported signals carefully
In the reported case, Googlebot continued crawling new pages, the old domain retained an estimated 950 indexed URLs, and the new domain had far fewer indexed pages than immediately after the move. Those observations narrow the investigation, but they do not establish a penalty, manual action, or a specific spam-system outcome.
Three Search Console states are particularly relevant:
- Google chose a different canonical than the user: Google has placed URLs in a duplicate or near-duplicate cluster and selected a different representative URL. A declared canonical is a hint, not a directive, as explained in Google’s canonicalization documentation.
- Crawled - currently not indexed: Google retrieved the page but has not selected it for indexing at that point. It is not, on its own, evidence of a manual action.
- Submitted and indexed on the old domain: An old URL may remain indexed while Google processes a move. The concern rises when old URLs remain selected alongside persistent exclusions of their new equivalents.
The source report describes some inspected old URLs being selected as canonical. It does not establish that Google selected old URLs across every page, across hundreds of pairs, or for the whole site. Any audit should measure the size and location of the problem instead of assuming its scale.
Establish whether the move is technically coherent
Google’s site-move guidance recommends mapping old URLs to new URLs, using permanent server-side redirects, updating references to the new URLs, and monitoring both properties. Completing those headline tasks is necessary, but it does not prove that every template, host variation, or legacy URL behaves consistently.
For a migrated article URL, the expected chain is straightforward:
- The old URL returns one direct permanent redirect to the closest relevant new URL.
- The destination returns 200 OK, is crawlable, and does not contain a
noindexdirective. - The destination declares itself as canonical and does not emit a conflicting canonical after JavaScript renders.
- XML sitemaps and internal links reference the final new URL rather than the old URL or an intermediate redirect.
- The old domain does not still serve an accessible 200-version of substantially the same page.
A CMS can look correctly configured while one of these layers fails. Typical examples include an old www host left live, a redirect chain through HTTP, a sitemap generated from stale URLs, or a JavaScript component that writes a legacy canonical into rendered HTML.
The right unit of analysis is the URL relationship, not the migration announcement. A landing page that redirects correctly says little about paginated archives, parameter variants, author pages, PDFs, alternate language URLs, or recently published articles.
Audit redirect pairs with a documented sample
For a site with approximately 2,200 URLs, a spreadsheet or crawler export can compare old URLs, redirect destinations, final response codes, and canonical targets at scale. Useful source lists include old XML sitemaps, Search Console exports, analytics landing pages, server logs, and backlink reports.
A review of 100 URLs can be useful for a large site, but it is an editorial sampling heuristic, not a Google threshold. The appropriate sample size varies with the number of templates, historical URL variants, traffic concentration, and technical complexity. A 50-page brochure site may need a full review; a publisher with dozens of templates may need stratified samples plus automated crawling.
Redirect failures that warrant attention
The following are concrete defects, not merely cosmetic differences:
- An old URL returns 200 OK and exposes duplicate content instead of redirecting.
- An old URL reaches the new destination through two or more hops.
- Thousands of old articles redirect to the home page or a generic category instead of the closest equivalent.
- The redirect target returns a 404, soft 404, 5xx, blocked response, or
noindexdirective. - Trailing-slash, uppercase, parameter, AMP, pagination, or alternate-host variants behave differently from the primary URL.
- Redirect behavior changes by country, cookie, user agent, or JavaScript execution.
For example, an old article about Company A’s Q2 results should normally redirect to the matching migrated article, not a broad earnings archive. If no replacement exists, a 404 or 410 can be more accurate than an unrelated redirect.
Google’s site-move documentation advises keeping redirects in place for at least one year. That is documented guidance, not a guarantee that all signals will consolidate within a year. Sites with durable backlinks, referral traffic, or long-tail URL variants may have a practical reason to retain redirects longer.
Investigate canonical selection without guessing a timetable
Google explains that canonicalization can take time because it must crawl, process, and evaluate signals. Its documentation does not provide a universal two-week re-evaluation guarantee for migration fixes. Teams should therefore avoid presenting a fixed waiting period as a Google commitment.
A practical diagnostic starting point is 20 affected old/new URL pairs, but that number is also an editorial heuristic. The sample should include the home page, major section pages, high-traffic pages, newly published pages, and examples from every affected template. If the first set reveals a template-level defect, expand the review to that template rather than relying on a percentage cutoff.
Create a canonical evidence table
For each inspected pair, record observable signals in a table like this:
| Signal | Old URL | New URL | Expected state |
|---|---|---|---|
| HTTP response | 301 | 200 | One direct move to the final URL |
| Declared canonical | N/A after redirect | Self-referential | New URL selected |
| Rendered canonical | N/A | Self-referential | Matches raw HTML |
| XML sitemap | Excluded | Included | Final new URL only |
| Internal links | Legacy links removed | Direct links | New URL used consistently |
| Search Console result | Inspection result | Inspection result | Evidence retained by date |
Google may temporarily show an old URL as the selected canonical even where the old URL redirects correctly. What matters is whether all available signals support the new URL and whether the pattern improves after defects are corrected. A stable contradiction across multiple representative templates deserves deeper review; it should not be dismissed as normal migration delay.
For a focused host-level diagnostic, Google Choosing www as Canonical: Fix Non-www Indexing covers conflicts between www and non-www versions.
Treat exclusion as an indexing-selection question
“Crawled - currently not indexed” means retrieval occurred. Repeated indexing requests are therefore unlikely to repair a redirect conflict, duplicate cluster, weak page template, or rendering failure. Google’s recrawl guidance says requests are subject to quotas and that repeatedly requesting the same URL does not make Google crawl faster.
After a specific improvement, teams can request indexing for a small, meaningful validation set: the home page, several historic organic landing pages, one or two category pages, and representative pages from corrected templates. This is a diagnostic use of the tool, not a replacement for fixing the inventory.
For each excluded page, compare it with an indexed page of similar purpose on the same site. Check whether the main content is accessible in rendered HTML, whether the page is materially distinct from close alternatives, and whether relevant hubs link directly to it.
A crawl does not promise index inclusion. Google’s systems can retrieve a page successfully and still decide not to index it at that time. The next step is to identify whether the pattern aligns with migration conflicts, content-template similarity, weak internal linking, server instability, or a combination of those factors.
Review template value and scaled-content risk
The publisher in the source case said its finance articles were generated with AI from filings and earnings-call transcripts, then supplemented with primary-source links and expectation-versus-results analysis. Those additions can create reader value, but a high-volume template still needs editorial controls.
Google’s guidance on generative AI content does not prohibit AI-assisted publishing. It says content should be accurate, relevant, and useful, while Google’s spam policies address scaled content abuse when many pages are created primarily to manipulate rankings rather than help users.
That does not mean a traffic decline near a migration proves a scaled-content finding. It means the content model merits an independent review, especially where many pages share the same structure and source material.
Test for information beyond the source document
A stronger financial-results page may include:
- Exact links to the filing, earnings release, and call transcript used as primary sources.
- A clear explanation of what changed from the prior quarter, with specific figures and context.
- Transparent methodology for any consensus or expectation comparison.
- Analysis of guidance changes, business segments, management commentary, or stated risks.
- A named reviewer, timestamp, corrections policy, and explanation of how automation is used.
- Links to prior-quarter coverage, company profiles, and relevant sector context.
The objective is not a fixed word count. A 1,500-word article that restates an earnings release may remain low-value, while a concise analysis with transparent sourcing and useful interpretation can be more helpful. Reviewing a mix of high-, medium-, and low-traffic pages helps determine whether the issue is isolated or template-wide.
Separate migration timing from suspected update effects
The source author associated the decline with an August 2026 spam update because the traffic loss happened around that period. That is a hypothesis, not confirmed causation. Google says its automated spam systems run continuously, while named spam updates refer to improvements in those systems; see Google’s spam update guidance.
A disciplined timeline can reduce unsupported conclusions:
- August 12, 2026: reported launch date for the new domain and brand.
- The following days: the author reported that rankings broadly held and about 1,900 new-domain pages were initially indexed.
- August 16, 2026: the author reported a sharp decline in impressions and average position.
- Later in August 2026: the author observed an update rollout and fewer new-domain URLs indexed.
- Afterward: the publisher reported adding source links, more analysis, internal links, and brand-transition messaging.
Overlay this timeline with Search Console Performance, Page Indexing, Crawl Stats, URL Inspection exports, deployment logs, and server error monitoring. If old canonical selections appeared before the visibility drop, technical consolidation is a strong candidate. If technical signals remain consistent while a large template set becomes excluded after expansion, a broader quality reassessment becomes more plausible. Either way, the available evidence may support more than one cause.
Use an ordered recovery plan, not numeric promises
A 30-day schedule can help teams sequence work, but it is an editorial operating plan, not a recovery promise or Google-defined timeline. Indexing and canonical selection vary by site history, crawl demand, implementation quality, and the scope of changes.
First phase: collect the baseline
Crawl both domains and export response codes, redirect chains, robots directives, raw and rendered canonicals, sitemap URLs, and internal-link targets. Check representative URL pairs from every template and record the inspection date. Review Crawl Stats for recurring 5xx responses, host-load warnings, or resource failures.
Second phase: fix clear contradictions
Correct stale host references, redirect chains, wrong canonicals, sitemap pollution, and inconsistent alternate URLs. Prioritize pages with historic organic traffic, conversions, backlinks, or strategic commercial value. Avoid changing redirects, canonicals, templates, and robots directives all at once unless an urgent defect requires it.
Audra can support this phase with a local crawl that outputs URL-level response codes, canonical declarations, indexability findings, internal-link data, performance checks, and accessibility issues in one audit. For example, a consultant can export a report filtered to old-domain URLs returning 200, new URLs with non-self canonicals, and sitemap URLs that redirect; that creates a client-ready remediation list rather than a generic product mention.
Third phase: validate directionally
After deployment, inspect a limited set of corrected priority pages and monitor canonical selection, indexed-page trends, crawl behavior, and impressions by page type. Do not define success as reaching a particular index count in 30 days. Better evidence is a reduction in contradictory signals, successful crawling of final URLs, and gradual recovery among high-value page groups.
Decide whether to keep publishing and when to escalate
Publishing can continue during a migration when new pages meet the same technical and editorial standards as the corrected site. But a publisher whose main template is under review may choose to slow production temporarily, especially if new pages would repeat known canonical, rendering, or quality weaknesses.
There is no Google rule that a 5% defect rate triggers escalation. As an editorial triage rule, any defect affecting a revenue-critical template, a major section, or a pattern of important URLs can justify immediate technical review even if the percentage is small. Conversely, a minor edge-case issue may be lower priority despite appearing in several URLs.
Escalation to an experienced migration or technical SEO specialist is reasonable when URL Inspection shows unexpected rendered content, old URLs remain accessible as 200 pages, redirect targets fail, server errors recur, or representative new pages remain excluded after demonstrable corrections and adequate observation time.
Once key URLs are indexed, the work is not necessarily finished. Page Indexed but No Impressions: What to Check After SEO Fixes addresses the separate question of why indexed pages may still not earn search demand. For inventory decisions during cleanup, Do Non-Indexed Pages Affect SEO? A Practical Triage Framework offers a useful next step.
FAQ
When should a site revert a domain migration?
Reversion is usually a last resort, not a response to a short-term indexing decline. It may be considered when the new domain has a fundamental legal, hosting, security, or implementation problem that cannot be corrected promptly. Before reversing, teams should document redirect behavior, canonical signals, crawl errors, and business impact, because a second migration can add further consolidation complexity.
Should a site keep publishing during migration recovery?
It can, provided new URLs are technically sound and offer distinct value. If new content uses a template with unresolved canonical, rendering, or thin-content concerns, slowing publication can make diagnosis cleaner. Priority should go to correcting high-value existing pages and ensuring every new page uses final-domain internal links, self-canonicals, and verifiable source material.
How can a team tell migration failure from a quality reassessment?
Migration failure is more likely when old URLs return 200, redirect chains exist, sitemaps contain legacy URLs, canonicals conflict, or rendered pages differ from raw HTML. A quality reassessment becomes more plausible when technical signals are consistently correct but many similar pages remain excluded. The evidence can support both explanations, so teams should test technical consistency before assigning a quality cause.
How long should old-domain redirects remain active?
Google’s site-move documentation recommends retaining permanent redirects for at least one year. That is a minimum guideline rather than an expiration date. Domains with enduring backlinks, bookmarks, referral traffic, or legacy URL variations often benefit from keeping redirects longer, as long as the old domain can be maintained securely and reliably.
Is an old URL selected as canonical proof that the migration failed?
No. A selected old canonical can occur while Google processes a move, particularly shortly after launch. It becomes more concerning when repeated inspections show the same pattern after clear signal conflicts have been fixed. Teams should verify the old URL’s response, the new URL’s canonical and render state, sitemap inclusion, and internal-link targets before drawing conclusions.
Sources
- https://www.reddit.com/r/SEO/comments/1xpbee4/after_rebranding_new_domain_not_getting_indexed/
- https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
- https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls
- https://developers.google.com/search/docs/fundamentals/using-gen-ai-content
- https://developers.google.com/search/docs/appearance/spam-updates
- https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl