In short

“Discovered, currently not indexed” is a status in Google Search Console. Google knows the address, for example from the sitemap or through a link, but has not fetched the page yet. As long as that stays the case, it appears in no search.

The status has two neighbours that are often confused. With “Crawled, currently not indexed”, Google has read the page and decided against the index for now. With “URL is unknown to Google”, as the URL Inspection tool puts it, Google has not registered the address at all yet.

What Google says about it

On “Discovered, currently not indexed”, Google writes: the page was found but not crawled yet. Typically Google wanted to crawl it but rescheduled the fetch because it was expected to overload the site.

On “Crawled, currently not indexed”: the page was crawled but not indexed. It may or may not be indexed in the future. There is no need to resubmit it.

For AI visibility, one more sentence from Google matters: to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet. A page outside the index is therefore also missing from Google’s AI answers.

An example from our own records

On 1 October 2026 we checked all 86 addresses from the sitemap of k-i-soft.ch one by one in URL Inspection.

Status Addresses
indexed 56
URL is unknown to Google 21
discovered, currently not indexed 4
crawled, currently not indexed 5

The most important offer page was unknown. The portal sketch page had been live since 11 September and was in the sitemap. Google had last loaded the sitemap on 26 September and still had not registered the page. After the sitemap was resubmitted, it showed “discovered” in the evening, and a few hours later URL Inspection reported it as “unknown” again. The status is a snapshot, and it jumps.

Not a single term page was indexed. Of the twelve pages our glossary series had at the time, German and English, none was in the index. The most likely reason: only 2 of 25 blog posts linked to a term. The pages were in the sitemap, but hardly any path led to them. On 1 October we added 18 links from the posts. Whether that works, we will measure.

There is movement all the same. The post “We are not a target” showed “discovered” in the afternoon and was indexed the same evening, crawled on 1 October.

The most common mistake

“The page is in the sitemap, so Google has it.”

The sitemap tells Google that an address exists. Whether and when Google fetches it, Google decides itself. Pages that no internal link points to are easily left lying, even when they are in the sitemap. And a page that is not in the index cannot appear as a source in any of Google’s AI answers either.

Where the boundaries run

Crawled, currently not indexed means Google has read the page and not taken it in for now. Discovered, not indexed is not yet a decision: Google simply has not been there.

Excluded by noindex means the page itself forbids being taken in. That is intentional, for example for old redirect pages.

Indexed only under an old address is a special case we see with several posts: Google lists the version without a trailing slash, which has long redirected to the new one, and does not know the new one yet. That resolves with the next crawl.

AI crawlers fetch pages independently of the Google index. Whether ChatGPT or Claude read a page is in the server logs, see AI crawler. For Google’s own AI answers, the index is what counts.

How to check it yourself

In Search Console under Indexing, Pages, the reason is listed for every address that is not indexed. Look at the list under “Discovered, currently not indexed” and ask for each page: how many internal links point to it, and from which pages?

For individual important pages, URL Inspection has the “Request indexing” button. Google limits how many requests are possible per day. Use them for the pages that sell, and for the rest add links from pages that are already in the index.

Sources

Provider pages retrieved on 1 October 2026.