Redirect Management: The SEO Guide to 301s, 302s, and Redirect Chains
Why Redirects Matter for SEO
Redirects tell search engines that a URL has moved. Done correctly, they preserve link equity and user experience. Done incorrectly, they leak authority, slow down your site, and confuse Google's crawler.
301 vs 302: When to Use Each
301 (Permanent Redirect)
Use when a page has moved permanently. This tells Google to transfer all ranking signals from the old URL to the new one and stop indexing the old URL.
Common scenarios:
- Changing your URL structure
- Consolidating duplicate pages
- After a domain migration
- When a product is permanently discontinued (redirect to closest alternative)
302 (Temporary Redirect)
Use when a page is temporarily unavailable and will return at the original URL.
Common scenarios:
- A/B testing with different URLs
- Temporary maintenance pages
- Seasonal content that comes back annually
- Geolocation-based temporary redirects
The Mistake
Using 302 when you mean 301 is one of the most common redirect errors. If you use a 302, Google may continue to index the old URL and not pass full link equity to the new one. When in doubt, use 301.
Redirect Chains: The Silent SEO Killer
A redirect chain occurs when URL A redirects to URL B, which redirects to URL C. Each hop in the chain:
- Loses a small amount of link equity
- Adds latency for users and crawlers
- Wastes crawl budget
After 3-4 hops, Google may stop following the chain entirely.
How to Find Redirect Chains
Run a crawl of your site using a tool like Screaming Frog or Zyptr's technical audit. Look for redirect chains longer than one hop.
How to Fix Them
Update the initial redirect to point directly to the final destination. If URL A redirects to B redirects to C, update A to redirect directly to C. Then update B to redirect directly to C as well.
Redirect Loops
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A. This creates an infinite loop that results in an error for both users and search engines.
These are usually caused by conflicting redirect rules in server configuration, CMS settings, or plugins operating on the same URLs.
Common Redirect Mistakes
Redirecting Everything to the Homepage
When you remove pages, redirect them to the most relevant remaining page, not the homepage. Mass redirecting to the homepage is treated by Google as a soft 404.
Not Updating Internal Links
After implementing a redirect, update all internal links to point to the new URL directly. This eliminates unnecessary redirect hops for your own pages.
Forgetting to Redirect After URL Changes
If you change a URL slug, you need a redirect from the old URL to the new one. Missing this creates a 404 that loses all the old page's accumulated authority.
Redirect Rules Conflicting with Canonical Tags
If page A redirects to page B, but page B has a canonical tag pointing to page C, you are sending conflicting signals. Ensure redirects and canonicals align.
Site Migration Redirect Checklist
During a site migration, redirects are critical:
- Map every old URL to its new equivalent
- Implement 301 redirects for all mapped URLs
- Create a catch-all redirect for unmapped URLs to the closest section
- Test every redirect before launch
- Monitor 404 errors daily for the first month after migration
- Keep redirects in place for at least one year