“Crawled – currently not indexed” means Googlebot fetched your page, read it, and decided not to add it to the index. It is not a crawl error, a robots.txt block, or a server problem — it is a judgement call about quality, duplication, and priority. Fixing it means giving Google a reason to change that judgement, not resubmitting the URL and hoping.
That distinction is the whole game, and it is where most teams waste months. In my experience auditing mid-market sites, the average client arrives having already clicked “Request Indexing” on the same forty URLs three times, convinced something is broken. Nothing is broken. Google looked at those pages and decided they were not worth the storage.
What “Crawled – Currently Not Indexed” Actually Means
Google’s Page Indexing report documentation describes the status plainly: the page was crawled by Google but not indexed, it may or may not be indexed in the future, and there is no need to resubmit the URL for crawling. That last clause is the part everyone ignores, and it is the most important one.
Indexing has never been guaranteed. Google’s Search Essentials are explicit that meeting the technical requirements makes a page eligible for indexing, not entitled to it. The index is a finite, expensive resource and Google allocates it selectively.
The scale of that selectivity is easy to underestimate. Ahrefs’ study of 14 billion pages found that 96.55% of pages get zero organic search traffic from Google. Plenty of those pages are indexed and simply never rank — but the same underlying filter is at work: most published content does not clear the bar for Google to spend resources on it.
So when you see this status, read it as feedback rather than as an error. Google is telling you it crawled the page and found nothing worth adding to a corpus that already contains something similar or better.
Crawled vs Discovered – Currently Not Indexed
These two statuses live next to each other in the Page Indexing report and get treated as the same problem constantly. They are not, and the fixes barely overlap.
Discovered – currently not indexed means Google knows the URL exists, usually from your XML sitemap or an internal link, but has not fetched it yet. This is a crawl capacity signal. It clusters on large sites, slow servers, and mass-generated URL sets, and it points at crawl budget, server response times, and site architecture.
Crawled – currently not indexed means Google spent the crawl and then declined. The technical layer worked. This is a content, duplication, and demand signal.
If you see both at scale, fix the crawl-side issue first — technical SEO work on server response times, sitemap hygiene, and architecture — because a page Google never fetches can’t be evaluated on quality at all. But do not apply crawl-budget fixes to a crawled-not-indexed problem. Speeding up a server does not make a thin page worth indexing.
Seven Real Causes of Crawled Currently Not Indexed
After enough audits, the same causes come up again and again. Work through them in this order.
1. Thin or near-duplicate content. The page technically says something, but says it in the same way as forty other pages on your site or five hundred elsewhere. Location pages, product variants, and service pages built from a template with the town name swapped are the classic offenders.
2. Programmatic pages generated faster than they earn value. Programmatic SEO works, but Google indexes a sample of a large URL set and extrapolates. If the sample is weak, the rest never gets indexed regardless of volume.
3. Weak or absent internal linking. Internal links are how you tell Google which of your own pages matter. A URL reachable only from the XML sitemap is being submitted, not recommended — and Google treats those very differently.
4. Site-level quality dilution. This is the one that surprises people. Index bloat from tag archives, filtered URLs, and abandoned content lowers the average quality of your site, and Google applies that assessment to new pages before they’ve had a chance to prove themselves.
5. Search intent mismatch or no real demand. If nobody is searching for the thing, or the page answers a different question from the one the query implies, Google has no reason to index it. Content that was never grounded in keyword and intent research lands here routinely.
6. Rendering problems on JavaScript-heavy pages. Google crawls the HTML, finds an empty shell, and evaluates what it can see. If the meaningful content only appears after client-side hydration and rendering is slow or fails, Google may index the shell — or nothing at all.
7. Conflicting or historical signals. A canonical tag pointing elsewhere, a leftover noindex from a staging environment, a URL that used to 404, or a sitemap that lists URLs your navigation contradicts. Google resolves the conflict by doing nothing.
A Six-Step Framework to Fix Crawled Currently Not Indexed Pages
Do not work URL by URL. Work in segments, decide deliberately, then act once.
Step 1 — Export and segment. Pull the full crawled-not-indexed export from Search Console and bucket every URL by template: blog posts, service pages, product pages, category pages, tag archives, paginated URLs, filtered variants, utility pages. You are looking for concentration. If 80% of the report is one template, you have one problem, not four hundred.
Step 2 — Decide keep, merge, or remove. For each bucket, make a call before touching content. Keep if the page targets real demand and should rank. Merge if it competes with a stronger page — consolidate and 301. Remove if it exists for users but not for search: noindex it and pull it from your sitemap. Most reports shrink by half at this step, and that is a win, not a loss.
Step 3 — Fix the keepers on substance, not length. Add the specifics only you have: real data, pricing, process detail, first-hand results, original examples. Adding four hundred words of generic framing to a generic page produces a longer generic page. Ask what this URL says that the currently ranking results do not.
Step 4 — Rebuild internal linking. Every page you decided to keep needs at least two or three contextual internal links from already-indexed, reasonably authoritative pages on your site — hub pages, related posts, service pages. This is the single highest-leverage step and it is almost always the one that’s been skipped — and making it part of how the team ships content, rather than a one-off cleanup, is usually where an ongoing SEO engagement pays for itself.
Step 5 — Clean the signals. Confirm each keeper is self-canonicalising, returns a 200, is in the XML sitemap, is not blocked in robots.txt, and renders its main content in the initial HTML. Remove the merged and noindexed URLs from the sitemap so your sitemap and your intent finally agree.
Step 6 — Request indexing once, then measure. Use the URL Inspection tool once per genuinely improved page. Then leave it alone and track the report weekly. Movement in the aggregate count is your signal, not any individual URL.
What Not to Do
Do not mass-request indexing. It does not change the assessment that caused the exclusion, and it burns your daily quota on unchanged pages.
Do not abuse the Indexing API. Google’s documentation restricts it to job posting and broadcast event pages. Using it for general content is unsupported and the results are widely misreported.
Do not pad word counts. Length has never been the criterion. A tight 700-word page with original data gets indexed ahead of a 2,500-word page that says nothing new.
Do not delete the sitemap entry and call it fixed. Removing a URL from your sitemap doesn’t get it indexed — it removes your reporting on the problem, which is the opposite of progress.
Do not treat the whole report as a to-do list. A large chunk of it is usually working exactly as intended.
How Long It Takes and How to Track It
Expect two to eight weeks before you can read the result. Google has to recrawl, re-evaluate the page, and in many cases re-evaluate site-level quality signals that were never about any single URL. Sites with high crawl frequency see movement faster; neglected sites take longer because the recrawl itself is slower.
Track three numbers weekly. First, total URLs in the crawled-not-indexed bucket — it should fall, partly because you noindexed the junk and partly because keepers got indexed. Second, indexed URLs that receive at least one impression, which separates real indexing from technical indexing. Third, impressions and clicks on the specific pages you fixed.
If the count is flat after eight weeks on pages you genuinely improved and linked properly, the problem is site-level rather than page-level, and a full technical SEO audit is the honest next step rather than another round of edits. When a site has accumulated years of index bloat, the fix is usually structural — and that’s a different scope of work than rewriting a dozen pages.
Crawled currently not indexed is not a bug to be cleared. It is Google telling you, per URL, whether a page earned its place — and the sites that treat it as an editorial standard rather than a technical ticket are the ones whose reports actually shrink.
Frequently Asked Questions
What does crawled currently not indexed mean?
It means Googlebot successfully fetched and read your page, then decided not to add it to the index. It is not a crawl error or a technical block. Google’s own documentation describes it as a page that was crawled but not indexed, which may or may not be indexed later, with no need to resubmit the URL.
What is the difference between crawled and discovered currently not indexed?
Discovered means Google knows the URL exists but has not fetched it yet, usually because of crawl capacity, server response times, or low perceived priority. Crawled means Google did fetch it and chose not to index it, which is almost always a quality, duplication, or demand judgement rather than a technical one.
How long does it take for a page to get indexed after you fix it?
Expect two to eight weeks for a meaningful change, not days. Google has to recrawl the URL, re-evaluate it against the rest of your site, and in many cases re-evaluate the site-level quality signals that caused the exclusion in the first place. Sites with strong crawl frequency see movement faster.
Should I use Request Indexing in Search Console to fix it?
Once per genuinely improved page, at most. Requesting indexing forces a recrawl but does not change the quality assessment that caused the exclusion, so repeatedly submitting an unchanged URL achieves nothing. Fix the page first, then request indexing once and leave it alone.
Is crawled currently not indexed always a problem?
No. Paginated URLs, filtered variants, tag archives, and thin utility pages sitting in that report are working as intended and should often be noindexed or removed from your sitemap. It only becomes a problem when commercially important pages, or a large share of your indexable URLs, are being excluded.
