Crawled - currently not indexed: why Google skips your pages and how to fix it

"Crawled currently not indexed" in Google Search Console means Googlebot fetched the page, looked at it, and decided not to add it to the index for now. It is not a penalty and not a technical error: it is a judgment call, and most of the time it comes down to the page not adding enough over pages Google already has, duplicating another URL, or being too weakly connected to the rest of your site to look important. The fix is rarely "request indexing again". It is deciding which pages deserve to be indexed, then making those pages clearly worth it.

Quick answer. First check whether the URL should be indexed at all; many should not. For the ones that should: confirm with URL Inspection that the page returns 200, is not noindexed, declares the right canonical and renders its main content. Then fix the cause in this order: remove or consolidate thin and duplicate URLs, fix canonical and rendering problems, improve the content so it offers something the indexed pages do not, link to it from strong pages on your site, and keep only indexable URLs in your sitemap. Request indexing for a few key pages after real changes, then give Google a few weeks.

What "Crawled - currently not indexed" actually means

Google's Page indexing report documentation (opens in a new tab) describes it in two lines: "The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling."

So crawling worked (robots.txt and server access are not the problem for this URL), Google chose not to index the page, and resubmitting the same page gets the same judgment.

Keep the scale in perspective too. The same help page says "Most sites have at least a few unindexed pages, but all of your important pages should be indexed," and "Don't expect every URL on your site to be indexed." A few hundred tag archives in this bucket on a blog is normal. Your main service pages in this bucket is a problem.

Crawled vs discovered currently not indexed

The two statuses sit at different stages of the same pipeline, and they point to different causes.

On a small site with a fast server, "discovered currently not indexed" is rarely about overload in the literal sense. In my experience it usually means Google does not yet see enough reason to spend a crawl on that URL: it is new, poorly linked, or one of many similar pages. On a large site, it is often a genuine crawl budget issue, covered further down.

Why is Google not indexing my pages? The real causes

When I audit a site with a large "Crawled - currently not indexed" count, the causes almost always fall into one of these groups. Usually more than one applies.

1. The page adds little over pages Google already indexed

This is the most common cause. Typical examples: service pages for ten cities where only the city name changes, blog posts that restate the top results with no example or experience of your own, product pages using the manufacturer's description word for word, and pages with a heading, two sentences and a contact form.

Google's guidance on helpful, people-first content (opens in a new tab) asks whether content provides "original information, reporting, research, or analysis" and "substantial value when compared to other pages in search results." A page that fails that comparison can be crawled forever and never indexed.

2. Duplicates and canonical confusion

If several URLs show the same content, Google picks one canonical and leaves the rest out. Accidental duplicates come from tracking parameters like ?utm_source=, sort and filter parameters, www and non-www or trailing slash variants that both return 200, and print versions.

Exact duplicates usually get their own statuses, such as "Duplicate without user-selected canonical". Near-duplicates that are not identical often land in "Crawled - currently not indexed" instead.

3. Weak internal linking

A URL that exists only in your XML sitemap, with no internal links pointing to it, tells Google you do not consider it important enough to link to. Products only reachable through filters and blog posts that drop off the homepage after a week suffer from this. Internal links are both a discovery path and a signal of importance.

4. Rendering problems

If the main content only appears after JavaScript runs, and that JavaScript fails, times out or depends on a blocked resource, Google sees an almost empty page. Client-side-only apps, APIs that block Googlebot and cookie walls covering the content are the usual suspects. Google can render JavaScript, as its JavaScript SEO basics (opens in a new tab) explain, but every extra step is a place where it can go wrong.

5. Pages that look like errors

A page that says "No products found" while returning a 200 status is a soft 404. Google reports clear cases as "Soft 404", but borderline pages (an almost empty category, a search page with one result) can be excluded under other statuses.

6. Crawl budget on large sites

For most sites, crawl budget is not the issue. Google's crawl budget guide (opens in a new tab) is written for sites with 1 million+ unique pages that change weekly, 10,000+ pages that change daily, or "a large portion of their total URLs classified by Search Console as Discovered - currently not indexed". A store with 2,000 products is almost certainly not limited by crawl budget; a marketplace with millions of filter combinations may well be.

7. The page is simply new

A post published three days ago on a young site may sit in either status for a while. Give new URLs a couple of weeks before treating it as a problem.

How to diagnose a page not indexed in Google Search Console

Here is the workflow I use. It moves from the report, to patterns, to individual URLs, and only then to fixes.

Step 1: export and group the URLs

In Search Console, open Indexing > Pages, click "Crawled - currently not indexed" and export the examples. Switch the filter at the top from "All known pages" to "All submitted pages" or a specific sitemap to see how many excluded URLs are ones you actually asked Google to index.

Then group the URLs by pattern: /tag/, /page/2/, ?sort=, /product/, /blog/. If most of the list is tag archives and filter URLs, you do not have an indexing problem; you have a URL hygiene problem.

Step 2: decide which URLs should be indexed at all

Go through each pattern and answer one question: would a searcher be glad to land on this page from Google?

This step alone often resolves most of the count, because it changes the question from "how do I get these indexed" to "which of these matter".

Step 3: inspect a sample with URL Inspection

Take five to ten URLs from each pattern you want indexed and paste them into the URL Inspection bar. In the indexed result, look at:

• Discovery: which sitemaps list the URL and the referring page Google found it on. No referring page usually means no internal links.
• Crawl: last crawl date, whether it was crawled as Googlebot smartphone, "Crawl allowed?" and "Page fetch".
• Indexing allowed?: a "No" here means a noindex you may not know about, often from a plugin or an X-Robots-Tag header.
• User-declared canonical vs Google-selected canonical: if they differ, Google thinks another URL is the better version. Google's help notes "There is no guarantee that Google will choose your preferred canonical."

Step 4: run a live test and look at the rendered page

Click Test live URL, then View tested page. Check that your main content is in the rendered HTML, look at the screenshot (available only in a live test), and open "More info" for blocked resources and JavaScript errors. A cookie wall, empty shell or spinner in the screenshot means a rendering problem.

Step 5: compare with what Google did index

Search for the topic of the page and open the top results. Be honest about what they have that your page lacks: a worked example, a table, original photos, prices, steps, a clear answer up front. If your page is a shorter version of what already ranks, that is the reason, and no technical fix will change it.

Crawled - currently not indexed fix: what to do, in priority order

The early steps are cheap and often solve the bulk of the problem; the later ones take real effort, so spend it only on pages that deserve it.

1. Remove or consolidate URLs that should not be indexed. Add noindex to utility pages, canonicalize parameter variants, return 404 or 410 for pages with no reason to exist, and 301 redirect thin duplicates into the strongest version.
2. Fix technical conflicts. Each indexable page should return 200, carry a self-referencing canonical, and use that exact URL in the sitemap and in internal links. Return a real 404 for empty pages.
3. Fix rendering. Put the main content in the server-rendered HTML where you can, and make sure scripts and API calls do not fail for Googlebot.
4. Improve the content where it falls short. Add what the top results lack: your own data, a real example, a comparison table, clear steps, answers to the follow-up questions. Merge two weak posts on the same topic into one strong one. My on-page SEO checklist covers the page elements; the substance has to come from you.
5. Strengthen internal links. Link to the page from relevant, well-linked pages (homepage, hub or category pages, related articles) with descriptive anchor text.
6. Clean up the sitemap. List only canonical, indexable URLs that return 200, with accurate lastmod values.
7. Then ask Google to look again. Use Request indexing in URL Inspection for a handful of your most important changed pages, and click Validate fix in the Page indexing report once you have fixed a pattern. Google says validation "typically takes up to about two weeks, but in some cases can take much longer."

If you would rather have someone work through this with your data, a technical SEO audit covers steps 1 to 3 and 6, and on-page SEO work covers 4 and 5.

How to fix discovered currently not indexed on large sites

When the "Discovered" count is large, the work shifts from individual pages to how much of your site Google is willing and able to crawl.

• Check server health. In Settings > Crawl stats, look at average response time and server errors. Slow responses and 5xx errors reduce how much Google crawls.
• Shrink the URL space. Faceted navigation can generate millions of color, size and price combinations. Block crawl traps in robots.txt and stop linking to combinations you do not want crawled.
• Do not use noindex to save crawl budget. Google's guide is explicit that it "will still request, but then drop the page when it sees a noindex meta tag or header." Use robots.txt for URLs you never want crawled.
• Fix soft 404s and redirect chains. Google says soft 404 pages "will continue to be crawled, and waste your budget," and that long redirect chains "have a negative effect on crawling."
• Keep sitemaps current. Split them by type so you can see the indexing rate per section.

What not to do

Some popular "fixes" waste time, and a few can do damage.

• Do not mass-click Request indexing. There is a daily quota, and Google's recrawl documentation (opens in a new tab) says "requesting a recrawl multiple times for the same URL won't get it crawled any faster" and "Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all." Use it after real changes, on a few pages.
• Do not use the Indexing API for ordinary pages. Google's Indexing API documentation (opens in a new tab) states it "can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject." It also says submissions "undergo rigorous spam detection" and that abuse can get access revoked. "Instant indexing" plugins that push blog posts or product pages through it are using it outside its stated purpose.
• Do not change dates without changing content. It does not make the page more useful, and it makes your lastmod values less trustworthy.
• Do not block a page in robots.txt to "reset" it. A blocked page cannot be crawled, so Google never sees your improvements.
• Do not publish more of the same. If a hundred similar pages are not indexed, a hundred more will not help. That is how sites drift toward scaled content abuse; my programmatic SEO guide covers where that line sits.
• Do not delete every unindexed page blindly. Some are fine as they are, some need improving, some need merging. Decide per pattern.

How long after fixing will pages get indexed?

There is no fixed number. Google's recrawl page says "Crawling can take anywhere from a few days to a few weeks." In practice, give fixed pages two to four weeks, and watch the trend in the Page indexing report rather than individual URLs. If the indexed count for a sitemap rises over a month or two, the fixes are working.

If you are launching a new site and want to avoid most of this from day one, my website launch SEO checklist covers the setup.

Frequently asked questions

Is "crawled currently not indexed" bad for my site?

Not by itself. It is a status, not a penalty, and almost every site has some URLs in it. It matters when pages you need to rank, such as service, product or key article pages, sit in that bucket for weeks.

How do I fix "page not indexed" in Google Search Console?

Open the Page indexing report, find the reason listed for the URL, and inspect it with URL Inspection. Each reason has a different fix: "Excluded by noindex tag" means removing a noindex, "Duplicate" statuses mean fixing canonicals, and "Crawled - currently not indexed" usually means improving or consolidating the content and its internal links.

Why is Google not indexing my pages on a new website?

On a new site, the usual reasons are that Google has not found the pages yet, has found them but not crawled them, or sees little reason to prioritize them. Verify the site in Search Console, submit a clean sitemap, link to every important page from your navigation or homepage, and publish fewer, more complete pages rather than many thin ones.

Will Request indexing fix crawled currently not indexed?

Only if the page has changed in a meaningful way since Google last crawled it. Requesting indexing for an unchanged page gets it recrawled at best, and the same page gets the same decision. Fix the cause first, then request indexing once.

If your important pages are stuck in "Crawled - currently not indexed" and you cannot see why, I can review the report with you as part of a technical SEO audit and tell you which pages to fix, merge or let go.