Page With Redirect in Search Console: Do You Need to Fix It?
Why redirecting URLs show as not indexed, when that is perfectly normal, and when it points to a real problem.
In Search Console's Page indexing report, "Page with redirect" often lists dozens of URLs as not indexed. It looks alarming, but in most cases it is exactly what should happen. A URL that redirects to another page is not indexed β the destination is.
What "Page with redirect" means
Google found the listed URL, followed it, and saw that it redirects somewhere else. So it indexes the destination instead. Typical examples:
http://versions redirecting tohttps://- Non-www redirecting to www (or the other way)
- Old URLs redirecting to new ones after a redesign
- URLs with or without a trailing slash
All of these are healthy redirects, and the status is informational.
When it is a problem
- Your sitemap lists redirecting URLs. Sitemaps should contain only final URLs. Rebuild it with the sitemap generator.
- Your internal links point to redirecting URLs. Update them to the final address so visitors and crawlers skip the hop.
- Important pages redirect by mistake β for example a plugin redirecting product pages to the homepage.
- The redirect goes to the wrong place, or through a chain of several hops.
- Temporary (302) redirects used for permanent moves, which can leave the wrong URL indexed.
How to check and fix
- Open the report, click "Page with redirect" and look at example URLs.
- Paste them into the redirect checker to see the status code and destination of each.
- If the destination is correct and the URL is an old or alternative version, leave it.
- If the URL appears in your sitemap or internal links, replace it with the final URL.
- If a redirect is wrong, chained or temporary, fix it on the server. Read how to fix redirect chains.
Do not "validate" healthy redirects
There is no need to press "Validate fix" for redirects that are working as intended. They will stay in this report, and that is fine.
A worked example
A blog owner saw 400 URLs under "Page with redirect" and worried. A sample of 20 in the redirect checker showed two groups. Most were http:// and non-www versions redirecting to the main HTTPS www address, which is correct and needs no action. But 35 were old post URLs that the sitemap plugin still listed, because the posts had been renamed. Regenerating the sitemap removed them, and the next crawl stopped reporting them as submitted URLs.
Quick checklist
- Sample the listed URLs and check where each one goes.
- Confirm the destinations are the right, indexable pages.
- Remove redirecting URLs from your sitemap.
- Update internal links to point straight to final URLs.
- Replace any chains or temporary redirects with single 301s.
Related guides
More free tools: browse all our free SEO tools, no sign-up needed.
Frequently asked questions
Is "Page with redirect" an error?
No. It is a status. It only needs action if the redirect is unintended or the URL is still used in your sitemap or links.
Will the redirected URL ever disappear from the report?
It may stay for a long time if Google still finds links to it. That is harmless.
Should I remove old redirects?
No. Keep redirects for old URLs that have links or traffic.
Why is my destination page also not indexed?
Check it separately in URL Inspection β it may have its own issue, such as noindex or thin content.