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

Page with redirect means Google tried the URL and was redirected to another one, so it did not index this URL. That is how redirects are meant to work: the target URL can be indexed instead. For most sites this status needs no action at all.

What does “Page with redirect” mean?

Google’s Page indexing report lists this as a non-indexed URL that redirects to another page. The redirecting URL itself is not indexed; the page it points to may be. Google lists it as an expected state, not an error. When the redirect is broken instead, for example a loop, the URL appears under Redirect error.

Is it a problem?

It is fine and expected for:

• http:// URLs that redirect to https://, and www to non-www (or the reverse).
• URLs with or without a trailing slash that redirect to one form.
• Old pages after a site migration or a URL change.
• Products or posts you merged into another page.

It needs attention when a page you want in Google is here, or when your own site keeps linking to redirecting URLs, which adds a hop for every crawl and every visitor.

What causes it, most likely first?

1. Normal domain and protocol redirects (http to https, www to non-www).
2. Internal links and sitemaps that use old URLs, so Google keeps finding the redirecting version.
3. Migrations and URL changes, including CMS slug changes.
4. Unintended redirects: a plugin, geo or language redirect, or a login redirect on a page that should be public.

How do I clean it up?

1. 1. Export the list and group the URLs

   Export the examples from the report and sort them by pattern: http vs https, www vs non-www, trailing slash, old URLs from a migration, and anything that looks like a current page.

2. 2. Ignore the expected ones

   Old addresses that redirect to their new home, and alternate spellings of your domain that redirect to the main one, are working as intended. Leave them.

3. 3. Check that each redirect lands on the right page

   For the rest, check where the redirect ends: it should be a single 301 or 308 hop to the closest matching page that returns 200. Redirects to the homepage for every old URL, or to an unrelated page, waste the old page's value and may be treated as soft 404s.

4. 4. Update links and the sitemap to the final URL

   Replace internal links, canonical tags, hreflang and sitemap entries that point to redirecting URLs with the final destination. This is the step that usually shrinks the list.

5. 5. Fix pages that should not redirect at all

   If a page you want indexed appears here, find what is redirecting it: a plugin rule, a CMS setting, a language or geo redirect, or a login wall. Remove the redirect, then request indexing for the page.

To see the full chain for a URL, request it without following redirects:

curl -sIL https://example.com/old-page | grep -iE "^(HTTP|location)"

How do I check the result?

Inspect the final URL in URL Inspection: it should be “URL is on Google”, with the Google-selected canonical matching it. The number of URLs in Page with redirect may never reach zero, and doesn’t need to.

How long does it take?

Changes to internal links take effect as Google recrawls the linking pages, typically days to weeks. Old URLs can stay in this list for months because Google keeps rechecking them, which is harmless.