murattunalı.
Reading

What “Crawled – currently not indexed” means and what to do.

“Crawled - currently not indexed” is a Search Console status reporting that Google visited and read a page but chose not to add it to the index. It is not a technical error: according to Google, the page may or may not be indexed in the future, and there is no need to resubmit it. The work to do is to ask honestly whether the page carries an answer worth indexing.

This status appears in Search Console’s page indexing report, in the table that lists why pages are not indexed. Clicking the row opens the list of addresses in that state. Next to the row, the source reads “Google systems”: in other words, the obstacle comes not from a setting on the site but from Google’s own assessment.

First, one distinction is needed: this row is not a crawl error. The server responded, the page opened, Google read the content. Not indexing is a decision, and the reasoning behind that decision is not explained page by page. This guide covers the possible reasons for that decision, how it played out in this site’s own history and what can be done. If you would like to read together how widespread the problem is on your site, SEO consulting starts with this report.

What is the difference between “Discovered” and “Crawled”?

The report has two rows that look very similar and mean different things. “Discovered - currently not indexed” says Google knows the address but has not visited it yet. According to Google’s explanation, this is mostly crawling being postponed so as not to overload the site; it is a queue state.

“Crawled - currently not indexed” is one step further: Google has visited the page, read it and chosen not to keep it. The first can be resolved by waiting; the second usually points to a question about the page itself.

Why does Google not index these pages?

Google does not explain the reason for every page; the list below is not a diagnosis but a checklist. Reading the page against these questions one by one often reveals the cause:

  • Is the content thin? A service page of a few sentences, a category page that says nothing beyond its title.
  • Is the page nearly identical to another page? Pages where only the city name or the product code changes can be treated as duplicates; the canonical address declares which one is the original.
  • Does the page receive links within the site? A page that receives no link from any page is as good as declared unimportant by the site itself.
  • Does the page answer a search? Tag archives, filter combinations and internal search result pages answer no question anyone is asking.
  • Is the site or the page very new? According to Google, these pages may or may not be indexed in the future.

Why did “crawled, not indexed” appear on this site?

First-hand evidence: in the Search Console reading on 22.08.2026, 13 pages of this site were in the “Crawled - currently not indexed” row. That day’s export was a summary and did not list which 13 pages they were. But our own measurement pointed to the same place: that day, none of the 58 pages on the site exceeded 800 words. The verdict Google gave from outside the site and the measurement taken from inside it said the same thing: the pages were thin.

The response had two layers. The first was content: the site’s later guide pages were written deep enough to answer a question in full. The second was discipline: for guide pages, anything under 800 words became a threshold rejected by the pre-release test. So a thin guide can no longer go live; it is not left to anyone’s attention, it is enforced in code.

A note of honesty: Google does not publish a word-count threshold. 800 is our own threshold, a floor set according to that day’s diagnosis. Word count is not quality itself but the most easily measured symptom of thin content. An empty 800-word text can stay out of the index as well.

The current state: in the 18–20.09.2026 reading, 461 of the site’s pages are in the index and the “crawled, not indexed” row holds 25 pages. The number rose from 13 to 25, but over the same period the number of pages on the site grew roughly eightfold. Someone looking at the absolute number sees a deterioration; someone reading it together with the page count sees that the problem has largely closed in proportional terms. Which pages the remaining 25 are is the work of the next round.

Crawled but not indexed is not an error but a verdict; what changes the verdict is not resubmission but the page itself.

What should you do about “crawled, not indexed”?

  • Open the row and export the list; see which pages are affected.
  • Ask each page one question: does this page answer a question someone is searching for?
  • If it does not, there are three paths: enrich the page, merge it with similar pages or deliberately leave it out of the index.
  • If it is a copy of another page, declare which one is the original with a canonical address.
  • If it is an important page, link to it from within the site; from related pages and from the main navigation.
  • After the fix, start validation of the fix in the report and wait for the result.

The last option in the third step should not be underestimated. Not every page needs to be in the index. Deliberately keeping out pages that should never reach a search result directs Google’s attention to the pages that really matter. The tool for this is the noindex tag.

Does resubmitting the page help?

Usually not. Google writes clearly that there is no need to resubmit an address in this state for recrawling. Requesting a crawl from the URL Inspection tool is possible, but Google states that this request has a daily limit and does not guarantee indexing. Resubmitting an unchanged page is asking for the same verdict again.

The same applies to tools that speed up discovery. Notification protocols such as IndexNow tell search engines that a page has changed; but Google does not support this protocol, and the protocol does not guarantee indexing on any engine. Knocking on the door earlier does not get you let in. If the page has changed, Google will reassess it on the next crawl anyway; if it has not, no notification changes the verdict.

Can a page in the sitemap also be in this row?

It can; this is a point where the two reports get confused. A sitemap tells Google “these pages exist”; it does not say “index these pages.” Google writes clearly that it does not guarantee that every address in the sitemap will be crawled or indexed. The sitemap makes discovery easier; it does not change the verdict.

Still, the relationship between the two lists is a diagnostic tool. Putting only the pages you want to see in the index into the sitemap makes the “Crawled - currently not indexed” list easier to read: every page that is in the sitemap and shows up in this list is a page you have declared important but Google is not convinced by. We explained how the sitemap is built in the sitemap guide.

How long should you wait after a fix?

Google gives no timeline for this. The fixed page is reassessed on the next crawl; the validation started in the report also takes time to complete. The most useful thing to do in the meantime is to write down the change and its date. When reading the result, comparing it with the previous state of the same report is the only reliable way to tell whether a change worked.

When should this row be treated as an alarm?

In two cases. First, if the list contains the site’s important pages: service pages, product pages, the contact page. These pages staying out of the index is a direct loss of business and should be looked at first. Second, if the number in the row grows faster than the site itself: if a significant share of newly published pages is not getting indexed, there is a quality problem in the publishing process itself.

Apart from that, it is normal for a few pages to sit in this row; no site has all of its pages in the index. The right question is not “why is this row not zero” but “should the pages in this row be in the index.” You can find the other reasons that keep a site as a whole from appearing on Google in the nine-check guide, and where the reports are located in the Search Console guide.

If you want to find out together why your site doesn’t show up on Google, SEO consulting audits every layer from crawling to indexing and makes the fix in the source code.

How to use Visibility check

SOURCES