Google Search Console Settings for Domain Migration
To answer directly: during a domain migration, you should change your address change tool settings, update your sitemap and robots.txt, and verify the new domain in Google Search Console—but the single most important setting to change is submitting an Address Change request in the old property after the new site is live. This tells Google to transfer ranking signals from the old domain to the new one. Below is a detailed walkthrough of every Search Console setting you should adjust, plus common pitfalls and post-migration checks.
Background: Why Domain Migrations Need Search Console Changes
When you move a website from one domain to another (for example, from example.com to example.net), search engines treat the new domain as a brand-new site unless you explicitly tell them otherwise. Without proper configuration, Google will not automatically transfer your rankings, backlinks, or indexing history. Search Console is the primary tool Google provides to manage this transition. It lets you verify ownership, submit sitemaps, and—most importantly—use the Address Change tool to signal that your site has permanently moved.
What Is the Address Change Tool and How Does It Work?
The Address Change tool is a feature within Search Console that tells Google your entire site has moved to a new domain. It is available only for domain properties (not URL-prefix properties) and requires that you own both the old and new properties. When you submit an address change, Google uses it as a strong signal to:
- Re-crawl the new domain and index its pages.
- Consolidate ranking signals (like backlinks) from old URLs to new ones.
- Update search results to show the new domain instead of the old.
The tool does not automatically redirect traffic—that is your web server’s job. It only affects how Google processes the move. You should submit the address change only after you have set up 301 redirects from every old URL to its corresponding new URL, and after the new site is fully live and crawlable.
Step-by-Step: Search Console Settings to Change
Here is the sequence of settings and actions to take in Search Console, in order of importance:
- Verify the new domain property. Add the new domain (e.g., example.net) as a new property in Search Console and verify ownership using DNS, HTML file, or Google Analytics.
- Submit your sitemap for the new domain. Go to Sitemaps in the new property and submit the sitemap URL (e.g., sitemap.xml). This helps Google discover new URLs faster.
- Use the Address Change tool. In the old property, go to Settings → Address Change, select the new property, and confirm. This is the core setting that tells Google to transfer signals.
- Update the old property’s sitemap. If you keep the old property active, remove the old sitemap or replace it with a sitemap that lists only redirect URLs—though it is usually cleaner to just remove it.
- Check robots.txt on the new domain. Ensure the new domain’s robots.txt does not block Googlebot. You can test it with the URL Inspection tool.
- Monitor the old property’s ‘Removals’ section. Do not use the Temporary Removals tool for the old domain, as it can delay the transfer. Instead, rely on 301 redirects.
Common Problems and How to Avoid Them
One of the most common mistakes is submitting the Address Change before the new site is fully ready. If Google crawls the new domain and finds broken pages or missing redirects, it may not process the move correctly. Another issue is forgetting to verify the new property—without verification, the Address Change tool will not work. Also, many site owners forget to update internal links to point to the new domain; while Search Console can help, consistent internal linking speeds up the transition. Finally, do not use the ‘Change of Address’ tool for a protocol change (HTTP to HTTPS) or a subdomain move—those require different handling (e.g., via redirects and property settings).
How to Choose Between Domain and URL-Prefix Properties
Search Console offers two property types: Domain and URL-prefix. For a migration, you need a Domain property for the Address Change tool to work. A Domain property covers all subdomains and protocols (HTTP, HTTPS, www, non-www) under that domain. If you only have a URL-prefix property (e.g., https://example.com), you cannot use the Address Change tool. If you are moving to a new domain, create a Domain property for the new domain. If you are moving from one subdomain to another (e.g., blog.example.com to www.example.com), you do not need an address change—just redirects and a new property.
Post-Migration Checks in Search Console
After you submit the address change and the new site is live, monitor the following in Search Console to ensure the migration is successful:
- Indexing report: Check that pages on the new domain are being indexed. Use URL Inspection to test a few key URLs.
- Sitemaps report: Confirm the new sitemap has no errors and that discovered URLs are increasing.
- Performance report: Compare clicks and impressions before and after. A temporary drop is normal, but it should recover within a few weeks.
- Coverage report: Look for ‘Page with redirect’ errors on the old property—these are expected, but they should not be ‘Soft 404’ errors.
Frequently Asked Questions
How long does an address change take to process? Google says it can take anywhere from a few days to several months, depending on the size of the site and how quickly Google recrawls. Most sites see the majority of the transition within 2-6 weeks.
Do I need to keep the old Search Console property after migration? Yes, keep it for at least a few months to monitor redirects and any crawl errors. You can also use it to see when Google stops crawling the old domain, which indicates the transfer is complete.
What if I cannot use the Address Change tool because I only have a URL-prefix property? You can still migrate, but you will need to rely on 301 redirects and sitemaps. The process will be slower and less reliable, so it is worth creating a Domain property for the old domain if you still have access.
Should I use the ‘Temporary Removals’ tool for old URLs? No. That tool is for hiding content temporarily, not for permanent moves. Using it can interfere with the address change process. Rely on 301 redirects instead.
Can I migrate without changing any Search Console settings? Technically yes, if you set up perfect 301 redirects and submit a sitemap, Google will eventually pick up the new domain. But you will likely lose ranking signals and experience a longer downtime. The Address Change tool is strongly recommended.
Alternatives and Additional Considerations
If you are moving to a new domain but also changing your site structure (e.g., new URL paths), you should combine the Address Change with individual URL redirects. There is no setting in Search Console that maps old URLs to new ones—that is done via server-side 301 redirects. Also, if you are using a subdomain like www vs non-www, you do not need an address change; just set up a redirect and verify the new property. Finally, remember that the Address Change tool only works for domain properties, so if you have a URL-prefix property, you must create a domain property for the old site before you can submit the change.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.