Page with redirect: usually fine, fix it only if the redirect is a mistake
The URL redirects to another page, so Google indexes the destination instead. For old URLs and http, www, or trailing slash variants, that is expected. Here is how to tell the normal cases from the ones you should fix.
What the status means
In the Page indexing report, "Page with redirect" means the URL is not the main version of the page and redirects somewhere else, so Google does not index it. In most cases this is the redirect working as intended.
The URL redirects
Google requested it and was sent to another URL. The content of the redirecting URL is ignored.
Google does not index it
The redirecting URL stays out of the index. Whether the destination is indexed is a separate decision.
It is often expected
Old URLs, http to https, www vs non-www, and trailing slash redirects all show up here and need no fix.
Definition from Google's Page indexing report help page.
Why URLs show up as Page with redirect
The first three are normal and need no action. The last three are worth fixing.
Old URLs you moved on purpose
You renamed a page, merged two pages, or changed your URL structure and redirected the old addresses. This is expected.
http to https, or www to non-www
http://example.com redirecting to https://example.com, or www.example.com redirecting to example.com, sends every visitor to one version of the site. This is expected.
Trailing slashes and other URL variants
example.com/pricing redirecting to example.com/pricing/, or uppercase paths redirecting to lowercase. Expected, as long as your links use the final version.
An accidental redirect
A page you want indexed redirects when it should not: a routing rule that is too broad, a login or locale redirect that catches Googlebot, or a redirect left over from a test.
Your own signals point at redirecting URLs
Internal links, canonical tags, hreflang tags, or your sitemap list the old URL instead of the destination. Google keeps finding and reporting it.
Redirect chains and loops
A redirects to B, which redirects to C. Long chains slow people down and Google stops after 10 hops. A loop never reaches a page and is reported as a redirect error instead.
Check where the URL redirects
Paste the URL from Search Console. The free checker shows if the address redirects and where it ends up. Then run the destination through the checker to make sure it can be indexed.
Progress
Checks that completed before it stopped are shown below.
Access and indexing settings
Content review
Already in Google?
Not checked
This check cannot confirm whether your page is already in Google, and it does not predict the outcome. It shows what could stand in the way.
· this address redirects to , which was not checked. Run a separate check on it.
Only part of this long page was reviewed.
Good to know
Completed before the check stopped
Use the free indexability checker at /tools/indexability. Enter a public page address and it reports whether the site lets Google visit the page, whether the page carries a noindex setting or points to another page as the original, and whether the content is thin, repeated, or unclear. It does not tell you whether Google has indexed the page.
Check and fix it in this order
Most URLs in this report need nothing. Work out which redirects are accidental, then make sure everything on your site points at the destination.
- 1
Check that each redirect is intended
Export the URLs from the report and scan them. Old pages, http, www, and trailing slash variants can be left alone. Look for pages you expected to be indexed.
- 2
Check where each URL ends up
Run the URL through the checker below or another redirect checker. The destination should be the page that genuinely replaces the old one and should return 200.
- 3
Remove accidental redirects
If a page you want indexed redirects, fix the rule that sends it away. Make sure Googlebot gets the same page as visitors, without a login or locale redirect.
- 4
Use permanent redirects for permanent moves
Use a 301 or 308 for pages that have moved for good. Google treats these as a strong signal that the destination is the main version. A 302 or 307 is a weaker signal.
- 5
Point everything at the destination
Update internal links, canonical tags, hreflang tags, and your sitemap so they list the final URL, not the one that redirects.
- 6
Collapse chains into one hop
Redirect each old URL straight to its final destination. Break any loops so every URL ends on a page that returns 200.
- 7
Then submit the destination
If the destination is new or recently changed, request indexing in URL Inspection or submit the destination URL with Index My Site.
When submitting helps, and when it will not
Google will not index a URL that redirects, so submitting it changes nothing. Submit the destination instead.
It helps when
- You submit the destination URL, and it is new or recently changed
- You removed an accidental redirect and the page now returns 200
- You collapsed a chain and want Google to crawl the final page
It will not help when
- You submit the URL that redirects
- The redirect is intended and the destination is already indexed
- The destination is itself blocked, noindex, or an error page
- Your links and sitemap still point at the old URL
When you submit a URL, we check it first and skip redirects, noindex pages, robots.txt blocks, error pages, and pages that point to another page as the original, without charging. Then we help Googlebot discover and crawl it and search Google for the exact URL after 24 hours, again around days 3 and 7 if it is not found yet, with a full report around day 5and final checks around day 14. A URL confirmed as not indexed gets its standard credit back. Google still decides what it indexes. See Submitting URLs for the details.
Other Page indexing statuses
Each reason in the report needs a different fix. Find the one Search Console shows you.
Discovered - currently not indexed
Google found the URL but has not crawled it yet.
Crawled - currently not indexed
Google crawled the page and chose not to index it for now.
Duplicate without user-selected canonical
The page does not name a main version, so Google picked another URL as the original.
Duplicate, Google chose different canonical than user
The page names itself as the main version, but Google picked another URL instead.
Alternate page with proper canonical tag
The page points to another page as the main version, and Google agreed.
Soft 404
The page loads, but Google thinks it looks like an error or empty page.
Excluded by 'noindex' tag
The page tells Google not to index it.
Blocked by robots.txt
Your robots.txt file stops Googlebot from crawling the page.
Tools for getting pages indexed
Every Page indexing status
What each reason in the report means, whether it needs fixing, and whether submitting helps.
Free indexability checker
The full checker page, with notes on what each result means and what to do next.
Indexing API
Submit fixed pages from your own code with one API key and track each one until it is indexed.
Automatic indexing
Submit pages every time you publish or fix them, from your sitemap, your deploy, or your agent.
Frequently asked questions
The URL is not the main version of the page and it redirects to another URL, so Google does not index it. Google decides separately whether to index the destination. Google also notes that a canonical URL with a redirect can be indexed.
Usually not. Most sites have redirects for old URLs, http to https, www to non-www, and trailing slashes, and they are meant to show up here. It is a problem when a page you want in Search redirects by mistake, or when your links, canonicals, or sitemap keep pointing at redirecting URLs. Your sitemap should list the destinations, not the URLs that redirect.
Yes. Google treats a permanent redirect (301 or 308) as a strong signal that the destination should be shown in search results. A temporary redirect (302 or 307) is a weaker signal, and Google may keep showing the original URL.
Googlebot follows up to 10 hops. Google advises redirecting straight to the final destination, and if that is not possible, keeping chains short, ideally no more than 3 hops. A chain that is too long, or a loop, is reported as a redirect error.
URL Inspection reports on the URL you entered, ignoring the redirect. To see the destination, use the Inspect button in the Page indexing section of the result, or inspect the destination URL directly. The live test follows redirects and tests the final URL without saying it did so.
We check the page for redirects, noindex tags, robots.txt blocks, and error pages, then help Googlebot discover and crawl it. A URL that redirects is skipped before sending and not charged, so submit the destination instead. We check every URL once after 24 hours. Your full report follows around day 5, with final checks around day 14. If Google has not indexed the URL at the final check, the standard credit comes back.
Each sent URL costs 1 credit, which is $0.20, or $0.10 on purchases of $1,000 or more. URLs skipped before sending, including redirecting URLs, are not charged.
What does "Page with redirect" mean?
The URL is not the main version of the page and it redirects to another URL, so Google does not index it. Google decides separately whether to index the destination. Google also notes that a canonical URL with a redirect can be indexed.
Is "Page with redirect" a problem?
Usually not. Most sites have redirects for old URLs, http to https, www to non-www, and trailing slashes, and they are meant to show up here. It is a problem when a page you want in Search redirects by mistake, or when your links, canonicals, or sitemap keep pointing at redirecting URLs. Your sitemap should list the destinations, not the URLs that redirect.
Does a 301 or a 302 matter?
Yes. Google treats a permanent redirect (301 or 308) as a strong signal that the destination should be shown in search results. A temporary redirect (302 or 307) is a weaker signal, and Google may keep showing the original URL.
How many redirects in a row are too many?
Googlebot follows up to 10 hops. Google advises redirecting straight to the final destination, and if that is not possible, keeping chains short, ideally no more than 3 hops. A chain that is too long, or a loop, is reported as a redirect error.
Why does URL Inspection say the URL is not indexed when the destination is?
URL Inspection reports on the URL you entered, ignoring the redirect. To see the destination, use the Inspect button in the Page indexing section of the result, or inspect the destination URL directly. The live test follows redirects and tests the final URL without saying it did so.
What does Index My Site do with a submitted URL?
We check the page for redirects, noindex tags, robots.txt blocks, and error pages, then help Googlebot discover and crawl it. A URL that redirects is skipped before sending and not charged, so submit the destination instead. We check every URL once after 24 hours. Your full report follows around day 5, with final checks around day 14. If Google has not indexed the URL at the final check, the standard credit comes back.
What does it cost?
Each sent URL costs 1 credit, which is $0.20, or $0.10 on purchases of $1,000 or more. URLs skipped before sending, including redirecting URLs, are not charged.
Submit the destination pages, not the redirects
Submit pages from the web app, the API, the CLI, or your AI agent. Redirecting URLs are skipped without charge. Credits start at $25.