You add a sitemap, wait a week, and open the Page Indexing report in Google Search Console. Some URLs are indexed. A pile of others sit under two headings that sound almost identical: Discovered – currently not indexed and Crawled – currently not indexed. Google tells you the state. It does not tell you what to do about it. Here is what each one means and how we pull them apart.

Discovered – currently not indexed

Google knows the URL exists. It found it in your sitemap or through a link, added it to the crawl queue, and then chose not to fetch it yet. Nothing has been downloaded, so nothing has been judged. This is a scheduling decision, and it usually comes down to how Google is spending crawl budget on your site.

Common reasons a URL stays here:

The site has a lot of low-value or near-duplicate URLs, so Google slows down and picks what to crawl.
The page has weak internal linking. If the only thing pointing at it is one line in a sitemap, Google has little reason to prioritise it.
The server has been slow or returned errors during earlier crawls, so Google backed off.

A URL can leave this state on its own after a few weeks. If it has been stuck for a month or more, treat it as a signal that the page is not earning its place: give it real internal links from pages that already get crawled, and make sure it is genuinely distinct from the rest of the site.

Crawled – currently not indexed

This one is further along. Google fetched the page, read it, and decided not to put it in the index. The page is not blocked and not broken. It was assessed and it did not make the cut, or Google is still deciding.

What tends to land a page here:

Thin or templated content: a few lines of text wrapped in a lot of boilerplate.
Duplication. Another URL on your site (or someone else’s) covers the same thing better, so Google keeps that one instead.
A mismatch between what the page promises and what it delivers, often on faceted or parameter URLs.

The fix is editorial more often than technical. Merge overlapping pages, add the depth a real answer needs, or accept that the URL should not be indexed and drop it from the sitemap.

Why the report stops there

Search Console is a mirror of Google’s decisions. It reports the outcome for each URL and leaves the diagnosis to you. That gap is the whole reason we built Index Intelligence. We read the per-URL verdict straight from Google’s URL Inspection API and store it as Google’s: a gscState of INDEXED, NOT_INDEXED, or UNKNOWN, plus the raw coverage state and the time we fetched it. We never edit that field.

Then we run our own checks on the URLs Google is not indexing, and we keep the result in a separate column: inferredState and inferredReason. So a row might read “Google: Crawled – currently not indexed” next to “Us: indexable, no technical blocker — the page is 80 words on a template shared by 400 other URLs.” Google’s word and our inference stay side by side. Neither one overwrites the other.

What to check first

Before you touch the content, rule out the technical causes. Paste the URL into our free index checker. It runs the same deterministic pass we run inside the product: HTTP status, robots rules, the X-Robots-Tag header, the meta robots tag, the canonical, and the redirect chain. If any of those is quietly telling Google to stay away, that is your answer and it is a five-minute fix.

If the technical side is clean and the URL is still not indexed, the problem is the page itself or the crawl priority it earns. Connect Search Console to a project and we will keep the per-URL history, re-check on a schedule, and tell you the day a URL flips state instead of leaving you to notice weeks later. See what that costs.