Page with redirect

“Page with redirect” in Search Console: when it’s fine and when to fix it

Redirected URLs aren’t indexed, by design. Here’s how to tell normal redirects from the few that cost you, and how to find where Google keeps finding them.

Explore the live demo →

5 days free · no card needed · ends on its own

Updated

Page with redirect in Google Search Console means Google crawled a URL that sends visitors on to a different URL, so it doesn’t index the redirecting URL itself. For URLs you redirected on purpose (old addresses, http to https, non-www to www) that is exactly the right result, and there is nothing to fix. It needs work only when your own sitemaps or internal links still point at the redirecting URLs, when the redirect runs through a chain or lands on the wrong page, or when the destination isn’t indexed either.

Quick check: inspect one of the URLs in Search Console’s URL Inspection tool. If the redirect goes straight to the right page and that page is indexed, leave it alone. If the URL is in one of your sitemaps or linked from your own pages, update those to the final URL.

What “Page with redirect” means

It is one of the reasons listed under “Why pages aren’t indexed” in the Page indexing report. Google’s description is short: this is a non-canonical URL that redirects to another page. Google follows the redirect and treats the destination as the page to index, so the original URL is reported as not indexed. Google also notes that the target may or may not be indexed, which is the one part worth checking.

It is not an error. You don’t need to click Validate fix, and the count doesn’t affect how the rest of your site ranks. On a site that has changed URLs, moved to https or merged pages, thousands of URLs in this status are normal, and they can stay in the report for months because Google still knows about the old addresses and rechecks them now and then.

Don’t confuse it with Redirect error, a different reason in the same report. That one means Google couldn’t complete the redirect at all, for example because of a redirect loop or a chain that was too long. Redirect errors do need fixing.

Where these URLs usually come from

SourceExampleUsually fine?
http to httpshttp://example.com/plumbers/austin-tx → httpsYes
www and non-wwwhttps://example.com/ → https://www.example.com/Yes
Trailing slash or letter case/Plumbers/Austin-TX → /plumbers/austin-tx/Yes, if links use the final form
Old URLs after a redesign or migration/austin/plumbing → /plumbers/austin-txYes, if each goes to its matching new page
Renamed or merged listings/listing/joes-plumbing-llc → /listing/joes-plumbingYes
Logged-out redirects/account/favorites → /loginYes; these pages shouldn’t be indexed
Sitemap or internal links to redirecting URLsSitemap lists the http or old URLNo: update the links
Redirect chains/a → /b → /cNo: redirect in one hop
Everything redirected to the home pageDeleted listings → /No: see below

When “Page with redirect” is fine, and when to act

Ask three questions about each group of URLs:

  1. Should this URL redirect? If it is an old or alternate address of a page that now lives elsewhere, yes. If it is a page you expected to be indexed (a live listing, a city page), something is redirecting it by mistake: a plugin rule, a forced login, a geo or language redirect, or a CMS setting.
  2. Does the redirect go to the right place, in one hop? Permanent redirects (301 or 308) tell Google the destination is the new canonical URL. Googlebot generally follows up to 10 redirect hops, but Google’s site move guide advises redirecting straight to the final URL and, if you can’t, keeping chains to ideally no more than 3 and under 5 hops.
  3. Is the destination indexed? Inspect the target URL. If the target is “Crawled - currently not indexed” or has its own redirect, noindex or 404, the redirect is not the problem; the destination is.

If the answers are yes, yes and yes, you are done. Everything else on this page is about the cases where one of them is no.

How to find where Google is picking these URLs up

Google keeps visiting redirected URLs mostly because something still points at them. Find that something:

  1. Filter the report by sitemap. At the top of the Page indexing report, switch from “All known pages” to “All submitted pages” or to one sitemap. If “Page with redirect” shows up there, your sitemap lists URLs that redirect. Sitemaps should list only final, 200-status, canonical URLs.
  2. Inspect a few examples. Open a URL from the list in URL Inspection and expand Page indexing. Under Discovery, Sitemaps shows which submitted sitemaps list it, and Referring page shows a page Google may have found it on. Google says the referring page is only one it possibly used, and it can be blank.
  3. Crawl your own site. Any site crawler will list internal links that return a 3xx status. Fix those links at the template level: the menu, the breadcrumb, the “related listings” block, the city list on a category page.
  4. Check canonical tags and hreflang. A canonical tag that points at a URL which then redirects sends Google two different answers about which page is the real one.

To see the full path of one redirect, run this in a terminal. Each block of headers is one hop; you want one 301 (or 308) and then a 200:

curl -sIL http://example.com/plumbers/austin-tx | grep -iE "^HTTP|^location"

The Page indexing report shows up to 1,000 example URLs per reason, so on a large site you see a sample, not every URL.

How to fix the ones that matter

  1. Point internal links at final URLs. Update menus, templates and content links so they link to the destination directly. Redirects should catch old links from other sites, not your own.
  2. Clean your sitemaps. Regenerate them so they contain only URLs that return 200 and declare themselves canonical. On WordPress this usually means checking the SEO plugin’s sitemap after a permalink change.
  3. Collapse chains. If /a redirects to /b which redirects to /c, change the first rule to go straight to /c. Chains build up after every migration that doesn’t update the previous one’s rules.
  4. Use permanent redirects for permanent moves. Google treats 301 and 308 as a strong sign the target should be canonical; 302, 303 and 307 are temporary, so Google generally keeps showing the source URL. Use server-side redirects; Google only recommends JavaScript redirects when nothing else is possible, because they’re seen later and only if rendering works.
  5. Redirect to the matching page, not the home page. Google’s John Mueller has said redirects of dead pages to the home page are mostly treated as 404s anyway. If there is no equivalent page, a 404 is the honest answer; see how to handle 404s.
  6. Make sure the destination is indexable. No noindex, a self-referencing canonical, and a 200 status. Then check it in URL Inspection.
  7. Keep the redirects. Google’s guidance for URL changes is to keep redirects for as long as possible, generally at least a year.

301, 302, 307 and 308: which redirect to use

CodeMeaningHow Google treats itUse it for
301Moved permanentlyStrong signal the target is canonicalMoved pages, http to https, merged listings
308Permanent redirect (keeps the request method)Same as 301The same, on servers or frameworks that default to it
302Found (temporary)Weak signal; the source usually stays canonicalShort-term moves you will undo
307Temporary redirect (keeps the request method)Same as 302The same, when the method must be kept

Source: Google’s HTTP status codes and redirects documentation. For search, 301 and 308 are interchangeable; pick whichever your server does natively.

On directory websites

Directories create redirects constantly, often without anyone deciding to:

How DirectoryLens helps

After a URL change, the URL changes report checks the old URLs that had the most visits from Google, or a map of old to new URLs you paste in. For each one it follows the redirect and flags chains, temporary redirects, loops, redirects to the home page, targets that are noindex or canonical elsewhere, and targets that don’t match your map. It then compares the traffic the old URLs had with what the new pages get.

In Google indexing > Individual pages you can start an inspection run on a whole sitemap. URLs that Google reports as “Page with redirect” appear under Other not indexed with Google’s coverage state, which is a quick way to find sitemap entries that still redirect. For more on how inspections work, see the URL Inspection tool guide, and for every other status in the report, the page indexing issues guide.

Questions

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

Google crawled a URL that redirects to another URL, so it indexes the destination (if it qualifies) instead of the redirecting URL. It is a normal status for old, http or non-www addresses, not an error.

Is “Page with redirect” bad for SEO?

No. It only matters when your own sitemaps or internal links still use the redirecting URLs, when redirects run through chains or go to the wrong page, or when the destination isn’t indexed.

Should I click Validate fix for “Page with redirect”?

Usually not. Redirected URLs are meant to stay out of the index. Validate only if you removed redirects that shouldn’t have been there and the URLs now return 200.

Should I use a 301 or 308 redirect?

For Google Search they work the same: both are permanent and tell Google the target is the canonical URL. Use whichever your server or framework does natively.

What does a 307 or 308 redirect mean?

A 307 is a temporary redirect and a 308 a permanent one; both keep the original request method. Google treats 307 like a 302 and 308 like a 301.

Is HTTP 302 a redirect?

Yes, a temporary one. Google generally keeps the original URL as canonical with a 302, so use a 301 or 308 when a page has moved for good.

Why isn’t the page my URL redirects to indexed?

The redirect only passes Google to the destination; the destination still has to qualify on its own. Inspect it in URL Inspection for noindex, a different canonical, another redirect, or thin content.

See which of your URLs Google left out, and why.

Connect Search Console and DirectoryLens inspects your pages by page type, including every sitemap URL that still redirects.

Explore the live demo →

5 days free · no card needed · ends on its own