Domain change SEO: the plan for a rebrand or merger

If your business is renaming itself or merging two sites under one name, the move to a new domain changes the address of every page Google has indexed for you. Google documents the search side of that move. Below, its steps run in launch order, with the ones that need a crawler, server access or Google Search Console ownership marked.

What a domain change does to search traffic

A domain change gives every URL on the site a new address, and Google moves its index one URL at a time: by its site-move guide, the move is complete only once Googlebot has visited every URL on the old site and the new one¹. Until then, old and new addresses share the index, and the old ones drop out as their redirects are crawled.

The redirects carry the old URLs’ link value across: the same guide says “301 and other permanent redirects don’t cause a loss in PageRank.”¹ The risk sits in the gaps: an old URL left without a redirect, a chain of hops, a redirect to the homepage instead of the mapped page, or an old domain that lapses and takes every redirect with it.

Search traffic follows on a longer clock than the index. A June 2026 study by SALT.agency, covering 1,052 domain changes, tracked when each new domain’s monthly organic search traffic first matched the old domain’s pre-move level: 22.80% had by day 90, and 13.9% had not after three years⁵. The sample mixes SALT’s own projects with hundreds crowdsourced from the SEO community, and because its data is monthly, each recovery date is accurate to about a month.

If the rebrand date is set and your developer or agency is building the new site, a domain-change plan with launch checks puts the URL inventory, the redirect map and the crawls around launch day into one SEO-only project.

One change at a time: rebrands, mergers and redesigns

Google’s site-move guide puts the domain change first and a new layout after it, one change at a time¹. When a rebrand comes with a redesign, the order of the two is the first decision to make. The Change of Address help states the cost of doing both at once: a move combined with a redesign of content and URL structure will “probably” lose some traffic, because Google “might need to relearn and reassess the individual pages.”²

The same help page says that keeping the same site architecture in the new location “helps to pass the signals more directly to the new site.”² Same paths, same templates and the same content on day one leave Google less to relearn.

A merger, where two or more sites move under one new name, adds two rules from that page:

• One site at a time. “Moving sites A, B, and C all to new location D can cause some confusion and traffic loss,” so Google suggests moving one site, then waiting until traffic stabilizes before the next².
• No chained moves. After a Change of Address from site A to site B, you “can’t immediately submit another change of address from site B to site C.”² Settle the final name before the first move.

Before launch: checks on the old and new domains

Four checks belong before the launch date is fixed, because each one can hold up the move:

• Ownership in Search Console. Verify every variant of both domains, www and non-www, HTTP and HTTPS¹. The Change of Address tool needs you to own both the old and the new property and to manage both from the same Google account².
• The new domain’s past. For a domain bought from a previous owner, Google’s guide says to check it for a manual action and for URL removals that owner left behind. A disavow file uploaded for the old domain should be uploaded again in the new domain’s property¹.
• The old domain’s renewal. Google 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.”² The redirects run on that domain, so a lapse ends them too.
• The reason for the new name. A keyword in the domain is not an SEO reason to move. Google’s SEO Starter Guide says that “from a ranking perspective, the keywords in the name of the domain (or URL path) alone have hardly any effect beyond appearing in breadcrumbs.”⁴

The domain-change plan in launch order

The plan follows Google’s site-move guide and the Change of Address help. Steps 1 to 4 run before launch; steps 5 to 9 start on launch day.

1. List the old domain’s URLs. Build the URL inventory from Search Console clicks and impressions, backlinks, the index and the current sitemaps. Include images and downloads such as PDFs: Google’s guide says those files “need to be moved in the same way as all other content on your website.”¹
2. Map each URL to its page on the new domain. Each URL on the inventory is mapped to one page, and the redirect map template has a column for each decision.
3. Prepare the new domain on staging. Point canonical tags, hreflang annotations, internal links and the new XML sitemap at the new URLs, and carry over the Search Console verification file¹.
4. Write the redirects at server level. Plan permanent server-side redirects, 301 or 308, from each old URL straight to its mapped page¹. Avoid temporary 302s, because for those Google’s indexing pipeline “doesn’t use the redirect as a signal that the redirect target should be canonical.”³
5. Launch and test. Switch the redirects on and crawl every URL on the inventory. The Change of Address tool runs a check of its own, but only “for 301s on a few pages on your site.”²
6. File the Change of Address. From the old domain’s property, file a request for every variant, “including www and non-www,” even the variants you do not use².
7. Submit both sitemaps. Submit the new sitemap, and the old-URL sitemap as well: Google’s guide describes the old one’s indexed count falling to zero as the new one’s rises¹.
8. Update the links you control. Change internal links, profiles, directory listings, ad campaigns, email signatures, business cards and letterhead. Google’s guide names profile links “such as from Facebook, Twitter, and LinkedIn”¹, and a Google Business Profile has its own website field⁹.
9. Ask the top linking sites to update. Google’s guide suggests contacting the sites that link to your old URLs, “prioritizing your efforts by the number of inbound visits for each link.”¹

If every path stays the same

When only the domain changes and every path stays identical, one pattern rule can redirect the whole site: Google’s guide notes that a domain change may need only “a wildcard server-side redirect.”¹ The inventory still earns its place. It is the list the launch crawl checks, and it shows which old URLs already redirect, so each one can redirect straight to its final address instead of hopping twice.

If the rebrand renames pages too

When the new brand also renames services or merges pages, each changed URL needs its own row in the redirect map, and the Change of Address advice above applies: keep every path that can stay the same on the new domain. Pages retired on purpose return a 404 or 410 rather than redirecting to an unrelated page such as the homepage¹. The launch checks every relaunch shares, from robots.txt to analytics, are in the SEO migration checklist.

Which steps need a crawler, server access or Search Console

Most of the plan can run in-house. Three resources decide where it stops: a crawler that can test every URL on the inventory, access to the server that answers for the old domain, and owner access in Search Console.

If one of the three resources is missing, that step is the one to hand over; the rest of the plan can stay with you.

The WordPress side of a domain change

WordPress keeps its address in two options, siteurl and home, which change under Settings > General or with WP-CLI’s option update command⁶. The handbook warns that after the move “references to the old domain name or location will remain in the database, and that can cause issues with links or theme display.”⁶

Those references need a search-replace that understands serialized data. A plain database replace can break settings, because “some themes and widgets store values with the length of your URL marked.”⁶ WP-CLI’s search-replace command “intelligently handles PHP serialized data,” and its dry-run option shows a report without saving any change⁷. The handbook’s own example skips the guid column, which it says never to change⁶.

Links typed by hand into theme templates, such as the sidebar and footer, sit outside those settings; the handbook says to search each template file for “manually entered references to your old domain name.”⁶

To have the database work, the redirects and the launch done as one project, you can move the site and domain together in an end-to-end WordPress migration.

After launch: day 180, year one and later

After launch, three dates matter: the first weeks of recrawling, day 180, when the Change of Address period ends, and the one-year mark Google gives for the redirects.

Two Google pages give two minimums for the redirects. The Change of Address help says to keep them “for at least 180 days–longer if you still see any traffic to them from Google Search”²; the site-move guide says “generally at least 1 year,” time for Google to recrawl and reassign “links on other sites that point to your old URLs.”¹ Plan for the longer one; from users’ perspective, Google suggests “keeping redirects indefinitely.”¹

SALT.agency’s figures put those dates in context: by day 180, 35.40% of the 1,052 domain changes had matched the old domain’s traffic level, and by day 365, 59.50% had⁵. The study ran no regression analysis against migration quality factors, so it describes timing, not causes⁵.

If clicks on the new domain are still falling after the redirects check out, a diagnosis of the drop compares Search Console data around the launch date, URL by URL, before anything is changed.

When to hand the domain change over

If organic search brings your business inquiries or sales, hand over the steps that need a crawler or server access: the URL inventory, the crawl that tests every redirect and, when nobody on your side controls the old domain’s server, the redirect rules. Two routes fit a rebrand:

• Your developer or agency builds the new site. The SEO Migration Package, from $1,980 / £1,560, covers the inventory, the redirect map and the crawls around launch; the SEO-only packages set out the domain-change tier.
• The site runs on WordPress and you want the move done too. The URL-Verified Migration, from $2,990 / £2,390, moves the site to the new domain end to end.

For the year the redirects have to stay live, Weekly Redirect Guard, an add-on at $149 / £119 a month, re-crawls the signed inventory and flags any URL that stops reaching its mapped page. Plan the move before the new name is announced: the redirects, the Change of Address and the profile updates all switch on the same launch day.