Lorixen.
EN

"Page with redirect" in Search Console: usually fine

Short answer: "Page with redirect" in Search Console's Page indexing report usually means things are working: the listed URL redirects somewhere else, so Google doesn't index it and looks at the target instead. Google's own help page says that not indexed isn't necessarily bad and that you shouldn't expect every URL to be indexed. It only deserves action if an important page is redirecting by mistake, if the redirect targets are wrong, or if your own links and sitemap keep pointing at redirecting URLs.

The Page indexing report shows a grey "Not indexed" bar, you click into the reasons, and there's "Page with redirect" with dozens or hundreds of URLs. It looks like an error. For most sites, especially after a move to https, a domain change or a redesign, it's exactly what you'd expect. Here are the common myths, and what's really going on.

What the status actually means

Google's help page defines "Page with redirect" as a non-canonical URL that redirects to another page, and so won't be indexed. The target of the redirect might or might not be indexed, depending on what Google thinks of that target. The same page notes that a canonical URL with a redirect can be indexed.

In plain terms: the old address points to a new address, and Google indexes the new one (if it's worth indexing), not the old one. That's the purpose of a redirect.

Myth 1: "Not indexed" means something is broken

Reality: Google says "Not indexed" is not necessarily bad, and that it's fine for URLs not to be indexed for the right reasons, such as a noindex tag, a duplicate URL, a robots.txt rule you intended, or a 404 for a removed page. Redirected URLs belong in the same category. The report's purpose, in Google's words, is to get the canonical version of every important page indexed; duplicates and alternates shouldn't be.

Myth 2: You need to "fix" every URL in this list

Reality: Most entries need no fix at all. Typical examples:

  • http:// versions of your pages redirecting to https://;
  • non-www redirecting to www (or the reverse);
  • old URLs from before a redesign redirecting to new ones;
  • URLs with or without a trailing slash redirecting to your preferred form.

All of these are working as intended. Google's report also has a Source column, and its help page notes that, in general, you can fix only issues whose source is listed as "Website", and suggests prioritising those that are in failed or not-started validation. A healthy set of redirects is not something to "validate away".

Myth 3: Redirected URLs pass nothing to the new page

Reality: Google's redirect documentation describes permanent redirects (301 and 308) as a signal that the redirect target should be canonical, and recommends permanent server-side redirects when a page's URL changes. Redirects exist to carry people and search engines from the old address to the new one.

Myth 4: If the number grows, something is wrong

Reality: The count often grows after legitimate changes, like a migration, as Google rediscovers old URLs from links around the web and records that they redirect. A rise right after a planned change is normal. A rise you can't explain is worth a look (see below).

Myth 5: The report shows the status of the target page

Reality: It shows the status of the URL that redirects. Google's help page points out that if you inspect such a URL in the URL Inspection tool, the information applies to the tested URL, ignoring redirects, and it describes how to check the canonical URL's own status from within the report. To confirm the destination is indexed, inspect the destination URL itself.

When "Page with redirect" does point to a real problem

Look for these patterns in the example URLs:

An important page is redirecting by mistake. If your contact page, a key service page or a top product is listed, check where it now goes. A plugin rule, a mistaken trailing-slash setting or an old migration mapping can hijack a live page.

Redirects land on the wrong place. Many old URLs redirecting to the homepage, or to an unrelated page, waste the redirect. Map old pages to their closest equivalents instead.

Your own site still links to redirecting URLs. If menus, internal links or your XML sitemap use old addresses, Google keeps meeting redirects that you created yourself. Update internal links and make sure the sitemap lists only final URLs.

Redirect chains or loops. If an old URL passes through several redirects, or never resolves, simplify the rules so each old URL goes straight to its final destination in one hop.

Temporary redirects on permanent moves. 302 or 307 redirects for changes you won't reverse send a weaker signal; switch them to 301 or 308.

A 15-minute check

  1. Open the "Page with redirect" list and scan 20 or 30 example URLs.
  2. Note any URL that should be a live page in its own right. Test it in a browser.
  3. For a few typical old URLs, check where they land: right page, one hop?
  4. Open your XML sitemap and confirm it doesn't contain redirecting URLs.
  5. Spot-check your menu and footer links.
  6. Inspect two or three destination URLs in URL Inspection to confirm they're indexed.

If all of that looks right, you can leave the list alone.

FAQ

Should I remove redirected URLs from Google?

No need. They aren't indexed anyway. Leave the redirects in place so visitors and links still reach the right page.

Should I click "Validate fix" for this status?

Usually not. Validation is for issues you've corrected. Correctly working redirects aren't an issue to fix.

How long until old URLs disappear from the report?

The report reflects Google's records as it recrawls. Redirected URLs can remain listed for a long time; that's harmless.

My new page isn't indexed either. Is that because of the redirect?

Not necessarily. Inspect the new URL and check its own reason in the report; the cause may be something else entirely.

If the "Page with redirect" list includes pages you expected to be live, send us a few of the URLs and we'll trace where they're going and why.

Sources

WhatsAppLet’s talk