“Crawled – currently not indexed”: what Google is actually telling you

Of all the statuses in Search Console, this is the one that wastes the most engineering time — because it reads like a bug, and teams reasonably go looking for the bug. There usually isn’t one.

Read the words literally. Crawled: Googlebot fetched the page successfully. Currently not indexed: having read it, Google decided not to store it. Every technical explanation you might reach for — a robots rule, a stray noindex, a failed render, a canonical pointing elsewhere — has its own distinct status. If you are seeing this one, those have already been ruled out for you.

That reframing matters, because it changes where you look. This is not a crawlability problem. It is Google declining to spend an index slot, and index slots are allocated on expected value.

First, confirm it really is this status

Before treating it as a quality issue, spend five minutes ruling out the cases that look similar in the URL Inspection report:

• Check the exact URL you inspected. Inspecting the non-canonical host (apex instead of www, or vice versa) reports on a redirect, not on your page.
• Read “Page fetch” and “Indexing allowed”. A successful fetch with a blocked indexing signal is a different problem with a different fix.
• Ignore the fields showing N/A. When a page is not indexed, Google never reached the canonical-evaluation stage, so empty canonical fields are a symptom of the status rather than a second fault to chase.
• Run “Test live URL”. If the live test renders your real content, the served HTML is fine and the answer is not in your markup.

The four causes that account for most cases

In rough order of how often they turn out to be the real reason:

1. The site has no external corroboration

Zero inbound links is the single most common denominator. Links are how Google forms an initial estimate of whether anyone would miss this page — and with none, a new URL on a new domain has nothing arguing for it. No amount of on-page work substitutes, which is what makes this the frustrating one: the fix is off your site entirely.

2. The page is thin relative to what already ranks

“Thin” is comparative, not absolute. Six hundred words can be plenty for a narrow question and nowhere near enough for a broad one. The test is whether your page answers the query more completely than the pages already indexed for it. If it does not, indexing it adds nothing to the index.

3. The site is simply too new

A domain with no history has no track record to extrapolate from. Weeks to a couple of months of this status on a genuinely new site is ordinary, and some pages resolve themselves with no intervention. This is the one case where waiting is a legitimate strategy — but only in combination with fixing the first two.

4. The page duplicates something, including your own work

Near-duplicates get deduplicated. Two pages selling the same thing in slightly different words compete for the same slot and often both lose. Internal duplication counts: a variant landing page, a printer-friendly version, a paginated archive that repeats its items.

It is usually a site-level verdict, not a page one

The status appears per URL, which makes it look like a per-page problem. If most of your pages carry it at once, the shared cause is almost always the domain, not the individual documents — and rewriting one page will not move it.

Two site-level signals are easy to miss. One is a large, recently-disappeared section: if a subdomain or directory that Google had indexed stops resolving, the domain reads as a site that just lost most of its content, and that colours how new URLs on it are treated. The other is a sitemap Google has never successfully fetched, which removes your clearest statement of which URLs you consider important.

The order to work in

1. Confirm the sitemap is fetched, not just submitted. A status of anything other than Success means Google is working without it. Free to fix, so fix it first.
2. Give every important page an internal link. A hub page — a blog index, a docs index — that links to each item is enough, provided the links are real anchors in the served HTML rather than JavaScript-only handlers.
3. Earn three to five genuine external links. Directory and profile listings for your category, and anywhere your project legitimately belongs. This is the step people skip and it is the one that most reliably works.
4. Then improve the page itself — depth, structure, specificity — measured against the pages currently indexed for your query, not against a word count.
5. Only now request indexing. Requesting a recrawl of unchanged content re-runs the same evaluation and reaches the same conclusion.

The honest summary: this status is Google telling you your page is not yet worth indexing, and it is usually right at the moment it says so. The work is making it wrong, which is mostly not a coding task. If you want to see how your pages are structured from an answer engine’s point of view, our free AI visibility audit reports on that side of it, and getting cited by AI search engines covers what extraction-friendly structure looks like in practice.