Page With Redirect Status
Page with redirect is usually Search Console reporting a redirect that works as intended, but internal links and chains deserve a closer look.
A "Page with redirect" status in Google Search Console means Google found a URL that redirects to another page, so that URL itself is not indexed. For blogs, it is often a harmless sign of normal redirects, such as HTTP to HTTPS or an old address after a migration. Search Console labels can change over time.
What the Status Means
In the Page indexing report, Google describes this status as a non-canonical URL that redirects to another page, and says the URL will not be indexed. The redirect target is judged on its own: it may or may not be indexed, depending on Google's assessment of that page.
Google's crawlers follow the redirect and process only the content of the final URL. With a permanent redirect (301 or 308), Google also uses the redirect as a signal that the target should be the canonical URL; with a temporary one (302 or 307), it follows the redirect but doesn't use it as that signal, according to Google Search Central.
When It Is Normal
For bloggers setting up HTTP to HTTPS redirects, or moving posts to a new URL structure, seeing many "Page with redirect" URLs in Search Console is common and expected. Any blog post with an old URL that redirects to its new URL can show up with this status while the new URL is indexed. The same applies when one host version redirects to another, for example example.com to www.example.com, or when a Blogspot blog with a custom domain sends its old blogspot.com addresses to the new domain.
The "Page with redirect" status should not be considered an error in these cases. It is not the destination page being excluded, but the redirecting URL itself, and no action is needed as long as the target is the page you intended and it is indexed.
When It Signals a Problem
Look closer when redirecting URLs are still used as internal links or listed in your sitemap. Google advises linking to the canonical URL within a site, and every URL in a sitemap is treated as a suggested canonical, so a sitemap full of redirecting addresses sends mixed signals. Redirect chains, where a URL passes through several redirects before reaching the final page, also waste crawling and slow visitors down. Google's crawlers follow up to 10 redirect hops by default; chains that are too long or loop appear under the separate "Redirect error" status, which does need fixing.
To check, open a sample of the listed URLs with the URL Inspection tool and confirm that each one lands on the intended page in a single step and that the destination is indexed. Then update internal links, menus and the sitemap so they point directly to the final URLs, and replace any chain with one redirect from the original address to the destination.
If the redirect targets are the pages you want in search and they are indexed, the redirecting URLs in the report are harmless and need no action.
