Found — the resource temporarily resides under a different URL
What 302 Means
The 302 error on the HTTP Status-Codes indicates found — the resource temporarily resides under a different url. This typically occurs due to a/b testing different page versions.
A 302 Found response indicates that the requested resource has been temporarily moved to the URL provided in the Location header. Unlike a 301, a 302 tells search engines not to update their links and browsers not to cache the destination indefinitely.
Technical Background
A 302 is the traditional way to handle temporary redirections in HTTP. When a client receives this response, it automatically issues a new request to the address specified in the Location header, but it retains the original URL for future visits.
Modern web development often favors 303 or 307 for strictly defining HTTP method preservation, but 302 remains the most universally understood temporary redirect across all legacy clients, web scrapers, and analytics tools.
Using a 302 instead of a 301 for permanent changes is a common SEO mistake. Search engines will continue to crawl the old URL, splitting linking authority and potentially degrading ranking performance.
Common Causes
- A/B testing different page versions
- Redirecting users while a page is under maintenance
- Tracking clicks through a short URL service
- Forwarding visitors based on their locale
Typical Scenarios
- A marketing campaign uses a short URL that redirects to the actual product page
- A web application momentarily redirects a user upon login to their personal dashboard
- A site administrator points traffic away from a page during temporary technical work
What to Know
A 302 redirect implies a transitory state where the original URL holds primary significance. If a client continues to receive a 302 long after a migration is complete, the server rules should likely be upgraded to a permanent 301.
Frequently Asked Questions
Common questions about HTTP 302 error
A 302 is used when you plan to bring the original URL back eventually. This prevents search engines from erasing the old URL from their indexes.
Historically, 302 redirects passed less link equity than 301 redirects, but modern search engines increasingly treat them similarly if the redirect appears relatively permanent.
By default, 302 responses are not cached unless the server explicitly includes caching headers like Cache-Control or Expires.