Page With Redirect in Search Console

By Amit Patel

“Page with redirect” is one of the calmest statuses in the Page indexing report: it means Google reached a URL, found it redirects elsewhere, and correctly declined to index the redirecting URL itself. In the overwhelming majority of cases this is exactly what you want and requires nothing from you. The value of understanding it is knowing the handful of situations where a redirect status is a symptom of a real problem — and being able to dismiss the rest without wasting time.

What the Status Actually Means

Google indexes destinations, not detours. When a URL returns a 301 or 302, Google records the redirecting URL as “Page with redirect” and indexes the target instead — so this status describes the source URL, and the real page is elsewhere and indexed normally.

This is why the status lives under “Not indexed” yet is not a failure: the not-indexed URL is a signpost, and the place it points to is what appears in search. You will see it accumulate naturally as a site ages — old post slugs, changed categories, HTTP-to-HTTPS moves, and trailing-slash normalizations all leave redirecting URLs behind. For how redirects fit into overall crawling, the crawlability guide gives the wider picture.

When It Is Completely Normal

Consolidated URLs, HTTPS migrations, www/non-www normalization, trailing-slash canonicalization, and retired pages pointed to sensible replacements all produce this status by design. None of them need fixing.

If you migrated to HTTPS, every old http:// URL should show “Page with redirect” — that is the migration working. The same is true after you consolidate thin pages or merge duplicate category paths. Confirm the destination is the one you intended with the URL Inspection tool, see it resolve to an indexed target, and move on. A large, stable count here is a sign of good housekeeping, not a backlog.

When It Signals a Problem

Four patterns deserve a look: redirect chains and loops, redirects to irrelevant destinations, important URLs that should return 200 but redirect, and internal links or sitemap entries still pointing at the redirecting URL.

A chain (URL A → B → C) wastes crawl budget and dilutes signals — collapse it to a single hop. A redirect that lands on the homepage instead of the closest equivalent page throws away the relevance of the original and often triggers a soft 404 instead. And if a page you actually want indexed shows up here, something upstream — a plugin, a canonical mismatch, or a server rule — is redirecting it by mistake. The most common self-inflicted version is leaving your XML sitemap and internal links pointing at old URLs, so Google keeps re-encountering the redirect; update them to the destinations, a housekeeping task the XML sitemap guide covers.

How to Investigate and Fix

Inspect the URL, read the redirect target and status code, and act only if the destination is wrong, the chain is long, or the URL should not redirect at all.

Use URL Inspection to see Google’s recorded redirect and its target. If the target is correct and it is a single 301, you are done — do not “validate fix,” there is nothing to fix. If it is wrong, correct the redirect rule at its source (server config, CMS, or plugin), point internal links and the sitemap at the final destination, and only then request a re-crawl. Distinguish this cleanly from a genuine indexing exclusion: a redirect status means Google found somewhere to go, whereas exclusions like “Crawled — currently not indexed” mean it chose not to index the page you wanted. Google’s own reference on redirects and Search is the authority on which redirect types pass signals.

Frequently Asked Questions

The Bottom Line

Treat “Page with redirect” as confirmation, not an alarm: it usually means your redirects are doing their job. Spend your attention on the exceptions — chains, wrong targets, and URLs that should not redirect — and keep your sitemap and internal links pointed at final destinations. Everything else in this status is the sound of a healthy, well-maintained site, and the rest of the Search Console cluster covers the statuses that do need work.