This post reviews a failed domain migration: after selling the old domain and switching directly to a new one, the site owner caused Google to treat the new domain as a completely new website. Indexation and traffic quickly fell to zero. The core issue was a misunderstanding of domain-level SEO assets. Keywords: domain migration, 301 redirects, Google indexation.
Technical Specifications Snapshot
| Parameter | Description |
|---|---|
| Domain Area | SEO / Website Migration / Domain Operations |
| Core Issue | The old domain expired without a migration path, causing search equity loss |
| Key Protocols | HTTP 301, HTTPS, Search Console Change of Address |
| Site Status | The original site once had tens of thousands of indexed pages; after migration, only single-digit pages remained |
| Core Dependencies | Google Search Console, web server redirects, sitemap |
| Risk Level | High |
This incident proves that a domain is not a shell but a carrier of search trust
The core lesson from this postmortem is straightforward: the site owner sold the old domain, then moved the entire site to a new domain without keeping the old site online or creating a migration path. The code, content, and structure remained, yet most search visibility still disappeared.
The problem was not in the frontend or deployment stack. It was in how search engines determine site identity. To Google, the disappearance of the old domain and the appearance of a new one does not automatically mean the same website has moved. It looks more like one old site died and one new site was born.
How search engines interpret this switch
The old domain carried more than just an entry point. It held historical indexation, backlink relationships, crawl stability, and topical trust. When the old domain went offline immediately, those signals could not be inherited naturally. The new domain had to rebuild everything from scratch.
# Example of an incorrect migration path
old-domain.com -> taken offline directly # The old domain disappears, so search engines cannot track the move
new-domain.com -> relaunched # The new domain is treated as a new siteThis example shows the key issue: without redirects and a formal site-move signal, search engines will not infer that the two domains share the same site identity.
The collapse in indexation was essentially caused by a broken indexing relationship
The symptoms described in the article are highly typical: in Google Search Console, indexed pages dropped from tens of thousands to single digits, while organic traffic nearly vanished. This was not a normal fluctuation. It was the chain reaction caused by breaking the indexed entity itself.
At this stage, many site owners mistakenly blame an algorithm update. The real problem, however, is that the site’s lifecycle was manually interrupted. When search engines face uncertainty, they default to a conservative strategy: remove invalid old pages first, then cautiously evaluate the new domain.
What usually happens after the old domain disappears
- Old URLs start returning invalid responses or become inaccessible.
- Original pages are gradually removed from the index.
- External links lose their landing targets, weakening signal transfer.
- The new domain enters a fresh evaluation period because it lacks history.
migration_effect = {
"old_domain": "carrier of historical authority", # The old domain is tied to historical trust
"redirect_missing": True, # No 301 redirects means signals cannot be transferred
"new_domain": "recognized as a new site" # The new domain must rebuild trust
}
if migration_effect["redirect_missing"]:
print("Indexation, backlinks, and authority are unlikely to transfer smoothly") # Core consequenceThis code summarizes the failed migration chain: without a 301 redirect, you are effectively giving up the inheritance relationship.
Unchanged content cannot replace domain-level trust transfer
One common misconception in the original article deserves emphasis: if the content, structure, and pages did not change, why did SEO still collapse? The answer is that search rankings have never depended only on the content files themselves. Search engines also evaluate the identity under which that content is published.
In search systems, a domain acts like a long-term trust account. An old domain with age, backlinks, and a stable crawl history starts from a very different trust level than a newly activated domain, even if the pages are identical.
Why a new domain struggles to gain traction immediately
First, a new domain has no history. Second, if the content is largely aggregated, automated, or template-driven, losing the old domain’s trust signals will expose quality weaknesses very quickly. The old site may have survived not because the content was inherently strong, but because its historical signals were strong enough to support it.
server {
listen 80;
server_name old-domain.com;
location / {
return 301 https://new-domain.com$request_uri; # Permanently redirect each old page to its corresponding new path
}
}This Nginx configuration shows the most basic migration action: make every old URL continuously pass its signals to the corresponding new URL.
A correct domain migration plan is actually a practical, executable process
An effective solution is not mysterious. The core principle is simple: keep the old domain as a bridge. In other words, do not let the old site disappear suddenly. Give search engines a migration process that is continuous, verifiable, and crawlable.
At a minimum, you should complete three tasks: page-to-page 301 redirects, keep the old domain active for several months or longer, and submit a Change of Address signal in Google Search Console. If the site is large, you should also update the sitemap, canonical tags, and internal links.
A safer migration checklist
# Minimum viable checklist for domain migration
1. Keep control of the old domain # Do not sell it or shut it down first
2. Configure one-to-one 301 redirects # Do not redirect everything to the homepage
3. Submit the new site's sitemap.xml # Speed up discovery of new URLs
4. Submit a Change of Address in Search Console # Explicitly notify Google
5. Continuously monitor indexation, crawling, and error pages # Evaluate migration qualityThe value of this checklist is that it turns a “site switch” into a continuous migration process rather than an instant cutover.
This postmortem is especially relevant for indie developers
Many indie developers focus on code, features, and shipping speed, but underestimate the asset value of a domain in the search ecosystem. Once a site depends on organic traffic, the domain is no longer just a brand address. It becomes a long-term SEO account.
Selling the old domain and then switching to a new one is effectively selling part of your visibility assets. Without a migration plan, that decision can wipe out indexation, backlinks, and historical trust at the same time. The recovery cost is often far higher than the revenue from the domain sale.
FAQ
When moving to a new domain, why can’t I just shut down the old one?
Because the old domain carries historical indexation and backlink signals. If you shut it down directly, search engines treat the old site as gone rather than moved, so authority and indexation cannot be inherited reliably.
Why must 301 redirects be one-to-one instead of sending everything to the homepage?
One-to-one 301 redirects preserve topical relevance and backlink value at the page level as much as possible. Redirecting everything to the homepage loses URL-level semantics, results in a lower-quality migration, and makes search engines more likely to ignore the redirect pattern.
How long should I keep the old domain to stay relatively safe?
In most cases, you should keep it for at least several months and continue until major pages have completed crawling, indexation, and traffic transfer. For large or high-value sites, keeping it for 6 to 12 months is safer.
AI Readability Summary
This article analyzes a real-world site migration failure and explains why selling an old domain before switching to a new one can nearly erase indexation, backlinks, and ranking signals. It also provides practical steps, including 301 redirects, Search Console Change of Address, and a transition period that keeps the old domain active.