How to move to a better domain without losing what you have built in search.

Why a domain move is worth doing carefully

Your current domain has built up things that are invisible until you lose them: pages Google has indexed, links from other sites, bookmarks, printed materials and the habits of returning customers. A domain move keeps all of that working only if every old address sends people, and search engines, to the right new one.

Google treats this as a known, supported situation. Its guide to site moves with URL changes lays out the process, and done that way most sites settle down. Expect some fluctuation while Google recrawls; a small site often settles within weeks, larger sites take longer.

Step 1: Prepare the new domain

• Buy the new name and check its history first (here is how). A name with a spammy past brings problems with it.
• Set up hosting and HTTPS on the new domain before anything goes live.
• Verify both the old and the new domain in Google Search Console, and in Bing Webmaster Tools if you use it. You will need both properties for the Change of Address step.
• Keep the new site blocked from public view only until launch day, and remember to remove any block. A forgotten “noindex” is one of the most common causes of a failed move.

Step 2: Map every old URL to a new one

This is the step people skip, and it is the one that matters most. Make a spreadsheet with every URL on the old site in one column and its new home in the next. Pull the list from your sitemap, your analytics (any page that gets visits) and Search Console’s performance and links reports (any page that earns clicks or links).

Each old page should redirect to its closest equivalent, not to the new homepage. Sending everything to the homepage throws away the relevance each page earned and frustrates visitors who wanted something specific. If you are keeping the same page structure and only changing the domain, the mapping is simple: same path, new domain.

Step 3: Use permanent, server-side redirects

Use permanent redirects (HTTP 301, or 308) from each old URL to its new URL, set up on the server or at your host. Google’s page on redirects and Google Search explains that permanent server-side redirects are the clearest signal that a page has moved. JavaScript or meta-refresh redirects are weaker fallbacks; a “domain forwarding” toggle at a registrar can work but often redirects everything to the homepage, so test it.

Avoid chains (old page → old page 2 → new page). Point each old URL straight at its final destination.

Step 4: Update everything you control

• Internal links on the new site should point to new URLs directly, not through redirects.
• Canonical tags, hreflang tags if you have them, and structured data should use the new domain.
• Submit the new XML sitemap in Search Console.
• Update your Google Business Profile website field, social profiles, email signatures, ad campaigns and payment or booking tools.
• Update business directory listings. If you are in the U.S., listings such as USABusinessSearch.com (and COBusinessList.com in Colorado) are quick to change.
• Ask the sites that send you the most valuable links to update them. Redirects will carry them, but a direct link is always cleaner.

Step 5: Tell Google with the Change of Address tool

Once the redirects are live, use Search Console’s Change of Address tool on the old property and point it to the new one. It is designed for moving a whole site from one domain to another; it is not for moving from http to https or for changes within the same domain. The tool checks that your redirects work on important pages before it lets you confirm. Its effect lasts for a set period (Google currently describes 180 days), which is one more reason the redirects themselves must stay in place.

Step 6: Keep the redirects, and the old domain, for a long time

Google’s site-move guide recommends keeping redirects for as long as possible, generally at least a year. Our advice is simpler: never let the old domain expire. Keep it on auto-renew with the redirects running. Old links, printed cards and customer bookmarks will keep arriving for years, and if the old name lapses, someone else can register it and catch that traffic, or worse, impersonate you.

Step 7: Watch the numbers for a few weeks

• Search Console: the Pages (indexing) report for the new site should rise as the old one falls. Check for 404 errors and fix any missed redirects.
• Analytics: look at visits by landing page, not just the total, so you can spot a page that lost its redirect.
• Calls and form fills: these are what actually matter. If they hold, the move worked.

Do not make other big changes (a new design, new URLs, removed content) in the same week if you can avoid it. When several things change at once, it is impossible to tell which one caused a dip.

Email and the less obvious bits

Keep email on the old domain working, or forward it, for at least as long as the redirects. Customers will keep replying to old threads. When you set up email on the new domain, configure SPF, DKIM and DMARC so your messages reach inboxes; our guide on what happens to email and DNS covers the records involved. Update any logins that use an old-domain address so password resets still reach you.

The mistakes we see most

• Redirecting everything to the homepage. It is quick, and it throws away the value of every individual page.
• Letting the old domain lapse. The redirects die with it, and a stranger can register the name you spent years building.
• Launching with the new site still hidden. A leftover noindex tag or robots.txt block from the staging site stops Google indexing anything.
• Changing everything at once. New domain, new design, new URLs and deleted pages in one weekend makes problems impossible to diagnose.
• Forgetting the offline world. Business cards, vehicle wraps, invoices and voicemail greetings keep sending people to the old name for years. That is fine while the redirects run; it is a disaster if they stop.

A launch-day checklist

1. Redirect map finished and tested on a sample of old URLs, including your top pages.
2. New site live on HTTPS, indexable, with the new sitemap submitted.
3. Permanent redirects switched on for every old URL.
4. Change of Address submitted in Search Console.
5. Business Profile, social profiles, directories and ads updated.
6. Old domain on auto-renew, email forwarding confirmed.
7. A reminder in your calendar to review Search Console and analytics weekly for the first month.

Is it worth it?

If the new name is clearly better, shorter, easier to say, a .com instead of a workaround, or simply the name customers already use for you, then usually yes. Done this way, you keep what you have built and gain a name that works harder in every channel. If you have not found that better name yet, tell us what you do and where; spotting the upgrade hiding in plain sight is exactly what we are good at. Browse the portfolio or a category like marketing & SEO to see the kind of names we mean.

Sources, none of them ours: Google: site moves with URL changes · Google Search Console: Change of Address tool · Google: redirects and Google Search