TL;DR: A temporary HTTP redirect that diverts traffic to another URL without telling search engines the change is permanent.
In a nutshell
Use a 302 when a page is briefly unavailable, you are running an A/B test, or you have a seasonal campaign page that will switch back later. Google keeps the original URL in its index and does not pass full ranking signals to the destination. For any permanent move, use a 301 instead.
Quick answer: A 302 redirect is a temporary HTTP redirect that tells browsers and search engines that a URL has moved to a different location, but only for now. Unlike a 301 (permanent) redirect, a 302 keeps the original URL in Google’s index and does not pass full ranking signals to the new URL. Use 302 only when the move is genuinely temporary.
What Is a 302 Redirect?
A 302 redirect is an HTTP status code that tells browsers and search engines that a page has been temporarily moved to a different location. Unlike a 301 redirect, which is permanent, a 302 suggests the original page will be back soon, and as such, it typically does not pass full SEO value or replace the original page in search results. The full list of HTTP response codes lives at the IANA HTTP status codes registry.
Used correctly, a 302 redirect helps preserve the original URL’s rankings, while providing a temporary detour for users. Used incorrectly, it can prevent search engines from indexing the correct version of your site or dilute your SEO efforts.
Why 302 Redirects Matter
While less commonly used than 301s, 302s still have important SEO applications:
- Running temporary promotional pages or A/B tests
- Redirecting users during maintenance or technical downtime
- Preserving the original URL’s SEO footprint while the page is unavailable
At BrisTechTonic, we’ve seen cases where misusing 302s (when a 301 was needed) has caused major indexation issues, pages staying in limbo or search engines ignoring the redirect entirely. That’s why we review every redirect type during a technical SEO audit or SEO package.
What Happens in a 302 Redirect?
When a browser or crawler encounters a 302, the server responds like this:
HTTP/1.1 302 Found
Location: https://www.example.com/temporary-page/This response tells bots: “Go here for now, but don’t forget the original URL.” As a result, Google typically keeps the original page indexed, unless the 302 redirect is left in place for too long, in which case Google may treat it like a 301 anyway.
When to Use a 302 Redirect
Use 302s when:
- You’re conducting A/B testing with different versions of a page
- You’re running a time-sensitive promotion or event page
- You’re temporarily taking a product or service offline
- You’re running region-based redirects that depend on user behaviour
- You want to display a splash page without permanently replacing the original URL
Just don’t use 302s if your change is permanent, that’s a job for a 301 redirect.
How to Implement a 302 Redirect
WordPress (via plugins)
- Rank Math: Use the Redirects module and choose “302 – Temporary”
- Redirection plugin: Easily select redirect type during setup
Apache (.htaccess)
Redirect 302 /old-page/ https://www.example.com/temp-page/NGINX
rewrite ^/old-page/?$ https://www.example.com/temp-page/ redirect;Shopify / Wix
Most modern platforms default to 301s, but with custom code or apps, you can implement 302s.
302 Redirect SEO Considerations
The biggest SEO risk is using a 302 when you actually want a permanent redirect. Search engines will continue to index the original page and may ignore the destination altogether, assuming it’s a short-term move.
However, Google has evolved: if a 302 stays in place long enough, Google may treat it as a permanent redirect and pass some link equity, but this is not guaranteed. It’s always safer to use the correct redirect type upfront. The official Google reference sits in the Google Search Central docs.
Google’s Take on 302s
According to Google’s guidance:
“If you use a 302 redirect and leave it for a long time, Google may start to treat it like a 301.”
That’s why we audit 302s during all site migrations and ensure nothing critical is accidentally left in “temporary” mode long-term.
302 vs 301: Quick Reference
| Redirect Type | Purpose | SEO Value | Indexation |
|---|---|---|---|
| 301 | Permanent redirect | Passes full link equity | New URL replaces old in index |
| 302 | Temporary redirect | Original page usually keeps SEO value | Original URL remains in index (at least initially) |
Common 302 Mistakes
- Using 302s for permanent changes, Your rankings won’t transfer
- Leaving 302s in place long-term, Google may ignore or misinterpret them
- Chaining multiple 302s, Slows crawl and confuses bots (see Redirect Chains)
- Incorrectly configuring the Location header, Results in broken redirects
How We Handle 302s at BrisTechTonic
In our technical audits and SEO training courses, we always check the type and purpose of every redirect. If a temporary redirect has been active for 6+ months, we usually recommend upgrading it to a 301 unless there’s a valid business case not to.
For ecommerce and campaign-heavy sites (like seasonal events), we also recommend tagging 302s in your CMS or redirect manager so they’re easier to track and replace later, and re-validating them during any website migration.
Testing and Managing 302 Redirects
Use the following tools to test redirect status codes:
- httpstatus.io – Quick header checker
- Screaming Frog – Crawl redirect chains
- Google Search Console – Track crawl behaviour
Related Glossary Terms
External Resources
Frequently Asked Questions
When should I use a 302 redirect instead of a 301?
When the redirect is genuinely temporary: A/B testing, seasonal landing pages, geo-targeted campaign URLs, or maintenance pages. For permanent moves, always use 301.
Does a 302 redirect pass any link equity?
Some, but less reliably than a 301. Google has stated it tries to interpret intent: if a 302 has been in place for many months without changing back, Google may treat it as a 301. The safer practice is to use the correct redirect type for the situation rather than relying on Google’s interpretation.
What happens to SEO if I use 302 by accident?
If a permanent move is misimplemented as a 302, Google keeps the old URL in its index and only partially passes signals to the new URL. The fix is straightforward: change the redirect to a 301 and request reindexing. Recovery typically takes a few weeks.
How do I check whether a redirect is 301 or 302?
Browser developer tools: open the Network tab, load the URL, and inspect the response status code. Curl from the command line is faster: curl -I https://yoursite.com/url shows the status code in the response header.
Take this further
Using the wrong redirect type is one of the most common SEO mistakes during site changes. Auditing redirects after any migration catches issues before they cost rankings.
Ready to apply this to your own site? Book a free discovery call, or explore our SEO strategy service.