Rebranding without losing existing SEO equity

A rebrand often comes with a new domain, a new URL structure, or both, and that's exactly the kind of change that puts years of accumulated search rankings at risk if it's not sequenced carefully. We've inherited more than one rebrand where organic traffic dropped by half in the weeks after launch, entirely avoidably, because redirects were an afterthought rather than part of the plan from day one.

The frustrating part is that almost none of this risk is inherent to rebranding itself. Search engines don't penalize a business for changing its name or its visual identity. They penalize broken paths: a URL that used to return real content now returning a 404, or a redirect chain so long the crawler gives up following it. Nearly every traffic drop we've cleaned up after a rebrand traces back to one of those two mechanical failures, not to anything about the new brand itself.

Before any new page goes live, we build a complete map from every existing indexed URL to its new equivalent. This isn't a nice-to-have, it's the single most important technical step in a rebrand, and skipping it is the most common cause of the traffic drops we've had to clean up after the fact.

We pull this list from three sources cross-checked against each other: the existing XML sitemap, a full crawl of the live site, and Search Console's own index coverage report, since any one of those three alone tends to miss URLs the others catch. A page that's indexed but no longer in the sitemap, an orphaned page nobody linked to recently but that still gets organic traffic, is exactly the kind of thing that falls through the cracks when the mapping exercise only checks one source.

Every old URL needs a permanent (301) redirect to its specific new equivalent, not a temporary (302) redirect and not a blanket redirect sending every old URL to the new homepage. A blanket homepage redirect is the single most damaging mistake we see: it tells search engines none of the old pages have a real replacement, and rankings for all of them can evaporate rather than transfer.

A 302 is a subtler version of the same mistake. It signals to search engines that the move is temporary, so ranking signals are held rather than transferred, which can leave a site in ranking limbo for weeks after a launch that was never actually temporary. We've had to fix this on inherited rebuilds where a developer used 302s by default simply because it was the framework's default redirect type, with nobody realizing the SEO implication until traffic had already dropped.

The first two weeks after a domain or URL structure change are when problems surface: crawl errors, unexpected 404s, redirect chains that got missed in the mapping. We check Search Console daily during that window specifically, rather than the usual weekly cadence, because catching a broken redirect on day two is a five-minute fix and catching it on day twenty is a much larger recovery project.

We also keep the old domain's Search Console property active and monitored for at least six months after the switch, even once it's fully redirected, because Google continues reporting against it during the transition period and that data is often the fastest way to spot a redirect that's silently failing for a subset of URLs.

Redirects preserve most of a backlink's value, but not all of it, so reaching out to a handful of high-authority sites linking to your most important pages and asking them to update the link directly is worth the effort for the top few, even though it's not worth doing at scale for every link in a backlink profile. We prioritize this outreach by the actual authority and traffic value of the linking page, not by how easy the site is to contact.

The same logic applies to business directories, industry citations, and any partner site listing the old brand name and domain. These rarely carry huge individual SEO weight, but a rebrand is also a trust and consistency exercise, and a prospective customer finding the old brand name on a partner's site months after the new brand launched is a worse experience than the marginal ranking impact would suggest on its own.

Even a well-executed rebrand typically shows a temporary dip in rankings and traffic for two to six weeks while search engines recrawl and reprocess the new URL structure, before recovering to at least the prior baseline. We tell clients this up front, with the actual data from past rebrands we've run, specifically because an unexpected dip during that window, even a normal and expected one, can trigger panic and a rushed, poorly considered change that makes the real recovery slower.

The clients who handle this best are the ones who agreed in advance on what "normal" looks like during that recovery window, so a week-two dip gets checked calmly against the redirect map and crawl reports rather than treated as evidence something went wrong. Nine times out of ten, the dip is exactly what we told them to expect, and the tenth time is exactly what the daily Search Console monitoring exists to catch early.

We've found it worth putting a specific number on this expectation rather than a vague warning. Telling a client to expect "some fluctuation" invites panic at the first sign of any dip at all. Telling them to expect organic traffic to sit ten to twenty percent below baseline for roughly a month before recovering gives them an actual threshold to check against, and it's a much calmer conversation when the real numbers land inside that range instead of outside it, rather than a scramble to explain an unexpected drop after the fact.