What is a 302 Redirect?

302 Redirect: temporary relocation without permanent commitment

A 302 redirect tells clients the requested resource is temporarily available at another URL. The original URL remains the conceptual "home" address; crawlers and browsers should not assume the move is permanent.

In SEO workflows, 302 is often misapplied. Marketing launches a "permanent" new URL but CMS defaults emit 302. Six months later, both URLs linger in indices and analytics splits traffic. Understanding when 302 is correct—and when it is a bug—prevents signal dilution.

302 response structure

GET /summer-sale HTTP/1.1
Host: example.com

HTTP/1.1 302 Found
Location: https://example.com/promotions/summer-2026
Content-Length: 0

The browser follows to the promotion page. Unlike 301 Redirect, the ecosystem should expect /summer-sale to matter again after the campaign ends.

302 vs 301: the SEO distinction

Google's John Mueller has noted that very old 302s may be treated like permanent redirects because the temporary signal erodes when nothing changes for years. That is not a substitute for correct HTTP semantics at launch.

Appropriate uses of 302 redirects

Seasonal and campaign URLs

/black-friday 302s to the current year's event hub each November, then the short path goes dormant or 302s elsewhere next season.

Maintenance and failover

Origin issues trigger temporary 302 to a status page or mirror. Restore 200 on the primary when healthy.

Geo and device routing (careful)

Some stacks 302 users to country subdomains. If every bot and user always 302s, reconsider 301 Redirect to the stable canonical host to avoid endless cross-domain hops.

A/B and experiment endpoints

Short-lived tests may 302 a fraction of traffic. Ensure experiment URLs are not primary crawl paths or sitemap entries.

Inappropriate 302 uses (common bugs)

1. Permanent site migration — use 301 or 308 Redirect.
2. HTTP → HTTPS — permanent infrastructure change; 301 standard.
3. WWW consolidation — apex vs www is not temporary.
4. Slug changes — /blog/old-title to /blog/new-title is permanent content move.
5. Default CMS setting — "Redirect" plugin emits 302 without admin awareness.

Audit migrations with curl -I on a sample of old URLs. Status line must match business intent.

Method handling: 302 and POST

Historically, 302 could cause clients to repeat POST as GET on the next hop (behavior clarified in modern specs). For form submissions and APIs, 307 Redirect preserves method explicitly. HTML page SEO rarely depends on this—but misconfigured checkout flows can.

Crawl and index behavior

Googlebot fetches the source URL, receives 302, fetches the Location target. Both URLs may appear in crawl reports during transition. Search Console may show redirects under indexing details.

Crawl budget impact: every internal link to a 302 source costs an extra hop. Update internal links to final URLs when the temporary window is known to be long.

Soft 404 risk at destination

If 302 points to a generic homepage or unrelated category, the destination may look like a soft 404 relative to source intent—similar to bad 301 mapping.

Implementation examples

Apache

Redirect 302 /summer-sale https://example.com/promotions/summer-2026

Nginx

location = /summer-sale {
    return 302 https://example.com/promotions/summer-2026;
}

Express

app.get('/summer-sale', (req, res) => {
  res.redirect(302, '/promotions/summer-2026');
});

Verify status code in response—not all frameworks default 302 when using generic redirect().

302 in redirect chains

/legacy → 302 → /staging → 301 → /production

Mixed chain types confuse monitoring. Prefer:

/legacy → 301 → /production   (if legacy is dead)
/summer → 302 → /promo-2026   (if summer path is seasonal)

Redirect chains with multiple 302 hops slow crawlers and dilute clarity.

Example: accidental 302 migration

docs.example moved to developers.example. Engineering used a load balancer rule labeled "temporary" emitting 302 for three years.

Symptoms:

• Both hosts received crawls
• Split indexed documentation URLs
• External links to old host still triggered 302 every crawl cycle

Fix: Replace with 301 Redirect to developers.example, update sitemaps, add Link headers on residual 301 responses. Consolidation accelerated within one crawl cycle pass on high-traffic paths.

Monitoring 302 redirects

• Log status=302 with Location field aggregated by path
• Crawl map: sources → destinations → final status
• Alert on new 302 rules after deploys
• Compare Search Console "Page with redirect" growth

Distinguish intentional campaign 302s from infrastructure drift.

302 vs 307 and 308

For HTML GET crawls, 302 vs 307 rarely matters. For sites mixing marketing pages and API gateways on same host, method semantics matter more.

How Crawlox helps with 302 redirects

Crawlox flags URLs that return 302, records each Location target, and builds redirect graphs across your site. Filter long-lived 302 patterns that should be 301, find internal links still pointing at hop sources, and verify destinations return 200 OK—so temporary redirects do not mask permanent structural problems or redirect loops.