Fix

“Crawled – currently not indexed”: causes and fixes

It is the most frustrating status in Search Console: Google read your page… and decided not to index it. The good news: it is not a penalty, and it is often reversible. Here is why it happens and what to do, in order.

What “Crawled – currently not indexed” means

Googlebot crawled the page (downloaded and read it), but Google chose not to add it to its index for now. According to Google's documentation, the page “may or may not be indexed in the future”. It is neither a technical error nor a penalty: it is a judgment call. At this point, Google thinks the page does not add enough to deserve a place in the index.

How it differs from “Discovered – currently not indexed”

Discovered, not indexedCrawled, not indexed
Google knows the URLYesYes
Google read the pageNo, not yetYes
Usual causeCrawl budget, slow server, too many URLsQuality or usefulness judged too low, duplicates
PriorityGet the page crawledImprove the page, then get it recrawled

The most common causes

  • Thin content or too close to other pages: short posts, product pages copied from the supplier, pages repeating what already exists elsewhere on the site.
  • Weak internal linking: the page is only linked from the sitemap or a deep archive. To Google, a page you do not highlight matters little.
  • Young or little-known site: Google indexes proven sites first. New sites see many pages left out.
  • Too many low-value pages: tags, date or author archives, internal search results, WooCommerce filters. They dilute Google's attention.
  • Conflicting signals: canonical tag pointing elsewhere, page missing from the sitemap, content loaded only with JavaScript.

Fixing it, step by step

  1. Check the technical side first. Inspect the URL in Search Console: no noindex, a self-referencing canonical, the page listed in the sitemap.
  2. Make the page essential. Answer the target question better than the current results: concrete information, examples, original images, up-to-date data. Merge posts that repeat each other.
  3. Link to it from your strong pages. Add two or three internal links from pages that already get traffic, with descriptive anchor text.
  4. Trim the site. Set tags, archives and pages with no search value to noindex (a setting in Yoast, Rank Math or SEOPress).
  5. Get the page recrawled. Once improved, request indexing in Search Console (a few requests a day), or submit all fixed pages at once with the plugin's Force Index, which brings Googlebot back.

What not to do

  • Resubmitting the same unchanged page over and over: Google has already read it, its decision will not change.
  • Only changing the publication date: it does not make the page more useful.
  • Publishing more thin pages to make up for it: that is often what caused the problem.

How long should you wait?

After a real improvement and a new crawl, it usually takes a few days to two or three weeks to see the status change in Search Console (its data lags behind). Then check page by page: a list of fixed pages is easy to track from the plugin dashboard, without waiting for the Search Console report.

Frequently asked questions

Is it a Google penalty?

No. It is a decision not to index for now, not a manual action. Real penalties show up in Search Console under “Manual actions”.

Should I delete the affected pages?

Not necessarily. Improve the ones worth keeping, merge the ones that repeat each other (with a 301 redirect) and set to noindex the ones that are not meant to be found on Google.

Is Force Index enough to get a thin page indexed?

It brings Googlebot back, which works well for good pages that were simply overlooked. A page judged too thin may still be refused: improve it first.

From theory to your own pages

Install the free plugin, or try Premium for 30 days without paying.

Free plugin