domain name change seo
Every URL on the site changes host at once. Nothing about a domain change is partial, which makes it the migration type with the least room for an incomplete redirect map.
Primary riskEvery historical signal has to be forwarded at once, with no partial credit for near-complete coverage.
Most migration types are partial. A replatform might leave URLs untouched. A design refresh might change only templates. A domain change is total: every URL on the site changes at the same moment, and every historical signal attached to those URLs has to be forwarded through a redirect.
There is no partial credit. A redirect map covering 95% of URLs means the remaining 5% lost everything, and those are usually the oldest, deepest, most heavily linked pages — the ones nobody remembers exist and other sites have been linking to for a decade.
Domain changes have one sequence that works, and the most common mistake is doing step five before step four.
Verify both properties in Search Console first. Change of Address requires both the source and destination to be verified, and verification propagation is not instant. Doing this a day before cutover creates avoidable pressure.
Get the redirects live and verified on the real host before filing Change of Address. The tool checks for a working sitewide redirect. Filing early either fails outright or produces a signal Google cannot act on.
Then hold. The instinct after a domain change is to start improving the new site. Resist it for a month. If you change content, structure and templates while Google is still processing the move, you will not be able to tell which change caused which effect — and something will always look like it moved in the wrong direction.
It announces the move. That is genuinely useful: it tells Google to treat the new domain as the successor rather than inferring it from redirect patterns alone.
It does not transfer anything by itself. If the redirects are wrong, filing the form does not fix them. If a page redirects to an irrelevant destination, Change of Address does not make that destination inherit the original page’s rankings. The redirects do the work; the tool sets the context.
It also only applies to full domain moves. It has no role in a protocol change, a subdomain-to-subfolder consolidation, or a URL restructure on the same domain — a point worth knowing before someone goes looking for it during a replatform.
After cutover, internal links in the codebase frequently still point at old-domain URLs. Everything works, because the redirects catch them.
That is the problem. Every internal navigation click now takes an extra hop, and crawlers spend budget traversing redirects instead of reading pages. On a large site this measurably slows how quickly the new URLs get discovered and processed.
Redirects exist for traffic you do not control. Your own internal links should point directly at their final destination. Fix them in the source, not at the redirect layer.
It usually is — a rebrand rarely changes only the name. If the URL structure is also changing, read URL structure change alongside this, because the mapping problem compounds. If two sites are merging into the new domain, site consolidation is the page that applies.
The full engagement covers all of these together, and the checklist sets out the phase gates in order.
What you see Traffic that was recovering suddenly disappears, and the old domain stops resolving. Referring links now point at nothing.
What fixes it Keep the old registration for at least a year, ideally indefinitely, on auto-renew with a named owner. It is the cheapest insurance in the whole migration.
What you see Deep pages on the old domain all land on the new homepage. Rankings for those pages disappear rather than transferring.
What fixes it Map URL to equivalent URL. Where no equivalent exists, redirect to the closest relevant category or return 410 deliberately — never a homepage catch-all.
What you see The tool rejects the request, or accepts it while Google finds no redirect and the signal does nothing.
What fixes it File it after the sitewide redirect is verified and both properties are verified in Search Console. Order matters here.
What you see Every internal navigation click takes an extra hop. Crawl budget drains into redirects instead of pages.
What fixes it Rewrite internal links to the new domain in the codebase, not just at the redirect layer. Redirects are for external traffic, not for your own navigation.
| Stage | Action | Timing | Must be true before moving on |
|---|---|---|---|
| Prepare | New domain verified in Search Console as its own property | 2–4 weeks before | Both old and new properties verified and collecting data |
| Map | One-to-one redirect map covering every URL with traffic or links | 2–6 weeks before | No URL in the priority tiers lacks a named destination |
| Lower TTL | DNS TTL reduced so the cutover propagates quickly | 48 hours before | TTL is at 300 seconds or lower and has propagated |
| Cut over | New domain live, redirects active on the old host | Launch window | Sampled redirects return one hop to a 200 on the live host |
| Signal | Change of Address filed in Search Console | Within 24 hours of cutover | Sitewide redirect verified, both properties verified |
| Hold | Old domain and its redirects kept live | At least 12 months | Renewal is set to auto and someone owns the registration |
Run these before the cutover window, not during it.
Old and new domains each verified as domain properties, both collecting data before the move. Change of Address requires this and it takes time to propagate.
Output Two verified properties
Every priority URL tested individually for final status code and hop count. Pattern rules are not evidence that a specific URL resolves.
Output Redirect test results
Canonical tags on the new domain must point at the new domain. A canonical still referencing the old host will keep signals pinned to a site you are trying to retire.
Output Canonical audit
Drop TTL to 300 seconds so the cutover propagates in minutes rather than hours, and so a rollback is fast if one is needed.
Output TTL confirmed at the registrar
Redirects carry most of the signal, but the top few referring domains are worth an email asking for a direct link update. It is an afternoon for a permanent gain.
Output Outreach list with status
Expect volatility for four to twelve weeks. Larger sites take longer because Google has to recrawl more URLs to discover the move. A complete redirect map and a filed Change of Address shorten it; an incomplete map extends it indefinitely for the pages that were missed.
At least twelve months, and ideally forever. The registration costs a few dollars a year and the redirects continue to carry value from old external links for far longer than most people expect. Letting it lapse discards signal permanently.
For a full domain move, yes. It tells Google explicitly that the site has moved, which speeds up processing. It does not replace redirects — the redirects carry the signals, the tool announces the intent. File it after the sitewide redirect is live and verified.
No, if you can avoid it. Changing two variables at once makes any traffic drop impossible to diagnose. Move the domain with content and structure held constant, confirm recovery, then make content changes. Sequencing costs weeks and saves months of guessing.
Send the launch date and what is changing. We will tell you which parts of this page apply to your situation and which do not.