All posts
Page With Redirect in Google Search Console: When to Ignore It (And When to Fix It)
Google Search ConsoleIndexingRedirect ChainsTechnical SEO

Page With Redirect in Google Search Console: When to Ignore It (And When to Fix It)

"Page with redirect" in Search Console usually means a redirect is working. Here's how to tell normal entries from the few that point to a real problem.

October 1, 2026 · 12 min read

If the Page Indexing report lists a batch of your URLs under Page with redirect, the short answer is that most of them need no action. Google's own definition is: "This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed." The redirect worked, Google followed it, and the destination page is the one that can be indexed.

The longer answer is that this status sits right next to a few real problems — sitemaps full of old URLs, internal links that never got updated, and redirects that land on the wrong page. This guide covers how to separate the harmless entries from the ones worth fixing.

What "Page With Redirect" Actually Means

When Googlebot requests a URL and gets a redirect back (a 301, 302, 307, 308, or a meta refresh), it doesn't index the URL it asked for. It records that URL as a pointer to somewhere else, follows the redirect, and evaluates the target instead. Search Console reports the original URL as "Page with redirect" so you know why it isn't in the index.

That's the expected outcome of almost every redirect you set up on purpose. If you moved /old-post to /new-post with a 301, you want /old-post to show up here — it means Google saw the move and stopped treating the old address as a page of its own.

One detail is worth knowing: the status only describes the redirecting URL. Google's documentation notes that the target "might or might not be indexed," depending on how Google assesses that target page. So the useful question is never "why is this URL here?" but "is the page it points to indexed?"

Common Reasons Blog URLs Land in This Report

On a typical blog, the entries usually come from a handful of predictable sources:

| Source | Example | Action needed? | |---|---|---| | HTTP → HTTPS | http://yourblog.com/post → https://yourblog.com/post | No | | www ↔ non-www | www.yourblog.com → yourblog.com | No | | Trailing slash rule | /post → /post/ | No, if consistent | | Changed slug | /2023/my-post → /my-post | No, if the target is right | | Merged or pruned post | Old post 301'd into a newer, fuller one | No, if the target covers the same topic | | Old URL still in your sitemap | Sitemap lists a URL that now redirects | Yes — update the sitemap | | Internal link to an old URL | A post still links to /old-post | Yes — update the link | | Redirect to an unrelated page | Deleted post sent to the homepage | Yes — reconsider the target |

The first five rows are housekeeping that Google handles on its own. The last three are where this report turns into a to-do list.

When It's Fine to Ignore

You can leave a "Page with redirect" entry alone when all three of these are true:

  1. You meant to redirect that URL. It's an old slug, a protocol or hostname variant, or a post you merged during a content pruning pass.
  2. The redirect is permanent. Google's redirect documentation says that with a permanent redirect (301 or 308), "the indexing pipeline uses the redirect as a signal that the redirect target should be canonical." With a temporary one (302, 303, 307), it doesn't use the redirect as that signal. If a move is permanent, the status code should say so.
  3. The target is indexed. Run the destination URL through the URL Inspection tool. If it shows as indexed, the redirect has done its job.

A large or growing count on its own isn't a warning sign. A site that switched to HTTPS or changed its permalink structure can easily have more redirecting URLs than real posts, and that's normal.

When "Page With Redirect" Points to a Real Problem

Your sitemap still lists the old URLs

A sitemap is supposed to tell Google which URLs you want indexed. If it's full of addresses that redirect, you're sending mixed signals: "index this," followed by "actually, go over there." Google's canonicalization guide treats a sitemap as a weak signal — "all pages listed in a sitemap are suggested as canonicals" — while a redirect is a strong one. List a URL that redirects and the two signals point at different addresses. Check whether the URLs in the report also appear in your submitted sitemap — if they do, regenerate the sitemap so it only contains final destination URLs. On most CMSs this means clearing a sitemap plugin's cache or fixing a hard-coded entry. Our sitemap best practices guide covers what else should stay out of the file.

Your own internal links point at the old address

Google's advice here is short: "When linking within your site, link to the canonical URL rather than a duplicate URL." Every internal link that points at a redirecting URL makes Googlebot (and readers) take an extra hop. One hop is harmless; but links rarely get updated once, and after a couple of restructures you end up with chains. Google's crawlers follow up to 10 redirect hops by default, and a chain that runs past the limit or loops back on itself gets reported as Redirect error instead — a status that does need fixing. An internal linking audit finds the links still pointing at old URLs, and a redirect chain checker shows how many hops each one takes.

Your canonical tags point at a URL that redirects

Google lists both rel="canonical" and redirects as strong canonicalization signals, and its guide warns against using different methods to name different canonical URLs for the same page. A canonical tag that points at a redirecting URL is a quiet version of that mistake. If a post declares /old-post as its canonical, but /old-post now 301s to /new-post, the tag says one address and the redirect says another.

This usually happens after a slug change. The redirect gets added, but a hard-coded canonical in a template, an SEO plugin field, or a duplicate page's canonical still names the old URL. The fix is to point every canonical at the final URL, the one that returns a 200. On your own posts, that means a self-referencing canonical tag should name the live address, not the one it replaced. Duplicates that correctly point at the final URL will show up as Alternate page with proper canonical tag, which is the healthy outcome.

The redirect goes to the wrong place

Redirecting a deleted post to your homepage, or to a loosely related category page, is a common shortcut. It technically resolves, so it shows up as "Page with redirect" rather than as an error. But if the target doesn't cover what the old page covered, it's not a real replacement. Google may treat a redirect like that as a soft 404 — a page that exists but doesn't deliver what the URL promised. If there's no true replacement, a 404 or 410 is the more honest response.

A page you want indexed is redirecting

Occasionally a URL you expect to rank shows up in this report. That usually means a plugin, server rule, or CDN setting is redirecting something it shouldn't — a trailing-slash rule that conflicts with your canonical tags, a language redirect based on visitor location, or an old rule matching more paths than intended. Treat any surprise entry as a bug: open the URL in a private window and run curl -IL against it to see every hop and status code.

How to Check Your Report in Five Minutes

  1. In Search Console, go to Indexing → Pages and open Page with redirect.
  2. Export the list and sort it. Scan for patterns: http://, www., missing trailing slashes, and old date-based slugs are expected. Anything else deserves a second look. The example list is capped at 1,000 rows, so on a large site treat it as a sample, not a full inventory.
  3. Pick a few URLs and check where they land with curl -IL https://yourblog.com/old-url. Confirm each ends on a 200 page with a single permanent redirect, not a chain or a 302.
  4. Search your sitemap for the same URLs and remove any that redirect.
  5. Inspect the destination URLs, not the redirecting ones. If a destination isn't indexed, that's the page to work on — the redirect itself is fine.

If any of your URLs land under Blocked due to access forbidden (403) or Excluded by 'noindex' tag instead, those are different problems with different fixes — the 403 guide and the noindex breakdown cover each.

Why URL Inspection Can Make a Redirecting URL Look Fine

Step 5 matters because the URL Inspection tool behaves differently with redirects than most people expect, and Google's help page spells it out.

For the indexed result, "if the URL redirects to another URL, the results reflect the tested URL in the index, not the redirect target in the index." Inspecting /old-post tells you about /old-post, which is exactly what you already knew: it isn't indexed because it redirects.

The live test is the bigger trap. Google says "the test first follows any redirects implemented by the page, then tests the page," but "the test does not indicate that it has followed a redirect, nor will it display the final URL that was tested." So a live test on an old URL can come back looking healthy when what it actually tested was the destination. If you're trying to confirm where a URL lands, the live test won't show you. Use curl -IL for the path, then inspect the final URL directly.

Should You Click Validate Fix for Page With Redirect?

Usually not. Google's Page indexing documentation is clear that "Not indexed is not necessarily bad" and that "Non-indexed URLs can be fine." A working redirect is one of those cases. There's nothing on the redirecting URL to fix, so there's nothing for validation to confirm.

Even when you do fix something nearby, such as removing old URLs from your sitemap or updating internal links, validation is optional. Google says "you can also fix issues without validating," and that it updates the count "whenever it crawls a page with known issues." If you do start a validation, Google says it "typically takes up to about two weeks."

Keep one expectation in mind: cleaning up your sitemap and links won't make those old URLs vanish from this list. Google already knows them, and as long as they redirect, "Page with redirect" is the accurate status for them. What you've changed is how often Google gets sent to them, not what they are.

Should You Ever Remove Old Redirects?

Generally, no. Google's site-move guidance says to keep redirects "for as long as possible, generally at least 1 year," so it has time to recrawl old URLs and move their signals — including backlinks from other sites — to the new ones. Removing a redirect too early turns a working "Page with redirect" entry into a 404 and throws away whatever links pointed at the old URL. The only redirects worth deleting are ones that send visitors somewhere wrong.

Page With Redirect Questions, Answered

Is "Page with redirect" an error?

No. It's one of the reasons a URL isn't indexed, and Google describes that whole group as pages that "have not been indexed, but not necessarily because of an error." It only becomes a problem in the specific cases above: the URL is still in your sitemap or internal links, a canonical tag points at it, the redirect lands on the wrong page, or the URL is one you wanted indexed.

What's the difference between Page with redirect and Redirect error?

"Page with redirect" means the redirect worked. "Redirect error" means Google couldn't complete it. Google lists four causes for the error: a redirect chain that was too long, a redirect loop, a redirect URL that eventually exceeded the maximum URL length, and a bad or empty URL in the chain. Redirect errors are worth fixing. A redirect chain checker is the quickest way to see which of the four you're dealing with.

Why is my homepage listed under Page with redirect?

Almost always because a variant of it redirects to the version you actually use: http:// to https://, or www. to the bare domain (or the reverse). That's expected. Inspect the homepage URL you serve, not the variant. If that one is indexed, there's nothing to do.

Does Page with redirect hurt my SEO?

Not on its own. The redirecting URL isn't meant to rank. The page that matters is the destination, and the questions worth asking are whether it's indexed and whether it kept the traffic the old URL used to earn.

How Do You Know a Redirect Cost You Traffic?

Search Console's indexing report tells you a URL redirects. It doesn't tell you whether the move hurt. The clearest sign is in your performance data: if the destination post doesn't pick up the clicks the old URL used to earn, something went wrong — the new page may not be indexed yet, it may target a different query, or the redirect may point at the wrong page.

That's a comparison worth watching for a few weeks after any URL change. Traffic Monitor pulls Search Console clicks and impressions for each post every day, and on paid plans it sends an alert when a post's clicks drop past the threshold you set, so a redirect that quietly lost traffic shows up as a change to investigate instead of something you notice months later.

Track your blog rankings automatically

Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.

Start free →