SEO Redirects: What Gets Broken Costs More Than You Think

An SEO redirect tells search engines and browsers that a URL has moved, either permanently or temporarily, and passes the user and any accumulated ranking signals to a new destination. Done correctly, redirects preserve the authority your pages have built over time. Done carelessly, they quietly drain it.

Most redirect problems are not dramatic. There is no single moment where rankings collapse. Instead, you lose a few percentage points of authority here, a crawl path there, and six months later you are wondering why organic traffic has softened and nobody can point to a cause. I have seen this pattern more times than I care to count, usually after a site migration that was treated as an IT project rather than an SEO one.

Why Redirect Type Is a Commercial Decision

The difference between a 301 and a 302 is taught in every introductory SEO course, but the commercial implications are still regularly ignored. A 301 signals a permanent move and passes the bulk of the page’s accumulated authority to the new URL. A 302 signals a temporary redirect and, in theory, tells search engines the original URL will return. In practice, Google has become better at interpreting 302s over time, but the safe position remains: if the move is permanent, use a 301.

Where I have seen this go wrong is in e-commerce. A product goes out of stock and a developer sets up a 302 to the category page as a holding measure. The product never comes back. The 302 stays in place for two years. The page had built genuine backlinks from review sites and comparison engines. All of that authority is sitting in a holding pattern, not being passed anywhere useful. Multiply that across a catalogue of discontinued products and you have a meaningful leak in your authority budget.

The fix is straightforward in principle: audit your 302s quarterly and make a deliberate decision about each one. Is this genuinely temporary? If not, convert it to a 301. If the product is gone permanently and there is no logical replacement, a 410 (content deleted) is often more honest than a redirect to a category page, though the right call depends on the backlink profile of that URL.

If you are building this kind of thinking into a broader SEO programme, the Complete SEO Strategy hub covers the full architecture of how technical decisions like redirect management connect to ranking outcomes and long-term organic growth.

Redirect Chains and Loops: The Slow Drain Nobody Notices

A redirect chain happens when a URL redirects to another URL that itself redirects, rather than pointing directly to the final destination. Chains are almost always the result of incremental site changes where nobody went back to update the original redirect. Version one of a page redirects to version two. Version two redirects to version three. The original redirect was set up eighteen months ago and nobody has touched it since.

Every hop in a chain costs something. There is a measurable reduction in the authority passed at each step, and there is a crawl cost because the bot has to follow multiple requests to reach the final URL. On large sites, this adds up. When I was running iProspect and we were managing enterprise SEO accounts, we would regularly find chains of four or five hops on sites that had been through multiple redesigns. The clients were always surprised. The chains had built up invisibly, one migration at a time.

The fix is to flatten every chain to a single redirect pointing directly to the live destination. This is a maintenance task, not a one-time project. Any time you change a URL that already has an incoming redirect, you need to update the source redirect to point to the new final destination rather than letting the chain grow.

Redirect loops are a more acute problem. URL A redirects to URL B, which redirects back to URL A. Browsers and crawlers will time out rather than follow the loop indefinitely, which means the page effectively does not exist from a search perspective. Loops are usually caught quickly because they produce visible errors, but they can be introduced by misconfigured HTTPS canonicalisation rules or botched www to non-www redirects, and they are worth checking explicitly after any server configuration change.

Site Migrations: Where Most Redirect Damage Actually Happens

If I had to identify the single most common source of serious SEO redirect errors, it would be site migrations. Not because migrations are inherently complex, but because they are routinely treated as development projects with SEO bolted on at the end. By the time the SEO team gets involved, the URL structure has already been decided, the redirects have been mapped by someone who has never looked at a crawl report, and the launch date is in two weeks.

I have been on both sides of this. Early in my agency career I accepted migration briefs where the client expected us to validate a redirect map that had been built without any reference to the existing site’s authority distribution. Pages with strong backlink profiles were being redirected to loosely related destinations. Pages that should have been consolidated were being kept as separate URLs. The map looked complete because every old URL had a corresponding new URL, but the logic was wrong.

A properly sequenced migration puts SEO requirements into the URL architecture decisions before development begins. The redirect map is built from a crawl of the live site, cross-referenced against backlink data and organic traffic data, so that high-value pages are mapped to genuinely equivalent destinations. The map is tested in staging before launch. Post-launch, crawl errors and traffic changes are monitored daily for at least four weeks.

The staging test is the step most often skipped. It adds time and requires co-ordination between SEO and development, but it is the only way to catch misconfigured rules before they go live. A redirect that works in isolation can break when it interacts with other rules in the htaccess file or the CMS routing logic. Testing in isolation is not enough.

For context on how redirect strategy fits into a migration plan alongside canonical tags, crawl budget management, and indexation controls, the Complete SEO Strategy hub is a useful reference point for the full scope of what a migration needs to cover.

HTTPS and www Redirects: The Basics That Still Get Missed

It should not still be necessary to write about HTTPS redirects in 2026, but the errors keep appearing in audits. The correct configuration is a single canonical version of your domain, consistently enforced: either HTTPS or HTTP (HTTPS), either www or non-www, and a 301 redirect from every other variant to that canonical version. Four variants of your homepage should resolve to one URL, not four different pages.

The problem is usually not that nobody set up the redirect. It is that the redirect was set up at the server level but the CMS is still generating internal links to the non-canonical version, or the sitemap still lists both variants, or old backlinks point to the HTTP version and the redirect chain has grown over time. Each of these is a separate issue but they compound each other.

Check your internal links. If your CMS is generating links to http://www.yourdomain.com and your canonical version is https://yourdomain.com, every internal link is adding an unnecessary redirect hop to every page load and every crawl. Fix the internal links at source rather than relying on the redirect to clean them up.

HSTS (HTTP Strict Transport Security) is worth implementing once your HTTPS configuration is stable. It tells browsers to always use HTTPS for your domain without needing to follow a redirect, which removes the redirect overhead entirely for returning visitors. It is a server-level configuration, not an SEO tactic specifically, but it has crawl and performance benefits that feed into ranking signals.

Handling Deleted and Consolidated Pages

Not every deleted page needs a redirect. This is a point that gets lost in the general instruction to “always redirect deleted pages.” The correct answer depends on whether the page had any meaningful authority, whether there is a logical destination to redirect it to, and how long ago it was last indexed.

A page with no backlinks, no organic traffic, and no internal links pointing to it can return a 404 without any SEO consequence worth worrying about. Redirecting it to the homepage or a tangentially related category page does not help users and does not pass authority in any meaningful way. It just adds noise to your redirect map.

Pages with genuine backlink profiles are a different matter. If a page has accumulated links from external sites, those links represent authority that can be preserved by redirecting to a relevant destination. The relevance matters. A redirect from a deleted blog post about email marketing to your homepage passes less value than a redirect to a related post on the same topic. Google has been explicit that relevance between the source and destination affects how much authority is transferred.

Content consolidation is a specific use case worth treating separately. When you have multiple pages covering the same topic at a shallow level, consolidating them into a single comprehensive page and redirecting the others can improve rankings for the consolidated page. I have seen this work well in practice, particularly for content that was created in volume without a clear topical architecture. The consolidated page outperforms the individual pages it replaced because the authority is concentrated rather than distributed across thin content. The redirect map in this scenario is part of the content strategy, not just a technical housekeeping task.

Soft 404s: The Problem Harder to Spot Than a Hard 404

A soft 404 is a page that returns a 200 OK status code but contains no meaningful content. The classic example is a search results page with no results, or a product page where the product has been removed but the template still renders with empty fields. From a user perspective, the page is useless. From a crawler perspective, it looks like a valid page because the server returned a 200 status, so it gets crawled and potentially indexed.

Soft 404s are more damaging than hard 404s in one specific way: they consume crawl budget without contributing anything to the index. A hard 404 is crawled, identified as an error, and deprioritised. A soft 404 keeps getting crawled because the server keeps saying everything is fine. On large sites with dynamic content, soft 404s can account for a significant proportion of crawl budget, which means high-value pages get crawled less frequently.

Google Search Console flags soft 404s in the Coverage report, which makes them detectable without a full crawl. The fix depends on the cause. If it is a product that no longer exists, the page should return a proper 404 or 410, or redirect to a relevant alternative. If it is a search results page with no results, consider blocking it from indexation via robots meta tag rather than serving it as a valid page.

The pattern I have seen most often is in e-commerce sites that use faceted navigation. Filter combinations that return no products generate unique URLs that return 200 status codes with empty product grids. Left unmanaged, these can run into tens of thousands of soft 404s on a mid-sized catalogue. The solution is usually a combination of canonical tags, robots directives, and in some cases, server-side logic that returns a proper 404 when the product count is zero.

Building a Redirect Audit Into Your Regular SEO Workflow

Redirects are not a one-time project. They require ongoing maintenance because sites change continuously and each change has the potential to introduce new redirect issues. The question is not whether to audit redirects but how frequently and with what scope.

For most sites, a quarterly crawl-based audit is sufficient for ongoing maintenance. The crawl should be configured to follow redirects and report on chains, loops, and broken redirects. Any chains longer than one hop should be flattened. Any 302s that have been in place for more than three months should be reviewed for conversion to 301s.

Before any significant site change, a pre-launch redirect audit should be mandatory. This means crawling the current site, exporting all URLs with their authority metrics, and mapping every URL that will change to its intended destination. The map should be reviewed by someone who understands the relationship between URL authority and redirect relevance, not just by a developer checking that every old URL has a corresponding new URL.

Post-launch monitoring should run for at least four weeks after any migration or significant restructure. Watch crawl error rates in Google Search Console, track organic traffic at the page level rather than just site-wide, and check that the redirect rules are behaving as expected in production rather than just in staging. The number of times I have seen a redirect map that worked perfectly in staging fail in production because of an interaction with a CMS plugin or a CDN caching rule is enough to make pre-launch testing feel insufficient on its own.

The tools that make this workflow manageable include Screaming Frog for crawl-based audits, Google Search Console for coverage and crawl data, and Ahrefs or a comparable backlink tool for identifying which URLs carry enough authority to warrant careful redirect planning. None of these tools give you a complete picture on their own, and this is worth remembering: the data from any single tool is a perspective on your site’s health, not a definitive diagnosis. Cross-referencing across sources is where the reliable picture emerges.

The Commercial Case for Getting Redirects Right

There is a tendency to treat redirect management as a technical hygiene task, something the SEO team handles in the background. The commercial framing is more useful. Every piece of link equity your site has accumulated represents real investment: content creation, outreach, PR, time. Redirects are the mechanism by which that investment is either preserved or lost when the site changes. A careless migration can write off years of authority accumulation in a single launch.

I spent a period judging the Effie Awards, where the entries are built around measurable business outcomes rather than creative executions. The marketing work that holds up under that scrutiny is always the work that treats every element of the programme as a commercial decision. Redirect strategy is no different. The question is not “did we redirect every old URL?” but “did we preserve the authority that drives the organic traffic that drives the revenue?” Those are different questions with different answers.

The sites that handle redirects well are usually the ones where SEO has a seat at the table before development decisions are made, not after. That is partly a structural question about how marketing and technology teams work together, and partly a question of whether the people commissioning site changes understand that URL structure and redirect logic are marketing assets, not just technical configurations.

If you are building the case internally for treating redirects as a commercial priority, the argument is straightforward: organic search typically delivers some of the highest-quality traffic a site receives, and redirect errors are one of the most preventable causes of organic traffic loss. The cost of getting it right is a fraction of the cost of recovering from getting it wrong.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions