stillindexedStart monitoringOpen the app

Search Console Page indexing: Why pages aren't indexed

Page with redirect in Search Console: is it a problem?

A redirecting URL is not indexed; its target may be. When "Page with redirect" is expected, when it is not, and what to clean up either way.

This URL redirects to another URL, so Google indexes the target instead. For old addresses after a migration, http to https or www changes, that is what should happen. It is a problem only if the redirect is unintended, or if the old URL is still in your sitemap or internal links.

What "Page with redirect" means

Google: "This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed. The target URL of the redirect might or might not be indexed, depending on what Google thinks about that target URL." The status describes the redirecting URL, not the target.

Is it a problem?

Usually fine

Usually not. Google lists redirects among the ordinary reasons for large numbers of non-indexed URLs: "Redirect URLs are not indexed, only the redirect target." Check that the targets are indexed and that the list holds no URL that should be serving its own content.

Causes, most likely first

  1. Deliberate redirects: http to https, www to non-www or the reverse, trailing slash normalisation, old URLs after a migration.
  2. Internal links, canonical tags or sitemap entries still using the old URL, so Google keeps finding the redirecting address.
  3. An unintended redirect: a page sending visitors to the home page, a login page or a country version after a deploy or plugin change.
  4. Redirects that depend on the visitor, such as country or device, sending Googlebot somewhere a browser does not go.

How to confirm it

  1. Run the redirect chain checker on the URL to see every hop and the final page.
  2. Inspect the target URL rather than the redirecting one; the status applies to the URL that redirects.
  3. Search your sitemap and templates for the redirecting URL to find where Google keeps discovering it.

Redirect chain checker

How to fix it

  1. For intended redirects, there is nothing to do on the redirecting URL. Make sure the target returns 200 and is indexed.
  2. Replace the old URL with the final one in internal links, canonical tags and the sitemap.
  3. Collapse chains so each old URL reaches the final page in one hop.
  4. Remove any redirect that should not exist, so the page serves its own content again, then request indexing for it.

How long recovery takes

Nothing to wait for when the redirect is intended: Google indexes the target. A page whose unintended redirect you remove has to be recrawled, which can take "anywhere from a few days to a few weeks".

Would monitoring have caught it?

A change to the redirect chain of a monitored URL is a warning, and a redirect that starts landing on a different domain is critical. A page that starts redirecting after a deploy is reported after the next check, rather than when this report updates.

stillindexed checks each monitored URL every 30 minutes on Starter and every 15 minutes on Agency, so the change is found on the next check and confirmed before it alerts, rather than waiting for this report to update.

See what monitoring covers

A migration or redesign losing pages from search, platform by platform

A broken or chained redirect, platform by platform

Further reading

Sources

Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-06. If Google has changed a page since, Google's page wins and we would like to know.