Discovered, currently not indexed: get Google to crawl the page
Google knows the URL exists but has not visited it yet. Here is what that status means, why pages get stuck in it, and what to fix before you send Googlebot back.
What the status means
In the Page indexing report, "Discovered - currently not indexed" means Google found the URL, from a link or a sitemap, but has not crawled it yet.
Google knows the URL
It is in Google's list of URLs to visit. Nothing is blocking discovery.
Google has not fetched it
The last crawl date is empty. Google has not seen the content, so it has not judged it.
The crawl was put off
Google says it typically rescheduled because crawling then was expected to overload the site.
Definition from Google's Page indexing report help page.
Why Google has not crawled it yet
The page itself is rarely the reason, because Google has not read it. The cause is usually the site around it.
Your server looked too busy
This is the reason Google gives. If crawling more would overload the site, Google reschedules. Slow responses, timeouts, and 5xx errors all lower how fast Google is willing to crawl.
Google is crawling low-value URLs instead
Filter and sort parameters, session IDs, endless calendar pages, and old redirects can soak up the crawling Google does on your site, so new pages wait in the queue.
Few links point to the page
A page that only appears in your sitemap, or sits several clicks deep, looks less important than one linked from your home page or navigation.
You published a lot at once
Hundreds of new URLs on a young site can take a while to work through. Google spreads the crawling out rather than fetching everything on day one.
The page is simply new
Google may have found the URL only days ago. A short wait is normal, especially on a new site with few links from elsewhere.
Google sees little value in crawling more of the site
Google crawls more where it expects useful pages. If many similar pages on the site were thin or duplicated, new URLs that look like them can wait longer.
Check the page before you do anything else
Paste the URL from Search Console. The free checker looks for robots.txt blocks, noindex tags, and thin or repeated content that could hold the page back once Google does crawl it.
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.
Fix it in this order
Work from the site down to the page. Submitting comes last, once Google will find something worth indexing when it arrives.
- 1
Make sure it is a page you want indexed
Filter combinations, internal search results, and tag archives are often fine left out. Focus on canonical pages that answer a search on their own.
- 2
Check the server is healthy
Open the Crawl stats report in Search Console. Look for host problems, 5xx errors, and slow average response times, and fix those first.
- 3
Link to it from pages Google already crawls
Add links from your home page, a hub or category page, related articles, or a changelog. Links in plain HTML are the most reliable.
- 4
Cut the crawl waste
List only canonical, indexable URLs in your sitemap. Stop linking to parameter and duplicate URLs, and block truly useless URL patterns in robots.txt.
- 5
Get Googlebot to the page
Once the page is ready, request indexing in URL Inspection for a handful of pages, or submit them in bulk with Index My Site.
When submitting helps, and when it will not
This status is waiting on a crawl, so getting Googlebot to the page is usually the right move. It does not change what Google thinks of the page once it gets there.
It helps when
- The page is new or updated and nobody has linked to it yet
- Your server is healthy again after slow or failing responses
- You shipped many pages at once and want the important ones crawled first
- The page is good, but sits deep in the site with few links
It will not help when
- The page is thin, empty, or a near copy of another page
- It is blocked by robots.txt, has a noindex tag, or redirects
- The server still struggles, so Google keeps backing off
- It is a filter, sort, or parameter URL you do not need indexed
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.
Discovered vs crawled, currently not indexed
The two statuses look alike but need different fixes. One is still waiting for a visit from Google. The other already had one.
| Question | Crawled, currently not indexed | Discovered, currently not indexed |
|---|---|---|
| What Google did | Found the URL, fetched it, and chose not to index it for now | Found the URL but has not fetched it yet, so there is no last crawl date |
| Usual causes | Thin, duplicate, or low-value content, or a page that looks like others Google already has | Server capacity, crawl spent on low-value URLs, weak internal links, or a large batch of new pages |
| Does submitting help? | Not on its own. It helps after you change the page, so Google sees the new version | Often, yes. The problem is getting Googlebot to the page, which is what submitting does |
| What to fix first | The page itself: make it useful, distinct, and clearly the main version | Server health and internal links, then submit the URL |
- What Google did
- Crawled, currently not indexedFound the URL, fetched it, and chose not to index it for now
- Discovered, currently not indexedFound the URL but has not fetched it yet, so there is no last crawl date
- Usual causes
- Crawled, currently not indexedThin, duplicate, or low-value content, or a page that looks like others Google already has
- Discovered, currently not indexedServer capacity, crawl spent on low-value URLs, weak internal links, or a large batch of new pages
- Does submitting help?
- Crawled, currently not indexedNot on its own. It helps after you change the page, so Google sees the new version
- Discovered, currently not indexedOften, yes. The problem is getting Googlebot to the page, which is what submitting does
- What to fix first
- Crawled, currently not indexedThe page itself: make it useful, distinct, and clearly the main version
- Discovered, currently not indexedServer health and internal links, then submit the URL
Other Page indexing statuses
Each reason in the report needs a different fix. Find the one Search Console shows you.
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.
Page with redirect
The URL redirects to another page, so Google does not index this URL.
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
Google found the URL but has not crawled it yet. Google says it typically wanted to crawl the URL, but expected that doing so would overload the site, so it rescheduled the crawl. That is why the last crawl date in the report is empty.
Not exactly. Search Console lists it under reasons pages are not indexed, but it often just means the page is waiting. It becomes a problem when important pages stay in this state for weeks, or when the count keeps growing.
There is no fixed time. Some pages move on within days. Others wait much longer on sites with slow servers, lots of low-value URLs, or few links to the page. If a page has been stuck for weeks, work through the fix order above.
Partly. Google describes crawl budget as a mix of how much your server can handle and how much Google wants to crawl. Most small sites do not need to think about it. Large sites, or sites with many parameter URLs, often do.
Source: Google Search Central: Large site owner’s guide to managing your crawl budget
It can get Googlebot to the page, which is what this status is waiting on. Google then decides whether to index it. If the page is thin or a near copy of another page, it may move to "Crawled - currently not indexed" instead.
We check the page for redirects, noindex tags, robots.txt blocks, and error pages, then help Googlebot discover and crawl it. 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 are not charged.
What does "Discovered - currently not indexed" mean?
Google found the URL but has not crawled it yet. Google says it typically wanted to crawl the URL, but expected that doing so would overload the site, so it rescheduled the crawl. That is why the last crawl date in the report is empty.
Is it an error?
Not exactly. Search Console lists it under reasons pages are not indexed, but it often just means the page is waiting. It becomes a problem when important pages stay in this state for weeks, or when the count keeps growing.
How long does it take to clear?
There is no fixed time. Some pages move on within days. Others wait much longer on sites with slow servers, lots of low-value URLs, or few links to the page. If a page has been stuck for weeks, work through the fix order above.
Is this about crawl budget?
Partly. Google describes crawl budget as a mix of how much your server can handle and how much Google wants to crawl. Most small sites do not need to think about it. Large sites, or sites with many parameter URLs, often do.
Source: Google Search Central: Large site owner’s guide to managing your crawl budget
Will submitting the URL get it indexed?
It can get Googlebot to the page, which is what this status is waiting on. Google then decides whether to index it. If the page is thin or a near copy of another page, it may move to "Crawled - currently not indexed" instead.
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. 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 are not charged.
Send Googlebot to the pages that matter
Submit URLs from the web app, the API, the CLI, or your AI agent. Credits start at $25.