# Changing domain name without losing SEO: redirects, Change of Address and what to expect > Changing your domain name keeps its rankings when every old URL redirects in one hop, Google is told through Change of Address, and every reference moves to the new domain. The steps, in order. Updated 2026-09-26 · Technical SEO · HTML version: https://getreport.app/guides/domain-change-seo Changing your domain name moves every URL your site has, so for SEO it is the biggest kind of move there is. It keeps its rankings when three things are true: every old URL redirects in one 301 hop to its equivalent on the new domain, Google is told about the move through the Change of Address tool in Search Console, and everything that names your domain, from canonicals and sitemaps to your Google Business Profile, is updated. Done that way, Google says most pages of a small to medium site move within a few weeks. This guide gives the steps in order, what changed in Google's guidance in 2026, and what to expect afterwards. For migrations in general, see the [website migration guide](https://getreport.app/guides/website-migration-seo). ## Quick answer - **Change only the domain if you can.** Keep paths, content and design the same, so any drop has one cause. - **Redirect path to path** from the old domain to the new one, in one 301 hop, over http and https, with and without www. - **Verify both domains in Search Console**, including the www, non-www and subdomain variants of the old one, then submit Change of Address for each variant. - **Update everything that names the domain:** canonicals, hreflang, sitemap, internal links, structured data, Open Graph tags, analytics, ads, email and business listings. - **Keep the old domain registered and redirecting** for years. Google asks for at least 180 days for Change of Address and at least a year for site moves. - **Verify every old URL** with the [migration redirect validator](https://getreport.app/tools/migration-validator) on launch day and a week later. ## Is a domain change worth the risk? Sometimes it is unavoidable: a rebrand, a merger, a legal dispute over a name, or a move from a country domain to a global one. But be clear about the cost. Every URL has to be recrawled and reassessed on the new domain, links from other sites keep pointing at the old one, and visitors who type the old name rely on the redirect for years. If the reason is cosmetic, such as a slightly shorter name, the gain rarely outweighs weeks of ranking movement. If the move is necessary, the steps below keep the risk small. ### Check the new domain's history A domain that has been registered before may carry baggage: spam, a manual action or a reputation you do not want. Before you commit, look at its history in a web archive, search for `site:new-example.com`, and once you own it, verify it in Search Console and check **Security & Manual actions**. A clean, unused domain is the easiest start. ## Before the move ### 1. Inventory the old site and record a baseline Collect every URL that matters: the XML sitemap, pages with impressions in Search Console, analytics landing pages and URLs other sites link to. Record traffic, rankings and indexed pages for your key pages, so you can compare after the move. The [before-and-after measurement guide](https://getreport.app/guides/measuring-before-and-after-a-redesign) shows what to record. ### 2. Build the redirect map If paths stay the same, the map is one rule: every path on the old domain to the same path on the new one. If any URLs change at the same time, list those pairs explicitly so they go straight to their final address instead of chaining through a same-path redirect. The [redirect mapping guide](https://getreport.app/guides/redirect-mapping-for-site-migration) covers building and testing the list. ### 3. Prepare the new domain Set up hosting, DNS and a certificate for the new domain, and build or copy the site there. Keep it out of search until launch with a password rather than a `noindex` that can be forgotten. Set up email on the new domain too, with its own SPF, DKIM and DMARC records, if your mail moves with it; the [email authentication guide](https://getreport.app/guides/spf-dkim-dmarc-email-authentication) covers those records. ### 4. Verify every variant in Search Console Verify the new domain in Search Console, preferably as a Domain property, which covers all its subdomains and both http and https. Verify the old domain the same way if you have not already. Google updated its site move guidance in June 2026: for a domain move, you should submit Change of Address requests for all subdomains and for both the www and non-www variants of the old domain, even variants you do not actively use, and verify each of them in Search Console first. Make a list of those variants now, such as `example.com`, `www.example.com`, `shop.example.com` and `en.example.com`. ## Launch day ### 5. Switch on the redirects Publish the site on the new domain and turn on the redirects at the same moment. Each old URL, in every variant, should answer with one 301 to the final https address on the new domain: ```text http://old-example.com/shop/mugs → 301 → https://www.new-example.com/shop/mugs https://www.old-example.com/shop/mugs → 301 → https://www.new-example.com/shop/mugs ``` The setups for Cloudflare, Apache, nginx, cPanel and registrar forwarding are in [how to redirect a domain to another domain](https://getreport.app/guides/redirect-domain-to-another-domain), including the DNS and certificate steps that are easy to forget. ### 6. Update everything on the new site Search engines should see the new domain everywhere on the new site, never the old one: - **Canonical tags** pointing at the new URLs. - **hreflang** annotations on the new URLs, for multilingual sites. - **The XML sitemap** listing new URLs only, and `robots.txt` on the new domain declaring it. - **Internal links** in content, menus and templates using new URLs, not old ones that redirect. - **Structured data:** the Organization `url` and `logo`, and any `sameAs` profile links. - **Open Graph and Twitter tags,** especially `og:url` and image URLs. Hard-coded absolute links in old content are the usual leftovers. Search the database or content export for the old domain name and replace it. ### 7. Submit Change of Address In Search Console, open the old domain's property, go to **Settings → Change of address**, choose the new property and follow the checks. Google's help page sets the conditions: you must be a verified owner of both properties with the same account, the 301 redirects must already work, and the tool works only for domain-level moves, not for http to https, www changes or moves within a domain. Repeat it for each variant of the old domain, as Google's 2026 guidance says. Its signals last 180 days. Then submit the new sitemap in the new property. Bing Webmaster Tools has a similar Site Move feature for moving a verified site to another verified site; use it if Bing traffic matters to you. ### 8. Verify every old URL > **Free tool:** [301 redirect map validator for site migrations](https://getreport.app/tools/migration-validator): Check your 301 redirect map after a migration. Paste up to 1,000 old and new URL pairs and see which land right, chain, go temporary or are lost. Free. Paste the old URLs with their expected new URLs, up to 1,000 pairs per run. The validator requests each old URL, follows every hop and gives each pair a verdict: correct, wrong target, not redirected or gone, chain, temporary redirect, or a target that is broken or set to `noindex`. Run it on launch day and again a week later. For single URLs and the http and www variants, the [redirect checker](https://getreport.app/tools/redirect-checker) shows every hop. Then run the full getReport report on key pages of the new domain. These findings catch most launch-day leftovers: > **Check: Canonical tag is present.** Without a canonical URL, search engines may index duplicate versions of this page (with and without trailing slash, with UTM parameters) and split its ranking signals. > > 1. Add in . > 2. In WordPress, Yoast or Rank Math add this automatically — check it is not disabled for this page. > **Check: og:url matches the canonical URL.** Facebook counts likes and shares per og:url. When it differs from the canonical URL, the counts split between two addresses and the card may link to the wrong version of the page. > > 1. Set og:url to exactly the canonical URL of this page, without tracking parameters. > 2. In WordPress, Yoast and Rank Math derive it from the canonical automatically; check for a hard-coded value in the theme. > **Check: Organization structured data has a logo and sameAs links.** Google uses logo for the brand box in search and sameAs (your social profiles) to connect the brand across the web. Without them the box shows no logo and no profile links. > > 1. Add "logo" with the URL of a square image of at least 112×112 px. > 2. Add "sameAs" with an array of your official profile URLs (Facebook, Instagram, LinkedIn, Wikipedia…). > **Check: The page can be indexed.** To appear in search, a page must return HTTP 200, carry no noindex directive and be allowed in robots.txt. If any of the three fails, the page is invisible to searchers. > > 1. Open the technical detail to see which condition fails, then fix that one; the individual findings above have the steps. > 2. After the fix, request indexing in Google Search Console to speed things up. ## After the move ### 9. Update everything off the site The redirects cover visitors who follow old links, but every place you control should point at the new domain directly: - Google Business Profile and other business listings. - Social media profiles and bios. - Paid ads, shopping feeds and affiliate links. - Analytics and tag manager settings, such as the domain in filters and cross-domain tracking. - Email signatures, invoices, printed material and app store listings. - Your most valuable backlinks: ask the sites that link to you most to update the URL. ### 10. Monitor, and keep the redirects Watch the new property's Page indexing report fill up, and the old property's pages move to "Page with redirect". Check your server or CDN logs for old URLs that answer 404 and add redirects for them. Compare key pages with your baseline at one, four and eight weeks. Keep the old domain registered and its redirects running. Google asks for at least 180 days for Change of Address and at least a year for site moves in general, and longer while Google Search still sends traffic to old URLs. Links from other sites and old bookmarks keep arriving for years, so most sites should keep the old domain for good. ## What to expect in search For a clean move, Google's documentation says rankings may fluctuate while it recrawls and reindexes, and that most pages of a small to medium site move within a few weeks. Popular pages switch within days; rarely visited pages take longer, because Google discovers each redirect only when it recrawls the old URL. Brand searches for the old name may show the new domain soon after, and your sitelinks rebuild over time. A drop that keeps growing after the first weeks, or that affects only some sections, points to a problem rather than the process. Check, in this order: old URLs without a redirect or redirecting to the wrong page, chains from older redirects, canonicals or sitemaps still naming the old domain, and a `noindex` or robots.txt block left over from staging. The [site migration checklist](https://getreport.app/guides/site-migration-checklist-domain-https-cms) has the full list of launch-day and after-launch tasks. ## Common mistakes - **Redirecting everything to the new home page.** Deep pages lose their rankings. Redirect path to path. - **Change of Address for only one variant,** such as `www.old-example.com`, while `old-example.com` and subdomains are left out. - **Using Change of Address before the redirects work.** The tool expects them in place. - **Canonicals, hreflang or the sitemap still on the old domain** after launch, contradicting the redirects. - **Changing domain, design and URLs in the same launch.** You cannot tell which change caused a drop. - **Letting the old domain expire** after a year. Its links then go to whoever registers it next. - **Forgetting email.** A domain change also moves mail, and the old domain's MX records must keep working until nobody writes to it. ## Questions people ask ### Will changing my domain name hurt SEO? Temporarily, a little; permanently, not if the move is done right. Rankings usually fluctuate for a few weeks while Google recrawls old URLs and follows their redirects. With a one-hop 301 for every old URL, Change of Address in Search Console and every reference updated, most sites recover their previous positions. Losses that last come from missing or wrong redirects. ### How long does it take Google to recognise a domain change? Google says most pages of a small to medium site move within a few weeks. Popular pages are recrawled and switched within days; pages Google visits rarely can take months, because each redirect is only found when the old URL is recrawled. The Change of Address signals last 180 days, and redirects should stay for at least a year. ### Do I need to use the Change of Address tool when changing domain? Yes, for a domain move it is strongly recommended. It tells Google the move is intentional and helps it transfer signals to the new domain. Since Google's June 2026 update, submit it for every variant of the old domain, including www, non-www and subdomains, after verifying each in Search Console and after the 301 redirects are live. ### Can I change my domain and my URLs at the same time? You can, but it doubles the risk and makes problems harder to trace. If you must, redirect each old URL straight to its final new URL, never through a same-path rule that redirects again, and verify the whole map on launch day. Where possible, change the domain first with identical paths and restructure URLs in a later project.