Google Reverting to Old Domain 4 Months After Migration: What's Going On?

A site owner who correctly executed a domain migration at the start of 2026 watched their new domain recover to roughly 5,000 impressions per day by April, only to see Google abruptly de-index over 5,000 pages and start serving the old domain again four months later. Barry Schwartz covered the story, sourced from a Reddit thread, at Google Search Showing Sites Old Domain Fourth Months After Domain Move?. Google's John Mueller responded to the user directly, and prominent SEO consultants Marie Haynes and Glenn Gabe confirmed they are seeing the same pattern with other migration clients.

This isn't a one-off glitch. It's a signal worth paying attention to if you're planning a migration, in the middle of one, or advising a client who is.

The Details: What the Source Actually Reports

According to the Reddit thread Barry flagged, the site owner made the switch to a new domain at the beginning of 2026 to cover an additional topic. They did things right: redirects were implemented correctly, and the Google Search Console Change of Address tool was used. By April, traffic had recovered and the new domain was receiving around 5,000 impressions per day.

Then things unraveled. Four months after the migration, Google de-indexed more than 5,000 pages on the new domain, categorizing them as "Crawled, currently not indexed." Impressions on the new domain collapsed to just 20 per week. Simultaneously, the old domain was fully re-indexed and all Search Console impressions and clicks shifted back to it.

John Mueller stepped in on the thread. He offered two observations. First, he noted that "sometimes things just take a particularly long time to be fully processed." Second, he flagged a documentation update worth knowing: the Change of Address tool should be configured for both the www and non-www version of the domain to allow a full migration. Whether either of those explains what happened here is unclear. Barry Schwartz himself admitted he couldn't imagine the www/non-www issue alone would cause something this dramatic, months after the new domain had already been successfully indexed.

What This Means for You

Here's the part that should get your attention. Barry mentioned he's been receiving emails from site owners about migrations going wrong months after the fact. And Marie Haynes shared a pointed theory on the same day the story broke: she believes a domain migration triggers a fresh quality assessment from Google, and that Google is becoming stricter about what it chooses to index.

Haynes noted that in most cases she's seen, the affected sites are "decent sites," but the content "offers nothing original compared to what is currently indexed." Google Search Console for these sites shows pages stuck in the "Crawled, currently not indexed" state. Meaning Google is seeing the pages. It's just choosing not to index them.

That's a meaningful distinction. This isn't a crawl access problem. It's a content quality and uniqueness problem surfacing at a vulnerable moment in a site's life: right when Google has reason to reassess everything from scratch.

Think about what a migration actually signals to Google. You're essentially saying, "This is a new home for this content." And if Google takes that as a trigger to re-evaluate the content with fresh eyes, sites that coasted on accumulated authority at their old domain may not pass that quality bar on their own merits. I've seen this kind of delayed reckoning happen with core updates too, where a site looks fine for weeks and then craters once Google's systems finish processing the changes.

What to Do Now

Whether you're mid-migration, planning one, or dealing with a client whose rankings just collapsed months after a move, here are the concrete steps that matter.

1. Check your Change of Address setup for both www and non-www in Google Search Console. Mueller specifically called this out. It's a quick audit item and easy to overlook.
2. Pull your Coverage report in Search Console and filter for 'Crawled, currently not indexed.' If you're seeing thousands of pages in that bucket on your new domain, you have a content quality signal problem, not just a technical one.
3. Audit your content for originality before you migrate. Don't move content that's thin, duplicative, or offers nothing beyond what's already indexed on the topic. A migration can expose weaknesses that domain authority was masking.
4. Keep both Search Console properties active and monitored for at least six months after a domain move. Impressions and clicks on your old domain property are a warning sign if they start climbing after you've migrated.
5. Do not cancel your redirects early. If the old domain is getting re-indexed, check whether your 301s are still functioning correctly at scale. A lapsed redirect can reopen the door for Google to treat the old domain as live.

If you're managing migrations for multiple clients, site audit tools that flag indexation status changes early give you a real advantage. Catching the 'Crawled, not indexed' signal at 50 pages is a very different conversation than catching it at 5,000.

Background and Context: Why This Pattern Is Growing

Domain migrations have always carried risk, but the calculus has shifted. Google has been consistently vocal about original, insightful content that demonstrates talent, genuine effort, and skill. That standard doesn't get applied only at launch. If Marie Haynes's theory holds, migrations are creating a re-evaluation window where Google applies that standard anew.

Glenn Gabe, one of the most respected names in algorithmic recovery, confirmed he's seeing migrations go wrong in the same delayed pattern. When Gabe, Haynes, and Schwartz are all hearing similar reports at the same time, it's not a coincidence. It's a pattern worth treating as a working hypothesis until Google gives a clearer answer.

The broader context here: Google has been tightening indexation standards across the board. Helpful Content signals, core quality assessments, and the general push toward fewer, higher-quality indexed pages all point in the same direction. A migration may now be the moment Google decides to run that assessment on your content, with your old domain's accumulated signals no longer available as a buffer.

Mueller's response asking for a direct message suggests Google may be investigating this specific case further. That's a good sign for the individual site owner. But it doesn't change the wider implication: if you're migrating to a new domain, your content needs to stand on its own quality, not just your redirect chain.

Aergos tracks indexation and impressions across both old and new domain properties during migrations, which makes it easier to catch a reversion like this early rather than weeks after the damage compounds.

The bottom line: a successful migration in month one does not mean a successful migration in month four. Keep watching your Search Console data well past the honeymoon period. Google isn't done evaluating your move just because it seemed to work at first.