
Changing Your Domain Name Without Losing SEO: What a Domain Move Needs That Other Migrations Don't
Changing your domain name? The steps that are specific to a domain move: every old variant, the Change of Address tool, the 180-day window, and slow indexing.
November 12, 2026 · 11 min read
You can change your domain name without losing your rankings for good, but only if Google can connect the old site to the new one. That connection rests on three things: a permanent redirect from every old URL to its exact new URL, a Change of Address request in Search Console for every version of the old domain, and enough time. Google's own guide says that for a small to medium-sized site it "can take a few weeks for most pages to move." A dip in that window is normal. A dip that never ends almost always traces back to one of the three.
A domain change is one kind of site migration, so the general work (the redirect map, the new sitemap, the launch-day checks) is the same as any other move. Our website migration SEO checklist covers that in order. This guide covers only what is different when the hostname itself changes: the parts people skip because they assume the redirect alone does the job. And if the rebrand comes with a new design, launch the two separately: Google's guide says to "change only one thing at a time," and our website redesign SEO guide covers the design half.
What Changes When You Change Your Domain Name
When you move /old-path/ to /new-path/ on the same domain, Google only has to learn about individual URLs. When you change domains, Google also has to learn that a whole site moved, and that the new domain should inherit what the old one earned.
Redirects handle the first job, one URL at a time. Google's site move guide says that 301 and other permanent redirects "don't cause a loss in PageRank," so the link value itself is not what you lose. If you want the detail on which redirect codes count as permanent, see 301 redirects and SEO.
The second job is what the Change of Address tool is for. Google's help page describes what happens when you file a request: it "tells Google to emphasize crawling and indexing your new site over crawling your old site," "forwards various signals from the old site to the new site," and "tells Google to prefer the new site over the old when determining canonical pages." Redirects alone don't send that site-level message.
Two warnings from the same page are worth reading before you start:
- Don't chain domain moves. "If you submit a change of address to redirect traffic from site A to site B, you can't immediately submit another change of address from site B to site C." Pick the final domain before you move.
- Don't merge several domains in one go. "Moving sites A, B, and C all to new location D can cause some confusion and traffic loss." Move them one at a time and let traffic settle between moves.
Before You Switch: Check the New Domain and List Every Old Variant
Check the new domain's history. If you bought the domain from someone else, Google's guide says to "make sure it's clean of any outstanding issues from the previous owner." Verify it in Search Console first and look at two places:
- Manual actions. If there's an action left from earlier spam, fix the problem and file a reconsideration request before you move anything onto the domain.
- Removals. Google specifically warns about "URL removals left over from the previous owner, especially a site-wide URL removal." A leftover removal will keep your new pages out of results no matter how good your redirects are.
List every variant of the old domain. This is the step most guides skip. The Change of Address tool "does not move any subdomains below the specified domain (including www)." Google's site move guide now says to submit Change of Address requests "for all verified variants of the old domain (including subdomains and www/non-www versions) to the new domain," and adds "even if you're not actively using these variants."
So if your old blog answered on example.com, www.example.com, and maybe an old blog.example.com, that's three requests, and each variant needs to be verified in Search Console first. Protocols are the one thing you don't need to repeat: the tool "moves all protocols of your source property," so http:// and https:// go together.
Use one Google account. The tool requires that you "must be an owner of both the old and new properties in Search Console" and "must use the same Google account to manage both properties." If the old property sits under a former agency's account, sort out ownership now, not on launch day.
Export a baseline. Save page-level clicks, impressions, and average position from the old property. After the move those numbers fall towards zero, and the export is the only "before" you'll have. Our Search Console performance report guide explains which columns hold up when you compare them later.
How to Use the Change of Address Tool
File the request after the redirects are live, not before. Google's prerequisite is to "implement a 301 redirect from your old homepage to your new homepage," and it recommends redirecting the old canonical pages too. The tool checks this: it runs "a quick check before sending the move request to Google, to confirm that you own both sites, and to check for 301s on a few pages on your site."
The steps, in order:
- Turn on the server-side redirects from the old domain to the new one, path by path.
- Open the old domain's property in Search Console. It has to be a domain-level property; the tool can't move a property at a path like
example.com/blog/. - Go to Settings → Change of address and pick the new property.
- Fix anything the pre-move checks flag as critical. Non-critical warnings let the request continue.
- Repeat for each variant on your list.
Once the request is accepted, both properties show a notice that the move is in progress, and Google says "you will see these notifications for 180 days."
That 180-day number matters more than it looks. The tool's effects "continue for 180 days after you start migration." You can cancel a request within the same window. And after it ends, "Google does not recognize any relationship between the old and new sites, and treats the old site as an unrelated site, if still present and crawlable." Google says to keep the redirects "for at least 180 days," and its broader site move guide says to keep them "for as long as possible, generally at least 1 year." It also recommends "continuing to pay for the old domain for at least a year to prevent others from buying and using your abandoned domain for malicious purposes." In practice: keep the old domain, and keep it redirecting, for as long as anything still links to it.
Why Your New Domain Isn't Getting Indexed
This is the question that shows up in forums a few weeks after a rebrand: the old domain is dropping out of Google, but the new one isn't replacing it. Work through these in order.
1. Is it just early? Google says that to consider a move complete, "Googlebot will have to visit every URL on your old and new site at least once," and that "the move takes place on a per-URL basis." A few weeks of partial indexing is the expected path, not a failure. Check whether the new property's indexed count is rising at all, even slowly. If it is, give it time.
2. Do the redirects land on the right page? Load a sample of old URLs, including deep posts and not just the homepage. Each should return a single 301 or 308 and land on the matching new page with a 200. Google's site move guide calls out "redirecting to the wrong (non-existent) URLs on the new site" as a common mistake, and warns against sending many old URLs to the new homepage, which "might be treated as a soft 404 error." Our redirect chain checker guide covers testing in bulk.
3. Is the new domain blocked? A noindex tag or a Disallow: / left over from staging will stop indexing cold. Google's troubleshooting list starts here: "Don't forget to remove any noindex or robots.txt blocks that were only needed for the migration."
4. Do the new pages point at themselves? Every new URL should have a self-referencing canonical. If your templates still output canonicals to the old domain, you're asking Google to keep the old URLs. The Page with redirect status on the old property is normal during a move; a canonical pointing back at it is not.
5. Did you file Change of Address for every variant? If you moved example.com but not www.example.com, the www site isn't part of the request, because the tool doesn't move subdomains, www included.
6. Is there a leftover removal or manual action on the new domain? Check again if you skipped it earlier.
7. Did you submit the new sitemap? Google's guide says to submit it in the new property, and adds that "Submitting a sitemap can help make the discovery process quicker." It should list only final URLs on the new domain. See sitemap best practices for what belongs in it.
If all seven check out, use URL Inspection on a few important pages. It shows whether Google has seen the new URL, which canonical it chose, and whether it's indexed. Some of the reasons a brand-new post lags apply here too (see why a new post isn't showing up in Search Console), and Discovered vs Crawled — Currently Not Indexed explains the two statuses you're most likely to see on the new property.
What We Found When We Checked Our Own Old Domain
We consolidated trafficmonitor.kr into trafficmonitor.app in July 2026. While writing this, we tested the old domain's redirects on 2026-11-12:
https://trafficmonitor.kr/returns a301tohttps://trafficmonitor.app/, and a deep URL like/blog/sitemap-could-not-be-readkeeps its path on the new domain. That's the behavior you want.http://trafficmonitor.kr/returns a308to thehttps://version first, then the301to the new domain. That's two hops: inside Google's advice to keep chains "ideally no more than 3," but one more than it needs to be.https://www.trafficmonitor.kr/doesn't redirect at all. It returns a200and serves the site, with a canonical tag pointing attrafficmonitor.app.
The last one is exactly the variant problem described above. The canonical limits the damage, but it only asks Google to prefer the new URL. It doesn't send visitors or crawlers there the way a redirect does. For a variant nobody types, it's easy to miss. Test every hostname you've ever served, with and without www, over both http and https, before you call a domain move done.
Domain Change SEO Checklist
Before the move
- Pick the final domain. Don't plan a second move soon after the first.
- Verify the new domain and check it for manual actions and leftover URL removals.
- List every hostname variant of the old domain and verify each one in Search Console.
- Make sure one Google account owns both the old and new properties.
- Export page-level clicks, impressions, and position from the old property.
Move day
- Turn on server-side
301or308redirects, path to matching path. - Test the homepage, deep posts, and every variant over
httpandhttps. - Remove staging
noindextags and robots.txt blocks on the new domain. - Check that new pages carry self-referencing canonicals.
- Submit the new sitemap in the new property.
- File a Change of Address request for each old variant.
The next six months and beyond
- Watch the new property's indexed count and the old property's decline, week by week.
- Use URL Inspection on your top pages until each shows the new URL as indexed and canonical.
- Keep the redirects for at least a year, and keep paying for the old domain.
The watching is the slow part. You're looking for the handful of posts that didn't make the jump while the rest recover. Traffic Monitor connects to Search Console with read-only access and shows clicks, impressions, CTR, and post performance, updated daily, so a post that's still missing on the new domain stands out. You can connect your new domain on the free plan. If the drop continues after the move has settled, the cause may not be the move at all; our guide to why blog traffic drops covers the other usual suspects.
Related posts
How to Add a User to Google Search Console (And Which Permission to Give)
How to add a user to Google Search Console, which level to pick (Owner, Full, or Restricted), the per-property limits, and how to remove access safely.
SEO Chrome Extensions for Bloggers: 6 Free Ones Worth Installing (And What Each Can't See)
The free SEO Chrome extensions a blogger actually needs, matched to one job each, plus the one Google retired and what no extension can tell you.
Track your blog rankings automatically
Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.
Start free →