Does “Page with redirect” hurt rankings?

No, the status itself doesn't. Google indexes the target and passes signals to it. It's still worth removing redirecting URLs from your sitemap and internal links.

Why does Google know these URLs at all?

From old links (including other sites), old sitemaps or its crawl history. After a migration this report naturally grows.

When a page that should respond on its own starts redirecting — for example after a server or CDN rule change — or when the redirect leads to the wrong place.

Page with redirect

The URL redirects to another one, so Google indexes the target instead. Usually that's normal — old URLs after a migration, or http and non-www versions. It becomes a problem when redirecting URLs sit in your sitemap, internal links or canonicals, or when a page that should rank starts redirecting.

What this status means

Google visited the URL and got a redirect (301, 302, 307, 308) to another URL. It doesn't index the redirecting URL, only — if it can — the target. In the Pages report this sits under "Not indexed", but it usually needs no action.

When it's normal

old URLs after a migration or a structure change,
http → https, non-www → www (or the reverse), trailing slash variants,
short campaign URLs, old promotions redirected to categories.

When to act

Redirecting URLs in the sitemap — a sitemap should list only URLs returning 200.
Internal links to redirects — each one adds a hop; replace them with the final URL.
A canonical pointing to a redirect — conflicting signals, Google will decide itself.
A page that should rank is redirecting — check server, plugin and CDN rules.
The redirect goes to the wrong place — for example the homepage instead of an equivalent.

How to check

The redirect checker shows the full chain for up to 10 URLs from the report at once: the status of every hop, the target and the final page's state. Look for chains, 302s and targets with errors.

How to keep an eye on it

An important page that suddenly starts redirecting is usually the result of a rule change after a release.

IndexRise checks the status code of monitored pages every night. When a page that used to respond on its own starts redirecting, you get a critical event with the redirect target.