"Crawled, currently not indexed" is the Search Console status that says Google fetched the page, understood it, and decided it was not worth a slot. No error, no penalty, no instruction. On one of our sites it applies to 19 of 63 content pages. This is what the status means and the order in which we look for the cause.
What does the status actually mean?
Answer. Googlebot fetched the page without error and the indexing system declined it. It is a quality decision, not a technical one.
Google's documentation says the page "may or may not be indexed in the future" and that there is nothing to fix on the crawl side. That is accurate and unhelpful. In practice the status clusters around four causes, and they are cheap to tell apart.
What does this check detect?
Answer. For every page in your inventory, the URL Inspection verdict: indexed, crawled-not-indexed, discovered-not-crawled, excluded by a tag or canonical, or an error.
Moonleap asks the Search Console URL Inspection API for up to 100 content pages a week (the API allows 2,000 a day per property) and stores the verdict per page. The finding lists the not-indexed pages, groups them by section, and shows how many of them are new since the last check. On 4 September 2026 the site in this case had 19 of 63 pages in this state, 3 of them checked by hand with the same result.
What are the four causes, in the order to check them?
Answer. Thin or templated content, near-duplicates of an indexed page, pages nothing links to, and pages the site itself treats as second-class. Check in that order because the first two explain most cases.
- Under ~200 words of unique text
- Same heading structure as ten siblings
- Fix: merge, expand, or remove from sitemap
- Another URL says the same thing better
- Google chose that one as canonical
- Fix: consolidate and redirect
- No internal link from an indexed page
- Reached only via the sitemap
- Fix: link it from where readers are
- Not in the main nav, no schema, generic title
- Fix: treat it like a real page or drop it
On our site the 19 pages are mostly cause 1 and 2: playbook pages in three languages with the same structure and a few hundred words each, where the English version is indexed and the translations are not. The candidate fix is not "make the Polish page longer for its own sake" but "give it the local examples and sources a Polish reader needs", which is also what would make it worth citing.
Why is resubmitting the wrong first move?
Answer. Because the page was already crawled. Asking for another crawl of the same content produces the same decision and uses a request you could spend on a changed page.
Request indexing after the page has changed, not before. Search Console lags two to three days behind the crawl, and Google may take weeks to revisit a page it declined; the honest measurement window is 28 days after the edit. This is why the finding on our site was snoozed for 30 days rather than closed: the pages were being rewritten, and re-checking before the recrawl would only have produced noise.
How do you verify progress?
Answer. Re-run the coverage check after the recrawl window and count the not-indexed set; a page that moved to "indexed" stays there unless the content regresses.
In Search Console, Indexing, Pages, the "Crawled, currently not indexed" row shows the count over time; the URL Inspection tool shows the verdict for a single page and lets you request indexing once the content has changed. Moonleap re-checks the same pages weekly and reports the delta in the Monday report.
FAQ
Is 30% not indexed bad?
It depends on what the 30% are. Login pages, tag archives and thin translations being left out is Google saving you from your own site. Product or guide pages being left out is lost traffic.
Will adding the pages to a new sitemap help?
No. The sitemap already told Google about them; that is why the status is "crawled" and not "discovered".
Does an AI Overview cite pages that are not indexed?
No. AI Overviews draw on the Google index. A page in this state cannot be cited until it is indexed.
Sources
- Google, "Page indexing report", status definitions https://support.google.com/webmasters/answer/7440203
- Google, "URL Inspection tool" https://support.google.com/webmasters/answer/9012289
- Case, omniroom.ai, 63 content pages checked with the URL Inspection API on 4 September 2026 (Moonleap index coverage check)