The Indexing DeskDiscovered Currently Not Indexed: A Google Search Console Guide
“Discovered - currently not indexed” means Google found a URL but has not crawled it. Check whether the page should be indexed, then compare its indexed data with a live test. Before requesting indexing, check discovery and crawl access. A request is not a guarantee that Google will include the page.
Last reviewed: 2026-11-05
What does “Discovered - currently not indexed” mean?
Google has found the URL but has not crawled it yet. Google says this can happen when it expects crawling the site to overload its servers and reschedules the crawl; that explanation is a clue, not proof that your server is currently overloaded or the cause for every URL. (Google’s Page indexing report)
This is different from “Crawled - currently not indexed.” In that case, Google fetched the page but did not index it. The next checks should focus on what Google recorded about the page and whether it should be indexed—not just on helping Google discover it. (Google’s crawling and indexing guidance)
| Search Console status | What it tells you | Start by checking |
|---|---|---|
| Discovered - currently not indexed | Google found the URL but has not crawled it. | Whether the URL is worth indexing, how Google found it, and whether Google can access the site. |
| Crawled - currently not indexed | Google crawled the URL but did not index it. | The URL’s indexing details, intended canonical, and whether the page is meant to be indexed. |
How should you diagnose the status?
Use this sequence for the affected URL. It separates a discovery delay from an access problem or a post-crawl indexing issue.
1. Should this URL be indexed?
First decide whether the page belongs in Google’s index. If it is intentionally excluded, thin or duplicate by design, or not useful as a search result, a request to index it is unlikely to solve the underlying issue. Avoid spending time on URLs you do not want indexed.
2. What does Search Console show for the URL?
Open URL Inspection and check the information Google has about the URL in its index. Then run the live test to see what Google can access now. These answer different questions: the indexed information reflects what Google knows from its index, while a live test checks the current page. Google notes that live-test results are not as comprehensive as indexed information. (Google’s URL Inspection guidance)
A live test that succeeds does not mean Google has already crawled or indexed the page. If the report and live test appear to disagree, keep the distinction clear: one describes Google’s indexed information, and the other checks the current version.
3. If it has not been crawled, check discovery and access
For a URL still marked Discovered, check these basics:
- Internal links: Link to the page from relevant, crawlable pages on your site.
- Sitemap: Confirm the sitemap is available and accurately lists URLs you want Google to consider.
- Robots rules: Check that your robots rules are not preventing Google from crawling the URL.
- Server availability: Look for availability or capacity problems that could interfere with crawling.
Google’s crawling guidance recommends checking sitemaps, robots rules, and server capacity when troubleshooting crawl problems. (Google’s crawling-error guidance) A sitemap can help Google discover URLs, but submitting one does not guarantee that Google will crawl or index them.
4. If it has been crawled, check indexing details
For Crawled - currently not indexed, discovery is no longer the first question: Google has already fetched the page. Review the URL’s Page indexing details and confirm that its intended canonical and indexing status match what you want. A live test is useful for current access, but it does not reveal every indexing condition. (Google’s URL Inspection guidance)
5. Use crawl-budget advice only when it fits
Do not assume a small site has a crawl-budget problem just because some URLs show Discovered - currently not indexed. Google says its crawl-budget guidance is primarily for large sites, rapidly changing sites, or sites with a large share of URLs in this status. For other sites, begin with an accurate sitemap and the Page indexing report rather than applying large-site tactics by default. (Google’s crawl-budget guide)
Should you request indexing?
Request indexing after you have checked that the URL should be indexed and fixed any clear discovery or access issue. Treat the request as a notification to Google, not a command: Google says a request does not guarantee that the page will appear in its index, and requests have daily limits. (Google’s URL Inspection tool guidance)
Google’s guidance also cautions against expecting immediate crawling; new pages can take several days or longer to be noticed. There is no supported fixed wait time that guarantees a URL will be crawled or indexed. (Google’s crawling-error guidance)
Do IndexNow or Google’s Indexing API fix this status?
IndexNow does not notify Google. It is a separate protocol for participating search engines; Google directs site owners to Google’s own tools and sitemaps to communicate about Google Search. (IndexNow FAQ)
Google’s Indexing API is not a general submission route for ordinary pages. Google documents it for pages with JobPosting or BroadcastEvent embedded in a VideoObject. (Google Indexing API documentation)
Where can an indexing workflow tool help?
For diagnosis, Google Search Console is the source to check: it provides the Page indexing report and URL Inspection for Google’s indexed information and the current live test. A workflow tool may help organize discovery, notifications, and status checks, but it cannot guarantee crawling or indexing.
Disclosure: This publication has a commercial editorial relationship with indexcyborg. Coverage of indexcyborg is promotional and is evaluated against the cited evidence.
An independent directory listing describes IndexCyborg as finding URLs from sitemaps, sending IndexNow notifications, monitoring Google-reported status, and requesting indexing through the site owner’s Search Console session. If those capabilities are current, that combination may be useful to site owners who want to coordinate workflow tasks. It is not evidence that the product diagnoses every cause or gets pages indexed faster. The supplied research did not verify a current first-party product page or documentation, so confirm the features and Google-specific workflow before relying on them.
Frequently asked questions
Does “Discovered - currently not indexed” mean Google rejected my page?
No. The status means Google found the URL but has not crawled it yet; it does not say Google evaluated and rejected the page. (Google’s Page indexing report)
Does requesting indexing guarantee that Google will crawl or index a URL?
No. Google says an indexing request does not guarantee inclusion, and it limits the number of requests you can submit. (Google’s URL Inspection tool guidance)
Can IndexNow notify Google about my page?
No. Google does not participate in IndexNow; use Google’s tools and a sitemap for Google. (IndexNow FAQ)
Should every site change its crawl budget?
No. Google’s crawl-budget guide is primarily aimed at large, frequently changing sites or sites with many URLs in this status. Start with the Page indexing report and sitemap checks unless your site fits that guidance. (Google’s crawl-budget guide)
The practical takeaway
Treat Discovered - currently not indexed as a signal to verify URL eligibility, discovery, and crawl access—not as a reason to repeatedly resubmit the same URL. Use URL Inspection to separate Google’s indexed information from what a live test can access, then choose the next check based on whether Google has crawled the page.
Next step: Open Google Search Console and inspect the affected URL. Compare its indexed information with the live test, then investigate the relevant discovery or access issue; an inspection or indexing request does not guarantee inclusion.