Part of our guide: canonical tags and indexing, every Search Console status explained →
Lees deze gids in het Nederlands →
“Page with redirect” means the URL forwards visitors elsewhere, so Google indexes the destination instead — usually exactly what you want. Its broken sibling, “Redirect error”, always needs fixing.
- A long “Page with redirect” list after an https move or redesign is a sign things went right.
- Act only when redirecting URLs sit in your sitemap, are linked internally, or point somewhere wrong.
- “Redirect error” = loop, too-long chain, oversized URL or a broken hop — test with a live URL inspection.
- Keep permanent moves on 301/308 and keep every redirect to a single hop: A→C, not A→B→C.
- Google states server-side redirects do not lose PageRank — chains just waste crawl effort.
“Page with redirect” means this URL redirects somewhere else, so Google indexes the destination, not this URL. That’s normal and usually correct.
It only needs attention when a redirecting URL is still in your sitemap or linked internally, or when the redirect goes somewhere it shouldn’t. Its evil twin, “Redirect error” — loops, long chains, broken targets — always needs fixing.
What it means
Normal vs. worth fixing
Redirect error — the one to fix
Clean-up checklist
FAQ
What “Page with redirect” means
Google’s wording: this is a non-canonical URL that redirects to another page, so it will not be indexed. The redirect works; Google followed it and put the destination in the index instead.
Redirects away
Status: “Page with redirect” — not indexed, on purpose.
Gets indexed
Status: should appear as indexed and inherit the old URL’s signals.
Normal vs. worth fixing
- Normal: http → https, non-www → www (or the reverse), old slugs after you renamed a post, trailing-slash normalisation, deleted pages redirected to a true replacement.
- Worth fixing: redirecting URLs listed in your XML sitemap — a sitemap should only list final, indexable URLs.
- Worth fixing: internal links and menus pointing to URLs that redirect. Every hop wastes crawl effort; link to the final URL directly.
- Worth fixing: a page you want indexed that redirects unexpectedly — often a plugin rule, a language redirect or a login redirect.
| Situation | Status you’ll see | Action |
|---|---|---|
| http → https, www normalisation, renamed slugs | Page with redirect | None — working as designed |
| Redirecting URL still in sitemap or menus | Page with redirect | Point sitemap/links at the final URL |
| Loop or chain that never resolves | Redirect error | Fix at one layer; flatten to one hop |
| Deleted pages mass-redirected to homepage | Soft 404 | Redirect to real equivalents or serve 404/410 |
“Redirect error” — the one you must fix
This separate status means Google couldn’t complete the redirect at all. Google lists the causes: a redirect chain that was too long, a redirect loop, a redirect URL that exceeded the maximum URL length, or a bad or empty URL in the chain. Test the URL with URL Inspection’s live test or any redirect-checker, and make each old URL go directly to its final destination in one 301 hop.
Loops often come from two systems fighting: e.g. a CDN forcing https while the server forces http, or a redirect plugin and .htaccess rule pointing at each other. Fix it at one layer only.
Clean-up checklist
- Sitemap: make sure it lists only final URLs (Yoast and Rank Math handle this automatically for normal posts).
- Internal links: update menus and in-content links to the final URL.
- Use 301 for permanent moves and keep redirects in place for at least a year after a migration.
- Flatten chains: A → B → C becomes A → C and B → C.
- Don’t redirect everything to the homepage — Google tends to treat that as a soft 404.
A long list under “Page with redirect” after a redesign or https move is a sign things went right. Spend your energy on the sitemap and internal links — and on any “Redirect error” entries, which are real breakages.
FAQ
Should I fix “Page with redirect” in Search Console?
Usually no. Only act if the redirecting URL is in your sitemap, linked internally, or is a page you actually wanted indexed.
Should I click Validate fix for “Page with redirect”?
There’s nothing to validate if the redirects are intentional. The URLs will remain in the report as long as Google knows about them, and that’s fine.
Do redirects lose ranking power?
Google has said 301 and other server-side redirects don’t cause a loss of PageRank. Chains still slow crawling, so keep redirects to one hop.
301 or 302?
Use 301 (or 308) for permanent moves. 302/307 signal a temporary move; Google may keep the old URL indexed longer.
How long should I keep redirects after a migration?
Google advises keeping 301 redirects in place for at least a year; longer costs nothing and preserves signals from old links.
Do redirects slow my site down?
Each hop adds a round trip for users and crawlers. One hop is fine; chains of three or more are worth flattening.