301 vs 302 vs 307 vs 308 Redirects for SEO

301 vs 302 vs 307 vs 308 Redirects for SEO

Redirects look simple: one URL sends visitors to another. For search engines, however, the status code explains whether the move is intended to be permanent or temporary. Choosing between a 301, 302, 307, and 308 redirect can influence which URL Google treats as canonical and which address it may continue to show in search results.

Google Search Central recently revisited these codes in its Non-Canonical Cabinet series. The practical lesson is not that one status is universally better. The correct choice depends on whether the original URL should return, whether the request method must be preserved, and whether the destination genuinely replaces the source.

What Google Says About Permanent And Temporary Redirects

Google’s redirect documentation groups 301 and 308 as permanent redirects. Googlebot follows them, and Google’s indexing systems use the redirect as a signal that the destination should be canonical. Use a permanent redirect when the move is not expected to be reversed.

The same documentation groups 302 and 307 as temporary redirects. Googlebot follows them, but the redirect is not used in the same way as a signal that the destination should replace the source as canonical. The destination can still be indexed when other signals support it, but the source URL may remain the preferred address in search.

StatusMeaningTypical SEO useRequest method
301Moved permanentlyPermanent URL replacement or migrationA client may change POST to GET
302Found, temporaryShort-lived campaign or service substitutionA client may change POST to GET
307Temporary redirectTemporary move when method must be retainedMust be preserved
308Permanent redirectPermanent move when method must be retainedMust be preserved

301 Versus 308: Permanent Moves

For ordinary page moves involving GET requests, a 301 and a 308 communicate the same permanent intent to Google Search. Google’s crawler guidance says that 308 is equivalent to 301 for Google. Both can support consolidation toward the destination when the rest of the site sends consistent signals.

The technical difference matters when forms, APIs, uploads, or other non-GET requests are involved. A 308 requires the client to preserve the HTTP method and request body. Historical client behaviour around 301 may convert a POST request into a GET. Engineering teams should choose deliberately rather than replacing every 301 with 308 without testing the application flow.

302 Versus 307: Temporary Moves

A 302 and a 307 both express temporary intent to Google. The source is expected to return, so Google may keep the source URL as the canonical address. This is useful for a short maintenance window, limited promotion, stock interruption, temporary regional route, or another reversible change.

A 307 explicitly preserves the original request method and body. A 302 may be handled more flexibly by clients and can change a POST to a GET. For a normal content page reached with GET, users may not notice a difference. For transactional or API routes, the distinction can affect whether the request continues correctly.

Choose The Code From The Business Decision

Start by asking whether the old URL will return. If a product, category, service, article, or domain has moved for good and the destination is a close replacement, use a permanent server-side redirect. If the change has a defined end date or the source will be restored, use a temporary redirect.

Do not use a permanent redirect simply because it sounds stronger. Likewise, do not leave a 302 in place indefinitely after a migration is complete. The status should match the actual decision. Record the owner, reason, launch date, expected duration, source, destination, and rollback plan in a redirect map.

Redirect To The Closest Relevant Destination

A redirect should preserve the user’s intent. Send an old service page to the replacement service, an expired product to a close successor, and a renamed article to its new URL. Redirecting every removed URL to the homepage creates a poor experience and can be treated as a soft 404 when the destination is not relevant.

Before implementation, inventory internal links, canonical tags, hreflang references, structured data URLs, navigation, feeds, and XML sitemaps. Update these references to point directly to the final destination. A professional SEO programme should treat the redirect as one part of a consistent set of canonical signals.

Avoid Chains, Loops, And Mixed Signals

A redirect chain sends users and crawlers through more than one hop, such as old URL to interim URL to final URL. Google’s site-move guidance recommends redirecting directly to the final destination and keeping unavoidable chains low. Each extra hop adds latency and creates another failure point.

Test for loops, destinations that return errors, protocol or hostname conflicts, and rules that catch more URLs than intended. Confirm that permanent redirects do not point to pages with a canonical back to the source. A technical SEO audit can identify chains and conflicting signals before or after a release.

Plan Redirects As Part Of A Migration

For a website migration, build a one-to-one map from valuable old URLs to relevant new URLs. Include indexed pages, traffic-driving landing pages, linked assets, campaign URLs, and pages with external links. Test the map in a staging environment, then crawl the live implementation after launch.

Update internal links and submit current sitemaps so crawlers discover the new structure efficiently. Monitor Google Search Console for indexing changes, unexpected not-found responses, and traffic shifts. SEO Shout’s website migration checklist covers the wider planning and ownership questions around a move.

Validate The Response, Not Just The Browser

A browser reaching the correct page does not prove that the implementation is correct. Inspect the first HTTP response and confirm the expected status code and Location header. Test desktop and mobile routes, query parameters, trailing slashes, uppercase variants, and both protocol and hostname versions where relevant.

Crawl a sample before launch and a complete list after launch. Keep dated evidence of results and monitor the rules over time. Remove obsolete temporary redirects when the source returns, and revise permanent rules when destinations change. For help reviewing a redirect map or migration, contact SEO Shout. Related on-page SEO work should update links and canonical signals so users and crawlers do not rely on redirects unnecessarily.

FAQs

Does Google treat 301 and 308 redirects differently?

Google treats both as permanent redirects. The HTTP difference is that a 308 requires clients to preserve the request method and body.

When should I use a 302 redirect?

Use a 302 when the move is temporary and the original URL is expected to return, provided preserving a non-GET request method is not required.

Can a redirect point every old URL to the homepage?

Avoid blanket homepage redirects. Each old URL should go to the closest relevant replacement; unrelated destinations can create a poor experience and soft-404 signals.

How many redirect hops are acceptable?

Redirect directly to the final destination whenever possible. If a chain cannot be avoided, keep it short and remove unnecessary intermediate hops.

How do I test a redirect correctly?

Inspect the first HTTP response, status code, and Location header. Also check the final response, loops, chains, query parameters, canonical tags, and internal links.

Does Google treat 301 and 308 redirects differently?

Google treats both as permanent redirects. The HTTP difference is that a 308 requires clients to preserve the request method and body.

When should I use a 302 redirect?

Use a 302 when the move is temporary and the original URL is expected to return, provided preserving a non-GET request method is not required.

Can a redirect point every old URL to the homepage?

Avoid blanket homepage redirects. Each old URL should go to the closest relevant replacement; unrelated destinations can create a poor experience and soft-404 signals.

How many redirect hops are acceptable?

Redirect directly to the final destination whenever possible. If a chain cannot be avoided, keep it short and remove unnecessary intermediate hops.

How do I test a redirect correctly?

Inspect the first HTTP response, status code, and Location header. Also check the final response, loops, chains, query parameters, canonical tags, and internal links.