A UK news publisher reportedly lost 98% of its visibility for trending news searches in the two weeks after moving from a .co.uk address to a .com domain.
That is a dramatic figure, but it needs context. The publisher has not been named, the underlying data is not public, and technical problems and earlier Google updates may also have contributed. The measurement came from NewzDash, which follows a changing set of trending queries rather than the fixed keyword lists used by many SEO tools.
Even with those caveats, the case is a useful warning for organisations in Bath and across the South West. Changing a domain is not a simple branding exercise. It changes every important URL on a website and asks search engines to transfer their understanding from the old address to the new one.
What appears to have happened
According to Search Engine Journal’s report, the publisher moved its whole site from .co.uk to .com overnight. NewzDash had tracked the old domain for 14 months. Its estimated visibility then fell from around 1% to 2% to just 0.02% after the move, while the new domain did not recover the missing visibility.
The 98% figure is an estimate of potential click share across news results, not a measurement of the site’s actual traffic. Other unnamed SEO tools apparently showed a smaller fall of roughly 60% to 70%. That difference matters because an ordinary migration report based on a stable list of evergreen keywords can miss losses on fast-changing searches.
The lesson is not that every move from .co.uk to .com will fail. Nor does this case prove that the new top-level domain caused the entire loss. It shows how severe the risk can be when a domain move, technical issues and volatile search demand overlap.
Why a domain change is bigger than a redirect
A permanent redirect is essential, but it is only one part of a successful migration. Google processes changes URL by URL. It must crawl the old address, follow the redirect, understand the new destination and update its index. Google says medium-sized sites can take weeks or longer to move across, with larger sites potentially taking more time.
Businesses also need accurate one-to-one URL mapping, self-referencing canonical tags on the new pages, updated internal links, fresh XML sitemaps and working analytics. Search Console properties should be verified for both domains, and an eligible domain move should use Google’s Change of Address tool.
Problems become harder to diagnose when a domain migration is combined with a redesign, a new content management system, rewritten pages or a different site structure. Google’s own guidance recommends changing one thing at a time where possible. Our approach to SEO for Bath businesses follows the same principle: preserve clear signals, measure the change and avoid adding uncertainty unnecessarily.
Do not judge the move from one dashboard
The reported case also highlights a measurement problem. A migration may look acceptable in a rank tracker while losing visibility for searches that were not on its original keyword list.
A local business will rarely need publisher-style news monitoring, but it should still watch more than a headline traffic total. Check branded and non-branded searches, important service pages, local queries, enquiries, telephone calls and conversions. Compare old and new URLs in Search Console, and look for crawling, indexing, canonical and redirect errors.
Seasonal demand can disguise a problem. A hotel, restaurant or visitor attraction might migrate during a busy period and initially see stable enquiries even while organic visibility weakens. A business-to-business firm with a long sales cycle may not notice the commercial effect for months. The monitoring plan should reflect how customers actually find and contact the organisation.
What to check before changing domains
- Make the commercial case. A shorter or more international domain may look attractive, but the expected benefit should justify the search and operational risk.
- Build a complete URL inventory. Include landing pages, images, documents and older pages that still receive links or traffic.
- Map each useful old URL to its closest new equivalent. Avoid sending everything to the home page or creating redirect chains.
- Test before launch. Crawl the staging site, check canonicals and metadata, and confirm that blocked staging rules will not reach production.
- Keep the old domain. Maintain redirects for as long as possible and continue renewing the domain.
- Prepare a monitoring baseline. Record search traffic, rankings, conversions, indexed pages and crawl errors before the switch.
For a large or frequently changing website, consider moving a quieter section first. Google specifically suggests testing a section that does not update often. That provides evidence before the highest-value pages are put at risk.
A migration needs an owner and a rollback conversation
Domain changes cross several disciplines: development, content, analytics, paid media, email, security and search marketing. Someone should own the checklist and the launch decision rather than assuming each supplier has covered the gaps.
A full rollback is not always the best response to early volatility, because reversing URLs again creates another change for search engines to process. But the team should agree in advance what would trigger investigation, which errors can be fixed in place and who can make urgent technical changes.
The unnamed publisher’s experience should not be treated as a universal forecast. It is better read as a reminder that search visibility is an asset worth protecting. If a new domain is genuinely necessary, plan it as a controlled migration, preserve every signal you can and monitor the measures that matter to the business—not only the easiest graph to find.
Sources: Search Engine Journal; Google Search Central’s site move guidance.
