URL Domain Changes and SEO: Why One Publisher Lost 98% of Visibility Moving to .com

The 98% Drop Nobody Planned For

A UK news publisher recently switched from their .co.uk domain to a .com extension. They followed the textbook: set up 301 redirects, mapped every URL one-to-one, timed the move for a quiet traffic window. Within weeks, organic search visibility collapsed by 98%. Not a typo. Ninety-eight percent of their hard-won rankings evaporated.

Domain migrations are supposed to be low-risk when done right. This case — reported by Search Engine Journal in early September 2026 — proves that "right" is a narrower window than most brands realise. For Indian D2C stores sitting on .in domains and eyeing .com for global appeal, or for brands consolidating multiple regional sites, this isn't an edge case. It's a warning that a single URL structure decision can torch years of SEO equity overnight. The publisher's mistake wasn't technical incompetence; it was underestimating how Google treats geographic domain signals and trust transfer. Here's what the wreckage reveals — and what you lock down before you ever consider a domain change.

Why Country-Code Domains Carry Geographic Weight (Even When You Think They Don't)

Country-code top-level domains — .in, .co.uk, .de — aren't just vanity extensions. Google's crawlers read them as implicit geo-targeting signals. When you operate on .co.uk, you're telling the algorithm "this content is for users in the UK" before a single tag is parsed. That signal stacks with server location, language tags, and content localisation, but the ccTLD is the loudest voice in the room.

The UK publisher's move to .com stripped that signal. Suddenly, Google had to re-evaluate: is this site still UK-focused, or is it now global? Without a ccTLD anchor, the algorithm downweighted the site's relevance for UK-specific queries. Even perfect 301 redirects can't patch that hole instantly, because the redirect tells Google where the page moved, not who it's for. The geo-targeting gap created ranking ambiguity, and ambiguity costs you visibility while crawlers re-index and re-rank.

For Indian D2C brands, the parallel is clear. If you're on .in and your entire customer base, content, and product catalog are India-specific, a move to .com means you're asking Google to infer your geography from weaker signals: hreflang tags, Search Console geo-settings, server IP, rupee pricing. Those matter, but they're secondary. A .in domain is a standing declaration; .com makes you argue your case page by page.

When .in beats .com for Indian D2C:

• You have no near-term plans to sell internationally
• Your brand equity and backlinks live on the .in URL
• Your product category competes locally (fashion, FMCG, personal care)
• You're still building domain authority — changing resets the clock

When .com makes sense:

• You're launching with multi-country intent from day one
• Your category is global-first (SaaS, B2B, niche hobbyist products)
• You haven't yet built significant .in equity (pre-launch or very early stage)

The rule: don't migrate to .com mid-growth. Do it at inception, or wait until you have enough authority and traffic diversity that a temporary dip won't kill your cash flow.

The Trust Transfer Illusion: Why 301 Redirects Are Necessary but Not Sufficient

The belief that a 301 redirect is a lossless handoff is SEO's most expensive myth. Yes, 301s are the correct technical implementation. Yes, Google's documentation says they pass "most" link equity. But "most" is doing a lot of work, and the time lag is a black box.

When you redirect Domain A to Domain B, Google doesn't instantly clone A's trust onto B. Instead, crawlers must:

1. Discover the redirect (via crawling the old URL or following updated sitemaps)
2. Re-crawl the new URL
3. Re-index the content under the new domain
4. Re-evaluate rankings based on the new URL's perceived authority
5. Update internal link graphs and backlink attribution

Each step has latency. If your old domain had 10,000 indexed pages, you're asking Google to re-process 10,000 URLs, re-score them, and re-rank them — all while the algorithm is also handling billions of other pages. Crawl budget becomes the bottleneck, especially for newer or lower-authority sites. The UK publisher's 98% drop suggests Google either didn't finish re-indexing the new domain, or it did re-index but assigned lower trust because the ccTLD signal vanished and the .com hadn't yet built comparable authority.

Comparison: Domain Migration Impact on Different Site Profiles

The table shows a pattern: the more equity you have on the old domain, the bigger the temporary hit — but also the faster the recovery, because high authority speeds re-crawling. New brands lose more and wait longer because they have less trust to transfer in the first place.

What this means for D2C migrations:

• Budget for a 30–50% traffic drop lasting eight to twelve weeks minimum
• Don't migrate during peak season (festive, sale windows)
• Keep the old domain's hosting and redirects live for at least twelve months
• Monitor Search Console's coverage reports daily to track re-indexing progress

The Migration Checklist Most Brands Skip (and Pay For)

The UK publisher's case hasn't released a full post-mortem, but Search Engine Journal's coverage signals the usual suspects: incomplete redirect mapping, missed Search Console steps, or failure to update external references. Here's the checklist that separates smooth migrations from catastrophic ones.

Pre-Migration (4–6 Weeks Before)

1. Audit the old domain's indexed pages. Export every indexed URL from Search Console or a crawler like Screaming Frog. If you have 5,000 products, you need 5,000 mapped redirects — no wildcards unless you're okay with broken URLs.
2. Map old URLs to new URLs one-to-one. Use a spreadsheet: Old URL | New URL | Redirect Type (301). If the page structure changes (e.g., category paths shift), decide now how to preserve URL hierarchy or accept ranking resets for those pages.
3. Verify the new domain in Search Console. Add the property, verify via DNS or HTML file, and confirm you can see data. Don't wait until migration day.
4. Set geo-targeting in Search Console for the new domain. If you're moving from .co.uk to .com but staying UK-focused, go to Settings > Geographic Targeting and select "United Kingdom". This partially replaces the ccTLD signal.
5. Notify Google of the domain change. In the old domain's Search Console property, go to Settings > Change of Address and select the new domain. This tells Google the move is intentional, not a hijack or duplicate.

Migration Day

6. Implement 301 redirects at the server level. Use .htaccess, Nginx config, or your CDN's redirect rules. Avoid JavaScript or meta-refresh redirects — they're slower and less trusted.
7. Update internal links on the new domain. Don't rely on redirects for your own navigation. Hard-code links to the new domain so crawlers follow direct paths.
8. Submit the new sitemap. Upload a fresh XML sitemap to the new domain's Search Console property. Remove the old sitemap from the old property to avoid duplicate crawl signals.
9. Check robots.txt on both domains. Ensure the old domain's robots.txt isn't blocking crawlers from discovering redirects, and the new domain's robots.txt allows indexing.

Post-Migration (First 90 Days)

10. Monitor crawl stats in Search Console. Track how many pages Google is crawling daily on the old domain (should decline) and the new domain (should ramp up). If the new domain's crawl rate stalls, you may have technical blocks or low authority.
11. Watch for 404s and redirect chains. Use Search Console's Coverage report to catch broken links. A redirect chain (Old URL → Temp URL → New URL) dilutes equity; fix chains to direct one-hop 301s.
12. Audit backlinks and update high-value ones. You can't control every backlink, but reach out to partners, directories, and press mentions to update their links to the new domain. Direct links are always stronger than redirected ones.
13. Track rankings for top-converting keywords weekly. Don't obsess over daily fluctuations, but if core terms drop >50% and stay there beyond six weeks, investigate whether geo-targeting, redirects, or content signals broke.

When a Domain Change Makes Sense for D2C (and When It Doesn't)

Not all domain migrations are bad bets. The calculus depends on growth stage, brand equity, and strategic intent. Here's when the risk/reward tips in favour of moving — and when you're better off staying put.

Green-Light Scenarios

You're pre-launch or in soft launch. If you have <100 indexed pages, <500 backlinks, and minimal traffic, the SEO cost of migration is negligible. Fix the domain now before you build equity on the wrong one.

You're consolidating multiple regional sites into one global .com. If you operate mybrand.in, mybrand.uk, and mybrand.com.au separately, merging into one .com with hreflang and geo-folders (/in/, /uk/, /au/) can simplify management and pool authority. The short-term hit per region is offset by long-term efficiency and cross-region link equity.

Your current domain has a penalty or toxic history. If you bought a dropped domain and later discovered a manual penalty or link spam, migrating to a clean domain and disavowing the old one is often faster than rehabilitation.

You're rebranding completely. If the business name changes, the domain must follow. Users expect brand-domain alignment. The SEO cost is unavoidable, so plan the migration with the full checklist and accept the recovery timeline.

Red-Light Scenarios

You're in the middle of a growth spike. If organic traffic is climbing month-over-month, don't touch the domain. Ride the wave, then migrate during a trough.

Your category is hyper-competitive and you're on page one. If you rank #2–5 for high-value terms, a migration could drop you to page two or three while competitors hold position. The revenue loss outweighs hypothetical .com benefits.

You lack the resources to execute a perfect migration. If you don't have a developer to map 301s, a marketer to update backlinks, and the budget to weather two months of halved traffic, don't start. A botched migration is worse than no migration.

Your brand equity lives on the current domain. If customers, partners, and press know you as mybrand.in and your social profiles, email signatures, and packaging all use .in, switching to .com creates brand confusion on top of SEO risk. The marginal SEO upside doesn't justify fragmenting recognition.

What Indian D2C Brands Should Do Right Now

If you're not planning a domain change, this case is still a gut-check for your current setup. Many D2C brands run sloppy redirect chains from old campaigns, duplicate staging environments that got indexed, or forgotten subdomains that split authority. Here's your housekeeping list.

Audit your redirect map. Crawl your site and check for 301/302 chains longer than one hop. Flatten them to direct redirects. A chain like oldproduct.com → newproduct.com → newproduct.com/product wastes crawl budget and leaks link equity.

Consolidate www vs non-www. Pick one canonical version (www.yourbrand.in or yourbrand.in) and 301 the other permanently. Split indexing dilutes authority.

Check Search Console for indexed subdomains you don't use. If staging.yourbrand.in or old.yourbrand.in is indexed, block it in robots.txt and request removal in Search Console.

Review geo-targeting settings. If you're on .in and serving only India, Search Console's geo-target should reflect that. If you're on .com and serving India, set the target explicitly — don't assume Google infers it from your content.

Plan a hypothetical migration. Even if you're staying put, sketch the checklist above as a disaster-recovery exercise. If your .in domain ever gets compromised, hijacked, or caught in a registrar dispute, you need a playbook to move fast without torching your rankings.

If you are considering a domain change — maybe you're eyeing .com for future international scale, or you're merging an acquisition's domain into yours — model the downside first. Pull twelve months of Search Console data: what's your baseline organic traffic? What's your top-landing-page revenue? If you lose 50% of that for eight weeks, can your paid channels and repeat customer base cover the gap? If the answer is no, you can't afford the migration yet. Build more authority, diversify traffic sources, and revisit in six months.

And if you're unsure whether your technical foundation can survive a migration, or you want a second set of eyes on your redirect architecture and crawl health, that's exactly the kind of diagnostic work our SEO team runs before any structural change. We don't recommend migrations