What Is a 302 Redirect? When Temporary Actually Matters

Jul 29, 2026 · SEO Glossary

The most common redirect mistake I've come across in client audits isn't a broken redirect. It's a working one — a 302 sitting where a 301 should be, sometimes for years. The site migrated, the developer reached for the default redirect setting, and nobody noticed that the server was telling Google "we'll be right back" about a move that was permanent.

So let's get the definition straight. What is a 302 redirect? It's an HTTP status code that means "Found" — the resource you asked for is temporarily living at another URL. The browser forwards you there, but search engines keep the original URL in their index, because you've told them the move won't last.

What is a 302 redirect telling Google, exactly?

Think of the difference between a mail-forwarding order and a note taped to your front door that says "back in 20 minutes, try the coffee shop next door." A 301 redirect is the forwarding order: update your address books, this is permanent. A 302 is the sticky note: don't update anything, this is a blip.

Concretely, when Googlebot encounters a 302:

• It keeps the original URL indexed and continues showing it in search results.
• It expects the redirect to disappear, so it re-checks the original URL more often than it would a 301 target.
• It does not immediately consolidate signals onto the destination the way it would with a permanent redirect.

That last point comes with an asterisk. Google's John Mueller has said repeatedly that a 302 left in place long enough gets treated as a 301 — Google infers your real intent from behavior. But "long enough" is undefined, the transition isn't instant, and in the meantime you can end up with the wrong URL ranking, split signals, or stale titles in search results. Sending the correct code from day one costs you nothing.

Legitimate reasons to use a 302

A 302 isn't a lesser 301. It's the right tool for genuinely temporary situations:

1. A/B testing. You're splitting traffic between two page versions for a month. A 302 keeps the original URL canonical in Google's eyes, which is exactly what Google's own testing guidelines recommend.
2. Seasonal or promotional swaps. Your /deals/ page points at the Black Friday landing page for two weeks in November, then reverts. Temporary by design.
3. Out-of-stock products. An item is gone for six weeks, so you temporarily forward shoppers to the parent category. When stock returns, the redirect comes off and the product page still holds its rankings — because Google never de-indexed it.
4. Maintenance and staged rollouts. Sending a fraction of users to a new checkout flow while you monitor error rates.
5. Geo or device-based routing. Forwarding visitors to a country-specific version while keeping the generic URL as the indexed one.

Notice the pattern: in every case, you intend to bring the original URL back. If you can't honestly say when the redirect will be removed, it isn't temporary, and you want a 301.

What happens when a 302 overstays its welcome

Here's a real-world shape of the problem. An agency I worked with rebuilt a plumber's site in 2023 and 302'd roughly 80 old URLs to their new equivalents. Eighteen months later, Search Console still showed a mix: some old URLs had been silently upgraded to permanent status by Google's systems, others were still indexed and ranking with the old titles, and a handful showed "Page with redirect" in the coverage report while their replacements struggled. Rankings weren't catastrophic — Google is forgiving — but the site spent a year and a half in an ambiguous state it never needed to be in.

Changing those 302s to 301s cleaned the index up within about six weeks. The lesson isn't that 302s are poison; it's that ambiguity has a cost, and the cost is paid in slow consolidation.

302 vs. 307: a quick footnote

You'll sometimes see a 307 Temporary Redirect instead of a 302, especially in Chrome DevTools when a site uses HSTS (the browser does an internal 307 from HTTP to HTTPS without asking the server). The technical difference is that a 307 guarantees the request method won't change — a POST stays a POST — while the 302 spec historically allowed browsers to convert POST to GET. For SEO purposes, treat 302 and 307 as the same thing: temporary, original URL stays indexed.

How to check what your redirects actually return

Never trust that a redirect is what you think it is. Verify:

• curl: run curl -I https://example.com/old-page/ and read the status line. Add -L to follow the whole chain and see every hop.
• Chrome DevTools: open the Network tab, load the URL, and check the status column. Watch for that internal 307 — it's the browser, not your server.
• Google Search Console: the URL Inspection tool shows how Google last crawled the URL and whether it registered a redirect.
• A site-wide crawl: checking URLs one at a time doesn't scale past a dozen. Run a free site audit and you'll get every 301, 302, chain, and loop on the domain in one report — then you can sort the 302s and ask of each one: "is this actually temporary?"

The one-question test

Every redirect decision collapses to a single question: will the original URL come back? Yes — use a 302, and put a reminder in your calendar to remove it. No — use a 301 and update your internal links to skip the hop entirely. The codes exist to communicate intent, and search engines genuinely listen to what you tell them. Tell them the truth.