Changing a website domain: why it is the most underestimated SEO catastrophe
One major media project in 2023 lost 90% of its organic traffic after moving to a new domain – from 25,000 clicks per day to 2,000. The reason is not sanctions or competitor machinations. More than 513,000 pages got stuck in the 'crawled, not indexed' status, the old domain continued to be crawled in parallel with the new one, and thousands of old URLs led to the wrong pages of the new site, generating soft 404s. Ordinary carelessness at the technical stage, which cost nine out of ten visitors.
I regularly see people treating a domain change as a technical trifle: 'we'll set up a redirect, wait a week, and everything will merge on its own.' It won't. Below — what you should know before, not after, the move.
In short, if you don't have time to read everything:
- A traffic drop during a move — that is normal, not a sign of an error. The question is the scale and recovery time.
- The main cause of catastrophic losses — redirects not to exact page equivalents, but to the homepage.
- Google and Yandex require different actions: the 'Change of address' tool and 'Site move' work by different rules.
- A new domain should be checked for cleanliness before purchase, not after problems are discovered.
- The old domain cannot be turned off immediately — redirects continue to pass weight long after the formal completion of the move.
When a domain change is actually justified
Before diving into the technical details, it's worth stating an uncomfortable truth: in most cases, a domain change is not a solution to a problem but a way to postpone it. If a site is under a filter, a new address by itself does not remove the filter — the reason the search engine penalized the site remains in place and moves along with the content.
Real reasons for a move are usually different: rebranding, merging several projects into one, a legal dispute over a trademark in the domain name, or a situation where the old domain is physically unsuitable for scaling the business. If none of these reasons exist and the domain is simply 'not very pretty' — leave it alone. The age and accumulated trust of a domain are worth more than aesthetics.
How much traffic is actually lost
Here it is worth separating horror stories from numbers. In 2023, Search Engine Journal analyzed 171 website migrations: on average, traffic according to third-party analytics services recovered in 229 days, and to the full pre-migration level — in 523 days. At the same time, 17% of the sites in the sample did not return to their previous volume even after 1,000 days; in an earlier similar study, the share of those that did not recover reached 42%.
There is also a much more optimistic benchmark: Local SEO Guide cites a range of 30–60 days for technically clean moves without accompanying errors. The same Search Engine Journal study also records a lower bound — where the move went without a parallel redesign and URL structure changes, minimum recovery times fell within 19–33 days. The difference between three weeks and 523 days — is the difference between 'the move was boring' and 'the move killed quarterly performance.' The formula is simple: the less that changes simultaneously with the domain — URL structure, templates, content — the closer the result is to the optimistic scenario.
How to check a new domain before buying
A domain with a history can drag along other people's problems – penalties, toxic links, reputation with email and anti-spam services. Checking takes an hour and saves from months of dealing with consequences.
Wayback Machine (archive.org) is the starting point: site snapshots from past years immediately show whether a casino site, doorway, or something worse used to sit on this domain. WHOIS services (nic.ru, reg.ru) show the registration date and ownership change history. Google Search Console after domain verification opens the 'Manual actions' section – there you can see whether Google penalized the previous domain owner. Yandex.Webmaster provides a similar section 'Security and violations'. Ahrefs Webmaster Tools, available free after verification, shows inbound links: a spammy or irrelevant backlink profile pulls you down regardless of the quality of content you put on this domain. Bertal.ru checks how the server responds to robots and catches redirect loops – a common error when server settings conflict.
For convenience – a summary of what and where to look:
Tool
What it checks
Free plan limit
Wayback Machine
visual content history, past domain topic
no strict limits for manual viewing
nic.ru / reg.ru
WHOIS: registration date, ownership history
no limits
Google Search Console
manual penalties from Google
domain verification required
Yandex.Webmaster
penalties and violations, server response speed
domain verification required
Ahrefs Webmaster Tools
inbound links, profile toxicity
free after verification
Bertal.ru
server response to robots, redirect loops
up to 300 requests to one host per day, response up to 4 MB
Additionally, it's worth checking the domain for a trademark – if the name contains a word registered as a brand by another company, the move may end not in a traffic drop but in a lawsuit. Five minutes in the Rospatent registry are cheaper than post-factum litigation.
Technical checklist: redirects, sitemap, canonical
A domain change is about making the search engine unambiguously understand: it's the same site, just at a new address. The slightest mismatch breaks this logic, and that's where most losses occur.
The key rule is a page-by-page 301 redirect. Every page of the old site should lead to its exact counterpart on the new one, not to the homepage. Mass redirects to the homepage are read by search engines as soft 404s – the weight is zeroed out, traffic to specific pages disappears, and that is exactly the mistake that killed 90% of traffic in the example at the beginning of the article.
Next on the list: a new sitemap.xml with the new domain's addresses, canonical tags pointing to themselves, updated Schema.org markup – in Product, Organization, and LocalBusiness blocks, old URLs, logos, and images often remain if not checked separately. A separate tactical trick: it's worth keeping the old sitemap.xml (with old URLs) accessible on the old domain for a short time – this way crawlers crawl the old addresses faster and discover the redirects. In Yandex Webmaster, the old map can additionally be submitted for re-crawling, with a limit of up to 150 URLs per day. And the final point that is somehow always forgotten: the content on the old and new domains must be identical at the time of the move. Simultaneous redesign, restructuring, or rewriting texts is no longer one migration but two overlapping ones, and the result is unpredictable.
Two more things that rarely make it into checklists but regularly ruin the picture. First, internal links should lead directly to the new domain, not through a redirect from the old one: if after the move page A links to page B via the old address, each transition is an extra hop that slows down the crawler and dilutes the weight. Second, redirect chains: old domain → intermediate → new – search engines cut weight at each link, and sometimes simply stop following the chain after a few hops. Both points can be checked with crawlers like Screaming Frog or Netpeak Spider – running through the entire list of old domain URLs before and after the move immediately shows where a redirect goes the wrong way or loops.
Specifics for online stores and local retail
For product cards and categories, the same redirect rules apply as for the rest of the site, but the cost of a mistake is higher: each product URL usually already has accumulated user behavior signals – time on page, scroll depth, returns to search results. This is especially sensitive for Yandex – its algorithm relies heavily on user behavior signals (CTR, time on site, bounce rate), and a new domain starts with zero interaction history. During a move, this history is not transferred automatically, even if the redirect is set up perfectly. The search engine sees the new URL as a new page and initially evaluates it from scratch, without any discount for past merits. Hence the temporary drop in rankings even with a technically flawless move – this is an expected part of the process, not a sign that something is broken.
Separately, it's worth checking the review markup – if product ratings are collected via Schema.org AggregateRating and Review, when changing the domain you need to make sure the markup moved along with the reviews themselves, and did not remain referencing the old URL of the review author or product. The break here is not immediately noticeable – the stars in the search results may disappear after a few weeks, when the search engine recalculates the data on the new domain.
Google and Yandex: different rules of the game
In Google Search Console, the move is handled through the 'Change of Address' tool. A nuance that is rarely mentioned: you need to verify ownership of all variants of the old domain – with www, without www, all subdomains, even unused ones. A forgotten domain variant means forgotten signals that are not transferred anywhere. Formally, the tool works for 180 days, but server redirects need to be kept much longer – at least a year.
In Yandex.Webmaster, the logic is different: the 'Site Move' tool is used, and its condition is stricter – both domains must be verified in the same account, the content on the old and new domains must be identical at the time of the move, both robots.txt files must allow indexing, and the server must respond quickly, ideally under 200 ms and certainly no longer than 10 seconds. Submitting requests to both panels simultaneously is not redundancy but a mandatory part of the plan: one search engine will not pull signals for another.
A separate conversation about 1C-Bitrix
For Bitrix sites, changing a domain adds specifics that general SEO migration guides usually do not mention. After the move, be sure to clear the cache – bitrix/cache and bitrix/managed_cache, otherwise the public part will continue to serve pages with old absolute links for some time, and robots will find a domain that no longer exists.
The second point is the URL rewrite rules in urlrewrite.php. During migration, they sometimes lose order or are partially overwritten, and then part of the catalog starts returning 404, even though the server redirects are configured absolutely correctly. Diagnosing this without direct access to the rules file is almost impossible – the symptom looks like an indexing problem, but the cause lies in the CMS configuration.
The third point is the settings in the section Settings → Product Settings → Sites. The 'Domain name' and 'Server URL' fields must be updated manually – if you leave the old domain there, the system will continue to generate incorrect canonical, sitemap, and service links, even if all the rest of the code already points to the new address. The fourth is that when transferring files as an archive (via restore.php or FTP), the .access.php file, which is responsible for user group access rights, is often lost or damaged. The result is that the site suddenly starts returning 403 Forbidden where everything worked before the transfer.
If the site is hosted on Bitrix24 or Bitrix.Domains hosting, a fifth point is added – setting up the main mirror at the platform level itself. Changing the bound domain there is done through the hosting panel, not just through configuration files, and if you change the domain in one place while forgetting about another, the site may continue to respond on two addresses simultaneously – and that is a direct path to duplicates and dilution of weight between the old and new URLs.
Maps and reviews: the most fragile spot
Here an error occurs that cannot be fixed after the fact. Google Business Profile and Yandex.Business are tied to the organization's listing, not to the site's domain. Only the URL in the existing profile changes – a new listing cannot be created. If, due to carelessness or on the advice of a 'specialist', a new listing is created instead of editing the old one, the entire review history and map positions are reset with no way to recover. For local retail or a delivery service, this is often more painful than a drop in organic positions: reviews take years to accumulate and are lost in one click.
Even a careful URL edit in an existing Google Business Profile does not go unnoticed: such a change can send the listing to re-moderation, which takes up to 3 days. For this period, the profile risks temporarily dropping out of the local pack – so it is worth planning this window in advance rather than being surprised afterwards by a drop in calls from the listing.
External factors: links, advertising, email campaigns
Redirects solve the issue with search engines, but not with platforms that link directly to the site. If the project has significant external links – from city media, industry directories, partner sites – you should, where possible, contact their owners and ask them to change the link directly to the new address. A redirect technically passes link equity, but a direct link to the current domain is more reliable and does not depend on how many more years you plan to keep paying for the old domain.
Next in line are ad campaigns in Yandex.Direct and Google Ads: they should be paused at the exact moment of DNS switching, rather than just changing links on the fly – otherwise some ads will temporarily point to broken redirects, which hurts both load speed and Quality Score, and may get disapproved by moderation in Google Ads. Campaigns can be restarted once the landing pages on the new domain already return 200 OK and are fully functional. The same goes for email newsletters and employee email signatures – a small detail that surprisingly often goes overlooked for weeks.
Post-migration monitoring
For the first 2–4 weeks, Search Console and Yandex.Webmaster should show a cross-over trend: impressions for the old domain decline while those for the new one grow. A sharp increase in "Crawled – currently not indexed" status or mass soft 404s is a direct signal of a problem with the redirect map, and you should respond within days, not weeks.
By weeks 8–12, positions enter the phase of basic stabilization. It is useful to check server logs: if Google and Yandex bots continue to actively crawl the old domain after two to three months, it means some unresolved addresses in the redirect chain or external links still point to the previous URL.
One question every client asks is how long to even keep this two-domain setup. Here are the benchmarks:
Item
Minimum term
301 redirects on the server
12 months
Payment and renewal of the old domain
indefinitely, if budget allows
The Change of Address tool in Search Console
formally 180 days, but does not affect redirects
Monitoring old domain crawling in logs
until requests subside to zero
Disabling the old domain ahead of time means cutting off link equity transfer in the middle of a process that spans months anyway.
Frequently Asked Questions
How much traffic is lost when changing a website domain?According to Search Engine Journal, with a technically correct migration, the average recovery time is from 30 days to several months. With errors in redirects and indexing, losses can reach 80–90% and take years to recover.
How to notify Google and Yandex about a domain change?In Google Search Console – through the Change of Address tool with verification of ownership of all variants of the old domain. In Yandex.Webmaster – through the Site Move tool, provided the content is identical on both domains.
Is it necessary to keep the old domain after the migration? Yes, at least a year, preferably indefinitely. Redirects continue to pass weight even after the migration tool in the webmaster panel formally completes its work.
Can changing a domain remove search engine penalties? By itself, no. The cause of the penalties remains in the content or backlink profile and moves with the site to the new domain unless it is addressed separately.
What happens to reviews in Google Business Profile when changing a domain? Nothing, if you only change the URL in an existing listing. If you create a new listing instead of editing the old one, the review history and map rankings are lost with no way to recover.
Conclusion
Changing a domain does not forgive multitasking. One redesign, one URL structure change, one forgotten domain version in Search Console – and instead of a technical formality, you get a six-month investigation into where the traffic went. If the decision to move is made, allocate as much time for preparation and monitoring as for the technical migration itself, and do not touch anything unnecessary in the first weeks after launch.
Sources
- Search Engine Journal (2023). How Long Should An SEO Migration Take? – https://www.searchenginejournal.com/study-how-long-should-seo-migration-take/492050/
- Local SEO Guide. How Long Does It Take To Recover From A Domain Migration? – https://www.localseoguide.com/how-long-does-it-take-to-recover-from-a-domain-migration/
- Search Engine Land (2023). How soft 404s and indexing issues caused a 90% traffic collapse – https://searchengineland.com/soft-404s-indexing-issues-traffic-collapse-477116
- Google Search Central. Site Moves and Migrations – https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
- Яндекс.Вебмастер. Site move to a new domain name – https://yandex.ru/support/webmaster/ru/yandex-indexing/moving-site
