Crawled, Currently Not Indexed: What It Means & How to Fix It

No status in Google Search Console's Page Indexing report raises more questions than this one. "Crawled — currently not indexed" means: Googlebot already visited the page, downloaded and analyzed its content, but decided not to include it in the index. Here is why that happens and what to do about it: after you improve the page, it needs a forced recrawl — the fastest way is a list of bot visits through AGD Index.

What the status actually means

Indexing has three steps: URL discovery → crawl → index inclusion. "Crawled — currently not indexed" marks the break between steps two and three:

Google knows about the URL;
Googlebot downloaded the content (not just "saw a link");
the evaluation algorithm rejected the page for the index — for now.

The operative word is "currently". This is not a life sentence: Google re-reviews such pages over time, and the verdict can change in either direction.

Crawled vs Discovered: the difference

Two similar statuses that get confused:

Status	What happened	What was missing
Discovered — currently not indexed	Google knows the URL (from sitemaps or links) but never visited	A crawl — budget/priority
Crawled — currently not indexed	Googlebot visited and downloaded the page but did not index	Quality/uniqueness/priority — the algorithm's call

The diagnostics differ. For Discovered, the problem is reaching the crawl stage (internal links, forcing visits). For Crawled, the problem is inside the page itself.

Why Google crawls but does not index

1. Content quality below the bar

The main reason. Google compares the page with what is already indexed for the same intent: if it adds no value — a short description, auto-text, an aggregator with no expertise of its own — it stays out. The classic case: 5,000 programmatic catalog pages of which Google indexes the 200 "best".

2. Duplicates and near-duplicates

Variant pages of one entity (sort orders, filters, print versions, regional copies) get crawled but not indexed — Google has already picked the canonical. Check the canonical tag and the "Duplicate" report cluster.

3. A young or weak domain

On a new site Google "window-shops" for a long time: crawls everything, indexes selectively. The indexed share grows over time — if the content proves its quality.

4. Crawl budget and queue priority

A large site with hundreds of CCNI pages is a normal picture: Google distributes a site's index "allowance" by priority. Low-priority URLs wait weeks for their turn.

5. Technical semi-problems

A canonical pointing elsewhere, a mild soft 404, content assembled by JavaScript after the bot's first pass, redirects inside the chain — all of this confuses evaluation.

The step-by-step fix plan

Step 1. Assess the scale and shape

Open Page Indexing → "Crawled — currently not indexed". Export sample URLs. Answer:

Are these mass same-type pages (programmatic, tags, filters) or single important ones?
How long have they been published?
Are they in the sitemap?

Mass programmatic pages and single hand-written articles are treated differently.

Step 2. Inspect concrete pages

Take 3–5 URLs and check:

Canonical — self-referencing or correct?
Duplicates — are there near-twins of this content on the site?
Quality — if you were Google, would you take this page into results over the existing ones?
Internal links — how many links point at the URL, and from which pages.

Step 3. Act by problem type

Weak content — strengthen the page: structure, facts, FAQ, unique data, answers to real questions. For programmatic pages this is the only long-term fix.

Duplicates — close the variants (canonical/301), keep one canonical version, remove duplicates from the sitemap.

An important quality page stuck in limbo — force a recrawl: "Request Indexing" in GSC (one by one) or bot visits by list. A forced recrawl after content improvements is exactly the case where forcing genuinely works: bot visit tariffs.

Thousands of junk pages — do not force their crawl; the opposite: block them from indexing and crawling, and save the crawl budget for URLs that matter.

Step 4. Check dynamics in cycles

The status gets re-reviewed on repeated crawls. The loop: fixes → 2–4 weeks of observation in the report → conclusions. Checking every two days shows nothing.

What not to do

Do not resubmit the same weak URL repeatedly — repeat visits do not change a quality verdict, they burn budget.
Do not trust "indexing guarantees" — a service can guarantee a bot visit (that is honest), but not Google's decision (that cannot be promised).
Do not remove pages from the sitemap "so Google is not confused" — the sitemap is not the cause of CCNI; it helps discovery.

FAQ

Is Crawled — currently not indexed bad?

Depends on the share. If 10–30% of secondary pages sit in this status, that is normal prioritization. If all new content slides into CCNI together with a traffic drop — it is a quality or technical signal.

How long until the status changes?

From days to months. A recrawl after content improvements speeds up the re-review — force it with bot visits or a GSC request.

Do bot visits help with Crawled — currently not indexed?

Partially. A repeat visit gives Google a chance to re-evaluate an improved page. But if the content is unchanged and weak, the verdict repeats. Quality first, forcing second.

How is it different from "Discovered — currently not indexed"?

Discovered — Google found the URL but has not spent a crawl on it (accessibility/priority problem). Crawled — the page was crawled and rejected (content or canonicalization problem).

Can CCNI be caused by noindex?

No — a noindex page lands in a different report cluster ("Excluded by 'noindex' tag"). CCNI is about quality and priority. Blockers are covered in the robots.txt and noindex guide.

Should CCNI pages be removed from the sitemap?

No. Keep only canonical, important URLs in the sitemap, but CCNI status alone is not a reason to exclude: those pages can enter the index later.