sfw/fix
Page with redirect low

Page With Redirect (Google Search Console)

The URL itself redirects elsewhere, so Google indexes the destination and excludes this URL — usually expected, occasionally a mistake.

What you see

Page indexing > Why pages aren’t indexed
Page with redirect
This page is not indexed

What’s actually happening

Search Console lists a URL under "Page with redirect" in the Page indexing report. Unlike "Redirect error," nothing is broken here — Google followed the redirect, reached the destination fine, and indexed that destination instead of this URL. For HTTP→HTTPS or www canonicalization this is exactly what you want, and there's nothing to fix. It only matters when a URL you actually wanted indexed is quietly redirecting, or when the redirect points at the wrong page or through a chain.

Common causes

  • Expected canonicalization — http→https, or www→non-www (or vice versa) — every old-protocol/host URL lands here by design.
  • A trailing-slash or lowercase normalization redirect (/Page → /page/).
  • A retired page 301'd to its replacement, so the old URL correctly drops out of the index.
  • A redirect you didn't intend — a plugin, a stale rule, or a misconfigured canonical-via-redirect sending a page you wanted indexed somewhere else.
  • The redirect resolves through a chain (A→B→C) rather than one clean hop, which still indexes C but wastes crawl budget.

How to fix it

  1. Confirm it's intentionalFor each flagged URL, ask whether it should redirect. If it's an old http/www/retired URL pointing at the right destination, this status is correct and needs no action — leave it. Most entries here are working as intended.
  2. Verify the destination is the intended canonical`curl -IL https://example.com/url` and check the final 200 URL. It should be the exact page you want ranking. If a URL redirects somewhere stale or wrong, fix the redirect rule (plugin, .htaccess, or CDN) to point at the correct target.
  3. Collapse any chain to one hopIf curl shows more than one redirect before the 200, repoint the source directly at the final URL so it's a single hop. A chain still indexes the destination but leaks a little equity and burns crawl budget on every pass.
  4. Recover a URL that shouldn't redirectIf a page you want indexed is landing here by accident, remove the unwanted redirect, make the URL return 200 with a self-referencing canonical, then use URL Inspection > Request Indexing to get it re-evaluated.

Stop it recurring

Keep canonicalization to a single host+protocol enforced once, and point internal links at final URLs so genuine pages never accidentally fall under a redirect rule.

Related errors