Ready to grow?Short answer: Yes, you can move to a new domain without losing your Google rankings, but only if you do two things. Point every old page to its exact match with a 301 redirect, then file a Change of Address in Google Search Console. Google says permanent redirects don't cost you PageRank, so your rankings follow the pages.
Picture a cafe that has spent three years earning its spot on Google. Someone searches "brunch near me" and there it is, page one, calls coming in on a Saturday morning. Now the owner wants to rebrand from oldname.com to newname.com. The fear is obvious: flip the domain and watch all that traffic vanish overnight.
That fear is reasonable, and it is also avoidable. The rankings you earned live on your pages, not on your domain name. Move the pages correctly and the rankings move with them. Do it sloppily and you can absolutely tank the whole thing. The difference between those two outcomes is a short, ordered checklist that you can follow in an afternoon.
What actually protects your rankings: two moves, not ten
Most of the advice out there makes a domain move sound like open-heart surgery. It isn't. Two things carry the weight, and everything else is detail.
The first is the 301 redirect. A 301 tells Google "this page moved permanently to this new address." According to Google Search Central's own guidance on site moves, "301 and other permanent redirects don't cause a loss in PageRank." Read that twice, because it is the whole reassurance you need. The credit your pages built up transfers through the redirect.
The second is the Change of Address tool inside Google Search Console. Google's Search Console Help says this tool "tells Google about your change, and helps to migrate your Google Search results from your old site to your new site." One is the plumbing that reroutes visitors and search engines. The other is the note that tells Google the move is real and permanent. You need both.
If you have never opened Search Console before, start with our beginner's walkthrough of Google Search Console so the next few steps feel familiar instead of foreign.
Step 1: Map every old page to its exact match on the new domain
Before you touch a single setting, make a list. Two columns. Left column, every URL on your old site. Right column, the exact page it becomes on the new one.
For the cafe, that looks like this. The menu page at oldname.com/menu becomes newname.com/menu. The hours page at oldname.com/hours becomes newname.com/hours. The contact page maps to contact, the about page to about, the gallery to gallery. One old page, one new page, matched like socks.
This one-to-one mapping is the part people skip, and skipping it is expensive. The goal is that a person (or Google's crawler) landing on any old address arrives at the same content in its new home, not somewhere close, not the homepage. Keep your URL structure identical if you possibly can. Google notes that "keeping the same site architecture in the new location helps to pass the signals more directly." Same paths, same structure, new domain in front. That is the safe move.
If you are tempted to clean up messy URLs while you are in here, resist for now. Our guide to clean, SEO-friendly URLs is worth reading, but do that work as a separate project, weeks before or after the domain switch, never during it.
Step 2: Set up 301 (permanent) redirects for every old URL
Now turn your map into redirects. For each old URL, create a 301 that sends it to its matched new URL. This is a permanent redirect, not a temporary one, and the distinction matters: a temporary redirect (302) tells Google the old address is still the real home, which is the opposite of what you want.
Where you set these up depends on your host. Most website builders and hosting panels have a redirects section, and on WordPress a redirect plugin handles it. If you run your own server, the redirects live in the server config. The mechanics vary, the rule does not: redirect every old page, not just the homepage.
Here is the trap in plain terms. Dumping every old URL onto the new homepage feels efficient. It is a rankings killer. Someone who ranked for "gluten free menu" landed on your old menu page; if that redirect drops them on the homepage instead, the specific relevance is gone and so is the ranking. Match each page to its real replacement.
Step 3: Verify both the old and new domain in Google Search Console
The Change of Address tool has strict entry requirements, so set them up now. Google's Search Console Help spells them out: to use the tool you must be an owner of both the old and the new property, signed in with the same Google account, and both must be domain-level properties (example.com, not example.com/some-path).
So add newname.com as a property in Search Console if you haven't already, verify ownership, and confirm oldname.com is verified too under the same login. Add both at the domain level. If you set up a property as a URL prefix or a subfolder, the tool will refuse to run. Get this right before you go looking for the Change of Address button, because a mismatch here is the most common reason owners get stuck.
Step 4: Submit the Change of Address in Search Console
With the redirects live and both domains verified, open the old site's property in Search Console and submit the Change of Address, pointing it at the new domain. Google is clear on timing: "Use this tool after you've moved and redirected your site." Redirects first, then the announcement.
Here is what happens behind the scenes once you file it. Google's Search Console Help explains that it forwards signals from the old site to the new one, shifts its crawling and indexing effort toward the new site, and starts treating the new site as the canonical, preferred version. Those actions "continue for 180 days after you start migration in Search Console." So the filing isn't a formality. It kicks off a six-month handover where Google actively moves your identity to the new address.
This is also the moment to think about the rankings you are protecting. If you are unsure which pages carry your traffic, our guide on why a website stops showing on Google helps you spot which pages you cannot afford to lose in the shuffle.
Step 5: Submit a fresh sitemap and test that the redirects actually fire
Two final jobs, and neither is optional.
First, submit a new sitemap for the new domain in Search Console. This hands Google a clean list of every page on the new site so it can crawl and index them faster. If the idea of a sitemap is fuzzy, our explainer on getting Google to index your new pages covers it.
Second, test the redirects yourself. Don't assume they work. Open a handful of old URLs in your browser and confirm each one lands on the correct new page, not an error, not the homepage. Check the menu, the hours, the contact page, a couple of blog posts. Google's own move sequence puts this testing step right in the middle of the playbook: turn on the redirects, check your canonical and robots rules on the new site, test the redirects, file the Change of Address, keep the redirects live, then submit the new sitemap. Following that documented order is the safest thing you can do.
What to expect after you flip the switch
Be ready for a dip. This is normal, it is temporary, and it does not mean you broke something.
Google is honest about this in its site move documentation: "With any significant change to a site, you may experience ranking fluctuations while Google recrawls and reindexes your site. As a general rule, a medium-sized website can take a few weeks for most pages to move in our index; larger sites can take longer." For a small cafe or shop, think a few weeks for most pages to settle into their new home. Rankings wobble, then recover, as long as the redirects stay in place and you leave the machinery alone.
The single hardest part of a domain move is doing nothing while Google catches up. In our experience helping owner-run businesses through moves like this, the panic almost always hits around week two, when a couple of keywords slip and the instinct is to start changing things. That is exactly when you hold steady. The owners who leave the redirects untouched and let the recrawl finish are the ones who come out the other side with their traffic intact.
How long to keep the redirects live
Long. Longer than feels necessary.
Google recommends keeping the redirects in place "generally at least 1 year," and it says to keep paying for and renewing the old domain for at least a year too. The reason is mechanical: those 180 days of active signal-forwarding are a floor, not a finish line, and Google's guidance is that after 180 days it no longer recognizes any relationship between the old and new site. If old URLs are still pulling any search traffic past that point, keep the redirects running even longer.
So don't cancel oldname.com the week after you move. Renew it. Keep the redirects on. That old domain is a bridge, and you want the bridge standing until every last visitor and crawler has crossed.
The mistakes that actually cost you rankings
Most horror stories about domain moves come down to three avoidable errors.
The first is redesigning at the same time. Google is blunt about this: "If you combine a site move with a redesign of the site's content and URL structure in the new location, you will probably see some traffic loss as Google might need to relearn and reassess the individual pages." Move first. Redesign later. Never both at once.
The second is redirecting everything to the homepage. We covered it in Step 2, and it earns a second mention because it is the most common self-inflicted wound. Each page gets its own destination.
The third is chaining redirects. That is when oldname.com/menu redirects to an interim address, which then redirects to newname.com/menu. Every extra hop weakens the signal and slows the crawler. Point each old URL straight at its final home in one jump.
Getting the domain itself right in the first place is a separate skill, and if you are still choosing your new name, our guide on how to choose a domain name will save you a second move later.
Frequently asked questions
Will I lose my Google rankings when I change domains?
Not if you do it correctly. Google states that 301 permanent redirects don't cause a loss in PageRank, so the credit your pages earned transfers to the new domain. Expect a short, temporary dip while Google recrawls, then recovery.
How long does it take to recover after a domain move?
Google says a medium-sized website can take a few weeks for most pages to settle into the new index, and larger sites can take longer. For a small business site, plan for a few weeks of fluctuation before things stabilize.
Do I have to use the Change of Address tool?
It is strongly recommended. Google's Change of Address tool actively forwards signals from the old site to the new one for 180 days and tells Google the move is permanent. The redirects do the rerouting, but the tool confirms the move so Google migrates your search results faster.
When can I stop paying for my old domain?
Not for at least a year. Google recommends keeping the redirects live generally for at least a year and continuing to renew the old domain over that period, because after 180 days it stops recognizing any relationship between the two sites. If old URLs still get search traffic, keep it going longer.
That cafe on page one for "brunch near me" doesn't have to gamble its Saturday mornings to get a new name. Map the pages, redirect each one to its exact match, file the Change of Address, and then sit on your hands while Google catches up. The traffic follows the pages when you move them carefully, which is the whole point of doing SEO on autopilot instead of holding your breath. Fonzy exists so the boring, load-bearing steps like this one get done right without you learning any of it.
