What Is a 302 Redirect?
A 302 redirect is an HTTP status code that tells browsers and search engines a page has moved temporarily to another URL. Unlike a permanent 301, a 302 signals that the original address will return, so search engines keep the old URL in their index rather than transferring ranking signals to the new one. It is the correct choice for short-lived moves like A/B tests, temporary promotions, or maintenance pages, and the wrong choice for permanent URL changes.
- Status code meaning
- 302 = Found, historically Moved Temporarily (HTTP/1.1 specification, RFC 9110)
- Index behavior
- Google keeps the original URL indexed and does not transfer signals to the target (Google Search Central)
- Related codes
- 307 is the strict temporary redirect that preserves the request method (RFC 9110)
- Common misuse
- Servers and CMS platforms often default to 302 when 301 was intended (industry-typical)
What does a 302 redirect mean? #
A 302 redirect tells the requesting browser or crawler that the page it asked for is temporarily available at a different URL, but the original address should be considered the real, lasting home. This single distinction drives everything about how search engines treat it. Because the move is flagged as temporary, Google keeps the original URL in its index, does not swap in the destination, and generally does not transfer the original page's ranking signals to the target. That behavior is exactly right when the move truly is short-term. If you send visitors to a temporary landing page during a two-week sale, you want Google to keep ranking your permanent page and simply route users for now. The trouble starts when a 302 is used by mistake for a permanent change, which is surprisingly common because many servers, plugins, and frameworks emit a 302 by default. Understanding intent versus code is the heart of using redirects well, a theme covered further in /wiki/what-is-a-301-redirect.
When should you use a 302 instead of a 301? #
Reach for a 302 whenever the original URL will genuinely come back. Classic cases include A/B testing, where you temporarily route a portion of traffic to a variant while keeping the canonical page indexed; seasonal or promotional pages that expire and revert; maintenance windows where you send visitors to a holding page for a few hours; geolocation or device routing that changes per visit; and out-of-stock ecommerce items expected to return. In each of these the shared trait is impermanence: you do not want search engines to abandon the original URL or consolidate authority onto the temporary one. If instead the change is forever, a URL rename, a domain move, an HTTPS switch, or a page merge, you need a 301, because a 302 in those situations leaves the old URL ranking indefinitely and starves the new one of authority. Ecommerce teams working with /services/ecommerce-development weigh this constantly when handling temporary product and category states.
How does Google treat a 302 redirect? #
Google interprets a 302 as a signal that the original URL remains the one to index and rank, so it keeps that URL in results and points searchers to it even while the redirect forwards them onward. It does not immediately transfer PageRank or other ranking signals to the destination, since the whole point of a temporary redirect is that the source will return. There is an important nuance Google has acknowledged: if a 302 stays in place for a long time, months rather than days, Google may eventually conclude the move is effectively permanent and start treating it like a 301, consolidating signals on the destination. You should not rely on this behavior, because the timing is unpredictable and you lose control over which URL ranks in the meantime. If your intent is permanent, declare it with a 301 from the start rather than hoping Google reinterprets a lingering 302 correctly.
302 versus 307: what is the difference? #
Both 302 and 307 signal a temporary redirect, but they differ in a technical detail that matters for forms and applications. The original HTTP specification for 302 was ambiguous about whether the request method should be preserved, and in practice many clients would change a POST request into a GET when following a 302. The 307 status code was introduced to remove that ambiguity: it is a strict temporary redirect that guarantees the original request method and body are preserved, so a POST stays a POST. For everyday content redirects on a marketing or local business site, the SEO effect of 302 and 307 is essentially the same, and search engines treat both as temporary. The distinction becomes relevant in web applications where form submissions, logins, or API calls are being redirected, which is the territory our /services/web-app-development team navigates. For a plumber or dentist site, 302 is the term you will encounter; for a transactional app, 307 may be the correct technical choice.
Why is accidental 302 misuse a common SEO problem? #
The most frequent 302 problem is not deliberate misuse but silent defaults. Many web servers, content management systems, security plugins, and CDN rules emit a 302 unless explicitly told to send a 301. A developer sets up what they believe is a permanent redirect, the platform quietly makes it temporary, and months later the site owner wonders why the new URLs never gained rankings while the old ones linger in search. Because the redirect works fine for human visitors, who simply arrive at the right page, the error is invisible without checking the actual status code. This is why any migration or redesign should include a header audit that verifies each permanent redirect truly returns 301, not 302. Tools that inspect HTTP responses, including our /tools/website-down-checker, expose the real status a URL returns. Catching a stray 302 before it costs you rankings is one of the quiet wins of a thorough /services/website-migrations process.
How do you check whether a redirect is 301 or 302? #
You cannot tell a 301 from a 302 by watching your browser, because both land you on the destination page seamlessly. You must inspect the HTTP response. Open your browser's developer tools, go to the network tab, load the old URL, and look at the status column for the first request, which will show 301 or 302. Command-line tools like curl with the head option print the status directly, and numerous free online header checkers do the same for anyone uncomfortable with a terminal. For sites with many redirects, a crawler that reports status codes across every URL is the efficient approach, and our /tools/website-grader flags redirect issues alongside other technical signals. When you find a 302 that should be a 301, fix it at the source, whether that is a server config file, a plugin setting, or a CDN rule, then re-test to confirm the corrected code before moving on.
Do 302 redirects pass link equity? #
In principle a 302 is not meant to pass ranking signals, because the original URL is supposed to keep them and remain the indexed version. That is the intended behavior and the reason you should never use a 302 to move a page you want the destination to inherit authority for. In reality, Google has said that if a 302 persists long enough that it looks permanent, the system may begin consolidating signals on the target as if it were a 301. This gray area is precisely why relying on a 302 for anything permanent is risky: you are betting on undocumented reinterpretation timing rather than sending a clear instruction. The professional approach is to make your intent explicit. If you want equity to flow to a new URL, use a 301. If you want the original to keep ranking while you temporarily route traffic, use a 302 and change nothing about your expectations for the destination's search performance.
When might a local business legitimately need a 302? #
Local businesses use 302 redirects less often than 301s, but real cases exist. A restaurant running a limited-time menu or event page might temporarily route its specials URL elsewhere and want the permanent page to keep ranking. A gym launching a short January promotion could route a campaign URL to a temporary offer without disturbing its evergreen membership page. A contractor performing site maintenance might send visitors to a brief holding page. A seasonal business, such as a landscaper closing for winter, might temporarily redirect certain service pages while keeping them indexed for spring. In each case the business wants its established pages to retain their local rankings, so a temporary redirect is correct. The mistake to avoid is leaving a 302 in place after the temporary situation ends, or using one for a change that turns out to be permanent. Teams behind pages like /web-design-for-restaurants and /web-design-for-landscapers keep these redirects short-lived and documented so they never quietly become permanent liabilities.
FAQ
Is a 302 redirect bad for SEO?
A 302 is not inherently bad; it is simply the wrong tool for permanent moves. Used correctly for temporary situations, it protects your permanent URL's rankings. Used by mistake for a permanent change, it prevents the new URL from gaining authority and leaves the old one ranking, which is where the SEO damage comes from.
Will a 302 pass PageRank to the new URL?
By design, no. A 302 keeps ranking signals on the original URL because the move is temporary. Google may eventually treat a long-lasting 302 like a 301 and consolidate signals, but the timing is unpredictable. If you want authority to transfer to a new URL, use a 301 instead of relying on this behavior.
How do I change a 302 to a 301?
Locate where the redirect is generated, which could be a server config file, a CMS or SEO plugin, a security tool, or a CDN rule, and set the status code explicitly to 301. Then re-test with developer tools or a header checker to confirm the corrected code before considering the fix complete.
What is the difference between 302 and 307?
Both are temporary redirects with the same SEO treatment. The difference is technical: 307 strictly preserves the original request method, so a POST stays a POST, while 302 historically allowed clients to switch a POST to a GET. For content sites, 302 is standard; 307 matters in web applications handling form submissions.
Does my browser show whether a redirect is 301 or 302?
Not visibly on the page, since both deliver you to the destination the same way. You must open developer tools and check the network tab, use a command-line tool like curl, or run an online HTTP header checker. The status code is the only way to tell the two types of redirect apart.
Should I use a 302 for an out-of-stock product?
It can be appropriate if the product will return soon and you want its URL to keep ranking. A 302 to a relevant category page routes shoppers temporarily while preserving the product page's index status. If the product is gone permanently, use a 301 to a replacement or let the page return a 404 instead.
Was this helpful?