The 302, often incorrectly called a “302 error” (it is not an error), is an HTTP status code that indicates a temporary redirect of a web resource. When a server responds with this code, it tells the client — typically a browser or a search engine — that the requested page is no longer at the original address, but that this move should be considered provisional. The resource still exists and remains accessible via a new URL provided in the response, but the server intends to restore the original address at an unspecified future time.
In SEO, the 302 matters because it influences which URL search engines choose as canonical. Google states that all 3xx redirects pass PageRank: the difference between 301 and 302 concerns the URL shown in results, not a loss of value. The 302 signals that the starting URL should remain canonical, but if it stays in place for a long time Google may treat it as permanent. Understanding this is essential for managing migrations, maintenance, and seasonal changes correctly.
What the 302 code indicates in the HTTP specification
The 302 code belongs to the 3xx status code family, those dedicated to redirects. The HTTP specification classifies it as “Found” and requires the server to include a Location field in the response header containing the URL to which the client must go. The browser automatically makes a second request to that address, without the user perceiving any obvious interruption in navigation.
From a semantic point of view, the 302 signals a temporary condition. The server essentially declares that the resource is momentarily available elsewhere, but that the original address remains the correct reference. This provisional nature clearly distinguishes the 302 from the 301, which instead indicates a definitive and permanent move.
301 vs 302: what changes for indexes and authority
The distinction between 301 and 302 is crucial for both technical infrastructure and SEO strategies. The 301 communicates that the resource has moved permanently: for Google it is a strong signal to choose the new URL as canonical and update the index. The 302, on the other hand, is a weaker signal: it tends to keep the original URL as the reference. In both cases PageRank is passed.
What happens to search results
When a site uses a 302 for a move that is actually permanent, search engines may continue to show the original URL in results, causing confusion and potential traffic loss. Conversely, using a 301 for a temporary diversion can cause a premature update of indexes, with consequent difficulties in restoring the original situation.
The 302 and the choice of canonical URL
With a 302 Google tends to consider the starting page as the URL to show, because the move is declared temporary. It is useful when you want to maintain control over the main URL, for example during A/B tests or temporary promotions; if the 302 stays in place for a long time, Google may treat it as permanent.
Maintenance, promotions, and A/B tests: use cases
The 302 is used in various operational situations. It is appropriate during scheduled maintenance, when a section of the site is temporarily disabled and users must be redirected to an information page. It is also suitable for seasonal promotional campaigns, where a product page is replaced by a dedicated landing page for a limited period.
Other typical scenarios include usability tests or graphic variant tests, where groups of users are directed to different versions of the same page without altering the canonical URL. Automatic redirection based on language or location should be used with caution: Googlebot mostly crawls from locations in the United States and may not see all versions, so a language selector is preferable to a forced redirect.
301, 302, and other codes compared
| Code | Meaning | Permanence | Signal for canonical URL |
|---|---|---|---|
| 301 | Moved permanently | Permanent | Strong |
| 302 | Found (temporary move) | Temporary | Weak; if long-lasting may be treated as permanent |
| 303 | See other | Temporary | Weak |
| 307 | Temporary redirect | Temporary | Weak |
| 308 | Permanent redirect | Permanent | Strong |
The most common configuration mistakes
One of the most frequent mistakes is applying a 302 to a domain change or a definitive URL restructuring. In these cases a permanent redirect would be the correct choice, because the 302 is a weaker signal and can slow down index updates: the old URL may remain in results for a long time.
Another mistake involves creating redirect chains, where a 302 points to another 302 and so on. These sequences slow down loading, confuse crawlers, and can lead to infinite loops if not handled carefully. It is also inadvisable to use the 302 to hide duplicate content or for cloaking practices, since such behaviors violate search engine guidelines.
Check redirects and switch to 301
- Use an HTTP analysis tool to identify all active redirects on the site.
- Check the status code returned for each URL and verify whether the 302 is really necessary.
- Assess whether the move is temporary or permanent by consulting the content team.
- If the move is permanent, replace the 302 with a 301 to clearly signal the new URL.
- Eliminate any redirect chains by reducing the steps to one.
- Update internal links so they point directly to the final destination URL.
- Submit a new sitemap to search engines to encourage rapid reindexing.
- Monitor server logs to verify that no residual errors or repeated requests are generated.
Frequently asked questions about 302 Redirect
What exactly does 302 Redirect mean?
302 Redirect is an HTTP status code that indicates a temporary redirect: the requested resource is momentarily available at a different address, but the original one remains valid as a reference.
Does a 302 Redirect harm SEO ranking?
Not necessarily. If used for temporary moves, the 302 keeps the original URL as the reference. It becomes problematic when used instead of a 301 for permanent changes, because the index may update more slowly. PageRank is still passed.
What is the main difference between 301 and 302?
The 301 signals a permanent move and is a strong canonical URL signal; the 302 indicates a temporary condition and keeps the original URL as the reference. For Google, both pass PageRank.
Can I use a 302 to change domain?
No, for a definitive domain change the 301 is preferable. The 302 does not communicate to search engines that the new domain should permanently replace the previous one.
How do I find 302 Redirects on my site?
You can use crawling and HTTP analysis tools that show the status code of each URL. Search engine webmaster dashboards also report detected redirects.
How long does it take for a search engine to handle a 302?
Times vary based on crawl frequency and site authority. Generally the crawler records the redirect on the next visit, but index updates may take days or weeks.
From glossary to projectDo you need to change domain or platform without losing visibility?SEO migration prepares the transition (redirects, structure, checks before and after) to reduce the risk of losing ranking on Google.Discover SEO migration
Related entries: