What does “Page with redirect” mean in Search Console?

Updated · Check Before Publish

“Page with redirect” means Search Console found a URL that redirects to another page, so that URL itself is not indexed; its target might be. Google's definition does not call it an error. Check where the redirect leads: if it leads to the page you want, leave it. “Redirect error” is the status that is an error.

The short version

  • Page with redirect is Google's name for a non-canonical URL that redirects to another page. Google says this URL “will not be indexed” and the target “might or might not be indexed”.
  • It is listed under Not indexed, and Google describes that list as pages that are “not necessarily because of an error”. The entry itself gives no instruction to fix anything.
  • Redirect error is different: Google lists a redirect chain that was too long, a redirect loop, a redirect URL that exceeded the maximum URL length, and a bad or empty URL in the chain.
  • Googlebot follows up to 10 redirect hops, but Google advises keeping a chain “ideally no more than 3 and fewer than 5”.
  • Permanent redirects show the new URL in search results; temporary redirects show the source page.

When to leave it alone

A URL you redirected on purpose will normally show up under this status: http:// to https://, example.com to www.example.com, or an old address after a move. Google says old URLs can keep appearing “even though the new URLs are already indexed. This is normal”. Two things are worth checking before you leave it:

  1. The redirect ends on the page you want people to find, in one step or very few.
  2. Your own links, canonical tags and sitemap point at the final URL, not at the redirecting one. Google's guidance is to link to the canonical URL and to replace redirect URLs in a sitemap with the URLs that should actually be crawled.

How Google reads each kind of redirect

RedirectWhat Google says it does
301 and 308 (permanent)Google follows the redirect and uses it as a strong signal that the target should be canonical.
302, 303 and 307 (temporary)Google follows the redirect and uses it as a weak signal. The target “might still be indexed if other canonicalization signals are present”.
Meta refreshAn instant one (0 seconds) is read as permanent; one with a delay is read as temporary.
JavaScript redirectGoogle says to use it only if you can't do server-side or meta refresh redirects, because rendering may fail and Google “might never see it”.

Google also says a server-side redirect has the highest chance of being interpreted correctly, and that the status codes it treats alike are still semantically different, so use the one that fits.

See the whole chain for one URL

Paste the URL that Search Console lists. The checker follows the redirects, shows every hop with its status code and the page it finally reaches, and says so when there is more than one hop. It checks the final page for everything else a pre-publish check covers at the same time.

Opens the Website Pre-Publish Checker and runs it. Free, no account. The address is not stored and never goes into the URL bar.

From a terminal, curl -sIL https://example.com/old-page prints the status line and Location header of every hop.

What we tested

On 2026-10-13 we ran the live Website Pre-Publish Checker on this site's own http:// address and on a small test site we built for this guide: a handful of redirect rules on a preview that search engines are told not to index, not part of this site. This is what it reported:

What we enteredWhat the checker reported
http://checkbeforepublish.com/ (this site)“The URL redirects 2× before loading”: 301 to https://checkbeforepublish.com/, 301 to https://www.checkbeforepublish.com/, then 200. Advice: redirect in one step.
One redirect, answered with 301, 302, 307 or 308 (four test URLs)“The URL redirects to a different page”, with the status code of the hop shown, then 200 on the target.
A chain of three 301s“The URL redirects 3× before loading”, with each hop listed.
A chain of twelve 301s“Couldn't check this URL. More than 5 redirects.”
Two 302 rules pointing at each other (a loop)The same message: “Couldn't check this URL. More than 5 redirects.”
A page with <meta http-equiv="refresh" content="0;url=/r/final">“No redirects”: the checker reports HTTP redirects only.

What that means for you: the checker follows at most five redirects, a limit lower than Googlebot's ten, and it cannot tell a long chain from a loop. For either case, use curl -sIL or your browser's developer tools to see where it goes. A meta refresh redirect is invisible to it, although Google reads an instant one as a permanent redirect.

How to fix a Redirect error

  1. Find out which of the four causes you have. Google suggests a web debugging tool such as Lighthouse for more details about the redirect.
  2. Chain too long: point the first URL straight at the final one. Fewer than five hops is Google's advice; one is better.
  3. Loop: look for two rules that send a URL to each other, often one in the server configuration and one in a CMS or plugin.
  4. Bad or empty target: fix the Location value the rule produces.
  5. Update internal links, canonical tags and the sitemap to the final URL, then choose Validate fix on the issue in Search Console. Google says validation “typically takes up to about two weeks, but in some cases can take much longer”.

What this can't tell you

It cannot see which URL Google chose as canonical, or whether the target is indexed: that is in URL Inspection. It fetches from our server, not Google's. And the Google pages we read give no time for a redirect change to show up in search; the only timing they give is for validating a fix.

Related: Alternate page with proper canonical tag, soft 404 and why a page isn't showing up on Google.

Sources

We read these official pages on 2026-10-13.

Related guides