What is a 302 Redirect in SEO?
6 min read
A 302 redirect (formally 302 Found in IETF RFC 9110, Section 15.4.3, and originally called Moved Temporarily in HTTP/1.0) is an HTTP redirection status code indicating that the target resource resides temporarily under a different URI. In technical SEO, a 302 redirect acts as a weak canonicalization signal that instructs Googlebot to follow the redirect for content retrieval while keeping the original source URL in the search index.
What is a 302 Redirect? (RFC 9110 Evolution & Core Mechanism)
Originally introduced in HTTP/1.0 (RFC 1945) as 302 Moved Temporarily and updated in HTTP/1.1 and RFC 9110 to 302 Found, this status code tells browsers and search engine crawlers: "The resource you requested is temporarily available at the URI in the Location header, so continue using the original URL for future requests."
Because the redirection is declared temporary, search engines do not immediately replace the original URL in search engine results pages (SERPs). Instead, Google retains the source URL in the index and anchors historical link equity (PageRank) to the original address until the temporary condition concludes.
How Google’s Canonicalization Pipeline Treats 302 Redirects
According to official Google Search Central documentation, Google does not treat redirects in isolation; it feeds them into its global canonicalization pipeline alongside canonical tags, XML sitemaps, and internal links:
- Short-Term 302 Behavior: Googlebot crawls the redirect target to understand the content, but keeps the original source URL indexed and displayed in search results.
- Long-Standing 302 Promotion (The Flip to 301): As confirmed by Google’s John Mueller, if a 302 redirect is left in place for an extended period (typically several months) or if all other site signals point exclusively to the destination URL, Google’s canonicalization system overrides the 302 hint and begins treating it as a permanent 301 redirect, indexing the destination URL instead.
- PageRank Preservation: While Google confirmed in 2016 that 3xx redirects do not suffer a mathematical PageRank decay penalty, using a 302 during a permanent domain migration causes severe indexing confusion, splitting ranking signals between the old and new URLs for weeks or months.
302 Found vs. 307 Temporary Redirect (And the Chrome HSTS 307 Mystery)
Technical SEOs inspecting redirects in Chrome DevTools frequently encounter 307 Temporary Redirect or 307 Internal Redirect and wonder how it differs from a 302:
| Redirect Type | Origin Layer | Protocol Behavior | SEO & Crawler Impact |
|---|---|---|---|
| 302 Found | Origin Server / CDN | Allows browsers to change POST requests to GET. |
Temporary redirect; retains source URL in Google index. |
| 307 Temporary Redirect | Origin Server / CDN | Strictly forbids changing HTTP method (POST stays POST). |
Treated identically to 302 by Googlebot for indexing. |
| 307 Internal Redirect | Local Browser Cache (HSTS) | Browser rewrites http:// to https:// locally via HSTS policy. |
Not a real server redirect; follow-up HTTPS request hits server directly. |
| 303 See Other | Origin Application | Explicitly redirects a POST submission to a GET confirmation URL. |
Used for checkout/signup flows; not indexed in search. |
Legitimate Use Cases for 302 Redirects in B2B SaaS
While 301 redirects should be used for 95% of SEO URL changes, a 302 redirect is the correct engineering choice in four scenarios:
- Server-Side A/B Split Testing (CRO): When routing 50% of visitors from
/pricingto a test challenger URL/pricing-variant-b. Using a 302 (paired with a canonical tag on Variant B pointing back to/pricing) ensures Google keeps your primary pricing URL indexed and prevents duplicate content issues. - Geo-Location or Language Banner Routing: Temporarily routing users based on IP headers while keeping the global canonical URL intact (though Google recommends non-intrusive locale banners over automatic IP redirects so Googlebot, which crawls primarily from U.S. IPs, can still access all regional versions).
- Gated Promotion or Waitlist Windows: Temporarily forwarding a feature URL to a launch webinar registration page for 72 hours before restoring the permanent product page.
- OAuth & SSO Authentication Flows: Redirecting unauthenticated users from
/app/dashboardto/loginvia 302 so browsers never permanently cache the login redirect.
B2B SaaS 302 Audit & Governance Checklist
Preventing Accidental 302 SEO Leaks
1. Override Default CMS / Framework Redirects: Many web frameworks (Express.js res.redirect(), PHP header("Location: ..."), and Apache Redirect without a status argument) default to HTTP 302 if you omit the status code! Always explicitly pass 301 for permanent moves.
2. Never Cache 302s Permanently: Ensure server Cache-Control headers on 302 responses are set to no-cache or a short max-age so browsers do not get stuck on a temporary test variant after an A/B experiment ends.
3. Crawl Production Routes Monthly: Filter your SEO audit crawl by 302/307 status codes to catch developers who accidentally used 302s when retiring old documentation or blog URLs.
Frequently Asked Questions
Why do PHP header("Location") and Express res.redirect() cause 302 SEO issues?
By default in both PHP and Node.js Express, calling a redirect function without explicitly specifying a status code automatically issues an HTTP 302 Found response. Developers frequently deploy permanent URL changes using default redirect functions without realizing they served a 302 instead of a 301.
Does a 302 redirect pass PageRank?
In the short term, PageRank stays anchored to the original redirecting URL because Google expects the original page to return. However, if a 302 remains active long enough for Google to treat it as permanent, PageRank consolidates at the destination URL.
Why do I see a 307 Internal Redirect in Chrome DevTools when I configured a 301?
A 307 Internal Redirect in Chrome DevTools is generated locally by your browser when your domain uses HSTS (HTTP Strict Transport Security). Chrome intercepts any http:// request and internally switches it to https:// before sending it over the network. Googlebot still sees your server-side 301 redirect.
How should I configure a 302 redirect for an A/B test without hurting SEO?
Use a 302 redirect to send test participants to the variant URL, place a rel="canonical" tag on the variant page pointing back to the original control URL, and never block the variant URL in robots.txt so Googlebot can read the canonical tag.