Fix "Page with redirect" excluded status in Search Console

"Page with redirect" in Search Console's coverage report isn't always an error. It means the URL you submitted redirects somewhere else, so Google indexed the destination instead. Whether that's a problem depends entirely on whether the redirect was intentional.

When it's completely fine

• Old URLs that 301 to new ones after a migration — exactly what you want; the destination should be indexed, not the old URL.
• HTTP redirecting to HTTPS, or non-www to www (or vice versa) — normal canonicalization.
• Trailing-slash normalization. As long as the final URL is the one that indexes, ignore the "Page with redirect" label on the source.

When it's a real problem

• The URL is in your sitemap but redirects — your sitemap should list final destination URLs, not redirecting ones. Clean it up.
• Internal links point at the redirecting URL, wasting a hop and a little link equity on every crawl.
• A redirect chain: URL A → B → C. Each hop loses time and equity; collapse it to A → C.
• An unexpected redirect — the page should be live, but something (a CMS rule, an ALB, a plugin) is bouncing it. That's a bug.

The fixes

1. Replace sitemap entries and internal links with the final destination URL.
2. Collapse redirect chains to a single 301 from the original URL straight to the final one.
3. Switch any 302 (temporary) redirects that are meant to be permanent to 301.
4. If a page is redirecting by mistake, remove the rule, then push the now-live URL through the Indexing API.

Confirm the destination is the one indexing

After fixing, run a status check on the destination URL (not the redirecting one). You want to see the destination reported as "URL is on Google" and self-canonical. Then push it through the Indexing API to speed up re-crawling of the corrected setup.