What is a 302 Redirect? SEO Guide for Beginners

Learn what a 302 redirect means in SEO, why it matters, and when to use it instead of a 301.

A 302 redirect is a temporary redirect. The official HTTP reason phrase for status code 302 is "Found", defined in RFC 9110 Section 15.4.3, and it indicates that the requested resource resides temporarily under a different URL given by the response's Location header (MDN). For SEO, a 302 tells search engines the page has moved for now but the original URL should remain the indexed, canonical one. Google's own documentation confirms this. With a temporary redirect, "Googlebot follows the redirect, but the indexing pipeline doesn't use the redirect as a signal that the redirect target should be canonical" (Google Search Central). Unlike a 301 (permanent) redirect, a 302 keeps the original URL in Google's index rather than replacing it with the new destination.

Why 302 Redirects Matter for SEO

Using the wrong type of redirect can quietly damage your rankings. If you use a 302 when you actually mean a permanent move, Google continues to index the old URL and does not fully transfer link equity to the new page. Your rankings end up stuck on a URL that redirects, rather than consolidating on the destination.

On the flip side, 302 redirects serve a genuine purpose when the move truly is temporary. A/B testing, seasonal promotions, maintenance pages, and geographic redirects are all situations where you want users to see a different page temporarily while preserving the original URL's place in Google's index.

I have audited sites that had hundreds of 302 redirects that had been in place for years. The site owner had used 302s for a domain migration two years prior and never switched them to 301s. Google was confused about which URLs to index, link equity was not flowing properly, and rankings were significantly lower than they should have been. Switching those to 301s led to a measurable ranking improvement within a few weeks.

The distinction between 301 and 302 seems small, but it has real impact on how Google treats your URLs and distributes authority across your site.

How 302 Redirects Work

When a browser or search engine crawler requests a URL that has a 302 redirect, the server responds with a 302 HTTP status code and a Location header pointing to the temporary destination. The browser follows the redirect and displays the new page.

The critical difference from a 301 is what Google does with this information. With a 302, Google keeps the original URL in its index and treats the redirect as temporary. It does not pass full link equity to the destination URL because it expects the original page to come back.

In practice, Google has gotten smarter about interpreting redirects. If a 302 redirect stays in place for a very long time, Google may eventually treat it like a 301 and start indexing the destination URL instead. But you should not rely on this behavior. Be explicit about your intent by using the correct status code.

Google lists three server-side codes that it treats as temporary: 302 (Found), 303 (See Other), and 307 (Temporary Redirect), versus 301 and 308 for permanent moves (Google Search Central). The practical difference between 302 and 307 is method preservation. Per the Fetch Standard cited by MDN, when a user agent receives a 302 in response to a POST request it may switch to GET on the follow-up request, whereas altering the method after a 307 is prohibited, so 307 preserves the original method. For ranking purposes Google treats all of its temporary codes the same way, so most of the time a plain 302 is what you reach for.

How to Improve 302 Redirect Usage on Your Site

Audit your existing redirects for misuse - Use Screaming Frog or Ahrefs Site Audit to crawl your site and list all 302 redirects. For each one, ask: is this move truly temporary? If the redirect has been in place for more than a few months and the original page is not coming back, change it to a 301.

Use 302s for A/B testing and experiments - When testing different versions of a landing page, 302 redirects are the correct choice. They tell Google to keep indexing the original URL while you route some traffic to the test variant. Once the test is over, remove the redirect or make it permanent.

Use 302s for geographic or language redirects - If you redirect users to a localized version of your site based on their location (e.g., redirecting US visitors from example.com to example.com/en-us), use 302. The original URL should remain indexed because different users should land on different versions.

Set calendar reminders to review temporary redirects - Every 302 redirect should have an expiration plan. When you create one, note when it should be removed or converted to a 301. Temporary redirects that linger for years defeat their purpose.

Check your CMS default redirect behavior - Many content management systems create 302 redirects by default when you change a page's URL. WordPress, Shopify, and others may need explicit configuration to use 301s instead. Know what your platform does and override it when necessary.

Common Mistakes to Avoid

Using 302 for permanent URL changes: This is by far the most common mistake. If you changed your URL structure six months ago and have no plans to revert, those should be 301 redirects. Every day a permanent move uses a 302, you are leaving link equity on the table.
Chaining 302 and 301 redirects together: Mixing redirect types in a chain confuses search engines about whether the move is permanent or temporary. If Page A has a 302 to Page B which has a 301 to Page C, Google receives mixed signals. Always point redirects directly to the final destination with a consistent redirect type.
Forgetting to remove temporary redirects after the test or event ends: A 302 for a Black Friday sale page that is still active in March is just a misconfigured redirect wasting crawl budget. Clean up temporary redirects as soon as they are no longer needed.

Key Takeaways

A 302 redirect signals a temporary move and tells Google to keep the original URL indexed rather than replacing it.
Use 302s only for genuinely temporary situations: A/B tests, seasonal content, maintenance pages, or geographic redirects.
If a redirect has been in place for months with no plan to revert, convert it to a 301 to ensure full link equity transfer.
Regularly audit your redirects to catch 302s that should be 301s, as this is one of the most common technical SEO issues.

In Practice

The difference shows up directly in the raw HTTP response. A temporary redirect returns a 302 status line plus a Location header pointing at the destination, with an empty body:

HTTP/1.1 302 Found
Location: https://www.example.com/maintenance
Content-Type: text/html; charset=UTF-8
Content-Length: 0

You can confirm what a live URL actually returns before trusting your config. Running a header-only request against a maintenance redirect looks like this:

$ curl -sI https://www.example.com/pricing
HTTP/1.1 302 Found
Location: https://www.example.com/maintenance

If that same Location line had been served under HTTP/1.1 301 Moved Permanently instead, Google would treat the destination as the new canonical and consolidate signals onto it. Under the 302 above, Googlebot follows the hop to /maintenance but keeps /pricing as the indexed URL, which is exactly what you want while a page is down temporarily and wrong if the move is permanent.

What is a 301 Redirect? - the permanent counterpart that consolidates ranking signals onto the destination URL.
What are HTTP Status Codes? - the broader family of 2xx, 3xx, 4xx, and 5xx responses that 302 belongs to.
What is Link Equity? - the ranking authority that a 301 passes along but a 302 deliberately does not.
What are Canonical Tags? - how Google picks the canonical URL, which redirects directly influence.
What is Indexing? - the process that decides whether the original or destination URL stays in Google's index.