A site owner who completed a clean domain migration in early 2026 suddenly saw Google reverse course four months later, dropping over 5,000 new-domain pages into a “Crawled, currently not indexed” state while re-indexing the old domain. Anyone running a site migration needs to understand what happened and which settings to double-check so the same reversal does not hit their property.
What happened to the migrated site
The site owner changed both the website name and the domain at the beginning of 2026 so the property could cover an additional topic. Redirects were implemented correctly and the Change of Address tool in Google Search Console was used. By April, traffic had recovered and the new domain was being indexed, with about 5,000 impressions per day showing in Search Console.
Four months later, the picture flipped:
- Over 5,000 pages on the new domain were classified as “Crawled, currently not indexed,” and impressions on the new domain collapsed to roughly 20 per week.
- Google fully re-indexed the old domain, and the search impressions and clicks for queries the site had been ranking for began surfacing on the old property in Search Console.
The site owner did not change the redirects, did not undo the Change of Address tool, and did not alter the content. The reversal came from Google’s side.
Why Google may flip back to the old domain
A Google search representative responded on the thread and asked the site owner to send the details directly. Two points came out of that exchange that any site owner can act on.
Processing takes time. Full processing of a domain move can take much longer than most owners expect. The representative noted that processing sometimes takes an unusually long time to complete.
Second, the Change of Address tool has to be set up twice if the site serves both versions. The same example surfaced in a documentation update: change of address should be configured in Search Console for both the www and non-www version of the new domain, so the property can be fully migrated. Missing one of those two is a common reason Google keeps one foot in the old domain.
Search Console is where the diagnosis lives in most cases. When the new domain’s coverage report is full of “Crawled, currently not indexed,” the pages are being fetched, Google is choosing not to keep them, and that choice usually traces back to how Google is reading the site’s content relative to what is already indexed.
Why migrations are triggering more reversals
The thread is not an isolated case. Several SEO practitioners have reported the same pattern across multiple migrations, forming a shared theory that a site migration can trigger a fresh quality assessment. When the reassessment runs against a site whose content does not stand out from what is already indexed, Google can scale back what it keeps.
Google has stated this standard publicly. Google’s system aims to index pages that offer some original insight, demonstrated skill, and genuine effort. Sites that add nothing new compared to what is already in the index are most likely to end up in “Crawled, currently not indexed” after a reassessment.
For a property that just moved domains, this is the moment Google is most likely to look hardest at what is on the page. A migration that worked in the first month can be re-tested one migration later if the content is borderline, so the reversal in this case showed up months after the redirect work was done.
What to check on a migration that is going wrong
Site owners seeing the old domain reappear in Search Console should work through this list before assuming a Google bug.
- Set up Change of Address for both versions. If the site is reachable at both www and non-www, run the Change of Address tool in Search Console for the version that matches what is in Search Console, and confirm the other version redirects cleanly to it.
- Read the Coverage report on the new property. Look for the “Crawled, currently not indexed” label and how many URLs it covers. That number is the clearest signal that Google is fetching the pages and choosing not to keep them.
- Compare against the old property. If the old domain is now showing impressions and clicks for queries the new domain used to rank for, the system is treating both as live.
- Audit the content for originality. The pattern in this case matched what others have described: pages that look interchangeable with what is already indexed are the ones that get dropped after a quality reassessment.
- Do not undo the redirects. Rolling back the 301s while the new domain is being re-evaluated can create a second round of confusion. Keep the redirects in place while the diagnosis is done.
A site owner who wants a structured read on coverage and indexing can run a technical audit that surfaces the exact pages stuck in “Crawled, currently not indexed,” along with the redirect and canonical signals behind each one. SEOScanPro’s full technical audit produces that breakdown and shows the measured result behind each check.
What this case means for future migrations
The lesson from this thread is not that domain moves are broken. It is that a domain move is now a quality gate as well as a technical task. The redirect map, the Change of Address tool, and the www/non-www setup are still required. The new variable is the content itself: if the new property is mostly a duplicate of what is already indexed under a different URL, Google can quietly stop keeping those pages months after the move.
For any team planning a migration, the move should be paired with a content review of which sites publish pages that look like the others on the same topic, and where the new property can publish something the rest of the index does not have. That is the part of a migration that no setting in Search Console can fix.
FAQ
Why is Google showing my old domain after a migration?
Google keeps a record of the old property and can re-surface it if the Change of Address tool was not set up for both the www and non-www version of the new domain, or if processing has not fully completed. In the case covered here, the new domain was de-indexed and the old domain was re-indexed four months after a clean migration.
What does “Crawled, currently not indexed” mean after a migration?
It means Google fetched the pages and chose not to keep them in the index. After a domain change, this label often shows up when Google is reassessing the content against what is already indexed and the new pages do not add anything original.
How do I stop Google from re-indexing my old domain?
Run the Change of Address tool in Google Search Console for both the www and non-www version of the new domain, keep the 301 redirects in place from the old domain, and confirm that the old property’s coverage report shows the old URLs as redirected rather than as live indexed pages.
Try the Search Console analytics view
SEOScanPro runs a full technical audit of a site and shows the measured result behind every check. Open the Search Console analytics view.