Page with Redirect in GSC: What It Means & How to Fix
"Page with redirect" appears in the Google Search Console Page indexing report when Googlebot hits the URL and receives a 301, 302, 307, or 308 redirect response. Google excludes the redirecting URL from the index and follows the redirect to try to index the destination instead. The status is informational by itself, but it often points to sitemap hygiene problems or misconfigured redirects.
What this GSC status means
Google fetched the URL and the server responded with a redirect (HTTP 301, 302, 307, or 308). Google then treats the redirect target as the indexable URL. The original redirecting URL is correctly excluded - two URLs that resolve to the same content should not both be indexed. The warning is really: "you told us about this URL but it is not the real URL."
Common causes
- Old URLs from a site migration or URL restructure still living in your sitemap.xml.
- HTTP URLs being submitted when the site enforces HTTPS (http://example.com redirects to https://example.com).
- Trailing slash redirects (/page redirects to /page/ or vice versa) where both variants are linked or submitted.
- www vs non-www redirects when internal links or the sitemap mix the two hostnames.
- Redirect chains (A to B to C) where Google reports the intermediate URL as a redirect.
- Affiliate, tracking, or short URLs (/go/xyz) being accidentally submitted for indexing.
How it affects indexing
A single redirect costs Googlebot one extra request per URL - not a disaster. But redirects in your sitemap or internal links waste crawl budget on every recrawl, and redirect chains can prevent pages from being indexed at all because Googlebot stops following after about 10 hops. If the redirect target is itself excluded (noindex, 404, or another redirect), the whole chain wastes crawl equity.
How to diagnose
In GSC, open the Page indexing report and click "Page with redirect" to get the full URL list. Pick a sample URL and run it through the URL Inspection tool - it will show the redirect target. Then test the URL with curl (curl -I URL) to see the chain. Pay attention to how many hops it takes and what the final status code is.
How to fix
1. Export the URL list from GSC (Page with redirect) so you have a full inventory. 2. Remove every redirecting URL from your sitemap.xml - submit only the final 200 destinations. 3. Collapse redirect chains: if A redirects to B redirects to C, change A to redirect directly to C. 4. Update internal links to point at the final URL, not the redirect source. 5. Check canonical tags - make sure they reference the 200 URL, not a redirecting one. 6. Pick one hostname variant (https, with or without www, with or without trailing slash) and enforce it everywhere. 7. Regenerate your sitemap and resubmit it in Search Console under Sitemaps.