sfw/fix
Page with redirect low

Page With Redirect (Excluded From Index)

The URL redirects somewhere else, so Google drops it and indexes the destination instead of the redirecting URL.

What you see

Page with redirect
Indexing: Excluded
This page is a redirect. Google did not index it.

What’s actually happening

A set of URLs lands under "Page with redirect" in the Pages report, excluded by design. URL Inspection shows the URL returns a 3xx and names the redirect target. For consolidation work — HTTP to HTTPS, www to non-www, trailing-slash normalization — this is the correct outcome. It only matters when a URL you want indexed is the one redirecting, or sits in a chain.

Common causes

  • Intentional consolidation: 301s from HTTP to HTTPS, www to non-www, or old paths to new ones — expected and excluded.
  • A redirect chain (A to B to C) where intermediate hops show up as excluded redirects.
  • A page you actually want indexed got a stray redirect from a migration, a CMS slug change, or a misfiring server rule.
  • Internal links and the sitemap still pointing at the old redirecting URL instead of the final destination.
  • A redirect loop or a soft 302 where a 200 was intended, confusing what Google should index.

How to fix it

  1. Separate expected redirects from mistakesReview the listed URLs. Old/duplicate URLs redirecting to canonicals are fine — no action. Flag any URL that should rank but is redirecting; that's the only real problem here.
  2. Restore a wrongly-redirecting pageIf a page you want indexed redirects, remove the rule so it returns 200 with its own content, set a self-referential canonical, and Request Indexing in URL Inspection.
  3. Flatten redirect chainsTrace hops with `curl -sIL https://example.com/old | grep -i location`. Rewrite each source to point straight at the final 200 URL so there's a single 301, not a chain that bleeds crawl budget and signal.
  4. Update internal links and the sitemapRepoint internal links and sitemap entries to the final destination URL. Linking through a redirect works but wastes crawl budget and keeps the old URL surfacing in reports.
  5. Confirm the right status codesUse 301 for permanent moves so equity transfers; reserve 302 for genuinely temporary ones. Verify the destination returns 200 and isn't itself redirecting.

Stop it recurring

After any migration, crawl the site and fix internal links so they hit final URLs directly instead of routing through 301s.

Related errors