Ignore it if
The URLs are old or alternate addresses that should redirect.
Page with redirectUsually fine
“Page with redirect” in Google Search Console: what it means and how to fix it
The URL redirects to another URL, so Google doesn't index it and indexes the destination instead. That's what redirects are for, like http to https, www to non-www, or an old slug to a new one, so it's usually fine. It's worth a look only when a redirect is a mistake or the destination isn't indexed.
What Google says
This is a non-canonical URL that redirects to another page, so it won't be indexed. The page it redirects to may or may not be indexed.
Paraphrased from Google's Page indexing report helpCauses
Why it happens
01http to https, or www to non-www, redirects.
02Trailing slash redirects.
03Old slugs redirected after a post was renamed.
04Your sitemap or internal links still point to the old URLs.
Triage
Is it a problem?
Fix it if
A page you want indexed redirects by mistake.
The redirect goes through several hops, or loops.
Your sitemap lists redirecting URLs.
Fix
How to fix “Page with redirect”
Check any single URL with URL Inspection. After fixing, open the issue in the Page indexing report and click Validate fix; Google says it typically takes up to about two weeks.
- 1Check where it goesRun URL Inspection on the destination, or use curl -I -L on the URL to see each hop.
- 2Make sure the destination is indexedIf it isn't, look up the destination's own status. That's the page that needs attention.
- 3Update your sitemap and linksList only final URLs in the sitemap and point internal links straight at them. It saves Google a hop and sends a clearer signal.
- 4Fix chains and loopsPoint every old URL straight to the final URL in one 301. Chains slow crawling, and loops never resolve.
On Blogizi
A Blogizi blog's sitemap lists each published post's final public URL, so it doesn't send Google to redirects.
Index checks for every post are part of Pro, $19/month with a 7-day trial for $0. Your AI agent can read the same statuses over MCP.
FAQ
Questions about “Page with redirect”
Usually not. Only if a page you want indexed is redirecting by mistake, or the destination isn't indexed.
Use 301 for permanent moves like a renamed post or a domain change. Use 302 only for temporary ones.
Because they redirect to https. That's expected, and Google indexes the https version.
Related statuses
Duplicate without user-selected canonicalGoogle picked another URL as the main version, because this page didn't say which one was.Read →Soft 404The page looks like an error or empty page to Google but returns a success code.Read →Alternate page with proper canonical tagThe page points to another URL as canonical, and Google agreed. Working as intended.Read →
Post not on Google at all? Start with why isn't my blog post on Google, or browse all 9 statuses.
Last reviewed October 19, 2026