Short answer
To keep your SEO value when you change domain, redirect every old URL to its new match with a one-step 301, use Search Console’s Change of Address tool once the redirects work, and keep the redirects for what Google generally advises: at least 1 year.
A company moves to a new brand name, buys the new domain and moves the site over at the weekend. The old domain is left idle; nobody touches it because “the new one is live anyway”. On Monday the old property in Search Console shows clicks near zero, and the new one shows none yet. SEO loss when you change your domain name mostly happens in that gap: the old address has gone dark before the search engine has learned the new one. This article sets out the order of work that closes the gap.
We covered what to protect when you rebuild a site in website redesign SEO, including how to build a URL inventory in detail. Here the address itself changes: a new domain, telling Google, and how long the redirects live.
1. Plan the move as a single job
Google’s site move guide and Search Console Help advise two things: change one thing at a time and, where you can, keep the old site’s architecture at the new location. If you change the domain, the design, the content management system and the URL structure on the same day, Google has to relearn every page and traffic loss becomes more likely. Move the domain first; change layout and structure once the move has settled.
Time it for a quiet period too; the guide says rankings may fluctuate temporarily during a move.
2. Verify both sides in Search Console
The Change of Address tool’s first requirement is that you own both the old and the new property and manage both with the same Google account. Do not leave this for move day.
- Add every variant of the old and new site: for example the
wwwand non-wwwversions, and the HTTP versions too if you use HTTPS. - Make sure your verification method still works on the new site. If you verify with an HTML file, put the file on the new copy; if you use a meta tag, check that the new theme carries it.
- Carry over the settings you made on the old site. The guide suggests that, if you uploaded a disavow file, you upload it again from the new property.
The domain, the registrar and DNS access need to be ready at this stage as well. We described who should hold which account in how to choose a domain name and hosting; a team that cannot reach DNS on move day loses a day.
3. Write the URL map
In the simplest domain change, where page paths stay the same and only the domain changes, a single wildcard rule on the server can be enough: old.com/any/path goes to new.com/any/path. The guide gives exactly this case as an example. If paths change too, you need a table that sets the new match next to every old address.
What belongs in the table: the addresses in your sitemap, the ones with the most traffic in analytics, the ones with external links in the Links report in Search Console, and images, PDFs, CSS and JavaScript files. The guide wants embedded content moved the same way as pages.
The rule: whatever the old page covered, the new address should cover. Do not send several unrelated old addresses to the new site’s home page; Google describes that as confusing for users and possibly treated as a “soft 404”. For content you are not moving to the new site, make sure those addresses return 404 or 410 there; if you merged several pages into one, their old addresses can redirect to the merged page.
4. Prepare the new site
Before you switch the redirects on, the new site needs the following:
- Canonical: every new page should carry a
rel="canonical"tag that points to itself. - hreflang: on multilingual pages, the annotations should use the new addresses.
- Internal links: menu, in-text and footer links should go straight to the new addresses without needing a redirect.
- Sitemap: prepare a sitemap of the new addresses in your map. Save the old addresses’ sitemap too; you will need both to monitor the move.
- robots.txt and noindex: if you blocked crawling or added
noindexduring development, prepare a list of the addresses where you will remove them when the move starts. The new site’s robots.txt should reflect the sections you want blocked. - Server capacity: after a move Google temporarily crawls the new site more heavily than usual. The guide asks that the new site can cope with that load.
The rest of the preparation, such as recording titles, measurement tags and launch-day checks, is the same as for a redesign; the technical SEO checklist helps you review them on the new domain.
5. Switch on the 301 redirects and test them
Set up server-side permanent redirects from the old addresses to the new ones. Google recommends HTTP permanent redirects such as 301 and 308, and says to use JavaScript redirects only if you cannot do a server-side redirect. The site move guide states that 301 and other permanent redirects do not cause a loss of PageRank. For the term itself, see the 301 redirect glossary entry.
As you set them up:
- Do not build chains. Googlebot can follow up to 10 hops in a chain, but Google recommends redirecting straight to the final target. Where that is impossible, it says to keep the number of redirects in a chain ideally no more than 3, and in any case under 5. Update redirects left from an earlier move to the new domain as well.
- Do not forget the home page. Search Console Help asks for a 301 from the old home page to the new home page before the move, and recommends 301s for the old site’s canonical pages too.
- Test. Use the URL Inspection Tool for single addresses and command line tools or a crawler for many. Confirm that each old address reaches the right new address in one step.
Once the redirects are live, check once more that the new site’s canonical tags carry the new addresses and that the development-time noindex rules are gone.
6. Use the Change of Address tool
Search Console Help says to use the Change of Address tool “after you’ve moved and redirected your site”. The tool tells Google to emphasise crawling and indexing the new site instead of the old one; it passes signals from the old site to the new and tells Google to prefer the new site when choosing canonical pages.
Not every move needs this tool. The table below summarises the distinction in Search Console Help.
| Change | Change of Address tool | What to do |
|---|---|---|
example.com to example.net |
Use it | 301 redirects, then the tool |
| From a domain to a path on another domain | Can be used | 301 redirects, then the tool |
| One subdomain to another subdomain | Use it | 301 redirects, then the tool |
| HTTP to HTTPS | Do not use it | Site move with URL changes guide and redirects |
www to non-www |
Do not use it | Redirects and canonical |
| Moving paths within the same domain | Do not use it | Redirects and sitemap update |
| New host or CDN, same URLs | Do not use it | Site move without URL changes guide |
The tool’s requirements:
- Ownership: you must own both the old and the new property and manage both with the same Google account.
- Domain-level property: the tool works only on domain-level properties. You can move
example.comorm.example.com; path-level properties such asexample.com/petstore/cannot be moved. - Every variant separately: the tool does not move subdomains under the domain you name,
wwwincluded. So you must submit a request for every verified variant, such asexample.com,www.example.comand anen.example.comyou do not currently use. Protocols move together: if you submithttp://example.com,https://example.commoves too. - Pre-checks: before it sends the request the tool confirms you own both sites and checks the 301s on a few pages of your site. If you fail a critical check you cannot continue until you fix it; non-critical checks only warn.
- No chained moves: if you submitted a move from site A to site B, you cannot immediately submit another from B to C. If you are combining several sites into one new location, the help page suggests moving them one at a time and waiting for traffic to settle before the next.
Know what the tool does not do, too: Google does not delete the old site from its index. Old addresses with no equivalent on the new site can keep appearing in search results if they are still available. For pages that do have a match, redirects and canonical tags reduce the number of old URLs shown.
7. Update links and sitemaps
You updated internal links in step 4. Right after the move starts, update external links as far as you can, for the sake of user experience and to reduce server load:
- Ask the owners of sites that link to you to point the link at the new address. The guide suggests prioritising by the number of visits each link brings.
- Switch the links in social media and business profiles, and the landing pages of ad campaigns, to the new address.
Submit the new site’s sitemap in Search Console. To monitor the move, the guide suggests submitting the sitemap of the old addresses as well: at first almost no pages from the new sitemap are indexed while many from the old one are. Over time the indexed count of the old sitemap should fall to zero as the new one rises. Seeing redirect warnings on the old sitemap is normal and you can ignore them.
8. Monitor
After move day, follow both properties:
- Page indexing and Sitemaps reports: the number of indexed pages on the new site should rise and the old one fall. Check regularly for unexpected errors.
- Search queries: addresses on the new site should start to get impressions and clicks. At the top of the new property you will see a note that another site has moved to it; as the move progresses, the other site’s traffic is added to the traffic here.
- 404 list: catch addresses missing from the map. The guide counts redirects that go to wrong or non-existent addresses among the most common mistakes.
- Server logs and analytics: watch Googlebot crawls and unexpected error codes in the server log, and traffic falling on the old site and rising on the new in your analytics.
Be patient: according to Google, a move is complete when Googlebot has visited every URL on the old and new sites at least once, and there is no fixed crawl frequency. On small and medium sites most pages take a few weeks to move; larger sites can take longer.
9. How long to keep the redirects
Two Google pages give two different periods, and both point the same way.
| Source | What it says |
|---|---|
| Site move guide | Keep the redirects as long as possible; this is generally at least 1 year. That lets links on other sites be recrawled and reassigned and signals pass to the new URLs. |
| Change of Address tool help | Keep the redirects for at least 180 days, longer if you still see traffic to them from Google Search. After 180 days Google does not recognise any relationship between the old and new sites. |
| The same help page, on the old domain | To stop someone else buying the domain you left and misusing it, keep paying for the old domain for at least a year. |
The guide also suggests that, for users’ sake, you consider keeping redirects indefinitely; because redirects are slow for users, though, try to point your own links and high-volume external links at the new address. Our practical rule: treat 180 days as the floor and 1 year as a sensible minimum; if visitors or crawls still arrive at the old address, do not remove the redirect.
Common mistakes
- Using the Change of Address tool before the redirects are in place.
- Putting the domain change on the same day as a design and structure change.
- Submitting a request for
example.comonly and skipping thewwwversion. - Letting the old domain expire; the redirects stop working that day.
- Changing the addresses again a few weeks later because it “did not work”.
The technical audit in our SEO service covers crawling, indexing, the sitemap and redirects. If you are new to Search Console, what is Google Search Console helps with setting up the two properties.
Common questions
Will changing my domain name cause SEO loss?
A temporary fluctuation in rankings is expected during a move; Google treats it as normal. If old addresses go to their new matches with 301s and the architecture stays the same, signals pass to the new address. The noindex or robots blocks, wrong redirects and outdated sitemaps that Google lists among common mistakes are the main sources of the risk.
Can I move without the Change of Address tool?
Redirects work on their own, but if you are changing domain Google asks you to use the tool after the redirects.
I submitted the Change of Address by mistake. Can I undo it?
You can cancel within 180 days of submitting. First remove the 301 redirects on the server, add 301s from the new site to the old one, then open the tool on the old site and choose “Cancel Move”.
The quickest job you can do today: in Search Console, check that every variant of the old and new domain (www, non-www, HTTP and HTTPS) is verified under a single account. If a variant is missing, add it before move day.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.