A UK news publisher moved from .co.uk to .com and, within two weeks, its visibility on trending Google news queries fell by 98%. That’s the headline number from NewzDash, the news-SEO platform run by John Shehata, and it should make every growth lead planning a rebrand pause for a second.
What actually happened
NewzDash tracked the publisher’s .co.uk domain for 14 months before the migration. Over that window the site held roughly 1% to 2% visibility across the UK news results NewzDash monitors. Similar-sized publishers, Shehata says, usually sit between 3% and 6%, so it was already underperforming.
Then the site moved overnight. Visibility slid during the migration and landed at 0.02% two weeks later. The new .com domain never absorbed what the old one lost. Four months on, Shehata reports only scattered, isolated appearances and no sign of recovery.
Important caveats, and Shehata flags them himself: the site was already bleeding visibility across several core updates, and internal technical problems likely played a part. The data does not prove the domain switch was the sole cause. The publisher isn’t named and the underlying data hasn’t been published, so the 98% can’t be verified independently.
Why the number is so much bigger than your rank tracker would show
This is the part performance teams should internalise. Shehata says conventional SEO tools showed a drop closer to 60-70%. The gap is about what’s being measured.
Standard tools track a fixed keyword set that skews evergreen. NewzDash’s Search Visibility score tracks a constantly changing set of trending news queries across Top Stories and organic results, estimating click share from ranking position, estimated CTR, how long a URL ranks, and how many URLs appear. It predicts clicks, not actual traffic.
So one methodology said “painful”, the other said “catastrophic”, and both were looking at the same site. If your traffic depends on fast-moving, time-sensitive queries, a migration report built only on evergreen keywords will flatter you.
What Google’s own guidance says
Google treats a domain change as a standard site move. Its guide covers mapping old URLs to new, permanent redirects, submitting a Change of Address in Search Console, and monitoring URLs afterwards. Google confirms 301s don’t harm PageRank and processes each URL change separately, while warning about ranking fluctuation during recrawling. Medium sites can wait weeks or longer for new URLs to surface; large sites, longer still.
Two lines from that guide matter most here:
- Large sites should test with one section first, ideally one that doesn’t change often.
- Don’t combine a domain move with a CMS change or a redesign.
For Google News, Publisher Center guidance adds: follow the same process, update the News sitemap when structure changes, keep the crawler’s path clean, and avoid long redirect chains. Google lists relevance, prominence, authoritativeness, freshness, usability, location and language as ranking factors for News, but neither page explains how those signals transfer across domains.
Back in June, Google’s John Mueller answered a Reddit user considering a .ca to .com move with a line worth pinning above your desk: “A site move is always a big deal, even if you take the time to do it right.”
Shehata’s theory: the “Google Reset”
Shehata argues that drastic changes such as a CMS swap, redesign or domain change push Google to re-evaluate the site from scratch. He calls it the “Google Reset”, his term, not Google’s. His view is that news surfaces weigh hostname-level signals like publication history and editorial trust, and while a 301 passes link equity, it “may not carry that history”.
Google’s documentation doesn’t state that news history is hostname-based, so treat this as a practitioner hypothesis backed by one tracked case.
What to do before you touch the DNS
The business rationale here was reasonable: one global domain, and an end to being classified as a UK site by ad systems. The execution is where the risk sat.
If a migration is on your 2026 roadmap:
- Baseline your trending-query visibility before the move, not after. Evergreen rank tracking alone will hide the damage.
- Move in sections rather than overnight, starting with content that rarely updates.
- Never stack a redesign or CMS change on top of a domain change.
- For news sites, confirm the new domain is showing in Google News before shifting everything.
- Fix known technical debt first. Migrating on top of existing issues makes attribution impossible when things go wrong.
The honest conclusion: nobody can cleanly separate migration damage from core update damage from technical debt in this case. But that ambiguity is exactly the point. Once you move overnight, you lose the ability to diagnose.
Source: Search Engine Journal
