Search Console's "Discovered" and "Crawled" not-indexed statuses mean different things. I compare Google's definitions with URL Inspection data from my own site, where sitemap-listed pages returning 200 still differed.
Contents (7)
When Search Console shows "Discovered - currently not indexed" or "Crawled - currently not indexed," it can look as if something is seriously wrong with the page.
But these two statuses do not mean the same thing.
Start by separating four statuses
| What Search Console or URL Inspection shows | What it tells you | What to do first |
|---|---|---|
| URL is on Google | Crawled and indexed | Usually nothing |
| Discovered - currently not indexed | Google found the URL but has not crawled it yet | Check how the page can be discovered (internal links, sitemap) and server health, then wait |
| Crawled - currently not indexed | Google read the page but did not index it | Check content, duplication, canonical, and so on. Do not keep requesting recrawls |
| URL is not on Google | URL Inspection has no information about the URL on Google's side | Check that the page is published, internal links, sitemap, noindex, and so on |
Google's Page indexing report defines "Discovered - currently not indexed" and "Crawled - currently not indexed" separately.
Reference: Search Console Help: Page indexing report
"Discovered - currently not indexed" means not crawled yet
According to Google, this status means the page was found by Google but has not been crawled yet.
Google gives a typical example: it tried to crawl the URL but expected that doing so would overload the site, so it rescheduled the crawl.
In this status, the last crawl date in the report is empty.
What this tells you:
Discovered = Google knows the URL exists
Not indexed = Google has not necessarily read and evaluated the page content yet
So it is not accurate to jump to "it is Discovered but not indexed, so Google judged it low quality."
"Crawled - currently not indexed" comes after the page was read
Google describes this status as the page was crawled but not indexed.
It may be indexed in the future, or it may not.
The important part is that, for this status, Google says there is no need to resubmit the URL for crawling.
In other words, repeatedly clicking "Request indexing" on the same URL is not a fix in itself.
It makes more sense to review:
- whether the content heavily overlaps with other pages
- whether the canonical is what you intended
- whether the page is really worth keeping as its own URL
- whether a searcher would have a reason to read this page on its own
- whether the page is linked from elsewhere on the site as an important page
But "Crawled - currently not indexed" does not mean "confirmed low quality" either. Google's definition only goes as far as "crawled, and not indexed for now."
I compared four URLs on oka-project
On September 16, 2026, I checked four oka-project URLs with the Search Console URL Inspection API. oka-project's main pages are in Japanese, so these are the Japanese URLs.
| URL | Status | Notes |
|---|---|---|
| /tools/markdown-editor | Submitted and indexed | Crawl succeeded, canonical matched, allowed by robots |
| /tools/markdown-viewer | Submitted and indexed | Crawl succeeded, canonical matched, allowed by robots |
| /blog/markdown-preview-online | Discovered - currently not indexed | Listed in the sitemap, no last crawl information |
| /blog/why-ai-copy-paste-formatting-breaks | URL is not on Google | Not known to Google in URL Inspection |
Even on the same domain, the statuses did not line up.
The tool pages being indexed did not mean the blog posts were automatically indexed, and being in the sitemap did not mean a URL was crawled right away.
This example also shows that you need to look at status URL by URL, not treat the whole site as simply "indexed" or "not indexed."
The Japanese page of Markdown Viewer was already indexed at the time of this check, while the Japanese version of Preview Markdown in Your Browser was "Discovered - currently not indexed" at the same point.
200, indexable, and in the sitemap, yet the statuses still differed
Separately from URL Inspection, I also checked the same URLs in a site audit on September 15, 2026.
| URL | HTTP | Indexable | Sitemap | Status on Google's side (9/16) |
|---|---|---|---|---|
| /blog/markdown-preview-online | 200 | Yes | Yes | Discovered - currently not indexed |
| /blog/why-ai-copy-paste-formatting-breaks | 200 | Yes | Yes | URL is not on Google |
At least these two URLs:
- returned a normal 200
- were not marked noindex
- were listed in the sitemap
Even so, on Google's side one was "Discovered - currently not indexed" and the other was not known at all.
What this example shows is that returning 200, being indexable, and being in the sitemap do not, on their own, guarantee an immediate crawl or indexing.
The site audit also has a value called internalLinkCount, but I could not confirm from the audit's specification that it means "the number of internal links pointing to that URL," so I did not use it as evidence about internal links. To judge internal linking, you need to check the actual linking pages or dedicated link data separately.
In URL Inspection, check the final URL after redirects
When you inspect a URL in Search Console, inspect the final URL that actually returns 200, not a similar-looking URL.
On September 16, 2026, oka-project's tools index showed this difference:
| URL inspected | HTTP status | URL Inspection |
|---|---|---|
https://oka-project.com/tools |
307 redirect to /tools/ |
URL is not on Google |
https://oka-project.com/tools/ |
200 | Submitted and indexed |
The /tools/ URL had been crawled on September 14, 2026, and both the Google-selected canonical and the user-declared canonical were https://oka-project.com/tools/.
So even if inspecting only the URL without the trailing slash makes it look as if "Google does not know about it," the canonical URL it redirects to may already be indexed.
Similarly, on oka-project, /blog was "Discovered - currently not indexed," while /blog/ was not known in URL Inspection. The list URL the site actually serves is /blog.
So before digging into why a page is not indexed, it is less likely to lead you astray if you:
- open the URL in a browser
- check whether it redirects
- check the canonical
- put the URL that finally returns 200 into URL Inspection
What to check, in order
When you find a URL that is not indexed, checking in this order makes it harder to mix up causes.
1. Does the page itself open normally?
Check that it returns 200, does not require login, and does not produce a server error.
2. Is there a noindex on it?
An unintended noindex contradicts the goal of appearing in search results.
3. Is robots.txt blocking the crawl?
robots.txt controls crawling. It has a different role from noindex.
4. Does the canonical point to the URL you intended?
When several URLs have the same content, Google chooses a representative URL.
Google Search Central explains that it groups similar pages and chooses the URL it considers most complete and useful as the canonical.
Reference: Google Search Central: What is URL canonicalization
5. Is it in the sitemap?
A sitemap is a way to tell Google about your important URLs.
But Google states clearly that having a URL in a sitemap does not guarantee it will be crawled or indexed.
Reference: Google Search Central: Learn about sitemaps
6. Is it linked from other pages?
Google uses links as a signal for finding new pages.
Its guidance recommends that every page you care about has a link from at least one other page on the same site.
Reference: Google Search Central: Link best practices
What to do for "Discovered - currently not indexed"
First, confirm that the page:
- is in the sitemap
- is linked internally
- returns 200
- is not noindex
- is not blocked by robots.txt
Then, if it was just published, wait a little.
By Google's definition, "Discovered - currently not indexed" means the page has not been crawled yet. Before rewriting the content over and over, it makes more sense to check whether your site's structure lets Google reach the page.
What to do for "Crawled - currently not indexed"
Here Google has already read the page.
Beyond technical blocks, check:
- whether the content duplicates other articles
- whether it has original information or measurements
- whether its search intent justifies a separate URL
- whether it is a thin list page
- whether the canonical choice is what you intended
On oka-project, rather than creating several comparison articles that target the same search intent, I drop overlapping article plans and fold them into existing articles.
I do not mechanically add more words just because a page is not indexed.
A log for checking whether the status changed
Avoid concluding "my fix got it indexed" from a single look at Search Console. Recording the time and conditions for each URL makes it harder to confuse the discovery stage, the crawl stage, and changes on your own site.
| What to record per URL | Example of what to keep |
|---|---|
| URL and date checked | The page's canonical URL and the date you checked |
| Status | The exact status name shown: Discovered, Crawled, indexed, and so on |
| Last crawl time | Only if Search Console shows it |
| Changes on your site | History of changes to the title, content, internal links, canonical, noindex, etc. |
| Other things you checked | HTTP status, robots, sitemap, reachability through internal links |
| Next check | Recheck the same URL later and record whether anything changed |
This is a log for observing changes. It does not prove that a particular fix directly caused Google's decision. The day you updated a page and the day Google fetched and evaluated it may not be the same.
URL Inspection and the live test do not guarantee indexing
"Request indexing" is not a guarantee
Search Console's URL Inspection lets you request indexing for the URL you inspected.
Google says that:
- it may take about a day in some cases
- it can take longer
- requesting does not guarantee inclusion in Google's index
- there is a daily submission limit
- for many URLs, you should use a sitemap
Reference: Search Console Help: URL Inspection tool
It is not a button that gets a page indexed when you press it.
Passing the live test does not guarantee indexing
URL Inspection has a live test.
But Google explains that even if the live test says the URL is available to Google, that is not a 100% prediction that it will actually be indexed.
In particular, things like:
- Crawled - currently not indexed
- Discovered - currently not indexed
- canonical selection
- some duplicate detection
cannot be judged from the live test alone.
The live test tells you whether the page can be fetched right now. It is not the final indexing result.
How many days should you wait?
There is no fixed number of days.
For indexing requests in URL Inspection, Google says it may take around one to two weeks, but that does not mean the page will definitely be indexed within that time.
For new sites, new URLs, and pages with weak internal linking, it can take a while to go from discovery to crawl.
So it is more useful to
record how the status in Search Console moves, from not known to Discovered to Crawled to indexed, rather than counting days.
Summary
It is more accurate not to lump Search Console's not-indexed statuses together as "Google does not like my site."
- Discovered - currently not indexed: Google knows the URL but has not crawled it
- Crawled - currently not indexed: Google read it but has not indexed it for now
- URL is not on Google: URL Inspection has no information about it on Google's side
- Submitted and indexed: indexed
Each status points you to a different place to look.
What matters is checking technical blocks, discovery paths, internal links, sitemaps, canonicals, and how original the content is as separate questions, and not applying the same fix mechanically to every URL that is not indexed.