Crawled not indexed means Google fetched the page but chose not to add it to the index that serves search results. It's a storage decision, not a penalty. It usually signals that the page adds little unique value compared with pages Google already has.
The fix is to make the page clearly worth storing: unique content, working canonicals, real internal links, and no conflicting directives. Then verify with URL Inspection and wait.
How to tell crawled, indexed and served apart
Three stages sit between a URL and a search result. Crawling is fetching: a bot downloads the page HTML. Indexing is storing: Google parses the page, extracts signals and decides whether to keep a copy in its index. Serving is ranking and displaying that stored copy for a query.
The status "Crawled – currently not indexed" in Google Search Console's Page indexing report means stage one happened and stage two did not. The page was fetched, but Google did not add it to the index. It can still be crawled again later.
Put simply: crawl is the visit, index is the filing cabinet, serve is the answer at the front desk. A page can pass the first and fail the second.
How to read the pipeline without mixing up the stages
Each stage has its own failure modes and its own diagnostics. Mixing them up leads to wasted fixes: people resubmit sitemaps when the real problem is duplicate content, or rewrite titles when the real problem is a noindex tag.
Google documents the crawl–index–serve pipeline in its Search Essentials documentation. The key point for site owners is that indexing is not automatic after crawling. Google's own guidance says it indexes pages it finds useful and may choose not to index pages it considers duplicates or low value.
| Stage | What happens | Where to check | Typical failure signal |
|---|---|---|---|
| Crawl | Bot fetches the URL and reads the HTML | Search Console URL Inspection, server logs | Discovered – currently not indexed; blocked by robots.txt |
| Index | Google parses, deduplicates and stores the page | Page indexing report, URL Inspection | Crawled – currently not indexed; Duplicate, Google chose different canonical |
| Serve | Stored page is ranked and shown for a query | Search results, Performance report | Indexed but no impressions; ranking below position 50 |
If the page is not in the table's middle row, no amount of title tweaking will help. Fix the index decision first.
How to spot the misconceptions that waste weeks
Several beliefs about indexing are common and wrong. Correcting them early saves time.
- Misconception: crawling ensures indexing. Correction: Google's documentation states that crawling is a precondition, not a commitment. Many crawled URLs are never indexed.
- Misconception: submitting a sitemap forces indexing. Correction: a sitemap helps discovery. Google's sitemaps documentation describes it as a hint about URLs, not a command to index them.
- Misconception: "Crawled – currently not indexed" is a penalty. Correction: it is a quality and priority decision. Penalties appear under manual actions or security issues, not this status.
- Misconception: requesting indexing in URL Inspection ensures a fix. Correction: it queues a crawl. The index decision still depends on the page's content and signals.
Each correction points to the same conclusion: fix the page's value and signals, not the submission mechanics.
How to diagnose why a small site gets stuck
Small sites face a structural disadvantage. A site with 40 pages and few inbound links gives Google fewer signals about which pages matter. Large sites with strong link profiles get crawled and indexed faster because their pages sit in a denser web of references.
Common causes for "Crawled – currently not indexed" on small sites include thin pages that repeat the same service description, near-duplicate location pages, canonical tags pointing elsewhere, and pages with no internal links from the main navigation.
There is no public figure for how many pages Google leaves unindexed. Any percentage you see quoted is an estimate, not a published metric.
How to run the fix checklist in order
Work through these steps in sequence. Each one removes a possible cause before you move to the next.
- Check the directives. Confirm the page does not carry a noindex meta tag or X-Robots-Tag header. Check robots.txt does not block the URL. A blocked page cannot be indexed, and a noindexed page will not be.
- Check the canonical. The canonical tag should point to the page itself, not to a different URL. A self-referencing canonical is the default correct state.
- Check for duplication. Compare the page against others on your site. If two pages say the same thing, merge them or make each one distinct. Google's guidance on duplicate content explains how it consolidates near-identical pages.
- Add unique substance. Give the page information no other page on the site carries: specific prices, process steps, named suppliers, local details. Thin pages are the most common cause on small sites.
- Add internal links. Link to the page from relevant pages using descriptive anchor text. A page with no internal links is effectively orphaned, and Google's crawler relies on links to judge importance.
- Request indexing. Use URL Inspection in Search Console to request a fresh crawl. This queues the URL; it does not ensure indexing.
Step one catches the most common self-inflicted errors. A page blocked by robots.txt or tagged noindex will never index, no matter how good the content is.
How to decide which pages to leave unindexed
Not every page should be indexed. Indexing thin or duplicate pages dilutes the site's quality signals and can slow down indexing for the pages that matter.
Leave these unindexed on purpose: tag archive pages, internal search results, paginated duplicates, test pages, and utility pages such as login or cart. Use noindex for pages you want crawled but not stored, and robots.txt for pages you do not want crawled at all.
The distinction matters. A noindex tag requires a crawl to be seen, so do not combine it with a robots.txt block on the same URL. Google's documentation on robots.txt and noindex explains that blocking crawl prevents the noindex from being read.
How to verify the fix and monitor the result
Verification happens in two places: URL Inspection for a single page, and the Page indexing report for the pattern across the site.
In URL Inspection, the "Coverage" section shows the current index status. After a successful fix, the status changes from "Crawled – currently not indexed" to "Submitted and indexed" or "Indexed, not submitted in sitemap." The change is not instant; it follows the next crawl and index cycle.
In the Page indexing report, watch whether the count of "Crawled – currently not indexed" falls over four to eight weeks. A falling count alongside stable indexed pages is the signal that the fixes worked.
Keep a simple log: URL, date checked, status, action taken, date rechecked. This turns a vague problem into a tracked process. The log also gives you evidence when you report progress to a client or manager, and it shows which fixes actually moved the status.
Key Facts at a Glance
- "Crawled – currently not indexed" means Google fetched the page but did not add it to the index.
- Crawling, indexing and serving are three separate stages with separate failure modes.
- Thin content, duplication, wrong canonicals and missing internal links are the most common causes on small sites.
- A noindex tag or robots.txt block prevents indexing entirely; check these first.
- Requesting indexing queues a crawl, not an index decision.
- Recheck status after two to four weeks; there is no published assured timeline.
What does "Crawled – currently not indexed" mean?
It means Google fetched the page but chose not to store it in the index. The page can be crawled again later, and the status can change if the page's content or signals improve.
How long until Google indexes a crawled page?
There is no published assured timeline. Google's documentation does not commit to a fixed period. Recheck after two to four weeks and look for a status change in URL Inspection.
Why are my pages crawled but not indexed?
The usual causes are thin or duplicate content, a canonical pointing elsewhere, no internal links, or a noindex or robots block. Check the directives first, then the content and links.
Does internal linking help indexing?
Yes. Internal links help Google find pages and judge their importance. A page with no internal links is effectively orphaned. Google's crawler relies on links as a discovery and priority signal.
How do I force Google to index a page?
You cannot force indexing. You can request a crawl via URL Inspection, fix the page's content and signals, and wait. The index decision remains Google's.
