serkankaya.
Türkçe sürüm
Let’s work together ↗

Crawled - Currently Not Indexed: How to Fix Both Statuses

How to fix Crawled - currently not indexed and Discovered - currently not indexed in Search Console: causes, a diagnosis order and practical fixes.

A not indexed error is a Search Console status showing that Google knows a URL but has not added it to its search index. It most often appears in two forms: “Crawled - currently not indexed” and “Discovered - currently not indexed”. In the first, Google has seen the page and chosen not to index it; in the second, it has not crawled the page yet. The fix is to identify which status you have first, then correct the cause specific to that status.

In this post I cover the two statuses separately and give a diagnosis order for each. Coming from a software development background, I prefer to read these errors as template or server behavior rather than as single-URL problems. I explained the general framework of crawling and indexing in my what is technical SEO post and the report itself in the how to use Google Search Console guide.

What does a not indexed error mean?

A not indexed error means the page is not a candidate to appear in Google Search results. Google Search has three stages: crawling, indexing and serving. According to Google’s guide, not every page makes it through all three stages, and indexing isn’t guaranteed.[2] The same guide lists low content quality, robots meta rules and the design of the website among common indexing issues.[2]

Discovery Crawling Indexing Appearing in results
Discovered shows URLs stuck at the second stage, Crawled shows URLs stuck at the third.

Search Console lists these statuses in gray in the “Page indexing” report, under “Why pages aren’t indexed”. Each row is a separate reason. Some of them are your own deliberate decisions: a page you set to noindex, an old address you redirected or a duplicate you pointed to another page with a canonical tag. These should not be in the index and do not need fixing.

The real problem is a page that should earn search traffic showing up on this list. That is why I always enter the report with one question: How many of the excluded URLs are pages I actually want to rank?

What is the difference between Crawled and Discovered?

With Crawled, Google visited the page but did not index it; with Discovered, Google knows the URL but has not visited it yet. This difference decides where the diagnosis starts. In one case the problem is the page itself; in the other it is Google’s priority for reaching the page.

Crawled - currently not indexed

  • Googlebot downloaded the page
  • Last crawl date is filled in the report
  • The decision is on the content and signal side
  • First check: originality, duplicates, internal links

Discovered - currently not indexed

  • URL found but not crawled
  • Last crawl date is empty in the report
  • The bottleneck is on the crawling side
  • First check: server, URL crowding, internal links
Both statuses appear in the same report but get stuck at different stages.

Google’s help page adds a clear note for the Crawled status: Google doesn’t index all pages across the web, so this message is common on many sites and doesn’t necessarily indicate an issue that needs attention.[1] For the Discovered status, Google’s explanation is this: Google wanted to crawl the URL, but expected the crawl to overload the site and rescheduled it.[1] That is also why the last crawl date is empty in the report.

How do you fix Crawled - currently not indexed?

Short answer

How do you fix Crawled - currently not indexed?

Crawled - currently not indexed is fixed by finding out why the page was not considered worth indexing and correcting it. First you separate the important pages. Then you use the live test to check how Google sees the page, its canonical selection and how the content differs from similar pages. As a last step you add internal links and request a recrawl.

  1. Export the affected URL list and separate the important pages.
  2. Run a live test in the URL Inspection tool and check the rendered HTML.
  3. Compare the user-declared canonical with the Google-selected canonical.
  4. Add information that sets the content apart from similar pages, or merge the duplicates.
  5. Give the page contextual internal links from related pages.
  6. After the fix, request indexing and monitor the report.

In this status Google has seen the page, so technical access is usually not the problem. The decision is about the value the page would add to the index. These are the main causes I look at during diagnosis.

Thin content and template weight

Thin content is page content that adds no original information for the user because it is short or template-heavy. If the menu, footer and sidebar make up most of the page and the main content is only a few sentences, Google may crawl the page but not index it. Empty tag pages, single-product categories and auto-generated city pages often end up in this status.

The fix is not adding words but giving the page a reason to exist. Google’s helpful content guide also asks whether content provides original information, analysis or value for the user. I covered this approach in detail in my how to write SEO-friendly content post. If the page truly doesn’t answer a search intent on its own, the right move is to merge it into a stronger page.

Duplicate and near-duplicate pages

Google selects one page from a set of identical or very similar pages as the canonical and generally doesn’t show the others in the index.[5] Product variants, list pages with sort parameters and language versions that were not translated well enough can be left out for this reason. Sometimes this shows up in the “duplicate” rows instead of Crawled, and sometimes it lands directly in the Crawled row.

Comparing the “User-declared canonical” and “Google-selected canonical” fields in the URL Inspection tool is the first step here. According to Google’s canonical guide, rel="canonical", redirects and sitemaps are each signals, and they need to point to the same address.[5] If the canonical points to one address, internal links to another and the sitemap to a third, Google makes its own choice.

A page that gets no links from anywhere on the site, or that only exists in the sitemap, signals to Google that it is unimportant. Such pages are called orphan pages. A contextual, descriptive link from the main category, a service page or related posts clarifies the page’s place on the site. On large sites I use the category tree approach from the ecommerce site architecture post to reduce click depth.

Rendering and technical quality issues

If the page’s main content loads later through JavaScript, the HTML Google sees may be empty or incomplete. That is why the “View tested page” screen and the crawled HTML in the URL Inspection live test are critical information. If the content is missing from the screenshot, the problem is in rendering, not in the content. Blocked CSS and JavaScript files also appear on the same screen.

How do you fix Discovered - currently not indexed?

Discovered - currently not indexed is fixed by removing the capacity and priority issues that make Google postpone the crawl. In this status Google has not seen the page’s content yet. That is why improving the content alone is not enough; you need to make it easier for Google to reach the page.

Google’s crawl budget guide clearly lists who should take this topic seriously: large sites with more than 1 million unique pages whose content changes about weekly, sites with more than 10,000 pages whose content changes daily, and sites with a large portion of their URLs classified as Discovered.[3] Google also notes that these numbers are a rough estimate, not exact thresholds.[3] If the Discovered row is large on a small site, the problem is usually the server or URL crowding.

Server response time and error codes

Google adjusts the crawl rate to the load the server can handle. When the server responds slowly or returns 5xx errors, Google slows down crawling.[3] The Crawl stats report under Settings in Search Console shows the average response time and the distribution of response codes. If spikes in this report line up with the dates the Discovered row grew, you have found the cause. I covered the user side of page speed separately in the improve Core Web Vitals post.

Crowding from low-value URLs

Filter combinations, session parameters, infinite calendar pages and internal search results pull Google’s crawl resources away from important pages. Google’s guide recommends using robots.txt for URLs you don’t want crawled and consolidating duplicates.[3] Noindex is not a solution on its own here, because Google still has to crawl the page to see the noindex.

Sitemap and discovery signals

A sitemap should only contain the canonical URLs you want in the index. Keeping redirected, noindexed or 404 addresses in the sitemap sends Google conflicting signals. Updating the lastmod value only when content actually changes also keeps the sitemap trustworthy. To speed up discovery on Bing and Yandex, you can also use the IndexNow protocol; Google does not support it.

Which not indexed statuses don’t need fixing?

Not indexed statuses that result from a deliberate decision don’t need fixing. Google’s help page explicitly describes several rows as working as intended.[1] Treating these rows as errors takes time away from the real problems.

Status in the reportWhen is it normal?When should you look?
Page with redirectWhen the old address moved to a new one with a 301When the target page is not indexed either
Alternate page with proper canonical tagWhen the page points to the correct canonicalWhen the canonical page is not indexed
Excluded by ‘noindex’ tagOn thank-you, cart and account pagesWhen it appears on a sales or service page
Not found (404)When the page was removed without a replacementWhen the page moved; a 301 is needed
Duplicate without user-selected canonicalOn parameter or variant duplicatesWhen Google picked the wrong page

Google states that 404 responses are not a problem if the page was removed without any replacement, and recommends a 301 redirect if the page moved.[1] For the noindex row, the first question is whether the directive was set on purpose. A noindex carried over from a staging environment to production can silently remove important pages from the index.

When does requesting indexing help?

Requesting indexing helps when you have fixed the issue on the page and want Google to look at it again. A request sent before the issue is fixed only gets you the same result sooner. According to Google’s recrawl guide, there is a quota for requests, and requesting a recrawl multiple times for the same URL won’t get it crawled any faster.[4]

The same guide says crawling can take anywhere from a few days to a few weeks and that requesting a crawl does not guarantee inclusion in search results.[4] If you fixed many URLs, submitting an updated sitemap is better than individual requests. After solving a bulk issue, you can have the related row rechecked with the “Validate fix” button in the Page indexing report.[1]

Checklist for a not indexed error

Order matters when fixing a not indexed error, because each step depends on the result of the previous one. I run through the list below from start to finish when an important group of pages is left out of the index.

Not indexed error diagnosis list0/9

Conclusion

A not indexed error is not a single problem but the shared name for URLs stuck at two different stages. With Crawled, Google has seen the page and not found it valuable; you need to fix content, duplicate and internal link signals. With Discovered, Google has not reached the page yet; you need to fix server capacity, URL crowding and discovery signals. In both cases, requesting indexing is the last step, not the first.

As a next step, open the Page indexing report in Search Console, export the sample lists for both rows and group them by URL pattern. If you want to audit your whole technical setup for issues like these, my SEO services page explains how I work, and you can read about my background on the about page.

Key terms

Crawled - currently not indexed
Crawled - currently not indexed is the Search Console status showing that Googlebot crawled a page but Google did not add it to the index. Because Google doesn't index every page, it appears on many sites; for important pages, check content originality, duplicate signals and internal links.
Discovered - currently not indexed
Discovered - currently not indexed is the Search Console status showing that Google found a URL but has not crawled it yet. According to Google, the crawl was usually rescheduled because it was expected to overload the site, which is why the last crawl date is empty in the report.
Thin content
Thin content is page content that adds no original information or value for the user because it is very short, template-heavy or a repeat of other pages. Google may crawl such pages and still choose not to index them.

Frequently asked questions

What does Crawled - currently not indexed mean?

This status means Googlebot visited the page but Google decided not to add it to its index. According to Google's help page, Google doesn't index every page on the web, so the message appears on many sites. If it shows up on an important page, check content originality, duplicate signals and internal link support.

Why does Discovered - currently not indexed happen?

Google has found the URL through a link or a sitemap but has not crawled it yet. According to Google, the typical reason is that the crawl was rescheduled because it was expected to overload the site. Slow server responses, a crowd of low-value URLs and weak internal links make this status grow.

Does requesting indexing fix the problem?

Not on its own. A request in the URL Inspection tool asks Google to recrawl the page, but it does not guarantee indexing. According to Google, requesting a recrawl multiple times for the same URL won't get it crawled any faster, so the reason the page was left out must be fixed first.

How long does it take for a non-indexed page to get indexed?

There is no fixed time. According to Google's recrawl guide, crawling can take anywhere from a few days to a few weeks. After a fix, monitor the process with the URL Inspection tool and the Page indexing report.

Is every non-indexed page a problem?

No. Redirected old URLs, pages with noindex, parameter duplicates and URLs pointing to another page with a canonical tag should not be in the index anyway. The real problem is an important page that should earn search traffic being left out.

Sources

  1. Search Console Help: Page indexing report
  2. Google Search Central: In-depth guide to how Google Search works
  3. Google Search Central: Crawl budget management for large sites
  4. Google Search Central: Ask Google to recrawl your URLs
  5. Google Search Central: How to specify a canonical URL