SEO Redirects: Best Practices for 301, 302 & Site Migrations

A redirect is often treated as a purely technical detail, but from an SEO standpoint it's a signal — a claim you're making to search engines about whether a URL change is permanent or temporary, and which address should own that content's rankings going forward. Getting that signal wrong is one of the more common, avoidable technical SEO mistakes.

This guide covers how redirects actually affect SEO, where the real risk comes from (it's rarely the redirect itself), and how to use them correctly across chains, migrations, and everyday link changes.

What Are SEO Redirects?

"SEO redirects" isn't a distinct technical mechanism — it's shorthand for using ordinary HTTP redirects (301, 302, 303, 307, 308) deliberately, with their effect on search engines in mind, rather than just as a way to route traffic. The mechanics don't change based on intent, but the outcome does: the same 301 that quietly sends a visitor to a new page is also the thing telling Google which URL should be indexed from now on.

For a full breakdown of what each status code does mechanically, see our types of redirects guide.

When Redirects Matter for SEO

Not every redirect carries the same weight. A few situations are where getting the redirect right actually matters for search visibility:

• Permanent URL changes — renaming a page, restructuring a URL path, or consolidating duplicate content.
• HTTP → HTTPS migrations, where every URL on the old protocol needs to point at its HTTPS equivalent.
• Domain and site migrations, where an entire site's worth of URLs needs to map to new addresses. See our domain redirect guide for the domain-level version of this.
• Removed or merged pages, where the redirect target needs to be a genuinely relevant substitute, not a default fallback.

A single, well-configured redirect for any of these is a normal and safe part of running a site — the goal isn't to avoid redirects, it's to make sure each one sends the signal you actually intend.

301 Redirects and SEO

A 301 is the default choice whenever a URL change is meant to last. Google's documentation on redirects states that for a 301 (or 308), its indexing pipeline "uses the redirect as a signal that the redirect target should be canonical." That's the mechanism behind the common shorthand "301s pass SEO value" — it's not that ranking power is transferred like a fixed quantity, it's that Google shifts which URL it treats as the authoritative one to index and rank.

The most common mistake here isn't misusing a 301 — it's using something else (usually a 302) for a change that's actually permanent, which is covered next.

For the full picture on 301s specifically — mechanics, examples, and implementation — see the 301 redirect guide.

302 Redirects and SEO

A 302 signals a temporary move, and Google's indexing pipeline deliberately does not treat it as a canonicalization signal — the original URL generally keeps that status while a 302 is in place. That's correct and expected behavior for a genuinely temporary change, like a seasonal campaign page.

The real SEO risk shows up when a 302 is used for a change that's actually permanent. The redirect keeps telling search engines "this might not be final," which can leave the old URL treated as canonical for far longer than intended — sometimes indefinitely, if the 302 is never revisited or converted to a 301.

For the full breakdown of 302 behavior and when it's the right call, see the 302 redirect guide; for the complete decision framework between the two, see 301 vs 302 redirect.

Redirect Chains and SEO

A redirect chain — a URL that passes through one or more intermediate hops before reaching its final destination — is a common byproduct of a site that's changed URLs more than once over time. Google's crawl budget documentation advises site owners to "avoid long redirect chains, which have a negative effect on crawling." That's the specific, current guidance; Google doesn't publish a percentage impact or a maximum hop count that makes a chain officially "too long."

What is clear from Google's separate site-move guidance is a practical target for migrations specifically: keep the number of redirects in any single chain low — ideally no more than three, and fewer than five. Beyond crawl efficiency, every additional hop adds latency for real visitors and gives you one more rule that has to stay correct.

See our redirect chain guide for a full walkthrough of what causes chains and how to shorten them.

Redirect Loops and SEO

A redirect loop is a more severe version of the same underlying problem — instead of taking a long path to a real page, the request never reaches one at all. A URL stuck in a loop can't be crawled, indexed, or ranked while the loop persists, because there's no actual content for a crawler to evaluate.

This is a different failure mode from a chain: a chain is inefficient but still resolves; a loop is a hard failure. If you're seeing a browser error like ERR_TOO_MANY_REDIRECTS, see our too many redirects troubleshooting guide for the diagnostic sequence.

Internal Links and Redirects

Redirects are meant to catch traffic and link equity aimed at an old URL — they aren't a substitute for updating the links you control yourself. Every internal link still pointing at a redirected URL forces visitors and crawlers through an extra hop on every single visit, even after the redirect itself is configured correctly.

After any URL change, review internal links and update them to point directly at the current URL. ProURLMonitor's Internal Linking Assistant can help surface existing content that still references outdated URLs so you can fix them at the source rather than relying on the redirect to paper over it indefinitely.

Website Migrations and Redirects

A full site or domain migration is where redirect mistakes tend to compound, because a single misconfigured rule can affect thousands of URLs at once instead of just one. Google's own site-move documentation is specific about what a migration needs:

• Server-side permanent redirects from every old URL to its new equivalent — Google's guidance is explicit that changing DNS alone is not sufficient, since DNS only routes traffic to a server, it doesn't tell search engines or browsers that a specific page has moved.
• A complete URL mapping, ideally one-to-one, rather than blanket-redirecting everything to a single new URL like the homepage.
• Redirects kept in place for at least a year, per Google's guidance, to give ranking signals time to fully transfer — and longer where practical, since old backlinks and bookmarks don't expire on a schedule.
• Sufficient server capacity on the new site to handle traffic during the transition, and separately verified old and new properties in Search Console.

For the domain-specific version of this — including the DNS vs. HTTP redirect distinction — see our domain redirect guide.

Redirect Best Practices for SEO

• Match the status code to the actual intent — permanent changes get a 301 (or 308 if method preservation matters), temporary ones get a 302 (or 307/303 for their specific cases).
• Redirect to the most relevant available page, not a default fallback like the homepage.
• Keep chains as short as possible — ideally a single hop, and never more than a handful even during a migration.
• Update internal links to the current URL instead of relying on the redirect to catch every visit indefinitely.
• Keep permanent redirects in place long-term — removing one too early can strand backlinks and bookmarks that haven't caught up yet.
• Audit redirects periodically, especially after a migration, a CMS change, or a bulk rule update, since it's easy for the wrong status code to slip in unnoticed.

How to Audit Redirects

A redirect audit doesn't require guessing at server configuration — it requires checking actual behavior. ProURLMonitor's Redirect Checker requests a URL, follows its full redirect path, and reports the status code, destination, and any protocol change at every hop.

1. Compile a list of URLs worth auditing — recently migrated pages, redirected domains, and any URLs known to have changed.
2. Run each through the Redirect Checker.
3. Confirm the status code matches the intent (permanent vs. temporary) for each redirect.
4. Flag any chain longer than a single hop, and any loop.
5. Confirm each destination is genuinely relevant to the original URL's content, not a generic fallback.
6. Re-check periodically, particularly after any server, CDN, or CMS configuration change.

Frequently Asked Questions

How do redirects affect SEO?

Redirects tell search engines whether a URL change is permanent or temporary, which determines which URL gets treated as canonical. A 301 or 308 signals the destination should become canonical; a 302, 303, or 307 signals the original URL should keep that status. Using the wrong type for a given situation is what actually causes SEO problems, not redirects in general.

Do redirects hurt SEO?

Not inherently. A correctly configured redirect to a genuinely relevant destination is a completely normal, safe part of running a site. What causes real SEO issues is a redirect to an irrelevant page, an unnecessarily long chain of redirects, a redirect loop, or the wrong permanence signal (a 302 for a permanent change, for example).

Should I use 301 or 302 redirects for SEO?

Use a 301 for any change that's genuinely permanent — it tells search engines to treat the new URL as canonical. Use a 302 only when the change is truly temporary and the original URL is coming back. Defaulting to 302 for a permanent change is one of the most common SEO redirect mistakes, since it can delay the new URL from being treated as canonical.

How long should redirects stay in place during a migration?

Google's own site-move documentation recommends keeping redirects in place for at least a year to let ranking signals fully transfer, and suggests keeping them indefinitely from a user's perspective, since old bookmarks and external backlinks can keep pointing at the original URLs long after a migration.

Do redirect chains hurt SEO?

Google's crawl budget documentation advises avoiding long redirect chains because they have a negative effect on crawling — it doesn't publish a specific number or ranking penalty. Beyond crawling, every extra hop adds latency for real visitors and makes a site's redirect setup harder to maintain and audit.

How do I audit redirects on my site?

Run your important URLs — old pages, migrated sections, redirected domains — through a redirect checker and review the status code, destination, and number of hops for each one. Look specifically for inconsistent status codes, unnecessary chains, redirects to irrelevant pages, and any loops that prevent a URL from resolving at all.