"Page with redirect" in Search Console: when to fix it and when to ignore it
"Page with redirect" means the URL redirects somewhere else, so Google indexes the destination instead of this URL. In most cases this is correct and needs no fix: an http URL redirecting to https, a www URL redirecting to the apex, or an old slug redirecting to a new one should all appear here. Google is confirming your redirects work.
It needs attention only when a URL you want indexed is redirecting, when your sitemap or internal links still point at redirecting URLs, or when the redirect goes somewhere unrelated.
Step by step
1. Scan the examples for URLs you want indexed
Open Indexing → Pages → Page with redirect and read through the examples. Expected entries:
http://versions of your pageswww.or non-www variants, whichever you do not use- Old slugs you changed, and posts you merged
- URLs without the trailing slash, if your permalinks use one
If every example fits those patterns, you are done. If you see a page that should be live and indexed, carry on.
2. Test the URL that surprised you
Check where it goes:
curl -sIL https://example.com/pricing/ | grep -i -E '^(HTTP|location)'
The -L flag follows every hop. Look for an unintended redirect: a leftover rule in Hydrogen SEO → Redirections, an old rule in .htaccess, a host or CDN redirect, or a plugin that redirects based on login state or country. Delete or edit the rule that should not be there.
3. Remove redirecting URLs from your sitemap
Your sitemap should list only final URLs that return 200. Open it from Hydrogen SEO → Sitemap → View Sitemap and spot-check a few entries with curl. Hydrogen SEO builds the sitemap from your current permalinks, so redirected slugs drop out on their own. If you still see old URLs, a page cache or CDN is serving a stale copy; purge it.
4. Update internal links to the final URL
Every internal link to a redirecting URL costs a hop. Replace links to old slugs and http URLs with the final https URL. Menus are a common place for old links to hide. After a domain or https move, a database search-and-replace fixes most of them in one pass.
5. Collapse redirect chains
If a URL redirects to another URL that redirects again, point the first rule straight at the final destination. In Hydrogen SEO → Redirections, edit the old rule's To URL. Chains often appear after two rounds of slug changes, or when an http-to-https redirect runs before a www-to-apex redirect. See fixing redirect chains.
6. Check that redirects go somewhere relevant
A redirect should land on the true replacement. Mass redirects of deleted posts to the homepage are often treated as soft 404s rather than redirects. If a URL has no replacement, let it return 404. The 301 vs 404 post explains the choice.
What the status means
Google does not index a URL that answers with a redirect. It follows the redirect and considers the destination for indexing. The redirecting URL is reported here so you can see it, not because anything failed. A permanent 301 and a temporary 302 both put a URL here, though Google treats a long-lived 302 much like a 301 over time.
When to leave it alone
Almost always. A large count after an https migration, a domain move or a permalink change is exactly what you want to see. The count stays high for months because Google keeps rechecking old URLs it knows about. There is no reason to click Validate fix for expected redirects, and no reason to remove working redirects to make the number drop.
Common questions
Is Page with redirect an error?
No. It is an informational status listing URLs that redirect. It needs action only when a page you want indexed is redirecting.
Will Page with redirect hurt my rankings?
No. The destination page is what gets indexed and ranked. Just keep internal links and your sitemap pointing at final URLs.
Why do http URLs show up here if I redirect them?
Because they redirect. Google found them through old links and reports that they now point to https, which is correct.