Website domain change: why it is the most underestimated SEO disaster
In 2023, one major media project lost 90% of its organic traffic after moving to a new domain–from 25,000 clicks a day to 2,000. The cause was neither penalties nor competitor interference. More than 513,000 pages became stuck with the status “crawled, not indexed,” the old domain continued to be crawled in parallel with the new one, and thousands of old urls led to the wrong pages on the new site, generating soft 404s. A routine oversight at the technical stage that cost the site nine out of ten visitors.
I regularly see domain changes treated as a minor technical task: “we’ll set up a redirect, wait a week, and everything will merge by itself.” It won’t. Below is what you need to know before, not after, the move.
In brief, if you don’t have time to read everything:
- A traffic drop during a migration is normal, not a sign of an error. The question is its scale and recovery time.
- The main cause of catastrophic losses is redirects leading to the homepage instead of exact page equivalents.
- Google and Yandex require different actions: the “Change of address” and “Переезд сайта” tools work according to different rules.
- The new domain must be checked for a clean history before purchase, not after problems emerge.
- The old domain must not be taken offline immediately–redirects continue to pass value long after the migration is formally complete.
When a domain change is actually justified
Before discussing the technical side, it is worth stating an uncomfortable fact: in most cases, changing the domain is not a solution to the problem but a way to postpone it. If the site is under a filter, a new address will not remove the filter by itself–the reason the search engine penalized the site remains in place and moves with the content.
The real reasons for a migration 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 simply unsuitable for scaling the business. If none of these reasons apply and the domain is just “not very attractive,” leave it alone. The domain’s age and accumulated trust are worth more than aesthetics.
How much traffic is actually lost
This is where scary stories and figures should be separated. In 2023, Search Engine Journal analyzed 171 website migrations: on average, traffic according to third-party analytics services recovered in 229 days, while returning to the full pre-migration level took 523 days. At the same time, 17% of the sites in the sample had not regained their previous volume even after 1000 days; in an earlier similar study, the share that failed to recover reached 42%.
There is also a much more optimistic benchmark: Local SEO Guide gives a range of 30–60 days for technically clean migrations without additional errors. The same Search Engine Journal study also records the lower bound–where the migration took place without a simultaneous redesign or change in url structure, the minimum recovery time was 19–33 days. The difference between three weeks and 523 days is the difference between “the migration was uneventful” and “the migration destroyed quarterly performance.” The formula is simple: the fewer things that change at the same time as the domain–url structure, templates, content–the closer the result is to the optimistic scenario.
How to check a new domain before purchase
A domain with a history may carry someone else’s problems–penalties, toxic links, and a reputation with email and anti-spam services. The check takes an hour and can save you from a months-long struggle with the consequences.
Wayback Machine (archive.org) is the starting point: snapshots of the site from previous years immediately show whether a casino site, doorway page, or something worse was hosted on this domain before. WHOIS services (nic.ru, reg.ru) show the registration date and ownership change history. Once the domain is verified, Google Search Console opens the “Manual actions” section, showing whether Google penalized the domain’s previous owner. Яндекс.Вебмастер has a similar “Security and violations” section. Ahrefs Webmaster Tools, available for free after verification, shows incoming links: a spammy or irrelevant backlink profile drags rankings down regardless of the quality of the content you put on the domain. Bertal.ru checks how the server responds to bots and catches redirect loops – a common error when server settings conflict.
For convenience, here is a summary of what to check and where:
Tool
What it checks
Free plan limit
Wayback Machine
visual history of content, the domain’s previous subject matter
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
incoming links, profile toxicity
free after verification
Bertal.ru
server response to bots, redirect loops
up to 300 requests to one host per day, response up to 4 МБ
It is also worth checking the domain for a trademark – if its name contains a word registered as another company’s brand, the move may end not with a traffic drop but with a legal dispute. Five minutes in the Роспатент registry is cheaper than dealing with the matter after the fact.
Technical checklist: redirects, sitemap, canonical
A domain change is about making sure the search engine clearly understands that it is dealing with the same site, just at a new address. The slightest lack of synchronization breaks this logic, and this is where most losses occur.
The key rule is a page-by-page 301 redirect. Each page on the old site should lead to its exact equivalent on the new one, not to the homepage. Search engines interpret mass redirects to the homepage as soft 404s – the value is wiped out, traffic to specific pages disappears, and this is exactly the error that killed 90% of the traffic in the example at the beginning of the article.
Next on the list: a new sitemap.xml with addresses on the new domain, self-referencing canonical tags, updated Schema.org structured data – in the Product, Organization, and LocalBusiness blocks, old urls, logos, and images often remain if they are not checked separately. One separate tactical measure is to keep the old sitemap.xml (with old urls) accessible on the old domain for a short time – this helps crawlers go through the previous addresses faster and discover the redirects. In Yandex.Webmaster, the old sitemap can also be submitted for recrawling, 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 migration. A simultaneous redesign, structural change, or rewriting of texts is no longer one migration but two overlapping ones, making the outcome unpredictable.
Two more things rarely make it onto checklists but regularly undermine the result. First, internal links should lead directly to the new domain, not through a redirect from the old one: if, after the migration, page A links to page B through the old address, every click is an unnecessary hop that slows the bot's crawl and dilutes the value. Second, redirect chains: old domain → intermediate domain → new domain – search engines cut the value at every link, and sometimes simply stop following the chain after several hops. Both issues can be checked with crawlers such as Screaming Frog or Netpeak Spider – crawling the entire list of urls on the old domain before and after the migration immediately shows where a redirect leads to the wrong place or loops.
Specific considerations for online stores and local retail
The same redirect rules apply to product and category pages as to the rest of the site, but the cost of an error is higher: each product url usually already has accumulated user behavior signals – time on page, browsing depth, returns to the search results. This is especially sensitive for Yandex – its algorithm relies heavily on behavioral signals (CTR, time on site, bounce rate), and a new domain starts with no interaction history. During a migration, this history is not transferred automatically, even if the redirect is configured perfectly. The search engine sees the new url as a new page and reassesses it from scratch at first, without taking its past achievements into account. Hence the temporary drop in rankings even after a technically flawless migration – this is an expected part of the process, not a sign that something has broken.
It is also worth checking review structured data separately – if product ratings are collected through Schema.org AggregateRating and Review, when changing the domain you need to make sure that the markup was transferred along with the reviews themselves, rather than remaining linked to the old url of the review author or product. The break is not immediately noticeable – stars in the search results may disappear several weeks later, when the search engine recalculates the data on the new domain.
Google and Yandex: different rules of the game
In Google Search Console, the migration is handled through the “Change of Address” tool. One detail that is rarely mentioned: you need to verify ownership of all versions of the old domain – with www, without www, all subdomains, even unused ones. A forgotten domain version means forgotten signals that are not transferred anywhere. Formally, the tool works for 180 days, but server redirects should be kept much longer – at least a year.
In Yandex.Webmaster, the logic is different: the “Site Move” tool is used, and its requirements are stricter – both domains must be verified under 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 within 200 ms and definitely no more than 10 seconds. Submitting requests in both panels simultaneously is not excessive but a mandatory part of the plan: one search engine will not transfer signals on behalf of the other.
A separate point about 1C-Bitrix
For Bitrix sites, changing the domain adds specifics that general SEO migration guides usually do not mention. After the move, you must clear the cache – bitrix/cache and bitrix/managed_cache, otherwise the public-facing part will continue serving pages with old absolute links for some time, and bots will discover a domain that no longer exists.
The second point is the SEF URL rules in urlrewrite.php. During migration, they sometimes lose their order or are partially overwritten, causing part of the catalog to return 404s even though the server redirects are configured perfectly. Diagnosing this without direct access to the rules file is almost impossible – the symptom looks like an indexing issue, while the cause lies in the CMS configuration.
The third point is the settings in Settings → Product Settings → Sites. The “Domain name” and “Server URL” fields must be updated manually – if the old domain is left there, the system will continue generating incorrect canonicals, sitemaps, and service links, even if all other code already points to the new address. The fourth is that when files are migrated as an archive (via restore.php or FTP), the .access.php file responsible for user group permissions is often lost or corrupted. The result is that the site suddenly starts returning 403 Forbidden where everything worked before the move.
If the site is hosted on Bitrix24 Hosting or Bitrix.Domains, there is a fifth point – configuring the primary mirror at the platform level. Changing the linked domain there is done through the hosting panel, not only through configuration files, and if you change the domain in one place while forgetting the other, the site may continue responding at two addresses simultaneously – which is a direct path to duplicates and diluted authority between the old and new URL.
Maps and reviews: the most fragile point
This is where an error can arise that cannot be fixed after the fact. Google Business Profile and Yandex.Business are linked to the business listing, not the website domain. Only the URL in the existing profile should be changed – a new listing must not be created. If, through inattention or on a “specialist’s” advice, a new listing is created instead of editing the old one, the entire review history and map rankings are reset with no possibility of recovery. For local retail or delivery services, this is often more painful than a drop in organic rankings: reviews accumulate over years but are lost with a single click.
Even careful editing of the URL in an existing Google Business Profile does not go unnoticed: this change may send the profile for re-review, which can take up to 3 days. During this period, the profile may temporarily drop out of the local pack – this window should be planned for in advance rather than followed by surprise at a post-migration decline in calls from Maps.
External factors: links, advertising, email campaigns
Redirects solve the issue with the search engine, but not with platforms that link to the website directly. If the project has valuable backlinks – from city media outlets, industry directories, or partner websites – it is worth contacting their owners where possible and asking them to change the link directly to the new address. A redirect technically passes on 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 on the list are advertising campaigns in Yandex.Direct and Google Ads: they should be paused at the moment the DNS is switched, rather than simply having the links changed on the fly – otherwise some ads will lead to broken redirects for a while, affecting both loading speed and ad quality score, while in Google Ads this may result in moderation rejection. Campaigns can be relaunched once the landing pages on the new domain return 200 OK and work fully. The same applies to email campaigns and employee email signatures – a minor detail that surprisingly often remains forgotten for weeks.
Monitoring after the migration
During the first 2–4 weeks, Search Console and Yandex.Webmaster should show a cross-over graph: impressions for the old domain fall while those for the new domain rise. A sharp increase in the “Crawled – currently not indexed” status or mass soft 404s is a direct signal of a problem with the redirect map, and it should be addressed within days, not weeks.
By weeks 8–12, the basic position stabilization phase begins. It is useful to check the server logs: if Google and Yandex robots continue actively crawling the old domain two or three months later, this means unresolved URLs remain somewhere in the redirect chain or external links, continuing to point to the previous URL.
A separate question every client asks is how long to keep this two-domain setup at all. The guidelines are as follows:
Item
Minimum period
Server-side 301 redirects
12 months
Payment and renewal of the old domain
indefinitely, if the budget allows
The “Change of Address” tool in Search Console
formally 180 days, but it does not affect redirects
Monitoring crawls of the old domain in the logs
until requests drop to zero
Disabling the old domain before the required period ends means cutting off the transfer of link equity halfway through a process that is already stretched over months.
Frequently asked questions
How much traffic is lost when changing a website's domain? According to Search Engine Journal, with a technically correct migration, the average recovery time ranges from 30 days to several months. With errors in redirects and indexing, losses can reach 80–90% and may not recover for years.
How do you notify Google and Yandex about a domain change? In Google Search Console – through the “Change of Address” tool, with ownership verification for all versions of the old domain. In Yandex.Webmaster – through the “Site Move” tool, provided the content on both domains is identical.
Does the old domain need to be kept after the migration?Yes, for at least a year, and preferably indefinitely. Redirects continue to pass authority even after the webmaster panel’s migration tool has formally completed its work.
Can changing the domain lift a search engine penalty?On its own – no. The cause of the penalty remains in the content or backlink profile and moves with the site to the new domain if it is not addressed separately.
What happens to Google Business Profile reviews when the domain changes?Nothing, if you only change the URL in the existing profile. If you create a new profile instead of editing the old one, the review history and map rankings are lost with no possibility of recovery.
Conclusion
Domain changes do not forgive multitasking. One redesign, one change to the URL structure, one forgotten domain version in Search Console – and instead of a technical formality, you end up with a six-month investigation into where the traffic went. If the decision to migrate has been made – allow at least as much time for preparation and monitoring as for the technical migration itself, and do not change 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
- Яндекс.Вебмастер. Moving a website to a new domain name –https://yandex.ru/support/webmaster/ru/yandex-indexing/moving-site
