Skip to content

Page with redirect in Search Console: when to leave it alone

What Page with redirect means in Search Console, why it is usually fine, and the four cases to fix: sitemaps, internal links, canonicals and stray redirects.

By Crawlito · 9 min read

In short

  • Google defines Page with redirect as a non-canonical URL that redirects to another page, so the source URL is not indexed and only the target can be.
  • The status is expected for HTTP to HTTPS, www to non-www and retired URLs that redirect, and Google's Page indexing report says not indexed is not necessarily bad.
  • It needs work when the redirecting URLs are in your sitemap, linked from your own pages, named in a canonical tag, or redirecting by accident to a login, country or slash variant.
  • URL Inspection reports the status of the URL you typed, not the redirect target, and its live test follows redirects without saying so.
  • Filtering the report to All submitted pages shows the redirecting URLs your sitemaps still list, which is the quickest way to find the ones worth fixing.
On this page

"Page with redirect" in Google Search Console means the URL answers with a redirect, so Google does not index it and considers only the page it redirects to. For old URLs, HTTP to HTTPS moves and host changes, that is exactly what you want, and the right action is none. It needs fixing only when your own site keeps pointing Google at the redirecting URL: through the sitemap, internal links or a canonical tag, or when the redirect was never meant to happen.

This post covers how to tell the two apart and how to check the target instead of the source. For how crawlers follow redirect chains and status codes in general, see status codes and redirects for AI crawlers.

What "Page with redirect" means in Search Console

Google's Page indexing report documentation defines the reason in one line: "This is a non-canonical URL that redirects to another page." Three details on that page are worth knowing:

  • The source is not indexed. The entry says the redirecting URL will not be indexed, and that the target "might or might not be indexed, depending on what Google thinks about that target URL". That is why the status alone tells you nothing about whether your content is in Search.
  • A canonical URL with a redirect can still be indexed. The status is about non-canonical URLs. A redirect does not automatically exclude a URL Google has chosen as canonical.
  • It sits under "Not indexed", not under errors. The same page says pages in that group "have not been indexed, but not necessarily because of an error", and that you should not expect every URL to be indexed, only the canonical version of each important page.

The type of redirect changes what Google does with the pair. Its redirects guide says a permanent redirect (301, 308, an instant meta refresh) is a signal that the target should be canonical, while a temporary one (302, 303, 307, a delayed meta refresh) is not, so the source may stay in results. Google keeps track of both URLs: one becomes canonical and the other an alternate name that can still appear for some queries.

If the URL in the report is the one that does not redirect at all, you are looking at a different problem. A chain that is too long or loops shows up as Redirect error, and a page that declares another URL as canonical shows up as Alternate page with proper canonical tag.

When to leave Page with redirect alone

Most entries in this report are the residue of decisions you made on purpose. Every redirect that exists for a reason can produce one, and the count often grows after a migration: Google's redirects guide says it keeps track of both the old and the new URL, and old URLs are still linked from other sites.

What the source URL isExampleAction
HTTP version of an HTTPS pagehttp://example.com/pricingNone
The host you do not usehttps://www.example.com/pricing when you use the bare domainNone, if the redirect is permanent
An old URL after a redesign or migration/blog/2019/old-slug to /blog/new-slugNone, keep the redirect
A merged or replaced pageTwo guides combined into oneNone
Parameter or case variants your server normalises/Pricing to /pricingNone

The test is simple: if the target is the page you want in Search, returns 200 and is the URL you use everywhere on your site, the entry is doing its job. The choice of preferred host is covered in www vs non-www. A rising count on its own is not a sign of trouble. It often just means Google has found more of your old URLs.

The cases that do need fixing

The status becomes a problem when your site keeps sending Google to the redirecting URL, or when the redirect itself is a mistake. Four cases cover most of it.

1. Redirecting URLs listed in your sitemap

Google's sitemap guidance says to include the URLs "that you want to see in Google's search results", and its guide to consolidating duplicate URLs notes that all pages listed in a sitemap are suggested as canonicals. A redirecting URL in the sitemap therefore suggests a URL as canonical while the redirect says the opposite.

Find them by changing the filter at the top of the Page indexing report from All known pages to All submitted pages, or to one sitemap. Any "Page with redirect" rows left are URLs your sitemap still lists. Replace each with its final URL, and fix the generator rather than the file, so the next build does not put them back. XML sitemaps for AI discovery covers generating sitemaps from the same source as your canonical URLs.

Google's consolidation guide says: "When linking within your site, link to the canonical URL rather than a duplicate URL." Navigation, footers and old articles that still link to http:// URLs, the other host or a pre-migration path keep Google rediscovering them, and every visit costs an extra request. The URL Inspection result includes a Referring page field, which names a page Google possibly used to discover the URL. Treat it as a lead rather than a complete list: Google's URL Inspection documentation says the field can show a grandparent or great-grandparent page, and an empty value does not mean nothing links there.

3. A canonical tag that names a redirecting URL

When page A says its canonical is B, and B redirects back to A or onward to C, the signals contradict each other. Google's guide warns against specifying "different URLs as canonical for the same page using different canonicalization techniques." Point every canonical at the final URL that returns 200. A template that builds canonicals from an old base URL, such as http:// after an HTTPS move, can create this across a whole site at once. The full set of canonical conflicts is in canonical tags and duplicate URLs.

4. Redirects nobody meant to add

Look for these patterns in the example URLs, because each one hides a page you want indexed:

PatternTypical causeWhat Google ends up with
Public pages redirecting to /loginA session check applied to the wrong routesYour login page instead of the content
Pages redirecting by country or languageGeo-IP or Accept-Language redirectsUsually one version only
/page and /page/ redirecting to each other's formFramework and server disagree on trailing slashesDuplicate entries, or a loop
Product or article URLs redirecting to the homepageA blanket rule for missing pagesNo page for that content
A permanent move done with a 302A plugin or CDN rule set to a temporary redirectThe old URL may stay canonical

Geo redirects deserve a closer look. Google's multi-regional sites guide says Googlebot usually crawls from the USA, sends no Accept-Language header, and advises you to avoid automatically redirecting users between language versions. A site that redirects visitors by location can show "Page with redirect" for every regional version except the one served to US requests.

How to inspect the target URL instead of the source

The URL Inspection tool reports on exactly the URL you enter, and that trips people up. Google's report documentation says the tool shows the index status of the tested URL, ignoring redirects, so inspecting an old URL will tell you it is not indexed, which is correct and not useful. Two more details from the URL Inspection documentation:

  • The live test follows redirects and tests the final page, but it does not tell you a redirect was followed or show the final URL. A clean live test on a redirecting URL is really a test of the target.
  • To see the status of the canonical, use the INSPECT button in the Page indexing > Indexing section of the inspection result, or paste the target URL in the inspection search bar yourself.

Find the target first with curl, which prints the status code, the number of hops and the final URL (the status codes post shows how to print every hop):

bash
curl -s -o /dev/null -L -w '%{http_code} %{num_redirects} %{url_effective}\n' \
  http://example.com/old-pricing
200 2 https://example.com/pricing

Then inspect https://example.com/pricing. You want "URL is on Google" (which Google describes as eligible to appear, not guaranteed), a Google-selected canonical equal to that URL, and the user-declared canonical matching it. If the target itself is not indexed, the problem is on the target, and its own status (crawled, duplicate, noindex) tells you where to look.

How to triage a large Page with redirect list

When the report shows thousands of URLs, sort them by cause instead of checking them one by one. The details page lists example URLs, limited to 1,000 rows and not necessarily every affected URL, and you can export the table.

  1. Filter to submitted pages first. Rows under All submitted pages come from your sitemaps, so they are fixable on your side. Fix those before anything else.
  2. Export the examples for the unfiltered view and save the URL column as urls.txt.
  3. Resolve every URL to its final destination and group the results:
bash
while read -r u; do
  printf '%s\t' "$u"
  curl -s -o /dev/null -L --max-redirs 10 \
    -w '%{http_code}\t%{num_redirects}\t%{url_effective}\n' "$u"
done < urls.txt > resolved.tsv

# Columns: source URL, final status, hops, final URL
# Targets that are not 200, or that need more than one hop
awk -F'\t' '$2 != 200 || $3 > 1' resolved.tsv
# Redirects that end on a login page or the homepage
awk -F'\t' '$4 ~ /^https?:\/\/[^\/]+\/(login.*)?$/' resolved.tsv
  1. Read the groups. Rows ending on a 200 page you want indexed in one hop are the expected case. Rows that end on a 404, on /login, on the homepage, or after several hops are the ones to fix. Then check the targets that remain against your sitemap and internal links.

This only shows what your server returns to a request from your machine. A CDN or firewall rule keyed to Googlebot can behave differently, so confirm surprising results with the live test.

Frequently asked questions

Should I click Validate fix for Page with redirect?

Usually not. For expected redirects there is nothing to fix, and Google's documentation does not describe validation for this reason specifically. Fix the sitemap, link and canonical cases instead and let Google recrawl.

Will Page with redirect URLs disappear from the report?

Not on any documented schedule. Google keeps track of old URLs and recrawls them from external links and its own history, so expected redirects can stay listed for a long time without causing harm.

Should I remove the redirects to make the count go down?

No. Removing a redirect turns the old URL into a 404 for visitors and crawlers that still use it, and Google's redirects guide treats a permanent redirect as the signal that the target should be canonical. Keep redirects for moved pages and clean up your own references to the old URLs.

Does a 302 show up as Page with redirect too?

Google documents one Page with redirect reason with no split by redirect type. The difference is in what Google does next: a 302, 303 or 307 is not used as a canonical signal, so the old URL may remain the one shown in results.

Is my page missing from Google if it shows Page with redirect?

Not necessarily. The status describes the redirecting URL. Inspect the target URL to find out whether the page itself is indexed.

Check the URLs your site still points at

The fixes for this status all come down to one question: does your site link, list and canonicalise the final URL, or the old one? The curl commands above answer it page by page. If you want a second look at an important page, the free check runs on a single page with no account. For a whole site, an audit covers up to 500 pages with human review and a PDF of evidence and prioritized fixes.

Filed under Access and robots.txt. Topics: redirects, search-console, google, sitemaps