Page with Redirect (GSC Status)

TL;DR — “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. is not an error. It just means the URL Google crawled sends visitors somewhere else (it redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't.), so Google indexes the destination instead of the redirecting URL. For most sites this is exactly what you want — old URLs pointing to new ones. You almost never need to do anything about it.

What “Page with redirect” means

Google defines this as a non-canonical URLHow search engines pick one canonical URL among duplicates and consolidate signals onto it. that redirects and therefore is not indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. as that URL. Evidence for this claim Google defines Page with redirect as a non-canonical URL that redirects and therefore is not indexed as that URL. Scope: Google Search Console report terminology and documented Search behavior; the label alone may not prove the underlying root cause. Confidence: high · Verified: 2026-07-14 Google: Page indexing report A redirect is also a canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. signal toward its target, but the target’s indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. is not guaranteed. Evidence for this claim Google recommends permanent server-side redirects for permanent URL moves and treats redirects as canonical signals. Scope: Google Search Console report terminology and documented Search behavior; the label alone may not prove the underlying root cause. Confidence: high · Verified: 2026-07-14 Google: Redirects and Search

You opened the Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results., scrolled to “Why pages aren’t indexed,” and saw Page with redirect with a count next to it. The word “redirect” plus the fact that it’s filed under “not indexed” makes it look like something broke.

It didn’t. A redirect is a way of sending people and botsA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. to a new URL when they ask for an old one. “Page with redirect” simply means: the URL Google tried to crawl redirects to another page. Because that URL is a doorway to somewhere else, Google doesn’t index the doorway — the redirecting URL doesn’t get indexed, on purpose. What happens to the destination is a separate question: Google evaluates it on its own merits, so it may or may not end up indexed. “Page with redirect” only tells you the doorway is closed, not that the room on the other side is furnished — check the destination itself if it matters.

Why this is normal

Almost every site has lots of these, and they’re healthy:

• HTTP → HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.'. Every http:// URL redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. to its secure https:// version. Those old http:// URLs show up here.
• www vs non-www. You pick one (say www.example.com) and redirect the other. The redirected one lands here.
• Trailing slashA trailing slash is the forward slash (/) at the end of a URL — example.com/page/ versus example.com/page. Except at the bare root domain, the two versions are different URLs to search engines, so you pick one format and enforce it.. /page redirecting to /page/ (or the reverse).
• Old pages after a move. You moved or merged a page and 301’d the old URL to the new one. The old URL now reports “Page with redirect” — which is the sign your redirect is working.

In all of these, you want the old URL out of the index and the new one in it. Seeing it here means Google understood the redirect.

Do I need to fix it?

Usually no. Nine times out of ten there’s nothing to do. You only look closer if:

• An important page you wanted indexed ended up redirecting somewhere by accident.
• The redirect points to the wrong or irrelevant page.
• It’s actually a broken redirect (a loop, or a long chain of hops) — but those usually show up under a different status called “Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\".”

That last one is the big thing to understand: “Page with redirect” and “Redirect error” are not the same. One is a working redirect (expected). The other is a broken redirect (a real problem). Don’t treat this status like an error just because it’s in the “not indexed” list.

Want the full breakdown — permanent vs temporary redirects, the side-by-side with “Redirect error,” and whether to click “Validate fix” — switch to the Advanced tab.

TL;DR — “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” is not an error. Google’s own wording: it’s “a non-canonical URLHow search engines pick one canonical URL among duplicates and consolidate signals onto it. that redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. to another page. As such, this URL will not be indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..” That’s a guarantee about the redirecting URL only — the destination is a separate question, and Google says the target “might or might not be indexed,” depending on its own evaluation of that URL. The whole “not indexed” group is, in Google’s words, “not necessarily because of an error.” Most entries are intentional 301s — HTTP→HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', www/non-www, trailing-slash normalization, old post-migration URLs. Keep it firmly separate from the sibling Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\", which flags broken redirects (chain too long, loop, over-length URL, bad/empty URL). For permanent (301/308) redirects, signals consolidate forward to the target, so you don’t lose the old URL’s equity. Only act if an important page was redirected by mistake, the target is wrong, or it’s a chain/loop actually causing problems — and you usually don’t need to click “Validate fix.”

It’s a status, not an error

The label reports a working redirecting URL rather than proving a redirect failure. Evidence for this claim Google defines Page with redirect as a non-canonical URL that redirects and therefore is not indexed as that URL. Scope: Google Search Console report terminology and documented Search behavior; the label alone may not prove the underlying root cause. Confidence: high · Verified: 2026-07-14 Google: Page indexing report Google recommends permanent server-side redirects when a URL has permanently moved. Evidence for this claim Google recommends permanent server-side redirects for permanent URL moves and treats redirects as canonical signals. Scope: Google Search Console report terminology and documented Search behavior; the label alone may not prove the underlying root cause. Confidence: high · Verified: 2026-07-14 Google: Redirects and Search

The single most important thing to fix in your head: this is a report status, not a problem report. Google groups “Page with redirect” under “Why pages aren’t indexed,” and the framing for that entire group is explicit — these pages “have not been indexed, but not necessarily because of an error.” You’re meant to read each status and decide whether that specific one needs attention. For this one, the answer is almost always no.

Google’s definition is one sentence: “Page with redirect” is “a non-canonical URL that redirects to another page. As such, this URL will not be indexed.” That last clause is doing all the work. The URL isn’t failing to be indexed — it’s correctly not indexed, because it’s a redirect, and you don’t index the doorway. Google is explicit that this doesn’t settle what happens on the other side of the door: “the target URL of the redirect might or might not be indexed, depending on what Google thinks about that target URL.” The status tells you about the source; the target needs its own check.

Why the URL isn’t indexed (and what is)

This is canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. in action. When the same content is reachable at more than one URL, Google picks one representative — the canonical — and indexes that. A URL that redirects is, by definition, non-canonical: it’s handing off to another URL, so the redirecting URL itself is not indexed. That’s guaranteed. What isn’t guaranteed is the redirect target: Google’s own wording is that the target “might or might not be indexed, depending on what Google thinks about that target URL.” A permanent redirectA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. is a strong hint the target should be canonical, not a promise it will be indexed — so “Page with redirect” reports the redirecting URL here regardless of what ultimately happens to the target.

The redirect type changes what Google does with it:

• Permanent redirects (301, 308) tell Google to show the redirect target in search results — the indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. pipeline uses the redirect as a signal that the target should be canonical. This is what you want for a real move.
• Temporary redirectsA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. (302, 303, 307, delayed meta refreshA meta refresh redirect is a client-side redirect written as an HTML <meta http-equiv=\"refresh\"> tag (or an equivalent HTTP Refresh header) — not an HTTP status code. The server returns a normal 200, then the browser navigates after the page loads. An instant (0-second) one is read by Google as permanent; a delayed one as temporary.) tell Google to keep showing the source page. If you used a 302 for a permanent move you want indexed at the new URL, that’s a signal mismatch worth correcting to a 301.

In practice Google can eventually treat a persistent 302 as if it were permanent. I’ve seen this directly — I once 302-redirected one established site to another, and once Google had seen the redirect for a while, it dropped the old domain in favor of the new one and moved indexing to the destination anyway. That’s a useful data point, not an excuse: for a permanent move you intend, use a 301/308 so the signal is unambiguous from day one rather than hoping Google reinterprets a temporary one.

You don’t lose the old URL’s equity

A worry I hear: “if my old URL isn’t indexed, am I throwing away its links and authority?” No — for permanent redirects, signals consolidate forward. As Joshua Hardwick and I put it in our Ahrefs redirects guide, permanent redirects are a strong canonicalization hint that signals from a page, like links, should consolidate forward to the new URL. The destination inherits the value. Being listed under “Page with redirect” is the mechanism of that consolidation showing up in the report, not evidence of loss.

The expected reasons you’ll see this

Run down the list and you’ll recognize almost all of your entries:

• HTTP → HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.'. Every insecure URL 301s to its secure version.
• www ↔ non-www normalization. You canonicalize to one host; the other redirects.
• Trailing-slash normalization. /page ⇄ /page/.
• Old post-migration URLs. After a migration, a flood of old URLs reporting “Page with redirect” is the healthy signal that your redirects are working — don’t expect the count to disappear or hit zero on a fixed timeline. Expected old URLs can stay known and reported indefinitely; what to actually track is whether the new URLs are getting indexed with themselves as canonical. A spike here after a migration is good news, not a fire, but confirm it by checking the destinations, not by watching the old count shrink.
• Retired pages 301’d to relevant replacements. Standard housekeeping.

”Page with redirect” vs “Redirect error” — the key difference

This is the distinction most write-ups blur, and it’s the whole reason to read this page. They are two different statuses with opposite meanings.

Page with redirect = a working redirect. The URL redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. somewhere, Google follows it, indexes the destination, and reports the source here. Expected. Not an error.

Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\" = a broken redirect Google couldn’t resolve. Google lists the causes: “a redirect chainA → B → C instead of A → C. Each hop loses link equity and adds latency. that was too long,” “a redirect loopA redirect loop is a chain of redirects that circles back on itself instead of ever reaching a live page — URL A redirects to B and B redirects back to A (or a longer cycle). No page ever returns a 200, so browsers show ERR_TOO_MANY_REDIRECTS and crawlers can't index anything.,” “a redirect URL that eventually exceeded the max URL length,” and “a bad or empty URL in the redirect chain.” That’s a genuine problem — fix the redirect itself.

So when you triage the Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason.: “Page with redirect” → almost always leave it. “Redirect error” → go fix the chain/loop. (There’s a full side-by-side in the Frameworks tab.) If you see a URL you expected to be a clean single hop showing up under Redirect error, that’s your chain or loop to collapse.

When you actually do need to act

The minority of cases where “Page with redirect” is telling you something:

1. An important page got redirected by accident. You wanted it indexed, and a bad rule (a stray rewrite, an over-broad 301, a CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. setting) is sending it elsewhere. Remove the redirect so the page returns 200.
2. The redirect points at the wrong or irrelevant page. A 301 to the homepage instead of the closest replacement, for instance. Repoint it to the right target.
3. It’s secretly a chain or loop. True loops will usually land in the separate “Redirect error” status. A chain that still “works” isn’t automatically a fire — I wouldn’t chase every single extra hop. What’s worth fixing: chains long enough to add real crawl or user latency, chains that make it hard to verify the actual final destination, or anything unreliable or annoying to maintain. Collapse A → B → C into A → C when one of those applies, not as a rule for its own sake.
4. A 302 that should be a 301. For a permanent move you want indexed at the new URL, switch temporary to permanent.

If none of those apply, you’re done — the entry is correct.

How to investigate a flagged URL

• Use URL Inspection on the specific URL. Confirm it does redirect, and that it redirects to the URL you intended.
• Check the destination is indexable — it should return 200 and be indexed itself (not noindex, not blocked, not another redirect). If the destination has its own problem, that’s where to look.
• Confirm the hop count. One hop is ideal. Multiple hops → collapse them.

TIP Verify the destination and hop count

A redirect is expected here; the useful check is whether it reaches the intended live destination directly.

Trace the source URL and inspect its final destination with my free HTTP Status Checker Free

1. Test the exact source URL reported by Search Console.
2. Confirm the final URL is the intended canonical live page.
3. Update the redirect when it points to the wrong host, wrong page, or an unnecessary intermediate hop.

Tap to enlarge

Do you need to click “Validate fix”?

For expected, intentional redirects: no. “Validate fix” is for statuses you’ve actually corrected — it asks Google to re-check URLs you changed. A working 301 isn’t something you fixed, so there’s nothing to validate. You’d only use it after you genuinely repaired something (removed an accidental redirect, collapsed a chain that was throwing a Redirect error). Don’t feel obligated to drive this count to zero; for most sites it never will be, and that’s fine.

One note on Bing

“Page with redirect” is a Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. label, not a universal concept. Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. surfaces redirect information differently and doesn’t use this status name. The underlying advice is the same on both engines — use 301s for permanent moves and avoid long chains — but if you’re looking for this exact wording in Bing, you won’t find it.

For the broader picture, see the Indexing hub and the Page Indexing report overview. The sibling statuses — Redirect error (broken redirects), Duplicate, Google chose a different canonical than user, and the Crawled – currently not indexedA Google Search Console Page Indexing status meaning Googlebot fetched the page but Google decided not to index it — usually a content- or site-quality signal, not a technical error. family — round out the “not indexed” reasons you’ll triage alongside this one.

AI summary

A condensed take on the Advanced version:

• “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” is not an error. Google: it’s “a non-canonical URLHow search engines pick one canonical URL among duplicates and consolidate signals onto it. that redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. to another page. As such, this URL will not be indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..” The whole not-indexed group is “not necessarily because of an error.”
• The redirecting URL is not indexed, by design — the target is a separate question. Google’s own wording: the redirect target “might or might not be indexed, depending on what Google thinks about that target URL.” Check the destination independently rather than assuming it’s indexed.
• Most entries are intentional 301s: HTTP→HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', www/non-www, trailing-slash normalization, old post-migration URLs, retired pages redirected to replacements.
• Permanent (301/308) vs temporary (302/307) matters: permanent redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. are a strong signal the target should be canonical; temporary redirectsA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. don’t carry that same signal, and Google may keep showing the source.
• You don’t lose equity: for permanent redirects, signals consolidate forward to the destination.
• “Page with redirect” ≠ “Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\".” The latter is broken — chain too long, loop, over-length URL, or bad/empty URL — and does need fixing.
• Don’t treat every extra redirect hop as a loss. Prioritize genuinely long chains, loops, and anything unreliable or hard to verify/maintain over chasing a single-hop ideal everywhere.
• A post-migration spike is healthy, but it won’t necessarily hit zero. Confirm health by checking the new URLs are indexed as canonical, not by watching the old count shrink.
• Act only if: an important page was redirected by accident, the target is wrong/irrelevant, it’s a genuinely problematic chain/loop, or a 302 should be a 301.
• Investigate with URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version.: confirm the redirect, confirm the target is the intended URL and is itself indexable (200, indexed).
• You usually don’t need to click “Validate fix” for expected redirects — that button is for things you actually corrected.

Official documentation

Primary-source documentation from the search engines.

Google

• Page Indexing report — the report itself, the “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” definition, the “not necessarily because of an error” framing, and the separate “Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\"” causes.
• Redirects and Google Search — how permanent vs temporary redirects affect what Google indexes, and why a permanent server-side redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. is the strongest signal.
• What is URL canonicalization — why a redirecting (non-canonical) URL isn’t the one indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..

Bing / Microsoft

• Bing Webmaster Guidelines — Bing has no “Page with redirect” status, but the underlying advice (use 301s for permanent moves, avoid long chains) is the same.

Quotes from the source

On-the-record statements from Google. Each link is a deep link that jumps to the quoted passage on the source page.

Google — what “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” means

• “This is a non-canonical URLHow search engines pick one canonical URL among duplicates and consolidate signals onto it. that redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. to another page. As such, this URL will not be indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..” — Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Help, Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason.. Jump to quote

Google — it’s not necessarily an error

• “These pages have not been indexed, but not necessarily because of an error. Read the specific description to see if this is an error that you should address.” — Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Help, Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason.. Jump to quote

Google — the different, broken status: “Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\"”

• The causes Google lists for Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\" (not this status): “A redirect chainA → B → C instead of A → C. Each hop loses link equity and adds latency. that was too long” · “A redirect loopA redirect loop is a chain of redirects that circles back on itself instead of ever reaching a live page — URL A redirects to B and B redirects back to A (or a longer cycle). No page ever returns a 200, so browsers show ERR_TOO_MANY_REDIRECTS and crawlers can't index anything.” · “A redirect URL that eventually exceeded the max URL length” · “A bad or empty URL in the redirect chainA → B → C instead of A → C. Each hop loses link equity and adds latency..” — Google Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. Help, Page IndexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. report. Jump to quote

Google — use a permanent server-side redirect for moves

• “If you need to change the URL of a page as it is shown in search engine results, we recommend that you use a permanent server-side redirect whenever possible.” — Google Search Central, Redirects and Google Search. Jump to quote

The mental models

1. Doorway vs room. A redirecting URL is a doorway; the destination is the room. Google indexes the room, not the doorway. “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” is just the report telling you which URLs are doorways. Nothing is missing — the content lives at the destination.

2. “Page with redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't.” vs “Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\"” — the side-by-side. The one table that prevents the most wasted effort:

3. The triage rule. For any “Page with redirect” entry, ask three questions. Did I intend this URL to redirect? Is it going to the right place? Is it a single hop? Three yeses → leave it. Any no → that’s your one to look at.

4. Permanent vs temporary = what gets indexed.

• 301 / 308 (permanent) → Google indexes the target and consolidates signals forward. Use for real moves.
• 302 / 307 (temporary) → Google may keep showing the source. If the move is permanent and you want the new URL indexed, switch to 301/308.

5. A migration spike is a feature, not a bug. After a migration, old URLs flooding into “Page with redirect” is the expected sign your redirects are live. Don’t expect the count to necessarily shrink to zero or on a set timeline — expected old URLs can stay known and reported indefinitely. Confirm health by checking that the new URLs are indexed with themselves as canonical, not by watching this number. Don’t panic-validate it.

”Page with redirect” triage checklist

Work an entry (or the whole list) through this. Most stop at the first box.

Is it expected? (almost always yes)

• The redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. is intentional — HTTP→HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', www/non-www, trailing-slash normalization, an old URL 301’d after a move, or a retired page sent to a relevant replacement.
• The page you want indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. is not in this list (only the old/duplicate URLs are). → If both true, you’re done. No action.

Confirm with URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. (when you want to be sure)

• URL Inspection shows the URL does redirect, and to the URL you intended.
• The destination returns 200 and is itself indexable (not noindex, not blocked, not another redirect).
• It’s a single hop, not a chain.

Act only if one of these is true

• An important page was redirected by accident → remove the redirect so it returns 200.
• The redirect points to the wrong/irrelevant page → repoint it to the correct target.
• It’s a chain (A → B → C) → collapse to A → C.
• It’s flagged under Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\" instead (loop / chain too long / over-length / bad URL) → fix the broken redirect there.
• It’s a 302 that should be a 301 for a permanent move → switch to permanent.

Don’t

• Don’t click “Validate fix” for redirects you didn’t actually change.
• Don’t try to drive this count to zero — for most sites it never reaches zero, and that’s correct.
• Don’t assume you’re losing link equityPageRank is Google's original recursive link-graph algorithm: a page's score depends on the scores of the pages linking to it, and in the published model each page's score is split across its outbound links (the simplified version: links are weighted votes). Google says it's evolved since launch but still part of its core ranking systems. — permanent redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. consolidate signals forward to the destination.

Mistakes people make with “Page with redirect”

Pulled from the misreadings I see most often — all preventable once you know what this status actually is.

Treating it as an error and trying to drive the count to zero. “Page with redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't.” sits under “Why pages aren’t indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.,” and that framing alone makes people chase the number down. Google’s own wording for the whole group is “not necessarily because of an error.” What to do instead: leave intentional redirects alone. For most sites this number never hits zero, and it shouldn’t.

Clicking “Validate fix” on redirects you never touched. That button asks Google to re-check URLs you actually changed. Clicking it on a working, untouched 301 wastes a validation cycle and tells you nothing you didn’t already know. What to do instead: only validate after you’ve genuinely corrected something — removed an accidental redirect, repointed a wrong target, collapsed a chain.

Missing that an important page got redirected by accident. A stray CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. rule, an over-broad rewrite, or a leftover 301 from an old test can quietly send a page you want indexed into this list, where it looks identical to the healthy HTTP→HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.' entries around it. What to do instead: scan the flagged list for any URL you didn’t intend to redirect, not just the total count.

Assuming “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” and “Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\"” are the same problem. They sound alike and sit in the same report, but one is expected (a working redirect) and one is broken (a chain, loop, over-length URL, or bad/empty URL in the chain). Treating both as “redirect trouble” means you either panic over healthy entries or, worse, ignore the ones that genuinely need fixing. What to do instead: triage them separately — see the Frameworks tab for the side-by-side.

Treating every extra hop as a material SEO loss. A→B→C can resolve fine and still report cleanly here, and I wouldn’t obsess over collapsing every single additional hop just because it exists. What actually deserves attention: chains long or slow enough to matter for crawl or user latency, chains that make it harder to confirm the real final destination, and anything unreliable or a pain to maintain. What to do instead: prioritize genuinely long chains, loops, and reliability problems over chasing a “single hop everywhere” ideal.

Redirecting to the wrong or irrelevant page during a migration. Blanket 301’ing old URLs to the homepage (instead of the closest matching replacement) is common under deadline pressure. It reports as a normal “Page with redirect” entry either way — nothing in the report distinguishes a good target from a lazy one. What to do instead: map each old URL 1:1 to its actual replacement before you ship the migration, not after.

Tools for checking a “Page with redirect” entry

Start with your own tools before reaching for GSCA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. one URL at a time — these cover the actual tasks this status raises: confirm the redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., confirm the hop count, and (for a migration-sized flood of entries) verify the whole batch at once.

• Redirect Checker — paste a flagged URL in and see the final status code, every hop, and the destination. This is the fastest way to confirm a single “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” entry is exactly what you expect: one hop, a real 301/308, landing on a 200.
• Bulk HTTP Status Code Checker — paste up to 500 URLs (the whole exported “Page with redirect” list works well here) and get status codes, full redirect chainsA → B → C instead of A → C. Each hop loses link equity and adds latency., and flagged problems — 302s sitting inside a permanent chain, multi-hop redirects, loops, meta refreshA meta refresh redirect is a client-side redirect written as an HTML <meta http-equiv=\"refresh\"> tag (or an equivalent HTTP Refresh header) — not an HTTP status code. The server returns a normal 200, then the browser navigates after the page loads. An instant (0-second) one is read by Google as permanent; a delayed one as temporary.. Use this instead of clicking through URL Inspection one row at a time when the report has more than a handful of entries.
• Redirect Chain Mapper — when a URL from the report turns out to have more than one hop, map it here for the per-hop breakdown (what changed at each step — HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.', www, slash, domain, path), a severity verdict, and exportable cleanup rules for Cloudflare, .htaccess, or nginx so you can collapse the chain to a single hop.
• SEO Migration Planner & Validator — the flood of “Page with redirect” entries you see right after a migration is exactly what this five-step workflow is built for: build and review the 1:1 redirect map, verify the deployed redirects, check old-URL status, compare sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., and spot-check Wayback history — all before or after you ship, instead of discovering a bad mapping URL-by-URL in GSC weeks later.
• URL Inspection (Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.) — still the right tool for confirming Google’s own view of one specific URL: whether it redirects, to where, and whether the destination is the Google-selected canonicalA Google Search Console Page Indexing status: you declared a canonical for this URL, but Google overrode your choice, picked a different page as the canonical, and indexed that one instead..

Prove a “Page with redirect” entry is actually fine

Most entries need no action at all, but when you want proof — after a migration, or because a flagged URL used to matter — these are the checks, in order.

Test 1 — It’s a single, real redirect

• Test to run — Paste the flagged URL into the Redirect Checker (or curl -sIL -o /dev/null -w "%{http_code} %{url_effective}\n" https://example.com/old-url).
• Expected result — One hop, a real server-side 301/308, landing on a destination that returns 200.
• Failure interpretation — More than one hop means a chain to collapse; a 200 on the “redirecting” URL means it isn’t a server redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. at all (JavaScript/meta refreshA meta refresh redirect is a client-side redirect written as an HTML <meta http-equiv=\"refresh\"> tag (or an equivalent HTTP Refresh header) — not an HTTP status code. The server returns a normal 200, then the browser navigates after the page loads. An instant (0-second) one is read by Google as permanent; a delayed one as temporary.); a 302/307 means a temporary code is doing a permanent move’s job.
• Monitoring window — Immediate — the server answers as soon as you check it.
• Rollback trigger — The chain runs long or loops — pull the rule and re-point the old URL straight at the final destination.

Test 2 — Google agrees the destination is canonical

• Test to run — Run URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. on the flagged (redirecting) URL, then on its destination.
• Expected result — The old URL’s status reads “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").,” and the destination is indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. with itself as the Google-selected canonicalA Google Search Console Page Indexing status: you declared a canonical for this URL, but Google overrode your choice, picked a different page as the canonical, and indexed that one instead..
• Failure interpretation — If the destination isn’t indexed, or shows a different URL as canonical, something else (a stray canonical tagA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content., a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. entry, internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. still pointing at the old URL) is muddying the signal.
• Monitoring window — Days to a few weeks for most sites; can run longer for very large ones.
• Rollback trigger — Don’t remove the redirect just because reprocessing is slow — only revisit if the destination never gets indexed at all.

Test 3 — The whole flagged batch is clean, not just one URL

• Test to run — Export the “Page with redirect” list from the Page IndexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. report and run it through the Bulk HTTP Status Code Checker.
• Expected result — Every URL is a single hop to a 200, with no loops, no chains over a couple of hops, and no 302s standing in for a permanent move.
• Failure interpretation — A cluster of chains or 302s usually traces back to one bad redirect rule (a rewrite added on top of an existing one) rather than dozens of separate problems.
• Monitoring window — Immediate for the status codes themselves; pair with a few weeks of GSC Performance data if you’re also confirming traffic recovered on the destinations.
• Rollback trigger — A shared pattern of chains/loops across many URLs — fix the rule that’s generating them, then re-run the batch check.

Test yourself: “Page with redirect”

Five quick questions on the “Page with redirectA Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate \"Redirect error\").” status in Google Search Console. Pick an answer for each, then check.

Page with redirect

A Google Search Console Page Indexing status for a URL that redirects elsewhere. It's not indexed by design because it's a redirect — the destination is a separate question, and Google says the target may or may not end up indexed — usually expected, not an error (unlike the separate "Redirect error").

Parent concept: Page Indexing report · Related: Redirect error, Redirect chain, 301 redirect

Page with redirect

Page with redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. is a status in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason.. It marks a URL that, when crawled, returned a redirect to another page. Because that URL is a redirect and not a final destination, Google doesn’t indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. it — by design. The redirect target is a separate question: Google’s own wording is that the target “might or might not be indexed, depending on what Google thinks about that target URL,” so check the destination independently rather than assuming it’s indexed.

In almost every case this is exactly what you want to see, not a problem to fix. It’s the normal result of an HTTP→HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.' move, a www/non-www or trailing-slash normalization, or any intentional 301 to a new URL. Google itself files these under “not indexed” but says they’re “not necessarily because of an error.”

It only deserves attention when an important page was redirected by mistake, the redirect points at the wrong page, or it’s actually a broken chain or loop — and broken chains and loops usually surface under the separate Redirect errorA Google Search Console Page Indexing status meaning Googlebot couldn't follow a redirect — a chain too long, a loop, a URL over the max length, or a bad/empty URL in the chain. It's a broken redirect to fix, not the normal \"Page with redirect.\" status, which is a genuine error to fix.

Parent concept: Page Indexing report · Related: Redirect error, Redirect chain, 301 redirect

Changelog