It means Google found an address on your site that sends visitors somewhere else, so it indexes the destination instead of the address itself. That's exactly what a redirect is meant to do, so most of the time there's nothing to fix. It's worth a closer look only when a page you want in Google is in the list, when your own links or sitemap keep pointing at old addresses, or when the destination isn't the page you expected.

What Google says this status means

Search Console's Page indexing report help (checked 16 November 2026) describes “Page with redirect” as a non-canonical URL that redirects to another page, and says this URL will not be indexed. It adds that the destination “might or might not be indexed, depending on what Google thinks about that target URL”.

The same help page lists redirects among the normal reasons a site has unindexed URLs: “Redirect URLs are not indexed, only the redirect target.” It also reminds owners that not every URL should be indexed, and that non-indexed URLs can be fine.

In plain terms: this list is a record of doors that lead to other rooms. Google is noting the door and indexing the room.

Why it shows up on ordinary small business sites

Almost every website has some. Common sources:

What you'll see in the list Where it usually comes from
http://yoursite.com/ The insecure version redirecting to https://
https://yoursite.com/about Redirecting to /about/ (or the reverse) because of a trailing-slash rule
https://www.yoursite.com/ The www version redirecting to the version without it, or the reverse
/old-services-page/ A page you renamed or merged during a redesign
/?p=123 A blogging platform's short link redirecting to the full article address

If each of these leads to the right page, and that page is indexed, leave them alone. These redirects are doing their job.

When “Page with redirect” is worth a closer look

1. A page you want in Google is listed

If a live service page or a key guide shows up here, something is redirecting it. Common causes are a redirect rule left over from a redesign, a plugin that redirects one page to another without you noticing, or a language or location setting that sends Google elsewhere.

2. Your own site keeps linking to old addresses

Redirects work, but every one is a small detour. If your menus, footer, internal links or sitemap still point at old addresses, Google keeps finding the redirecting version. A sitemap is meant to list the pages you want found, so one full of redirecting addresses sends mixed signals.

3. The destination isn't the right page

A redirect is only as good as where it lands. Sending every old page to the homepage is a common shortcut that frustrates visitors looking for something specific. Point each old address to the closest matching page instead.

4. It's actually a “Redirect error”

That's a different status. Google lists it separately for redirect chains that are too long, redirect loops, redirect addresses that become too long, and bad or empty addresses in the chain. Redirect errors do need fixing, because neither visitors nor Google reach a page.

How to check, in about five minutes

  1. In Search Console, open Pages under Indexing and click Page with redirect.
  2. Scan the example URLs. Are they old addresses, http:// or www variants and short links, or real pages you want in search?
  3. Open a few in your browser and see where you land. Is it the right page, in one step?
  4. For anything that looks wrong, run it through URL Inspection. Google's help page notes the live test follows redirects and then tests the final address, without telling you it did so, so compare the address you entered with the page it reports on.
  5. Inspect the destination too, and check it's indexed.

Google's help page also notes that the example list is limited to 1,000 URLs and isn't guaranteed to show every affected address, so treat it as a sample.

How to fix the problems you find

Google's guide to redirects and Google Search (last updated 14 April 2026, checked 16 November 2026) sets out the basics:

  • Use a permanent redirect for permanent moves. Google says permanent redirects (such as 301 or 308) show the new address in search results, while temporary ones (such as 302 or 307) show the source page. If a page has moved for good, a temporary redirect sends the wrong signal.
  • Prefer server-side redirects. Google says server-side redirects have the highest chance of being interpreted correctly. It treats an instant meta refresh as permanent and a delayed one as temporary, and says to use JavaScript redirects only if nothing else is possible, because Google might never see them if rendering fails.
  • Remove redirects you didn't mean to add. If a page you want indexed is redirecting, find the rule (often in your platform's redirect settings or an SEO plugin) and turn it off, then request indexing in URL Inspection.
  • Update your own links. Point menus, internal links and your sitemap at the final addresses, so Google meets fewer detours.
  • Collapse chains. If A redirects to B and B to C, change A to go straight to C.

On WordPress, Wix, Shopify and similar platforms, redirects usually live in the platform's settings or a plugin rather than in code. If you're not sure where yours come from, ask whoever manages your website before changing anything.

A hypothetical example

This is an invented example, not a client result. A physiotherapy clinic renames its “Sports massage” page from /sports-massage/ to /treatments/sports-massage/ during a redesign, and adds a redirect. A month later, the old address appears under “Page with redirect”, which is expected.

What isn't expected: the clinic's footer and three blog posts still link to the old address, and the sitemap lists it too. The owner updates the footer, the blog links and the sitemap to the new address. The redirect stays in place for anyone with an old bookmark. Nothing about the redirect itself was wrong; the clean-up simply removed the detours.

How it differs from look-alike statuses

Status What it means Usually needs action?
Page with redirect This address redirects elsewhere, so Google indexes the destination No, if the redirect is intended
Redirect error The redirect is broken: a loop, a chain that's too long or a bad address Yes
Alternate page with proper canonical tag This page names another page as its main version, and Google agreed No, unless an important page is listed
Duplicate without user-selected canonical No main version was named, so Google picked one Only if Google picked wrong

For the canonical statuses, see our guides to “Alternate page with proper canonical tag” and “Duplicate without user-selected canonical”.

What's in your control, and what isn't

In your control: which redirects exist, whether they're permanent or temporary, where they land, and whether your own links and sitemap point to final addresses.

Not in your control: whether Google indexes the destination page, and how quickly reports update. Google says the destination might or might not be indexed depending on its own assessment, and indexing is never guaranteed.