"Page with redirect" is a status in the Page indexing report of Google Search Console. It lists URLs that Google tried to crawl and found redirect somewhere else. Those URLs are not indexed, because the page they redirect to is the one Google indexes instead. In most cases that is exactly what should happen. A page with redirect only needs fixing when your own site keeps sending Google to the old URL, or when the URL you want indexed is the one redirecting.
What "Page With Redirect" Means
When Googlebot requests a URL and gets a 301, 302, 307 or 308 response, it follows the redirect and indexes the destination. The original URL goes into the "Page with redirect" list under "Why pages aren't indexed". The URL is not broken. It just is not the final address.
| Situation | Action |
|---|---|
| Old URL after a migration or slug change redirects to the new URL | None. This is expected. |
http:// or non-www version redirects to the main version | None. This is expected. |
| The URL you want indexed is in the list | Fix: remove the redirect or update the canonical. |
| Your sitemap or internal links point at redirecting URLs | Fix: link to the final URL. |
| The redirect goes through several hops, or loops | Fix: one hop to the final URL. |
When a Page With Redirect Is a Problem
- The redirect goes the wrong way. For example,
/pricingredirects to/pricing/but every link, canonical and sitemap entry uses/pricing. Google keeps crawling the redirecting version. - Your sitemap lists redirecting URLs. A sitemap should contain only final, indexable URLs. Redirecting entries waste crawl budget and send mixed signals.
- Canonical tags point at redirecting URLs. A canonical should point at a page that returns
200, not at a URL that redirects. - Redirect chains and loops. Each extra hop slows crawling and users. A loop means the page never loads at all. The redirect chains guide explains the costs.
- Temporary redirects left in place. A
302that has been live for months should usually be a301. - Redirects to irrelevant pages. Redirecting removed products to the homepage can be treated as a soft 404. See how to fix soft 404 errors.
How to Fix Page With Redirect
1. Export the list and check the destinations
In Search Console, open Indexing, then Pages, then "Page with redirect", and export the examples. For each pattern, use URL Inspection to see where Google ended up. If every URL redirects to the page you want indexed, you can stop here.
2. Trace each redirect hop by hop
Paste the URLs into the redirect checker. It shows every hop, the status code at each step, and flags loops, chains longer than one hop and HTTPS to HTTP downgrades. To check many URLs at once, the HTTP status checker takes up to 20 URLs and shows the first and final status for each.
3. Update internal links to the final URL
Search your templates, menus and content for links to the old URLs and point them straight at the destination. Internal links are the main reason Google keeps revisiting a page with redirect. A site crawl helps here: the SEO Optimizer crawls up to 25 pages and reports links and canonicals that do not resolve cleanly.
4. Clean up the sitemap and canonical tags
Remove redirecting URLs from your XML sitemap and list the destinations instead. Check that each page's canonical tag points at a URL that returns 200. The sitemap checker and canonical checker catch both. The robots.txt and sitemap guide covers what belongs in a sitemap.
5. Collapse chains to a single 301
If http://example.com/old redirects to https://example.com/old, then to https://www.example.com/old, then to https://www.example.com/new, change the rules so every variant goes straight to the final URL in one hop. Use 301 or 308 for permanent moves.
6. Remove redirects from pages you want indexed
If an important URL is in the list by mistake, find where the redirect comes from: a server rule, a CMS redirect plugin, a framework config or a CDN rule. Remove it, make the URL return 200, and request indexing in URL Inspection.
7. Validate the fix
After fixing the cases that matter, click Validate fix on the "Page with redirect" row. URLs that are supposed to redirect will stay in the list, and that is fine. The count matters less than making sure the right pages are indexed.
Page With Redirect vs. Redirect Error
These are different statuses. "Page with redirect" means the redirect worked and Google indexed the destination. "Redirect error" means Google could not follow it: a loop, a chain that is too long, a redirect URL that is too long, or an empty or bad destination. Redirect errors always need fixing, and the redirect checker shows exactly where the chain breaks. For the other common indexing statuses, see "Discovered, currently not indexed" and "Duplicate without user-selected canonical".