"Crawled — Currently Not Indexed": What It Really Means and How to Fix It

By Paweł Zinkiewicz · Published August 13, 2026 · 9 min read

Google visited your page, read it, and decided the index doesn't need it. That's the whole message — and it's why most of the standard advice doesn't work. Here's what actually moves pages out of this status, based on monitoring indexing daily across 16 production sites.

On this page 1. What the status actually means 2. Why it's not a technical error 3. Diagnose before you fix 4. The real causes, ranked 5. Fixes that work (and ones that don't) 6. Monitoring at scale 7. FAQ

1. What the status actually means

"Crawled — currently not indexed" is a coverage state from Google Search Console. Broken into its parts:

This makes it fundamentally different from statuses like "Blocked by robots.txt" or "Excluded by 'noindex' tag". Those are instructions you gave. Crawled-not-indexed is a judgment Google made — an editorial decision that the page doesn't add enough value to the index right now.

One more distinction that trips people up: "Discovered — currently not indexed" means Google knows the URL exists but hasn't crawled it yet (usually a crawl-budget or perceived-importance issue). Crawled-not-indexed means the crawl happened and the page still didn't make the cut. The causes and fixes are different.

2. Why it's not a technical error

The instinct is to hunt for a technical problem — re-validate the sitemap, check canonical tags, run the page through an SEO auditor. Usually everything comes back green, which makes the status even more frustrating. r/SEO is full of threads titled some variation of "crawled currently not indexed hell — no technical issues".

That's because there is no technical issue. Google has publicly said the index is not meant to contain every page on the web. Indexing is selective, and selection got noticeably stricter from 2022 onward. When a crawled page stays out, Google is effectively saying one of two things:

  1. "This content doesn't add enough." Thin, templated, near-duplicate, AI-generated-without-editing, or simply covering a topic the index already answers well.
  2. "This page doesn't look important on your own site." Few or no internal links, buried deep in the architecture, orphaned after a redesign. If you don't link to it, why should Google index it?

Both signals are fixable — but not with a validator.

3. Diagnose before you fix

Before changing anything, get precise data per URL. Search Console's Pages report shows you the bucket; the URL Inspection tool shows you the details for each page:

FieldWhat to look for
VerdictNEUTRAL with "URL is not on Google" confirms crawled-not-indexed. FAIL means a different, technical problem.
Last crawlThe date Googlebot last fetched the page. Weeks or months ago = Google lost interest; the page also isn't being re-evaluated. Recent crawl + still not indexed = pure quality signal.
Google-selected canonicalIf it differs from your declared canonical, Google considers the page a duplicate of another URL — that's your real problem, not indexing.
Referring pageHow Google found the URL. "Sitemap only" is a red flag: it means no crawled page on your site links to it.

Sort your affected URLs by last crawl date. Two groups emerge, with different treatments:

4. The real causes, ranked

From most to least common, across the sites we monitor:

1. Weak internal linking / orphan pages

The single most common cause on real sites — and the most underdiagnosed, because audits focus on the page itself instead of the paths to it. Pages linked only from a sitemap, or three clicks deep behind paginated archives, look unimportant. After a redesign or category cleanup, hundreds of posts can silently become orphans.

2. Content that duplicates what's already indexed

Not plagiarism — redundancy. The 40th article on "how to boil eggs" with nothing new gets crawled, compared against the index, and skipped. Programmatic and AI-assisted pages fail here most often: technically unique text, zero unique information.

3. Thin or templated pages

Tag archives, near-empty category pages, auto-generated location pages, product variants. Each individually "fine", collectively teaching Google that the average new URL from your domain isn't worth indexing.

4. Site-level quality dilution

Indexing decisions have a domain-level component. A site where 60% of known URLs are low-value trains a low prior for everything new you publish. This is why deleting or noindexing junk often improves indexing of the good pages.

5. New site / low crawl demand

Young domains with little authority get a trickle of indexing regardless of quality. Time plus consistent publishing plus a few real external links is the only honest answer here.

5. Fixes that work (and ones that don't)

What actually works

  1. Link to the page from pages Google already crawls. Add links from your most-crawled pages — recent posts, high-traffic evergreens, site-wide templates. This is the highest-leverage, lowest-effort fix, and it addresses both the discovery and the importance signal at once.
  2. Make the page genuinely better than what's indexed. Add the information the current top results lack: original data, real examples, actual experience. Rewriting the same content "but nicer" doesn't change the evaluation.
  3. Consolidate. Three thin posts on one topic → one strong post + two 301s. Fewer, stronger URLs beat more, weaker ones for indexing every time.
  4. Prune the junk. Noindex or delete tag archives, empty categories, and zombie pages nobody visits. Reducing the low-value share of your domain raises the prior for everything else.
  5. Then — and only then — request indexing. After a real change, Request Indexing in Search Console shortens the wait for re-evaluation. Before a real change, it's a no-op.

What doesn't work

Fixing this at scale on WordPress

The fix everyone agrees on — internal links from frequently-crawled pages — is tedious to maintain by hand: which pages are not indexed today, and who links to them?

IndexFixer automates exactly this loop. It checks the real Google index status of every URL on your site daily (via the official URL Inspection API, read-only), and its widget automatically lists your not-indexed posts as normal internal links in a "You may also like" box — on pages Googlebot already crawls. When a page gets indexed, it drops out of the widget and the next not-indexed page takes its place. You see the whole picture in your WordPress dashboard: per-URL verdicts, coverage states, last crawl dates, and a history of every status change.

See how IndexFixer works →

6. Monitoring at scale

A single URL Inspection in Search Console tells you about one page, today. The problem is dynamic: pages drop out of the index (yes, indexed pages regularly fall out — day-to-day fluctuation is normal), new posts sit unindexed for weeks, and nothing notifies you. Whatever tooling you use, monitor three things:

Google's URL Inspection API allows 2,000 checks per day per property, which is enough to keep a full daily picture of most sites — it just needs automation to be practical.

7. FAQ

How long does "Crawled — currently not indexed" last?

Anywhere from days to forever. Pages sometimes get indexed on a later crawl with zero changes; others stay out permanently. If a page has been stuck 4–6 weeks and its last crawl date is stale, waiting is no longer a strategy — change the content or the links pointing to it.

Is it a penalty?

No. It's not a manual action and doesn't affect the rest of your site directly. It's a per-page quality/value judgment. (A large share of your site in this bucket is a site-quality signal, though.)

Does clicking Request Indexing fix it?

Rarely on its own. It re-queues the crawl but doesn't change the evaluation that excluded the page. Use it after improving the page or its internal links.

Can internal links really get a page indexed?

Yes — in our experience it's the most reliable single lever. Links from frequently-crawled pages pass both discovery and importance. It's the entire mechanism behind IndexFixer's widget.

Is this caused by AI content?

Not per se. Google indexes plenty of AI-assisted content. What fails is content — human or AI — that adds no information to what's already indexed. AI just makes it easier to produce that kind of content at volume.

Related reading: IndexFixer setup guide · IndexFixer for WordPress