Website Domain Change: Why It’s the Most Underrated SEO Disaster
One major media project lost 90% of organic traffic in 2023 after moving to a new domain, from 25,000 clicks a day to 2,000. The reason is not sanctions and not in the machinations of competitors. More than 513,000 pages hovered in “crawled, unindexed” status, the old domain continued to crawl in parallel with the new one, and thousands of old URLs led to the wrong pages of the new site, generating a soft 404. The usual inattention at the technical stage, which cost nine out of ten visitors.
I regularly see how to change the domain is treated as a technical trifle: “let’s put a redirect, a week wait, everything will stick together.” It won't stick together. Below is what you should know before, not after, moving.
If you don’t have time to read everything:
Traffic dip when moving is the norm, not a sign of error. The scale and timing of the recovery.
The main cause of catastrophic losses is redirects not to exact analogues of pages, but to the main one.
Google and Yandex require different actions: the tool “Change of address” and “Move the site” work according to different rules.
A new domain should be checked for cleanliness before buying, not after problems have been discovered.
The old domain can not be turned off immediately - redirects transfer weight long after the formal completion of the move.
When a domain change is justified
Before disassembling the technique, it is worth saying an uncomfortable thing: in most cases, changing a domain is not a solution to the problem, but a way to postpone it. If the site is under a filter, the filter itself does not remove the new address – the reason why the search engine punished the site remains in place and moves along with the content.
The real reasons for moving are usually different: rebranding, combining several projects into one, litigation over a trademark in a domain name, or a situation where an old domain is not physically suitable for scaling a business. If none of these reasons, and the domain is just “not very beautiful” – leave it alone. Age and accumulated domain trust are more expensive than aesthetics.
How Much Traffic Is Really Lost
Here it is worth dividing horror stories and numbers. Search Engine Journal in 2023 analyzed 171 migration sites: on average, traffic on third-party analytics services recovered in 229 days, and to the full pre-migration level – in 523 days. At the same time, 17% of sites from the sample did not return the previous volume even after 1000 days, in an earlier similar study, the share of those that did not recover reached 42%.
Local SEO Guide calls the range of 30-60 days for technically clean moves without the accompanying errors. The same study by Search Engine Journal captures the lower limit – where the move did not involve a parallel redesign and a change in the structure of the url, the minimum recovery time was 19-33 days. The difference between three weeks and 523 days is the difference between moving was boring and moving killed quarterly numbers. The formula is simple: the less changes simultaneously with the domain – the structure of the URL, templates, content – the closer the result to the optimistic scenario.
How to check a new domain before buying
A domain with a history can cause other people’s problems – sanctions, toxic links, reputation for email and anti-spam services. The inspection takes an hour, and saves from months of struggle with the consequences.
The Wayback Machine (archive.org) is the starting point: photos of the site from past years immediately show whether the casino site used to sit on this domain, or what was worse. WHOIS services (nic.ru, reg.ru) show the date of registration and the history of the change of owners. Google Search Console, after domain verification, opens the “Manual Measures” section to see if Google penalized the previous domain owner. Yandex. The webmaster gives a similar section "Security and Violations". Ahrefs Webmaster Tools, available for free after verification, shows inbound links: a spammy or irrelevant link profile pulls down regardless of the quality of content you put on that domain. Bertal.ru checks how the server responds to robots, and catches cyclic redirects – a common error in the conflict of settings on the server.
For convenience - a summary of what and where to watch:
Tool. | Checking. | Free fare limit |
|---|---|---|
Wayback Machine | visual history of content, past domain themes | without strict restrictions for manual viewing |
nic.ru / reg.ru
WHOIS: date of registration, history of owners
limitless
Google Search Console
manual sanctions from Google
Domain verification is required
Yandex. webmaster
sanctions and violations, server response speed
Domain verification is required
Ahrefs Webmaster Tools
Inbound links, profile toxicity
free of charge after verification
Bertal.ru
server response to robots, cyclic redirects
up to 300 requests per host per day, up to 4MB
Additionally, it is worth checking the domain for a trademark - if the name has a word registered as a brand by another company, the move may end not with a traffic drawdown, but with a legal dispute. Five minutes in the register of Rospatent is cheaper than the proceedings after the fact.
Technical checklist: redirects, sitemap, canonical
Changing the domain is about the search engine to clearly understand: it is the same site, just a new address. The slightest desynchronization breaks that logic, and that’s where most losses occur.
The key rule is a page-by-page 301 redirect. Each page of the old site should lead to the exact analogue on the new one, not the main one. Mass redirects to the main search engines are read as soft 404 – the weight is zeroed, traffic to specific pages is lost, and this is exactly the mistake that killed 90% of traffic in the example from the beginning of the article.
Further down the list: a new sitemap.xml map with the addresses of the already new domain, canonical tags pointing to themselves, an updated Schema.org micromarkup – in the Product, Organization and LocalBusiness blocks, old url, logos and images often remain, unless they are checked separately. Separate tactical technique: the old sitemap.xml (with old url) should be left available for a short time on the old domain - so crawlers quickly bypass the old addresses and detect redirects. Yandex. The old card can be additionally sent to the webmaster for bypass, with a limit of up to 150 url per day. And the final point, which for some reason is always forgotten: the content on the old and new domains should be identical at the time of moving. Simultaneous redesign, change of structure or rewriting of texts is not one migration, but two overlapping, and the result is unpredictable.
Two more things that rarely make it onto checklists but regularly spoil the picture. First, internal links should lead directly to the new domain, and not through a redirect from the old: if after moving the page A links to page B through the old address, each transition is an extra jump that slows the robot’s bypass and blurs the weight. The second is the chain of redirects: old domain → intermediate → new – search engines cut the weight at each link, and sometimes simply stop following the chain after a few jumps. You can check both moments with crawlers like Screaming Frog or Netpeak Spider – a run through the entire url list of the old domain before and after the move immediately shows where the redirect leads to the wrong place or loops.
Features 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 error is higher: each product url usually already has accumulated behavioral factors - time on the page, depth of viewing, returns to the results. This is especially sensitive for Yandex – its algorithm relies heavily on behavioral signals (CTR, time on the site, bounce rate), and the new domain starts with zero interaction history. When moving, this story does not automatically carry over, even if the redirect is set up perfectly. The search engine sees the new URL as a new page and at first evaluates it anew, without a discount on past merit. Hence, a temporary drawdown of positions, even with a technically flawless move, is an expected part of the process, not a signal that something has broken.
Separately, it is worth checking the micromarkup of reviews - if the product ratings are collected through Schema.org AggregateRating and Review, when changing the domain, you need to make sure that the markup has moved along with the reviews themselves, and not left to refer to the old url of the review author or product. The gap here is not immediately noticeable - the stars in the 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 made through the Change of Address tool. Nuance, which is rarely spoken: you need to confirm the rights to all versions of the old domain - with www, without www, all subdomains, even unused ones. Forgotten domains are 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.
Yandex. The webmaster’s logic is different: the tool “Move the site”, and the condition for it is tougher – both domains are confirmed for one account, the content on the old and new should be identical at the time of moving, both robots.txt allow indexing, and the server responds quickly, ideally up to 200 ms and exactly no longer than 10 seconds. Applying to both panels at the same time is not redundancy, but a mandatory part of the plan: one search engine will not pull up signals for the other.
A separate conversation about 1C-Bitrix
For sites on Bitrix, domain change adds specificity that general SEO migration guides don’t usually mention. After moving, it is necessary to clean the cache - bitrix/cache and bitrix/managed cache, otherwise the public part continues to give pages with old absolute links for some time, and robots find a domain that no longer exists.
The second point is the CNC rules in urlrewrite.php. When transferred, they sometimes lose order or partially overwrite, and then part of the directory begins to give 404, although the server redirects are configured absolutely correctly. Diagnosing this without direct access to the rule file is almost impossible - the symptom looks like an indexing problem, and the cause sits in the CMS configuration.
The third point is the settings in the Settings section → Product settings → Sites. Domain Name and Server URL fields need to be updated manually – if you leave an 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 a new address. Fourth, when transferring files by archive (via restore.php or FTP), the .access.php file, which is responsible for access rights for user groups, is often lost or corrupted. The result is that the site suddenly begins to give 403 Forbidden where everything worked before the transfer.
If the site lives on hosting Bitrix24 or Bitrix. Domains, a fifth point is added – setting the main mirror at the platform level. Changing the associated domain there is done through the hosting panel, not just through the configuration files, and if you change the domain in one place, forgetting about the other, the site can continue to respond to two addresses at the same time – and this is a direct path to duplicates and blurring the weight between the old and new url.
Maps and reviews: the most fragile place
There is a mistake that cannot be corrected after the fact. Google Business Profile and Yandex. Businesses are tied to the card of the organization, not to the domain of the site. Only the URL in the existing profile changes – you cannot create a new card. If, due to inattention or on the advice of a “specialist”, a new card is created instead of editing the old one, the entire history of reviews and positions on the cards are zeroed without the possibility of recovery. For a local retail or delivery service, this is often more painful than a drawdown in organics: reviews accumulate for years, and are lost in one click.
Even careful editing of the url in the existing Google Business Profile profile does not go unnoticed: such a change can send the card for re-moderation, which takes up to 3 days. For this period, the profile risks temporarily falling out of the local package - it is worth laying this window in advance, and not be surprised after the fact by the drawdown of calls from cards.
External factors: links, advertising, mailings
Redirects solve the issue with the search engine, but not with sites that link to the site directly. If the project has significant external links - from the city media, industry directories, partner sites - if possible, you should write to their owners and ask them to change the link to the new address directly. The redirect technically conveys weight, but a direct link to the current domain is more reliable and doesn’t depend on how many years you plan to pay for the old domain.
Next on the list – advertising campaigns in Yandex. Directe and Google Ads: they should be stopped at the moment of switching DNS, and not just change links on the fly – otherwise some of the ads for some time will lead to broken redirects, which beats both the download speed and the quality of ads, and in Google Ads risks getting rejected by moderation. Campaigns can be re-launched when landing pages on a new domain already give 200 OK and are fully operational. The same goes for emails and signatures in employee emails—a trifle that surprisingly often gets forgotten for weeks.
Post-relocation monitoring
The first 2-4 weeks in Search Console and Yandex. The webmaster should observe a cross-graph: the impressions of the old domain are falling, the new one is growing. A sharp rise in “scanned, unindexed” status or a massive soft 404 is a direct signal of a redirect card problem, and it’s worth reacting to within days, not weeks.
By 8-12 weeks, the phase of basic stabilization of positions begins. It is useful to check server logs: if Google and Yandex robots continue to actively scan the old domain after two or three months, then somewhere in the redirect chain or in external links there are unresolved addresses that continue to point to the previous URL.
A separate question that each client asks is how much to keep this design of two domains at all. The benchmarks are:
Element | Minimum period |
|---|---|
301 redirects on the server | 12 months |
Payment and renewal of the old domain | Indefinitely if the budget allows |
Change of Address Tool in Search Console | 180 days but does not affect redirects |
Monitoring the scanning of the old domain in logs | until they reach the point of zero. |
Turning off an old domain ahead of schedule means cutting off weight transfer in the middle of a process that’s already stretched for months.
Frequently asked questions
How much traffic is lost when you change your website domain? According to the Search Engine Journal, with a technically correct move, the average recovery time is from 30 days to several months. For errors in redirects and indexation, losses can reach 80-90% and not recover for years.
How to tell Google and Yandex about a domain change? In Google Search Console – through the tool “Change Address” with confirmation of rights to all versions of the old domain. Yandex. Webmaster – through the tool “Move the site” provided identical content on both domains.
Do I need to keep an old domain after moving? Yes, at least a year, and preferably indefinitely. Redirects continue to transfer weight even after the relocation tool in the webmaster panel formally completes the work.
Can a domain change remove search engine sanctions? Not by itself. The reason for the sanctions remains in the content or link profile and moves with the site to the new domain, if it is not eliminated separately.
What happens to Google Business Profile reviews when you change your domain? Nothing if you only change the URL in your existing card. If you create a new card instead of editing the old one, the history of reviews and positions on the cards are lost without the possibility of recovery.
Conclusion
Changing a domain does not forgive multitasking. One redesign, one change in the URL structure, one forgotten version of the domain in Search Console – and instead of a technical formality, you get a six-month investigation where the traffic went. If the decision to move is made - lay on the preparation and monitoring time is not less than on the technical transfer itself, and do not touch anything superfluous 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
Yandex. Webmaster. Moving the site to a new domain name https://yandex.ru/support/webmaster/ru/yandex-indexing/moving-site



