Temporary Redirects
What This Means
One or more URLs return a 302 (Found) or 307 (Temporary Redirect) response. These status codes signal that the redirect is temporary and the original URL should be retained as the canonical version.
Why It Matters for SEO
Temporary redirects tell search engines: "The content has moved, but temporarily — keep the original URL in mind." As a result, search engines may not fully transfer ranking signals from the temporary source to the destination, and may continue to index the original URL. If you've permanently moved content, a temporary redirect will not consolidate the ranking signals as effectively as a 301.
Common misuse: developers set up 302s during site migrations intending to switch to 301s, but the 302s remain in production indefinitely.
What the Platform Checks
The platform records the HTTP status code for each response. Fires for every URL that returns a 302 or 307 status code.
How to Fix It
- For any redirect that represents a permanent URL change: change the 302/307 to a 301.
- For genuine temporary redirects (maintenance pages, seasonal content): 302 is correct — review and remove when the original URL is available again.
- Check your server configuration (Apache .htaccess, Nginx config, CDN rules) for redirect rules that should be 301 but are configured as 302.
Find every temporary redirectthat should be permanent
The audit distinguishes between 301 and 302 redirects so you can identify which temporary redirects should be changed to permanent.