Page with redirect: why redirecting URLs are not indexed

Last updated: 2026-10-30

In short

Page with redirect means the URL is a non-canonical URL that redirects to another page, so Google does not index it. That is expected for old URLs, HTTP or www variants and moved pages. Check that the redirect target is correct and indexable, and stop linking to redirecting URLs from your pages and sitemap.

Exact label in Search Console: Page with redirect

What it means

Google's Page indexing help says this is a non-canonical URL that redirects to another page, so this URL will not be indexed. The redirect target might or might not be indexed, depending on what Google thinks of it. Google also notes that a canonical URL with a redirect can be indexed, that the indexed data in URL Inspection applies to the tested URL, and that the live test follows redirects and tests the final URL without saying so.

Permanent redirects (301 and 308) are a strong signal that the target should be canonical; temporary ones (302 and 307) are a weak signal. Google keeps track of both the old and the new URL, and after a move it may still occasionally show an old URL in results as an alternate name.

Is it a problem?

Usually not. Google's FAQ lists redirects among the most common reasons for non-indexed URLs and says redirect URLs are not indexed, only the target. It matters when a URL that should be a live page is redirecting by mistake, when the target itself is not indexed, or when your sitemap and internal links are full of redirecting URLs.

Common causes

Site moves and URL changes

Old URLs after a migration, slug change or merge redirect to new ones. This is intended.

Protocol and host normalization

HTTP to HTTPS, non-www to www or trailing slash redirects. Also intended.

Sitemaps and internal links pointing at old URLs

Your own site keeps sending Google to URLs that redirect, so they keep appearing in the report.

Unintended redirects

A plugin, geolocation, language detection or login wall that redirects pages which should load directly.

Temporary redirects left in place

A 302 used for a permanent move sends a weaker signal about which URL should be canonical.

How to fix it

  1. Confirm the target is right. Inspect an example URL, then use the INSPECT button in the Page indexing section of URL Inspection to check the canonical URL. Make sure the target returns 200, is indexable and has the content the old URL had.
  2. Use permanent server-side redirects for permanent moves. Google recommends 301 or 308 server-side redirects when a change is permanent. Use meta refresh or JavaScript redirects only when server-side redirects are not possible.
  3. Update internal links and sitemaps. Link directly to final URLs and list only final, canonical URLs in your sitemap. This saves crawl requests and keeps your signals consistent.
  4. Remove redirect chains. Point every old URL straight to its final destination in one hop. Google warns that long redirect chains have a negative effect on crawling.
  5. Remove unintended redirects. If a page should load directly, remove the rule that redirects it, then run Test live URL and request indexing.

Check it with GSC Magic

Running gsc_inspect_urls_batch, or report_index_health starting from your sitemap, shows which listed URLs Google reports as Page with redirect. It is the quickest way to find stale sitemap entries after a migration. On Pro and Agency with write mode on, gsc_submit_sitemap resubmits the cleaned sitemap, and indexnow_submit notifies Bing and other IndexNow engines about the changed URLs. IndexNow does not reach Google; see IndexNow vs Google Indexing API.

report_index_healthgsc_inspect_urls_batchgsc_submit_sitemapindexnow_submit

Prompts to copy

Run an index health check on my sitemap and list every URL reported as Page with redirect, so I can replace them with their final URLs.

Inspect these old URLs from our migration and confirm each one is reported as Page with redirect and that its Google-selected canonical is the new URL.

I have uploaded the cleaned sitemap. Resubmit it in Search Console and show me its status, errors and warnings.

Guides on the blog

Redirect error

Redirect error means Google tried to follow a redirect from the URL and failed. Google lists four causes: a chain that was too long, a redirect loop, a URL that grew past the maximum length, and a bad or empty URL in the chain. Trace the redirect hop by hop and point the URL straight at a working final page.

 Duplicate, Google chose different canonical than user

This status means the page is marked as canonical for a set of pages, but Google decided another URL is the better representative and indexed that one instead. A canonical tag is a hint, not a rule. Compare the pages involved, then make redirects, canonical tags, internal links and sitemaps all point at the same URL.

 Alternate page with proper canonical tag

This status means the URL is an alternate version that correctly points to another canonical page, and that canonical is indexed. Google says there is nothing you need to do. Spot-check that the canonical is the URL you want and that no important page ended up here by mistake.

 Not found (404)

Not found (404) means Google requested the URL and your server answered 404. Google says a 404 is not necessarily a problem when a page was removed without a replacement. Fix the 404s you link to yourself or list in a sitemap, and 301 redirect pages that moved.

Frequently asked questions

Do I need to fix Page with redirect?

Only if the redirect is a mistake or points to the wrong place. For old URLs and host or protocol variants, Google says redirect URLs are not indexed, only the target, which is the result you want.

301 or 302: does it matter?

Yes. Google treats 301 and 308 as a strong signal that the target should be canonical and 302 and 307 as a weak one. Use permanent redirects for permanent moves.

Why does the live test pass when the URL redirects?

Google's help says the live test follows redirects and tests the final URL without indicating that it did. The indexed result is the one that shows the redirect.

Will old URLs ever disappear from search results?

Google keeps track of redirect sources, and after a move it may still occasionally show old URLs as alternate names. Google says this fades over time without you doing anything, as long as the redirects stay in place.

Sources