What does "Page with redirect" mean in Google Search Console?

Q: What does "Page with redirect" mean in Google Search Console?

The URL redirects elsewhere, so Google indexes the target instead. Usually that is expected; act only if the redirect is a mistake or still linked.

It means the URL redirects to another address, so Google does not index it; it considers the page the redirect points to instead. Google's Page indexing help describes it as a non-canonical URL that redirects to another page. For addresses you moved on purpose, such as http to https, that is expected and needs no fix. Act only when the redirect is a mistake, or when your sitemap and links still use the old URL.

Why does Google report it?

Google keeps a memory of URLs it has found through links, sitemaps and earlier crawls. When it recrawls one and gets a redirect, it follows the redirect, processes the target's content instead, and files the original under Page with redirect in the "not indexed" part of the Page indexing report. The count often grows after a migration or a URL clean-up, simply because Google is still visiting the old addresses.

Is it a problem?

Usually expected	Worth fixing
`http://` redirecting to `https://`	An important page redirecting by mistake
`example.com` redirecting to `www.example.com`, or the reverse	Old URLs sending visitors to the home page instead of the matching new page
A renamed or merged page with a 301 to its successor	Your sitemap still listing URLs that redirect
Trailing-slash or letter-case variants redirecting to one version	Internal links still pointing at redirecting URLs

If the redirect target is the right page and it is indexed, you can leave the entry alone; it is a record, not an error.

How to check a URL in the report

Inspect the redirecting URL with the URL Inspection tool to confirm the status.
Inspect the target URL. It should say "URL is on Google". If the target is not indexed, the problem is the target page, not the redirect.
Check the redirect type with curl -I https://example.com/old-page. Google's redirects guide treats permanent redirects (301 and 308) as a strong signal that the target should be the canonical; temporary ones (302, 303, 307) are not, and the old URL may stay in results.

How to clean up redirects

Point internal links at the final URL, so visitors and crawlers skip the hop.
List only final URLs in your sitemap. Google wants the URLs you want in its results, so a sitemap full of redirects sends mixed signals.
Avoid chains. Google's crawlers follow up to 10 redirect hops, but Google warns that long redirect chains have a negative effect on crawling. Redirect each old URL straight to its final destination.
Use the matching page as the target. A deleted page with no replacement should return 404 or 410 rather than redirect to the home page.
Keep migration redirects in place. After a site move, Google's site move guide recommends keeping redirects for as long as possible, generally at least a year.

Page with redirect vs Redirect error

They sound alike but mean opposite things. Page with redirect says the redirect worked and Google followed it. Redirect error says Google could not complete it, for example because the chain was too long or looped back on itself. Redirect errors need fixing; see Google Search Console coverage errors. Other "not indexed" statuses are covered in Google Search Console excluded pages.

How AutoPSEO helps

AutoPSEO's URL Inspection can inspect the URLs in a sitemap, up to 500 per run, and show each one's coverage state, so redirecting URLs that still sit in your sitemap stand out in one table. The same table flags URLs where the canonical Google selected differs from the one you declared, which shows when Google prefers another address. The Index Tracker then rechecks the target pages daily.