„Crawled - currently not indexed“ means: Google visited the page and decided not to include it in the index. Not a bug, not a server problem, not a broken sitemap. It's simply a ranking decision for now.
This is exactly why the usual guides with their ten technical fixes rarely help. Anyone who checks the status of canonicals, resubmits the sitemap, and requests indexing at this stage is treating a symptom whose cause lies elsewhere. What the status actually says, when action is necessary, and when waiting is the right response: Let's dive in.
What the status means - and what it doesn't
Crawling and indexing are two separate steps. Googlebot fetches a URL, that is crawling. Whether the page is then added to the index is decided by a separate evaluation process. With „Crawled - currently not indexed,“ step one has happened, and step two has not.
How Google itself views this, John Mueller and Martin Splitt discussed in an episode of the Google podcast Search Off the Record explained. In essence: Google knows the page, has looked at it, and will come back when its own systems are ready. From Google's perspective, the status is not an error state that the website operator needs to technically fix. Mueller says it quite directly in the podcast: One should not treat these situations as a technical problem to be fixed.
This contradicts the reflex triggered by Search Console's error appearance. Red status means something must be broken. But usually, it isn't.
Found vs. Crawled – Not Currently Indexed: The Difference
The Search Console has two similarly sounding statuses that mean different things:
| Status | What happened | Typical cause |
|---|---|---|
| Found - not currently indexed | Google knows the URL but hasn't crawled it yet | Prioritization, crawl budget, very new content |
| Crawled – currently not indexed | Google fetched the URL and did not index it | Review: Content, Redundancy, Site Quality |
„Found“ means: Google wasn't there yet. This is normal for new websites and newly published areas and often resolves itself. „Crawled“ means: Google was there and decided against it. The second case is the more interesting one, because here an evaluation took place.
Why Google deliberately does not index pages
In the podcast, Mueller names three reasons that cover almost all cases in practice.
First: Doubts about the overall quality of Website. If Google's systems assess a site critically overall, they reduce crawling and indexing. From Google's perspective, it simply isn't worth spending a lot of time on the website. The status of individual URLs is then a symptom of a site-wide signal.
Secondly: Redundancy. There is already enough equivalent content on too many topics. The question Google implicitly asks is not „Is this page good?“ but „What is missing from the index without this page?“ A solidly written article that exists in a similar form thirty times over does not answer this question. This also applies to AI-generated content, but not across the board. Mueller puts it this way in the podcast: You read some pages and think anyone could have written that. Interchangeability is the problem, not the tool.
Third: the overall experience. Google doesn't just evaluate the text itself, but how users experience the page. A good article buried under ad banners, cookie layers, and 800 words of filler before the actual content isn't a good page from this perspective. Users don't have a reading mode that just shows the main text. Google factors in the rest.
Read the pattern instead of fixing pages
The most important perspective shift comes from the Search Console team itself: the indexing report is not a to-do list or an inventory that must be entirely green. It's a change detector. The right question isn't „Is page X indexed?“, but „Is the website behaving as I expect?“.
Practically, this means: pay attention to patterns rather than individual pages.
The trend line first. A brief spike in non-indexed pages that flattens out again is usually a server hiccup or a data delay. A line that rises steeply and stays up warrants analysis. A consistently high but stable number is often simply the website's normal state.
Then the distribution. If the status affects a specific template, such as all product variant pages or all tag archives, the cause is within your own sphere of influence: thin content, near-duplicates, generated pages with no intrinsic value. If it affects the entire website or everything behind a CDN, this indicates an infrastructure problem.
With this interpretation, the path from „300 pages not indexed, panic“ leads to a diagnosis in twenty minutes. Click on example URLs, check two or three of them, name the patterns. The result is often: everything is fine, the change was expected.
When Action Is Needed: The Real Problem Cases
There are cases where a technical problem is behind the status. However, these have little to do with standard checklists.
The most common: Bot protection at the CDN or host. Some providers activate protection mechanisms when crawl traffic is high, which then also block Googlebot. Instead of a clean 503 („come back later“), the server returns 403 or 404. The indexing report shows this as a sudden increase in errors or excluded pages that were previously indexed without issues.
The most insidious: Soft errors. A bot interstitial („Are you human?“) is delivered with status code 200. For Google, this is a normal page, so it will be indexed – and replace the actual content. Because the same query page appears on many URLs, sometimes even across domains with the same CDN provider, Google can, in extreme cases, choose a foreign page as canonical. In Search Console, this appears as deduplication in favor of some other URL. Visitors notice nothing of this; the interstitial only appears for bots. Diagnosis runs via the URL inspection tool in Search Console: there you can see what Googlebot actually receives.
If such a problem is found and fixed with the host or CDN, the „Mark as fixed“ button is used effectively. Google then checks a sample of the reported URLs and, if successful, initiates a faster recrawl of the rest. For everything else, especially for „Crawled - currently not indexed“ without a technical cause, the button has no effect. There is nothing technical for Google to verify.
404 Errors in Search Console: Often Not a Problem
A related misconception concerns 404 errors in Search Console. They are marked in red, they are called errors, so you want to get rid of them. However, many 404s are exactly the right behavior: If you remove content from the website, you want the old URLs to deliver an error code. After a relaunch with clean redirects, an increase in „Page with redirect“ also belongs to the expected picture. Absence would be the warning sign.
It becomes problematic when supervisors interpret Search Console as a traffic light and set „everything green“ as a target. Then teams optimize error counts downwards, which aren't errors at all. Who needs to have this discussion: The distinction that matters is 404 (expected, correct) versus soft 404 (page exists but returns error content or the mentioned interstitial). Only the second case costs visibility.
The Ratio Myth: How Many Pages Need to Be Indexed?
A number that regularly causes concern in the indexing report: the ratio of indexed to non-indexed pages. „Only 20 percent of my pages are in the index, Google thinks my website is bad.“
This ratio is not a measure of quality. There is no target value. Websites with a million unindexed pages and half a million indexed pages perform best. The most prominent example is Google itself: according to Mueller in the podcast, around five percent of the pages in its own developer documentation are.
The question that matters: Are the pages indexed that bring clicks and business in the performance report? If so, the ratio is noise.
The difficult part: honestly assessing one's own quality
The case remains where many important pages are permanently stuck in status and technically nothing can be found. Then the uncomfortable answer is: It is a quality issue. And this can hardly be answered by looking at one's own website, because everyone thinks their content is good. After all, they wrote it the way they thought was right.
[INSERT EXAMPLE FROM YOUR PRACTICE – Placeholder draft, please replace with a real case:] An example from a project: A machine manufacturer had built up around 400 glossary and guide pages over several years, two-thirds of which were in the status „Crawled – currently not indexed.“ Technically flawless. The finding after content analysis: The texts explained basic concepts that Wikipedia and three competitors covered in similar depth, without any reference to their own applications. After consolidation to around 150 pages with practical relevance from their own machine portfolio, the indexing rate of the remaining pages increased significantly within three months, as did the clicks.
The mechanism behind it: Less, but self-contained content answers Google's redundancy question. What is missing from the index without this page? For generic foundational content: nothing. For a page with measurement data, use cases, or empirical values that only this company has: quite a bit.
Frequently Asked Questions
How long does it take for Google to index the page?
There is no timeframe for this. Google phrases it openly: the systems will check again when they are ready. This can take days or months. For individual pages, waiting is usually the right strategy, while for widespread occurrences, root cause analysis is worthwhile.
Does requesting indexing via URL inspection help?
For individual, important pages: worth a try, the request will trigger a re-crawl. For hundreds of pages: no. The request does not change the assessment that led to the status.
Is „Crawled - currently not indexed“ a ranking issue?
Not directly. An unindexed page cannot rank, but the status does not negatively affect the rankings of indexed pages. However, as a site-wide pattern, it can indicate quality signals that also harm the rest of the website.
Does the status disappear on its own?
Often, yes, especially with new websites and fresh content. If it remains on business-relevant pages for months, that's an invitation to critically examine the content and context of those pages.
The short version
The indexing report is a change detector, not a bug list. If you notice anomalies, first check the trend line and patterns, then example URLs. Technical causes like bot protection and soft errors are rare, but serious, and need to be fixed. In all other cases, the status poses a question that no tool can answer: What does this page offer that the index doesn't already have?
This is precisely where internal reflection regularly fails. How we proceed with the assessment when large parts of a website are not indexed is explained in [LINK: SEOPerformance page Audit-Article].
