A website redesign is one of the few marketing projects that can undo years of search visibility in a single afternoon. Not because the new design is worse, but because the new site almost never uses the same URLs as the old one. Pages get renamed, sections get consolidated, a blog moves from /news/ to /blog/, and every link and every stored search engine record that pointed at the old address now points at nothing.
Redirects are the mechanism that carries that history forward. They are also the part of a launch that gets handed to whoever is available at the end of the project, which is how sites lose rankings they spent years earning. Here is what redirects actually do, where the mistakes happen, and the sequence that keeps a redesign from costing you traffic.
What a redirect actually tells a search engine
When a browser or a crawler requests a URL, the server answers with a status code before it sends any content. A 200 means “here is the page.” A 404 means “there is nothing here.” A redirect status — 301, 302, 307, 308 — means “the thing you asked for lives somewhere else, go there instead,” and includes the new address.
For a visitor, every redirect type behaves identically: the browser follows it and the new page loads. For a search engine, the number matters, because it determines what happens to the accumulated signals attached to the old URL. Google’s documentation on redirects and Google Search describes permanent redirects as a strong signal that the redirect target should be the canonical URL — meaning the old address is retired and the new one inherits its place in the index.
That inheritance is the entire point. The links other sites built to your old service page, the fact that the URL has been requested and crawled for years, the relevance the page established for particular queries — a permanent redirect is how you tell Google to move all of that to the new address rather than start over.
301 and 302 are not interchangeable
A 301 is a permanent redirect. A 302 is temporary: it tells a crawler the original URL is still the real one and will be back, so keep the old URL indexed and do not transfer canonical status to the destination.
The distinction matters because many content management systems and plugins will happily issue a 302 when you are not paying attention, and because a 302 does exactly the wrong thing during a permanent move. Google is reasonably good at inferring intent — if a 302 stays in place indefinitely, it will often be treated as permanent eventually — but “eventually” is not a launch plan, and relying on it means the search engine is guessing at something you could simply have declared.
The correct use for a 302 is genuinely temporary: a product page pulled for a week, a location page down while a suite is renovated, a test routing part of your traffic elsewhere. If the old URL is never coming back, use a 301. In practice this is a one-line difference in a redirect rule or a dropdown in a plugin, and it is worth checking rather than assuming.
The redirect map is the part people skip
The failure mode is rarely a wrong status code. It is a missing redirect — an old URL nobody remembered to account for, now returning a 404.
A redirect map is a two-column list: every URL that existed on the old site, and the URL on the new site that replaces it. Building one means pulling old URLs from more than one source, because no single source is complete. An XML sitemap only lists what the old CMS knew about. A crawl of the live site only finds pages that are linked internally. Server logs and Search Console’s page indexing report will surface URLs that receive traffic but were orphaned years ago — the intake form someone links to from a referral partner’s site, the old landing page still printed on a brochure.
Every one of those URLs needs a destination. Where a direct equivalent exists, map it there. Where three thin pages were consolidated into one strong page, map all three to the new page. Where content was genuinely retired with no replacement, a 404 is an honest answer — but that should be a decision you made, not one that happened to you.
Chains, loops, and the homepage shortcut
Two patterns cause trouble after the map is built.
The first is the redirect chain: URL A redirects to B, which redirects to C. Chains accumulate naturally across successive redesigns, because each launch adds a layer of rules on top of the last. Every hop adds latency for the visitor, and long chains risk a crawler abandoning the path before it reaches the destination. When you launch, update the old rules so that A points directly at C. A loop — A to B, B back to A — is the more severe version, and it makes the page unreachable for everyone.
The second is redirecting everything to the homepage. It is tempting because it is fast and eliminates 404s in one rule. It also destroys the value you were trying to preserve. Google treats a redirect to an irrelevant destination as a soft 404 — functionally the same as the page not existing — so a blanket homepage redirect throws away the signals from every mapped URL while producing a worse experience for anyone who clicked expecting specific content. Map to the closest relevant page, or let it 404.
What redirects do not fix
Redirects handle the address change. They do not handle everything else a redesign changes.
Internal links should be updated to point at the new URLs directly, not left pointing at old addresses that happen to redirect. Canonical tags on the new pages should reference the new URLs; a canonical left pointing at a retired address sends a contradictory signal, and Google’s guidance on consolidating duplicate URLs covers how those declarations interact. Your XML sitemap should list only the new, live URLs — a sitemap full of redirecting addresses wastes crawl attention and muddies the signal you just spent a week getting right.
Structured data, page titles, and body content also travel with the redesign, and a new template that drops the schema markup or truncates every title tag will cost you regardless of how clean the redirect map is. Titles beyond roughly 60 characters tend to get truncated in the search result, and a new template that prepends a long brand name to every title can push the distinguishing part of the title out of view across the entire site at once.
A launch sequence that holds up
Before launch, crawl the old site and export every URL, cross-reference against Search Console and server logs, and build the map. Have someone who did not build it review the rows for pages mapped to obviously wrong destinations. Confirm the rules produce 301s and not 302s, and test a sample against the staging environment.
At launch, spot-check the highest-value URLs by hand — your core service pages, your best-performing blog posts, anything with external links pointing at it. Check the status code, not just whether the page loads, because a page that loads after three hops still needs fixing. If you are also changing domains, submit the move through Search Console’s Change of Address tool; Google’s site move documentation walks through the sequence and what to expect afterward.
In the weeks after, watch the page indexing report for a rise in 404s and soft 404s, and work through them as they appear. Keep the redirect rules in place indefinitely. There is no expiration date at which it becomes safe to remove them, and old links keep sending people for years.
Why this matters more in some industries
For behavioral health and treatment providers, the pages at risk are usually the ones that took longest to earn: program pages, clinician bios, insurance and admissions information. These are the pages referral partners and directories link to, and those inbound links are difficult to rebuild once broken. A redesign that quietly 404s a program page can remove a provider from consideration at exactly the moment a family is searching.
Industrial and B2B manufacturers face a similar problem with a different shape: deep catalogs of product and specification pages whose URLs get pasted into customer documentation and purchasing systems. Those addresses need to keep resolving long after the redesign.
None of this makes a redesign a bad idea. A slow, dated, hard-to-navigate site costs more than a careful migration does. The point is that the redirect map deserves the same attention as the visual design, and it should be built during the project rather than the night before launch.
If you are planning a rebuild, our web design and SEO services teams plan migrations together for this reason. And because AI-driven search surfaces increasingly cite specific URLs, keeping those addresses stable matters for answer engine optimization as well.
