← Back to blog

Technical SEO · November 13, 2026 · 8 min read

Page With Redirect in Search Console: What It Means

"Page with redirect" means Googlebot was forwarded elsewhere, so that URL is not indexed. Most entries are harmless old addresses; only three patterns are worth fixing.

By FluxWriter

Page With Redirect in Search Console: What It Means

Page with redirect in Search Console means Googlebot asked for a URL, got sent somewhere else, and will therefore not index that URL. It is a status, not an error, and on most sites the large majority of the entries are old addresses doing exactly what you told them to do. The list grows every time you change a slug, move to HTTPS or merge two posts, and it shrinks only slowly, as Google stops re-crawling addresses nothing links to any more. This walks through which entries you can ignore permanently, the three that are genuinely costing you something, and how to separate them in about twenty minutes.


The Status Describes The URL, Not The Destination

You will find it under Indexing, then Pages, in the group headed "Why pages aren't indexed". That grouping is what causes the alarm. Sitting a few rows below "Server error (5xx)" and "Soft 404", the label reads like a fault report.

What Google is telling you is narrow and literal. It requested URL A, the server answered with a redirect to URL B, so URL A will not be indexed. Nothing in that line says anything about B. If B is a healthy page returning a 200, your content is in search and the entry is simply a record of a move you made on purpose.

The status that does describe a fault has a different name. "Redirect error" means Googlebot could not resolve the chain at all: a loop, too many hops, an empty or invalid URL in the middle. That one deserves attention the day you see it. "Page with redirect" is closer to a filing note.

While you are in there, check which response code you are actually serving. As a rough rule, use a 301 for a move you do not intend to reverse and a 302 only while you genuinely plan to restore the original. Google has said it works out the intent either way over time, but a 302 that has been sitting in place for eight months is signalling something you probably do not mean.

Most Of The Entries Are Old URLs Doing Their Job

Four things fill this report on a normal site, and none of them need fixing.

The first is protocol and hostname normalisation. Every http:// version of every page forwards to https://, and www forwards to the bare domain or the other way round. On a 200-page site that is up to 400 possible entries before you have published anything new.

The second is trailing slashes and letter case. Most servers forward /about to /about/, or /About to /about. Every variant Google has ever encountered gets its own line in the list.

The third is slug changes. WordPress remembers a post's previous slug and forwards the old address automatically, so every time you edit a published post's slug you add another entry here. Shopify offers to create a redirect when you change a product handle, and most people accept. This is correct behaviour. The only cost is a longer list in Search Console.

The fourth is merges. You combine two thin posts into one better one, redirect the loser to the winner, and the loser sits in this report from then on.

Add those up over three or four years of ordinary editing and the report can easily hold more URLs than your site has pages. Assume that anything you deliberately moved will stay in this list for years. It is a history file, not a backlog.

Six Patterns Cover Almost Everything In That List

Export the report and nearly every row will fall into one of six shapes. The table below is a triage sheet rather than a measurement; the order reflects what tends to appear most often on small sites, not a counted average.

What the URL looks like What it usually is Worth acting on
An http:// version of a live page HTTPS migration working correctly No
/page and /page/, or mixed case The server normalising the address No
An old slug for a post that still exists A rename or a merge you made No
A URL still listed in your sitemap A stale or wrongly generated sitemap Yes, this week
A URL your own nav or body copy links to An internal link nobody repointed Yes, this week
A target that returns a second redirect Two migrations stacked on each other Yes, first

The three "No" rows can be left alone for the life of the site. The three "Yes" rows are the rest of this post.

Redirected URLs In Your Sitemap Are The First Thing To Clean Up

A sitemap is a list of the URLs you want indexed. A URL that answers with a 301 cannot be indexed, so listing it is a contradiction. You are asking for a page to be crawled and then refusing to serve it.

This happens more often than it should. Sitemap plugins build from the database rather than from live responses, so a page you redirected at the server or CDN level still shows up in the file. Static generators output whatever is in the content folder, including pages you stopped publishing. Hand-maintained sitemaps go stale within weeks.

The cost is small per URL and real in aggregate. On a 400-URL sitemap carrying 50 redirected entries, 12.5% of what you submit is a dead end, and that is the share of every sitemap-driven crawl spent reading forwarding addresses instead of pages.

The check itself is quick. In Search Console, filter the Page indexing report by sitemap rather than by all known pages. That view contains only URLs you submitted, so anything appearing there as "Page with redirect" is a mistake in your own file rather than an artefact of Google's crawl history. Fix the generator rather than the individual rows, or the same URLs return next month.

Internal Links That Point At Redirects Cost You On Every Crawl

When you rename a post, the redirect handles visitors. It does not go back and edit the twelve other posts linking to the old address.

Those links keep working, which is precisely why nobody notices. Every click and every crawl now takes two requests instead of one. More usefully for you, an internal link is the clearest statement you can make about which URL you consider the real one, and a link to an address that immediately forwards elsewhere is a muddled statement.

The fix is mechanical. Crawl your own site with any tool that reports internal links resolving to a 3xx, then edit the source links to point at the final URL. On a blog of a few hundred posts, expect an afternoon the first time and roughly twenty minutes a year after that. Prioritise the navigation, footer and sidebar, because those appear on every page and usually account for most of the redirected internal links on the whole site.

A Redirect Target That Redirects Again Is Where Pages Go Missing

The genuine failure case in this report is the chain. URL A forwards to B, and B forwards to C. It appears on any site that has been through two changes: a slug edit one year, an HTTPS migration the next, and the old http:// slug now takes two hops to land on anything real.

Every hop is a request that returns no content. One hop costs two requests to reach a page. Two hops cost three. Across 200 old URLs that is 200 extra fetches returning nothing but a forwarding address, repeated every time those URLs get crawled.

The larger risk is the ceiling. Googlebot follows only a limited number of hops in a single crawl attempt before giving up and logging a redirect error instead, and browsers apply their own limit. Two hops will not get you near it. Chains have a habit of growing by one every time someone restructures, though, and almost nobody audits them, so a site can reach the ceiling years after the original move without anyone deliberately touching a redirect rule.

Flattening is the fix and it is dull work. Point A directly at C. Keep B pointing at C as well, because something external may still link to B. Do not delete the intermediate rule in the name of tidiness, because you would be removing a path someone else's link depends on.

FAQ

Should I delete old redirects to clear the report?

No. Deleting a redirect turns a working forward into a 404 and breaks every external link aimed at the old address. The count in Search Console is a record of what your site used to be, not a score you are marked against. Working redirects should stay in place indefinitely.

Will the number ever go down on its own?

It can, slowly. Google re-crawls URLs less often when nothing links to them, and entries do eventually drop out of the report. Treat a falling count as an accounting change rather than an improvement, and do not use it to judge whether a fix worked.

Does this status mean the new page is indexed?

It says nothing about the target at all. The entry only reports that the old URL forwards somewhere. Inspect the destination separately with the URL Inspection tool, because a redirect pointing at a page that is itself excluded is the version of this problem that actually loses you traffic.

The Practical Takeaway

Twenty minutes buys you the triage, and the repairs only follow if the triage finds something. Export the Page indexing report filtered to "Page with redirect", then run three checks in order: whether any of those URLs appear in your sitemap, whether any of them are still linked from your own navigation or posts, and whether any of their targets return a second redirect. Anything surviving all three is history and should be left exactly where it is. Start with the sitemap, because it is the one check you can finish in two minutes. Open your sitemap.xml, run the first twenty URLs through a header checker, and if any of them answer with a 301 you have confirmed the first of the three problems in this report that are actually costing you something.



← All posts