Page with redirect in Search Console: when it's fine and what to fix

Search Console lists redirected URLs as not indexed. Most of them are fine. This table shows which redirects need a fix and exactly what to change.

Published

Three URL fields linked by arrows, the middle one red, and a 2 hops pill
In short

"Page with redirect" in Search Console looks like lost pages, but it usually isn't. The listed URLs redirect somewhere else, so Google may index the target instead. For a retired URL or an old http address, that is expected and needs no work. Fix it only when the listed URLs are pages you want in search, or when your own links, sitemap or canonical tags still point at them.

What "Page with redirect" means

A redirect sends a visitor or crawler from one URL to another. Google's Page indexing report help describes this status as a non-canonical URL that redirects to another page, so the URL itself is not indexed.

The redirect target "might or might not be indexed, depending on what Google thinks about that target URL." So the status tells you about the old address, not about the page that matters. You find it in the Page indexing report, in the "Why pages aren't indexed" table.

Google doesn't call it an error. Its help page only says to "read the specific description to see if this is an error that you should address."

When it's fine and when to fix it

Look at why each URL redirects. The table covers the causes you will see most often.

Why the URL redirectsFine or fixWhat to do
You retired the page and 301 it to its replacementFineInspect the target and confirm it is indexed
An http or www variant redirects to your main addressFineKeep the http URLs out of your sitemap
Your sitemap lists URLs that redirectFixList only the final URLs
Internal links point at URLs that redirectFixLink straight to the final URL
The redirect passes through several hopsFixRedirect the first URL straight to the last one
Many old URLs all redirect to the homepageFixRedirect each one to its closest relevant page
A permanent move uses a 302 or a delayed meta refreshFixSwitch to a 301 or 308
The redirect only happens in JavaScriptFix if you canMove it to a server-side redirect

If every row you find is "Fine", leave the report alone. A large count is normal after a site move or an HTTPS switch, because every old URL shows up here.

How to check a listed URL

URL Inspection has one trap: its report is about the URL you typed, and it ignores the redirect. Google's help says the inspection "reflects the tested URL" and doesn't follow redirects, so you have to check the target separately.

  1. Open the Page indexing report and click the "Page with redirect" row.
  2. Scan the example URLs. Old slugs, http addresses and parameter variants are usually fine.
  3. Paste a URL you care about into the URL Inspection bar at the top.
  4. Under Page indexing, find the Indexing section and click the INSPECT button there. That runs the report on the canonical page, which is usually your redirect target.
  5. Confirm the target says it is on Google. If it isn't, the problem lives on the target page, not on the redirect.

The live test does follow redirects, but Google notes it doesn't tell you that it followed one. A green live test on an old URL can be the target's result, not the old URL's.

How to fix the problem cases

Every fix aims at the same result: your site should point only at final URLs that return a 200 status. Redirects stay for visitors and old backlinks, but your own signals skip them.

Sitemap and internal links

Google says that "all pages listed in a sitemap are suggested as canonicals." Listing a redirecting URL asks Google to index a page you moved away from. Replace each one with its final address.

Do the same for menus, footers and links inside your content. Google's site move guide tells you to update your own internal links to the new URLs. It also tells you to keep the redirects for at least a year.

Redirect chains

A redirect chain is a URL that redirects to another URL that redirects again. Google says to avoid chaining and redirect to the final destination directly. If you can't, it asks for "ideally no more than 3 and fewer than 5" hops.

Google's HTTP status code guide says its crawlers follow up to 10 hops by default. A hop is one redirect, so three URLs in a row make 2 hops. Collapse the chain so the first URL points straight to the last one:

Start URLMiddle URLFinal URL
Before (2 hops)http://example.com/shoeshttps://example.com/shoeshttps://example.com/shoes/
After (1 hop)http://example.com/shoeshttps://example.com/shoes/

Our guide to redirect chains shows how to find them across a whole site.

Redirects to the homepage

Sending many old URLs to one unrelated page, such as the homepage, "might be treated as a soft 404 error," says Google's site move guide. A soft 404 is a page that returns 200 but looks like a missing page to Google. Redirect each old URL to the page that replaced it.

If nothing replaced it, a plain 404 or 410 is the honest answer. Merging several old pages into one new page and redirecting them all there is fine. If removed pages start showing up as errors instead, see pages returning errors.

Temporary redirects and JavaScript

Google treats a 301 as "a strong signal that the redirect target should be processed" and a 302 as "a weak signal." A 308 equals a 301, and a 307 equals a 302. Google's redirects guide adds that permanent redirects show the new URL in results, while temporary ones show the old one.

An instant meta refresh counts as permanent, and a delayed one as temporary. For JavaScript, Google says to use it "only if you can't do server-side or meta refresh redirects," because Google might never see it if rendering fails.

Found this useful?

Share it with whoever runs your site’s SEO.

Ready when you are!Crawly, the UpCrawler mascot

Catch the next drop on day one.

UpCrawler watches your uptime, crawls every page and tracks Search Console, so you see the turn the day it happens.

14 days freeNo cardNothing to install