knowledge base284 articles
knowledge base/seo & search
glossary term

"'Page with Redirect' in Search Console"

Updated

A Search Console status for addresses that send visitors on to another page, which is usually exactly what should happen.

What it means

"Page with redirect" means the address forwards visitors to a different address, so Google doesn't index it; it indexes the page at the end of the redirect instead, if it judges that page worth indexing. In most cases this status needs no action at all.

A redirect is an instruction from your server that says "this page lives somewhere else now, go here". Search engines index the destination, not the address that points to it, so every redirecting address on your site lands in this bucket.

Why it matters

This status often lists dozens or hundreds of addresses and looks like a problem. Usually it's the opposite: it's Google confirming that your redirects work. Typical, healthy entries:

Redirecting address Where it goes Why it's normal
http://example.com/menu https://example.com/menu Your site forces the secure version
example.com/menu www.example.com/menu (or the reverse) Your site picks one version of your domain
example.com/menu example.com/menu/ Your site adds or removes the trailing slash
example.com/old-services example.com/services You renamed or merged a page

It's worth a closer look when:

  • A page you want in search is listed here. Then something is redirecting it, perhaps a rule added during a redesign or a plugin setting. Note the difference: the listed address is the one doing the redirecting, so check it's not your live page.
  • Your sitemap lists redirecting addresses. A sitemap should list final addresses only. Redirecting entries won't break anything, but they send Google on a detour and are a sign the sitemap is out of date.
  • Your own menus and links point to redirecting addresses. Updating them to the final address saves a hop for visitors and Google.
  • The destination isn't indexed. Google indexes the target only if it judges it worth indexing. Inspect the target, not the redirecting address, to see its status.
  • A temporary redirect is doing a permanent job. A 302 tells search engines the move is temporary. If the move is permanent, use a 301. See 301 vs. 302 redirects.

A separate status, Redirect error, is the one that signals a broken redirect: a redirect chain that's too long, a loop that sends visitors in circles, or a redirect to a bad or empty address. If you see that one, fix it; "Page with redirect" on its own is not an error.

How to fix it

  1. Look at the list. In Search Console, open Indexing → Pages and click Page with redirect in the "Why pages aren't indexed" table. Most addresses will be http, www or trailing-slash variants of real pages; those need nothing.
  2. Pick out anything surprising. Look for addresses you expected to be live pages, not old or variant ones.
  3. Inspect a surprising one. Click the inspect icon next to it. The indexing information you see applies to the address you inspected, not where it leads. To see the destination's status, use the Inspect button in the Page indexing section, which opens the page Google actually indexed. Note that the live test follows redirects silently and tests the final page.
  4. Remove redirects you didn't mean to add. If a live page is redirecting by mistake, remove the rule in your site builder's redirect settings, your SEO plugin, or your server configuration.
  5. Clean up your sitemap and links. Replace redirecting addresses in your sitemap and internal links with the final address, then resubmit the sitemap under Indexing → Sitemaps. See how to submit a sitemap.
  6. Check the destination is indexable. If the target page shows a different status, such as Soft 404 or a duplicate status, fix that page instead; the redirect is doing its job.

Don't click Validate fix for this status unless you've actually changed something: if the redirects are intended, there's nothing to validate.

ask datanephew

Are any of my real pages accidentally redirecting?

Ask datanephew to check the addresses listed under "Page with redirect" against your sitemap and the pages that used to get search traffic. It reads your Search Console indexing data for free, follows each redirect to where it ends, and flags any that point somewhere you didn't expect.

Does my sitemap list pages that redirect?

Ask datanephew to walk your sitemap and check each address. It will list the ones that redirect and the final address each should be replaced with. On the Owner plan, it can resubmit the sitemap to Google and Bing once you've updated it.

Is the page my old address redirects to actually on Google?

Ask datanephew to inspect the destination page. It will tell you whether Google has indexed it and, if not, the reason Google gives, which is the status that actually needs attention.