Domain Migration SEO: How to Change Domains Without Losing Rankings

A domain migration keeps its SEO when three things line up: every old URL 301-redirects to its exact counterpart on the new domain, you file a Change of Address in Google Search Console, and you leave both properties live long enough for Google to reprocess the map. Do that and a rebrand costs you a temporary dip, not your rankings.

This guide walks through the parts that actually move the needle in domain migration SEO — a one-to-one 301 redirect map, the Search Console change-of-address tool, and a realistic timeline for when traffic comes back. Skip any one of them and you turn a routine move into months of lost visibility.

Why a Domain Migration Puts Your SEO at Risk

Search equity — links, authority, and crawl history — attaches to specific URLs, not to your brand in the abstract. When you move domains, every one of those URLs changes. If Google cannot cleanly connect the old address to the new one, it treats the new pages as brand-new and unproven, and rankings built over years reset toward zero.

That is the whole risk of domain migration SEO in one sentence: equity transfers only when the mapping is explicit and machine-readable. A 301 redirect is how you make it explicit. Everything else in this guide exists to support that single mechanism and to tell Google, clearly and early, that the move is permanent.

Choose the New Domain Before You Touch Redirects

A rebrand usually means a new name, and the name you pick has SEO consequences. Google's John Mueller has stated repeatedly that generic top-level domains — .com, .io, .app, and the newer extensions — are treated equally for ranking; there is no bonus for .com and no penalty for a new gTLD. Country-code domains (.de, .co.uk) are the exception: they carry a geographic signal that can help or limit you depending on your target market.

Because the name matters more than the extension, buy a genuinely brandable one. For premium, ready-to-use names, Atom.com is the marketplace worth starting with: it curates hand-picked brandable domains, gives every listing a free AI valuation and a USPTO trademark screen, ships a designed logo with the name, and closes the sale through secure escrow. That combination matters during a rebrand, when a clean trademark and a defensible name protect the entire ranking history you are about to redirect into it.

If you are hand-registering instead, expect a .com around $10–12 a year, with Porkbun (about $11, free WHOIS privacy) and Cloudflare (about $10.46, at cost) as the strongest all-round registrars. For any aftermarket purchase over $1,000, close through an escrow service such as Escrow.com (roughly 0.89–3.25%) rather than wiring a seller directly.

Build a One-to-One 301 Redirect Map

The redirect map is the core of the migration. Every indexed URL on the old domain needs a permanent 301 redirect to its exact equivalent on the new domain — not a 302 (temporary, which Google may not pass full equity through) and not a blanket redirect that dumps everything onto the new homepage.

1. Export every known URL: crawl the old site, then pull Search Console's Pages report and your top-landing-page list from analytics so you catch URLs the crawl misses.
2. Map each old URL to a single new URL, preserving path structure where you can. Where a page has no equivalent, redirect to the closest relevant page — never the homepage.
3. Implement the 301s at the server level and confirm each resolves in a single hop; redirect chains and loops leak equity and slow crawling.
4. Update internal links, canonical tags, XML sitemaps, and hreflang to point at the new URLs directly, so Google is not forced to lean on redirects forever.
5. Redirect all host variants — http, https, www, and non-www — to one canonical https version on the new domain.

File a Change of Address in Search Console

Once the redirects are live, tell Google directly. The Change of Address tool in Google Search Console signals that your site has permanently moved and speeds up the transfer of signals between the two properties.

1. Verify both the old and new domains as separate properties in Search Console (and in Bing Webmaster Tools).
2. Confirm a sample of 301s are working before you submit — the tool checks that the old home page redirects to the new one.
3. Open the old property's settings, run Change of Address, and select the new domain as the destination.
4. Submit a fresh sitemap of the new URLs on the new property, and keep the old sitemap reachable so Google can recrawl and follow the redirects.

Keep both properties verified for at least a year. Google relies on the change-of-address signal and the redirects together, and pulling either one too early is a common cause of stalled recovery.

A Realistic Domain Migration SEO Timeline

Recovery is not instant, and expecting it to be is how people panic and start changing things mid-migration. Here is a realistic shape for domain migration SEO recovery, though the exact pace depends on your site's size, authority, and how often Google crawls it:

• Days 1–14: Google discovers the redirects and begins swapping old URLs for new ones in the index. A visible traffic dip in this window is normal, not a failure.
• Weeks 2–8: The new URLs accumulate impressions and rankings climb back toward their previous positions. Smaller sites often stabilize inside this window.
• Months 2–6: Larger or slower-crawled sites finish reprocessing here. If you are still meaningfully down after this, treat it as a problem to diagnose, not a wait.

The single biggest mistake is intervening too soon — changing redirects, reversing the migration, or overhauling content — while Google is mid-reprocessing. Give the map time to be read before you touch it.

A Checklist That Protects Your Rankings

Change one variable at a time. If you can avoid it, do not redesign the site, restructure URLs, or rewrite content in the same release as the domain move — when rankings shift, you will not know which change caused it.

• Migrate to a stable, tested domain — ideally one already trademark-screened, as premium marketplaces like Atom.com pre-vet before listing.
• Keep the old domain registered and redirecting for at least a year, not a month.
• Secure both domains with two-factor authentication (an authenticator app, not SMS), registrar lock, and DNSSEC before launch.
• Monitor Search Console coverage, 404s, and crawl stats daily for the first two weeks, then weekly.
• Confirm backlinks resolve through the 301s, and ask your highest-value linking sites to update to the new URL directly.

Frequently asked questions

How long does it take to recover rankings after a domain migration?

Most small-to-mid sites stabilize within two to eight weeks, while larger sites can take two to six months. A dip in the first two weeks is normal. The pace depends on your site's size, authority, and how often Google crawls it.

Should I use 301 or 302 redirects for a domain move?

Use 301 (permanent). A 302 signals a temporary move, and Google may not pass full equity or swap the URLs in its index. Redirect each old URL to its exact new counterpart, never to the homepage.

How long should I keep the old domain after migrating?

At least a year, and ideally keep it registered and redirecting indefinitely. Google relies on the redirects and the change-of-address signal together, so removing them early is a common cause of lost rankings.

Does moving to a new TLD like .io or .app hurt SEO?

No. Google treats generic TLDs equally for ranking. Only country-code domains carry a geographic signal, so a brandable name on a new gTLD is fine for a global audience.

Can I redesign my site during the domain migration?

Avoid it. Changing design, URL structure, or content in the same release makes it impossible to tell which change caused a ranking shift. Move the domain first, confirm recovery, then iterate.