Crawled, Currently Not Indexed: What It Means and How to Fix It
Google's John Mueller said again this week that a site full of these pages usually has a quality problem, and that shrinking the site doesn't fix it. Here is how to rule out the technical causes in minutes, with a script, and what to do with the pages that are left.
Crawled currently not indexed is a Search Console status that means Googlebot fetched the page and Google chose not to add it to its index; Google calls it a common message for many sites.
Discovered currently not indexed means Google knows the URL but hasn't crawled it yet, often because it expected the crawl to overload the site.
On Nov. 10, 2026, Google's John Mueller wrote that a large share of these pages is usually a sign Google's quality systems are unconvinced about the site, and that making the site smaller doesn't significantly raise its quality.
Before treating it as a content problem, rule out technical causes: a noindex tag or header, a canonical pointing elsewhere, a redirect or error, a robots.txt block, or a missing sitemap entry.
Google's own help page says sites with fewer than 500 pages probably don't need the Page indexing report, and that not every URL on a site should be indexed.
Crawled, currently not indexed is a status in Google Search Console's Page indexing report. It means Googlebot fetched the page and Google decided not to add it to its index, so it can't show in search results. Google's help page calls it "a common message for many sites": seeing a few is normal. Seeing a large share of your site there is a signal worth acting on.
Google's John Mueller said as much on Nov. 10, 2026, answering a site owner on Bluesky who asked whether to noindex, redirect or wait out a large share of these pages. A site that consistently has many of them, he wrote, is "usually" a sign "that Google's quality systems are unconvinced about your site." And he added: "Just making the site smaller doesn't significantly raise the overall quality of the site." (Search Engine Roundtable reported the exchange first.)
This guide covers what the status means, how to rule out the technical causes quickly with a script we wrote, and what to do with the pages that are left.
What does crawled, currently not indexed mean?
Google saw the page and chose not to index it, for now. Google's help page puts it in one line: "The page was crawled by Google but not indexed." It doesn't give a reason for any single URL, and the status can change on a later crawl without you doing anything.
Two things it doesn't mean: it isn't a penalty, and it isn't an error on your server. If Google couldn't fetch the page, you'd see a different reason, such as a server error or a 404.
What is the difference with discovered, currently not indexed?
Discovered, currently not indexed means Google knows the URL exists, from a link or a sitemap, but hasn't crawled it yet. Google's help page says it usually rescheduled the crawl because crawling then was expected to overload the site, which is why the last crawl date for these URLs is empty. If your server has been slow or erroring, or you just moved it behind a CDN, fix that first; our post on Google's advice for CDN moves covers how.
In practice the two often travel together. Mueller answered both statuses in the same reply. On a small site with a healthy server, a long list of discovered pages usually points the same way as the crawled ones: Google doesn't see enough reason to spend effort on them yet.
Should you worry about it?
Not always. Google's help page says that if your site has fewer than 500 pages, "you probably don't need to use this report," and that "you should not expect all URLs on your site to be indexed, only the canonical pages." Duplicates, filtered versions, paginated archives and thin tag pages are often fine to leave out.
Worry when the pages in the list are ones you want found: product pages, service pages, articles you wrote to rank. That is the case Mueller was talking about.
How do you check for technical causes?
Rule these out first, because they are quick to fix and they are your doing, not Google's judgment:
A noindex in a meta robots tag or an X-Robots-Tag header. (A noindex usually shows under its own reason, "Excluded by 'noindex' tag", but templates change after a crawl.)
A canonical tag pointing to another URL. Google treats it as "a strong signal" that the other URL is the one to index.
A redirect or an error on the URL as it is today.
A robots.txt rule blocking the path.
No sitemap entry for a page you want indexed.
A title shared with other URLs, a sign of near-duplicate pages.
To check them all at once, export the list from the report: open the Page indexing report, click Crawled - currently not indexed in the "Why pages aren't indexed" table, and use the export button. Google notes the list of examples is limited to 1,000 rows.
Then run this Node.js script (Node 18 or later, no packages). It reads any file with URLs in it, such as the exported CSV, and checks each URL for the causes above. The URLs with none of them are printed shortest first, by a rough word count of the page.
// not-indexed-check.mjs: node not-indexed-check.mjs <urls.csv> [sitemap-url]import { readFileSync } from 'node:fs';const [file, sitemapUrl] = process.argv.slice(2);const urls = [...readFileSync(file, 'utf8').matchAll(/https?:\/\/[^",\s]+/g)].map((m) => m[0]);const inSitemap = new Set();if (sitemapUrl) { const xml = await (await fetch(sitemapUrl)).text(); for (const m of xml.matchAll(/<loc>\s*([^<\s]+)\s*<\/loc>/g)) inSitemap.add(m[1]);}const robotsCache = {};async function blockedByRobots(u) { const { origin, pathname } = new URL(u); robotsCache[origin] ??= await fetch(origin + '/robots.txt').then((r) => (r.ok ? r.text() : '')); // Simple reading: Disallow lines in the "*" or "Googlebot" groups, prefix match. let applies = false; for (const line of robotsCache[origin].split('\n')) { const [k, ...rest] = line.split(':'); const v = rest.join(':').trim(); if (/^user-agent$/i.test(k.trim())) applies = v === '*' || /^googlebot$/i.test(v); if (applies && /^disallow$/i.test(k.trim()) && v && pathname.startsWith(v)) return true; } return false;}const titles = {};const rows = [];for (const url of urls) { const res = await fetch(url, { redirect: 'manual' }); const html = res.status === 200 ? await res.text() : ''; const flags = []; if (res.status !== 200) flags.push(`status ${res.status}${res.headers.get('location') ? ' to ' + res.headers.get('location') : ''}`); if (/noindex/i.test(res.headers.get('x-robots-tag') || '')) flags.push('noindex header'); if (/<meta[^>]+name=["']robots["'][^>]+noindex/i.test(html)) flags.push('noindex meta'); const canon = html.match(/<link[^>]+rel=["']canonical["'][^>]+href=["']([^"']+)/i)?.[1]; if (canon && new URL(canon, url).href !== url) flags.push(`canonical points to ${canon}`); if (await blockedByRobots(url)) flags.push('blocked by robots.txt'); if (sitemapUrl && !inSitemap.has(url)) flags.push('not in sitemap'); const text = html.replace(/<(script|style|noscript)[\s\S]*?<\/\1>/gi, ' ').replace(/<[^>]+>/g, ' '); const words = (text.match(/[A-Za-z0-9']+/g) || []).length; const title = html.match(/<title>([^<]*)<\/title>/i)?.[1]?.trim() || ''; if (title) (titles[title] ??= []).push(url); rows.push({ url, words, title, flags });}for (const r of rows) if (titles[r.title]?.length > 1) r.flags.push('title shared with another URL');const technical = rows.filter((r) => r.flags.length);console.log(`${rows.length} URLs checked, ${technical.length} with a technical cause\n`);for (const r of technical) console.log(`${r.url}\n ${r.flags.join('; ')}`);console.log('\nNo technical cause found (a content question), fewest words first:');for (const r of rows.filter((r) => !r.flags.length).sort((a, b) => a.words - b.words).slice(0, 15)) console.log(` ${String(r.words).padStart(6)} words ${r.url}`);
Its limits: the robots.txt reading is simple (prefix matches only, no wildcards), it only sees the HTML the server sends (not pages built by JavaScript in the browser), and the word count includes menus and footers. It's a first pass, not a verdict.
What we found when we ran it
This site has fewer than 500 pages, so by Google's own measure we don't need the report. But we wanted to see the script work, so on Nov. 11 we ran it on the 58 URLs in our sitemap plus three URLs we knew were wrong: a blocked path, a page that doesn't exist, and a URL with a trailing slash. It flagged exactly those three: a 404 that robots.txt also blocks, a plain 404, and a 308 redirect to the version without the slash. All 58 sitemap URLs passed every check.
The bottom of the output is where the useful work starts. Our 15 thinnest pages by the script's count were section, topic and site pages, at 327 to 592 words including the menus and footer. If any of those showed up as crawled, currently not indexed, that would be the honest answer: a list page with little of its own to say. It's the same question Mueller is pointing at.
Should you noindex crawled, currently not indexed pages?
Not as a fix for indexing. Mueller's point is that removing pages doesn't make the rest of the site better in Google's eyes. Noindex or remove a page when it shouldn't be in search anyway (a duplicate, a filter, an empty tag page), not to shrink the list.
Our view on what to do with each page the script leaves:
Pages that matter and are thin: make them worth indexing. Add what only you can say: real details, prices, photos you took, answers to the questions customers ask. A rewrite that says the same thing at greater length won't change Google's mind.
Pages that overlap: merge them into the strongest one and redirect the others to it.
Pages nobody needs: remove them or noindex them, and drop them from the sitemap. Do this because they are weak, not because of the report.
Then request indexing for the pages you improved. In the URL Inspection tool, click Test live URL, then Request indexing. Google says a request "does not guarantee" indexing and that there is a daily limit, so save it for pages you changed.
How long does crawled, currently not indexed take to clear?
There is no set time. Google doesn't promise to re-crawl or re-judge a page on a schedule. If you use Validate fix in the report, Google says validation typically takes about two weeks, sometimes longer, and that you shouldn't click it again until it succeeds or fails. Earlier in the same Bluesky thread, on Nov. 9, Mueller wrote about a fairly new site that "it can take time for the systems to understand the unique value" of its content.
What we don't know
Which signals decide it. Google doesn't say why a single page wasn't indexed. Word counts, links and freshness are all guesses about the inputs.
How many pages is "a lot." Neither Google's help page nor Mueller gives a share at which it becomes a site problem.
Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.