Migrating a domain without losing six months of rankings

Changing domains, whether from a rebrand, a business acquisition, or simply moving to a better name, is the single highest-risk event a site's SEO can go through. Even a well-executed migration carries some temporary ranking volatility while search engines reprocess the change, and a poorly executed one can genuinely cost months of accumulated authority. The process matters enormously here.

Every indexed URL on the old domain needs an individually mapped 301 redirect to its specific equivalent on the new domain, not a single wildcard rule redirecting everything to the new homepage. This is the single most important, most commonly rushed step, and skipping proper individual mapping is the most common cause of migrations that lose significant traffic.

For domain changes, Google Search Console has a dedicated change-of-address tool that explicitly signals the migration, which helps the process along faster than relying on redirects and re-crawling alone. This is a step some teams skip entirely simply because they don't know it exists, and it's a free, direct way to communicate the change.

Beyond redirects, update the URL everywhere you have direct control: social media profile links, email signatures, business directory listings, any co-marketing partner links you can reasonably ask to be updated. Redirects handle the technical case, but consolidating direct, non-redirected links to the new domain reinforces the signal and reduces long-term dependency on the redirect chain.

We avoid migrating during a site's known high-traffic season if at all possible, since any temporary volatility during peak business periods carries higher real cost than the same volatility during a slower period. If a specific launch date is tied to a business event and can't move, we build in extra pre-launch testing time to reduce the odds of a technical redirect error compounding the already-expected temporary dip.

A well-executed migration typically shows a temporary dip followed by recovery to prior levels within several weeks to a couple of months, as search engines fully reprocess the new domain's signals. A migration still showing significant traffic loss well beyond that window usually indicates a real redirect mapping gap or technical error worth auditing immediately, not more patience.

Rather than testing redirects for the first time on the live new domain, we build a full redirect map and test it against a staging environment first, verifying every mapped redirect actually resolves correctly, no redirect chains (a redirect pointing to another redirect rather than the final destination), no accidental redirect loops, and correct status codes throughout. This pre-launch verification catches the large majority of mapping errors before they ever reach a real visitor or search engine crawler, and it's a meaningfully different risk profile than discovering a broken redirect chain after the new domain is already live and search engines have already started crawling it.

We also specifically test redirects for URL parameters and edge cases, a product page with a tracking parameter appended, a paginated URL, a filtered category view, since these variations are easy to miss in a redirect map built only from the primary indexed URL list, and they can represent a meaningful share of real incoming traffic that a simpler mapping approach would silently break.

A domain migration touches more parts of a business than the SEO team alone usually realizes upfront: customer support needs to know old bookmarked links might redirect differently, sales needs updated materials with the new domain, and any internal tools or automations referencing the old domain need updating too. We run a short internal stakeholder check before any migration to surface these dependencies, since an SEO-perfect migration that breaks an internal sales tool or confuses a support team fielding customer questions about a changed URL is still a rough launch experience, even if the search rankings themselves recover cleanly.

A common question from clients is how long the old domain needs to stay registered and redirecting after a migration, and the honest answer is longer than most people expect: we recommend keeping 301 redirects live for a minimum of one to two years, not the few months it might take for search rankings to visibly recover, since backlinks pointing to the old domain from other sites, external references in old content, and even bookmarks saved by real users can keep sending traffic to old URLs for a surprisingly long time after the migration itself is technically complete and rankings have stabilized. Letting the old domain lapse or removing redirects too early quietly cuts off this long tail of residual traffic and link equity, an easily avoidable loss for the relatively small ongoing cost of maintaining domain registration and redirect rules.

For particularly high-authority old domains with a long backlink history, we sometimes recommend keeping redirects live indefinitely rather than setting a hard expiration date at all, treating the old domain as permanent infrastructure rather than a temporary bridge, since the ongoing cost is minimal compared to the risk of losing accumulated authority that took years to build in the first place.

The first two weeks after a domain migration get the closest monitoring of any point in the process: daily checks of Search Console for crawl errors, daily spot-checks of key page rankings for the most important target queries, and daily verification that redirect rules haven't been accidentally altered by an unrelated deployment or configuration change elsewhere on the site. This tight monitoring window is when a real problem, if one exists, is most likely to be both detectable and still cheaply fixable, and we'd rather catch a mapping gap on day three, when correcting it costs an hour of work, than discover it during a monthly review six weeks later, when the same gap has already cost real, harder-to-recover traffic.