Crawled — currently not indexed
Google has fetched the page but has not included it in its index. Start by checking the page’s purpose and current response; repeating an indexing request is not a diagnosis.
Troubleshooting guide · Public signals and practical next steps
What this means
This Search Console status describes a page that was crawled but is not currently indexed. It does not identify one universal technical cause.
When it’s normal—and when to investigate
Often expected
A recently published page may still be under evaluation. A low-value variant, empty archive, or substantially repeated page may never need its own search result.
Worth investigating
Investigate when an important, original page remains excluded, especially if similar pages are indexed or the exclusion appeared after a template change.
Work through these checks
Compare the recorded crawl with today’s page
Inspect the exact URL in Search Console and note the last crawl date. Run a live test separately. A successful live fetch does not mean the stored indexing decision has changed.
Eliminate visible technical contradictions
Check the final response, noindex directives, and declared canonical below. If the canonical points to a different page, decide whether that consolidation is intentional.
Read the page as a visitor
Does it answer a distinct question or offer something beyond another page on your site? Compare the actual main content, not just the title. Check rendered HTML if the server response contains very little text.
Review how people and crawlers reach it
Link to the page from a relevant existing page. Include the preferred URL in a sitemap if appropriate. Avoid creating many trivial variations just to add more URLs.
Common causes
- Repeated content spread across parameters or near-identical articles.
- An empty or incomplete template was served at the last crawl.
- Important content depends on scripts or an API that fails during rendering.
- The page is accessible but offers little that distinguishes it from existing pages.
Possible fixes
- Correct a mistaken noindex or canonical at its source, then confirm the live response.
- Improve the substance of a useful page; consolidate pages that serve the same purpose.
- Provide essential content in the server HTML when practical, and repair rendering failures.
- After a meaningful change, request indexing once and monitor the recorded crawl date.
Make changes that match the page’s intended purpose. A technically valid page is not guaranteed to be indexed.
What this tool can and cannot verify
It can
Check today’s public response for exclusions, canonical signals, and a very thin server-rendered body.
It cannot
See Google’s stored content, judge its quality systems, explain an undisclosed indexing decision, or guarantee acceptance.
Google’s own indexing status is available through Search Console / URL Inspection for a verified property. The live test and the recorded indexing report answer different questions.
A useful follow-up
Would adding more words solve this?
Not by itself. There is no universal minimum word count. A short page can satisfy its purpose; extra text that adds no useful information does not make a better page.
Official reference: Google: Page indexing report. See also the Page indexing report documentation.