SEO Redirects: What Gets Broken and How to Fix It

An SEO redirect tells search engines and browsers that a URL has moved, either temporarily or permanently, and passes the user and any accumulated ranking signals to a new destination. Done correctly, redirects preserve organic equity across site migrations, consolidations, and URL restructures. Done carelessly, they quietly drain authority, slow page load times, and leave crawl budgets wasted on chains that go nowhere useful.

Most redirect problems are not dramatic. They accumulate slowly, buried in old site migrations and CMS updates, and they only become visible when rankings drop for no obvious reason.

Why Redirects Matter More Than Most Teams Realise

Redirects are one of those technical SEO topics that most marketing teams treat as an IT problem. Someone changes a URL, someone else raises a ticket, the developer adds a redirect, and everyone moves on. The issue is that this approach produces no coherent redirect architecture. It produces a graveyard of single decisions made in isolation, with no view of how they interact or accumulate over time.

I ran an agency for a long time. We inherited site migrations from previous agencies on a regular basis, and the redirect situation was almost always worse than the client knew. Not because anyone had been negligent, exactly, but because no one had ever treated redirects as something that needed ongoing ownership. The result was chains four and five hops long, loops that crashed certain crawlers, and 302s sitting on URLs that had not moved temporarily in three years.

The business cost of that is real. Rankings that should have transferred did not. Authority built over years on old URLs was sitting in a chain rather than reaching the destination. And because the symptoms look like a dozen other things, the root cause often goes undiagnosed for months.

If you are building or refining your approach to technical SEO, the Complete SEO Strategy hub covers the full picture, from crawlability and site architecture through to content and link signals. Redirects sit at the technical foundation, and getting them right makes every other element of the strategy easier to execute.

What Are the Different Types of SEO Redirects?

There are several redirect types, but three matter most for SEO practitioners.

A 301 redirect signals a permanent move. It passes the majority of the linking page’s authority to the destination URL and tells search engines to update their index accordingly. This is the correct choice for any URL that has permanently changed, any page that has been consolidated into another, and any HTTP to HTTPS migration.

A 302 redirect signals a temporary move. It does not reliably transfer link equity, and search engines will typically continue to index the original URL because the instruction is to treat the move as short-term. A 302 is correct when you genuinely intend to restore the original URL, for example during A/B testing or a short-term campaign. It is not correct for a URL you changed six months ago and have no intention of restoring.

A 307 redirect is the HTTP/1.1 equivalent of a 302 and carries the same temporary signal. It is technically more precise in certain server configurations, but for most SEO purposes the distinction between 302 and 307 is less important than the distinction between temporary and permanent.

There are also meta refresh redirects and JavaScript redirects. Both can be crawled and followed by Googlebot, but neither is as clean or reliable as a server-side redirect. Meta refreshes with a zero-second delay are treated similarly to 301s by Google, but they add render complexity and should be replaced with proper server-side redirects wherever possible. JavaScript redirects are the least reliable option and should only be used when server-side access is genuinely unavailable.

How Do Redirect Chains and Loops Damage SEO?

A redirect chain is what happens when URL A redirects to URL B, which redirects to URL C. Each hop in that chain introduces a small amount of signal loss. More importantly, Googlebot has a crawl budget. When it follows a chain, it is spending that budget on intermediate URLs that do not need to exist. On large sites, this is not a marginal concern.

A redirect loop is worse. URL A redirects to URL B, which redirects back to URL A. Googlebot stops. The user gets an error. Nothing reaches the destination. Loops are usually the result of conflicting redirect rules in different places, a .htaccess rule contradicting a platform-level redirect, for instance, or a CMS plugin overriding a server configuration. They are not always obvious from the front end, which is why crawl tools are essential.

When I was growing the agency from around twenty people to over a hundred, we had a period where our technical team was stretched thin and a junior developer had been managing redirects for a client’s e-commerce site through the CMS plugin rather than the server config. By the time we audited it properly, there were over two hundred chains, some of them five hops deep. The client’s category pages had lost meaningful ranking positions over the preceding six months. It took us three weeks to clean up a problem that would have taken three hours to prevent.

The fix for chains is straightforward: update the origin URL to point directly to the final destination. Not to the next hop in the chain. Directly to the end. This requires a full crawl of your redirect inventory, not a spot check.

How Should You Handle Redirects During a Site Migration?

Site migrations are the highest-stakes redirect scenario in SEO. A well-executed migration preserves rankings. A poorly executed one can take twelve to eighteen months to recover from, and some sites never fully recover.

The starting point is a complete URL inventory of the existing site before any work begins. Every URL that generates organic traffic, has inbound links, or appears in the sitemap needs to be in that inventory. This is not the developer’s job. It is the SEO team’s job, and it needs to happen before the migration plan is written, not during it.

From that inventory, you build a redirect mapping document. Old URL on the left, new URL on the right. For every single row. The mapping should be informed by traffic data, link equity, and content relevance. A high-traffic URL that maps to a loosely related destination is not a good redirect. It is a signal to search engines that the destination is something it is not.

There is a temptation during migrations to redirect everything to the homepage when a direct equivalent does not exist. Resist it. A redirect to the homepage from an old product page tells Google that the homepage is the best available match for that product query. It almost certainly is not. A 404 is often cleaner than a misleading redirect, though the better answer is to find the closest relevant destination or create it.

After launch, monitor crawl errors daily for the first two weeks. Google Search Console will surface 404s and redirect errors faster than any other tool. The window for fixing migration errors without lasting ranking impact is narrow, and the first two weeks are when you have the most leverage.

For anyone wanting a broader grounding in how technical decisions like these connect to overall search performance, Moz’s Whiteboard Friday on explaining SEO value is a useful reference point, particularly for teams that need to make the business case for migration investment to stakeholders who see it as a cost rather than a risk mitigation exercise.

What Happens to Link Equity When You Use a Redirect?

Google’s official position has evolved over the years. For a long time, the accepted rule of thumb was that a 301 redirect passed around 85 to 99 percent of link equity. Google has since indicated that a properly implemented 301 passes essentially full PageRank. But “essentially full” is doing a lot of work in that sentence, and the practical reality is that any redirect introduces some uncertainty.

What is not uncertain is that redirect chains reduce equity transfer at each hop. A single well-implemented 301 is as close to neutral as you can get. A chain of three 301s is not. And a 302 sitting on a URL that should be a 301 is not passing equity reliably regardless of chain length.

The other variable is time. When Google first encounters a redirect, it takes some time to fully consolidate signals. During that period, you may see ranking fluctuations that look alarming but are actually just the index catching up. The mistake is to interpret that volatility as evidence that the redirect is wrong and start making changes. Patience is underrated in technical SEO.

I judged the Effie Awards for a period, which gave me an unusual perspective on how marketing effectiveness gets measured and misread. The same problem shows up in redirect management. Teams see a ranking drop two weeks after a migration and conclude the redirects failed. Often the index just has not settled. The answer is to monitor for four to six weeks before drawing conclusions, not to start reversing decisions.

How Do You Audit Your Existing Redirects?

A redirect audit has three outputs: a list of chains, a list of loops, and a list of 302s that should be 301s. Everything else is secondary.

The tools most commonly used for this are Screaming Frog, Sitebulb, and Ahrefs Site Audit. Each will crawl your site and flag redirect issues. Screaming Frog is particularly useful because it lets you trace the full redirect path for any URL, which makes chain identification straightforward. Run the crawl with JavaScript rendering enabled if your site uses a JavaScript framework, because redirect behaviour can differ between the rendered and non-rendered versions.

Beyond your own site, check your inbound link profile. If high-authority external links point to old URLs that now redirect, those redirects need to be clean single-hop 301s. If they are chains, or if the destination has changed since the redirect was set up, the equity transfer is compromised. You cannot control what external sites link to, but you can control where those links end up.

Pair your crawl data with Google Search Console. The Coverage report will show you URLs that are returning redirect responses when they should be returning 200s, and the Links report will show you which redirected URLs still have significant inbound link equity attached to them. That combination tells you where to prioritise the cleanup.

For teams that want to add user behaviour data to their technical audit, Hotjar’s free tier can surface cases where redirects are creating visible friction in user journeys, particularly on mobile where redirect latency is more pronounced.

When Should You Use a Redirect Versus a Canonical Tag?

This is one of the most common points of confusion in technical SEO, and it matters because the two signals do different things.

A redirect moves the user and the crawler to a new URL. The original URL no longer serves content. A canonical tag tells search engines which URL is the preferred version for indexing, but the original URL remains accessible and continues to serve content to users.

Use a redirect when the original URL should not exist anymore. Use a canonical when you need multiple URLs to exist for functional reasons but want to consolidate ranking signals on one of them. Pagination, faceted navigation, and URL parameter variations are typical canonical use cases. Deleted pages, consolidated content, and restructured site architecture are redirect use cases.

The mistake I see most often is using canonicals as a substitute for redirects because it feels less significant. It is not less significant. It is a weaker signal that Google treats as a suggestion rather than an instruction. If a URL genuinely should not exist, redirect it. Do not canonicalise it and hope for the best.

There is also a version of this problem in the other direction: teams that redirect URLs they should have canonicalised, typically because they did not want to deal with the URL parameter logic. The result is that legitimate URL variations, filtered category pages for instance, return redirects instead of content, which breaks the user experience and creates unnecessary crawl overhead.

How Do You Handle Redirects for HTTPS Migration?

HTTP to HTTPS migration is now one of the most routine technical SEO tasks, but it still gets executed poorly more often than it should. The principles are the same as any migration, but there are specific failure modes worth knowing.

The most common error is redirecting HTTP to HTTPS at the root domain but leaving internal links pointing to HTTP URLs. This creates a redirect on every internal link click, which adds latency and creates unnecessary redirect hops throughout the site. After any HTTPS migration, update all internal links to point directly to the HTTPS versions. Do not rely on the redirect to handle it.

The second common error is implementing the HTTPS redirect correctly but leaving the XML sitemap pointing to HTTP URLs. Search Console will flag this, but it is better to catch it before submission. The sitemap should reflect the canonical HTTPS URLs from day one of the migration.

Mixed content warnings, where an HTTPS page loads HTTP resources, are not strictly a redirect issue but they often surface during HTTPS migrations and can affect how Google evaluates the page. A full mixed content audit should be part of any HTTPS migration checklist.

HSTS (HTTP Strict Transport Security) is worth implementing after a stable HTTPS migration. It tells browsers to always use HTTPS for your domain, which eliminates the initial HTTP request entirely for returning visitors and reduces redirect overhead. It is a server-level configuration and should be treated as a post-migration step rather than something to rush into before you are confident the HTTPS setup is stable.

What Is the Right Process for Managing Redirects Ongoing?

The single biggest improvement most teams could make to their redirect management is to treat it as a process rather than a series of one-off decisions. Every redirect that gets created should be logged. Every redirect log should be reviewed quarterly. And every CMS or platform update that touches URL structure should trigger a crawl before and after.

The logging requirement sounds basic, but it is not standard practice. I have worked with clients who had no record of why certain redirects existed, who had created them, or what the original URL had been ranking for. When you have no record, you have no ability to audit. You are managing a black box.

A redirect log does not need to be sophisticated. A shared spreadsheet with columns for the original URL, destination URL, redirect type, date created, reason, and owner is sufficient. The discipline is in maintaining it, not in the tool.

Quarterly reviews should check three things: chains that have formed since the last review, 302s that have been in place long enough to be treated as permanent, and redirects pointing to destinations that have themselves since moved or been deleted. That last category, redirects pointing to 404s, is a common source of silent ranking loss that only surfaces in a full audit.

There is a broader principle here that I think about often. The most sustainable thing marketing can do is stop funding work that should not exist. That applies to redirect sprawl as much as it applies to campaign activity. Every redirect in a chain that could be a direct link is work the server is doing for no reason. Every 302 that should be a 301 is equity that is not being transferred. The accumulation of small inefficiencies is what turns a technically sound site into one that underperforms its content and link profile.

For a complete view of how technical decisions like redirect architecture connect to your broader search strategy, the Complete SEO Strategy hub covers everything from site structure and crawlability through to content signals and competitive positioning. Redirects are one piece of a larger system, and they work best when the rest of the system is coherent.

Common Redirect Mistakes That Cost Rankings

To make this practical, here is a list of the redirect mistakes I encounter most often when auditing sites, in rough order of how frequently they appear and how much damage they cause.

Using 302 instead of 301 for permanent moves. This is the most common mistake and the easiest to fix. If the URL is not coming back, use a 301.

Redirecting to the homepage instead of a relevant destination. This is particularly common after content is deleted or restructured. A homepage redirect is almost never the right answer for a non-homepage URL.

Not updating internal links after a redirect is created. Every internal link that goes through a redirect is a redirect that does not need to exist. Update the link, remove the hop.

Creating redirects without checking for existing redirects on the origin. This is how chains form. Before creating a redirect from URL A, check whether URL A is already the destination of another redirect. If it is, update the origin of that redirect to point directly to the new destination.

Not monitoring redirect performance after a migration. The migration is not finished when the redirects go live. It is finished when you have confirmed that rankings have transferred, crawl errors are resolved, and the index reflects the new URL structure. That typically takes four to eight weeks of active monitoring.

Leaving redirect rules in multiple places. Platform-level redirects, .htaccess rules, CMS plugin redirects, and CDN-level redirects can all interact in ways that produce unexpected behaviour. Centralising redirect management in one place, wherever your infrastructure allows, reduces the risk of conflicts and loops.

The Search Engine Journal has covered the technical mechanics of redirect handling extensively over the years, and it remains a useful reference for teams working through the finer points of server-side implementation. For the SEO community’s longer view on how redirect best practices have evolved alongside Google’s crawling and indexing behaviour, Search Engine Land provides useful historical context on how Google’s handling of various signals has changed over time.

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