Crawled – Currently Not Indexed in Google Search Console: What It Means and What to Fix First
A URL sitting in "crawled not indexed" status is Google's way of saying it visited, read your page, and decided not to include it. That one-line status in the Page Indexing report has triggered more panic-driven "Request Indexing" clicks than probably any other item in Search Console.
The distinction matters more than you realize: Google already spent the crawl budget. It fetched the page, evaluated it, and passed. That's a fundamentally different problem from "Discovered – currently not indexed," where Googlebot hasn't even shown up yet. Treating both statuses the same way wastes time and can actually make things worse. Below is a triage workflow you can run in a single sitting, along with guidance on when to wait, when to fix, and when to stop caring.
Key Points
- Crawled not indexed means Google successfully fetched your page but chose not to add it to the index, usually because the content is too similar to something already indexed, too thin to warrant its own entry, or your site's authority doesn't justify indexing every URL.
- Discovered not indexed and crawled not indexed require completely different fixes: discovered means Google hasn't visited yet and needs better crawl signals like stronger internal links, while crawled means Google already looked at the content and rejected it based on quality or uniqueness.
- Before fixing anything, confirm the URL should actually be indexed by checking for conflicting noindex tags or robots.txt rules, verifying the canonical tag matches what Google selected, and ensuring the content is meaningfully different from pages you already have indexed.
- Request Indexing should only be used after you've made a meaningful change like consolidating thin content or fixing a canonical mismatch, and only for pages stuck after roughly 28 days, because spamming it on unchanged pages just asks Google to re-reject the same content.
- A page can be technically indexed but still generate zero impressions if it ranks so far down that no one sees it, so check the Performance report for actual impression data on your target queries to confirm Google is serving the page in results.
What is crawled not indexed?
Google Search Console's Page Indexing report (formerly called the Coverage report) sorts every URL it knows about into buckets.
"Crawled not indexed" sits in the "Not indexed" category, but it carries a specific signal most operators misread.
It means Googlebot successfully fetched your page. No server errors, no robots.txt block, no redirect loop.
The crawl itself worked fine.
Google then evaluated the content and chose not to add the page to its index. The reasons vary, but they almost always come down to one of a few things: the content is too similar to something already indexed (yours or someone else's), the page is too thin to warrant its own entry, or your site's overall authority doesn't justify indexing every URL.
Page types that commonly trigger this status
Faceted navigation pages, tag archives, paginated listing pages, and near-duplicate location pages show up here constantly. So do thin blog posts that restate what another page already covers better.
A parameter-heavy filter URL that Google crawled but declined to index? That's Google doing exactly what you'd want.
The real issue is when pages you need ranking are stuck in this bucket.
What the page indexing report tells you
The Page Indexing report in Google Search Console is where you'll find every URL Google knows about, organized by indexation status. Each status tells you where your URL sits in Google's crawl-and-index pipeline.
"Indexed" means the page is eligible to appear in search results. "Not indexed" covers everything else, and within that bucket you'll find multiple sub-statuses that each require different fixes.
"Crawled not indexed" is one of those sub-statuses, and it sits alongside others like "Discovered – currently not indexed," "Blocked by robots.txt," and "Page with redirect."
The report updates on a rolling basis as Google recrawls your site, so you won't see changes immediately after you make fixes. Check back weekly rather than daily to track progress.
You can export the full list of URLs for any status, which is important when you're auditing at scale. Click into any individual URL to inspect it with the URL Inspection tool, which shows you exactly what Google saw when it last crawled the page.
The report also shows you trends over time, so you can spot sudden spikes in "not indexed" URLs that might signal a technical issue like a misconfigured canonical tag or a site-wide noindex that slipped through during a deployment.
Why crawled not indexed happens: common causes
Google crawls billions of pages but indexes only a fraction of them. Understanding why your pages land in "crawled not indexed" helps you fix the right problem instead of guessing.
Duplicate or similar content across your site
When multiple pages on your site target the same topic or use nearly identical text, Google picks one to index and ignores the rest. This happens constantly with faceted navigation, tag pages, and location pages that differ only by city name.
Google sees the overlap and decides your site doesn't need five indexed pages saying the same thing.
Thin or low-value content
word page on a topic your competitor covers in depth gives Google no reason to add yours.
Thin content also includes pages with little unique text: product pages with only specs, category pages with just a list of links, or blog posts that summarize without adding insight.
Low site authority relative to crawl demand
Google allocates crawl budget based on your site's perceived authority and the value it expects from indexing more of your pages. If your site is new or has limited backlinks, Google may crawl your pages but decline to index them because it doesn't see enough signal that they'll serve users better than what's already in the index.
Canonical tag conflicts
When your declared canonical points to a different URL, Google may crawl your page but index the canonical target instead.
This is one of the most common causes of "crawled not indexed" for pages that look fine on the surface.
How to find crawled not indexed pages in Google Search Console
Open Google Search Console and go to the Indexing section in the left sidebar. Click "Pages."
Scroll down to the "Why pages aren't indexed" table. Look for the row labeled "Crawled – currently not indexed."
Click that row to see the full list of affected URLs.
You can export the list or click individual URLs to inspect them with the URL Inspection tool. The report updates on a rolling basis, so check back weekly after making changes rather than expecting instant results.
Crawled not indexed vs. discovered not indexed: two different problems
"Discovered – currently not indexed" means Google found the URL (through a sitemap, an internal link, or an external reference) but hasn't crawled it yet. Googlebot knows the address exists; it just hasn't visited.
This is a crawl-budget and prioritization problem.
"Crawled not indexed" means the visit already happened. Google looked at the content and said no.
This is a content-quality or uniqueness problem.
Why the difference changes your fix
If a URL is stuck in "Discovered," your first move is improving crawl signals: stronger internal links, sitemap inclusion, and reducing crawl waste from low-value URLs.
Search Engine Land's triage guide documents how sites that cut crawl-waste URL patterns and strengthened internal linking saw a week-over-week drop in Discovered-not-indexed URLs.
If the URL is "Crawled – not indexed," better crawl signals won't help. Google already crawled it. You need to improve what it found when it got there.
| Status | What It Means | Root Cause | First Action |
|---|---|---|---|
| Discovered – currently not indexed | Google knows the URL exists but hasn't crawled it | Crawl budget / prioritization | Improve internal links and sitemap signals |
| Crawled – currently not indexed | Google crawled the page and chose not to index it | Content quality / uniqueness | Audit content against competing indexed pages |
Triage checklist: diagnose and fix non-indexed urls in one sitting
Before you change anything, ask one question: should this URL be indexed at all?
Plenty of URLs in the "not indexed" bucket belong there. Filter pages, internal search results, and staging remnants don't need indexing.
If the answer is yes, this page should rank, run through these steps in order.
Step 1: confirm the url is meant to be indexed
Open the URL Inspection tool in Google Search Console.
Check for a noindex meta tag, an X-Robots-Tag header, or a robots.txt disallow that contradicts your intent.
Google Search Central's troubleshooting documentation lists seven common URL coverage error types that prevent indexing, and several of them stem from conflicting directives.
This sounds basic, but we see it on audits more than you'd expect: a noindex tag left from staging, or a robots.txt rule that blocks an entire subdirectory.
Step 2: check canonical tags and duplicate signals
If Google sees a canonical tag pointing to a different URL, it may crawl your page but index the canonical target instead.
Inspect the "Google-selected canonical" field in URL Inspection. Does it match your declared canonical?
A mismatch here is one of the most common causes of "crawled not indexed" for pages that look perfectly fine on the surface.
Step 3: evaluate content uniqueness and depth
Google won't index a page that restates what an already-indexed page covers.
Search your own site for the page's target query. If another page already ranks for it, you're competing with yourself.
Thin content is the other half of this problem. A 200-word page on a topic your competitor covers in depth with original research gives Google no reason to add yours. Either consolidate the thin page into a stronger one or expand it with different information. If you're running a broader audit of which pages deserve investment and which need pruning, an SEO content audit driven by Search Console performance data helps you sort that faster than guessing.
Step 4: strengthen internal links and sitemap inclusion
A page with zero internal links pointing to it signals low importance.
Add contextual links from topically related pages. Include the URL in your XML sitemap if it isn't there already.
Neither of these guarantees indexing, but they remove a common barrier.
Step 5: wait 28 days, then escalate
This is where operators get impatient.
After making fixes, Google needs time to recrawl and re-evaluate. A URL that's been stuck for less than four weeks after changes is just waiting in line.
Only escalate (via Request Indexing or a support ticket) URLs that are still stuck after roughly 28 days, when they clearly should be indexed based on your content quality and site authority.
Best practices for preventing crawled not indexed
Fixing pages after they land in "crawled not indexed" is reactive. Preventing the issue in the first place saves you time and preserves your crawl budget.
Audit new content before you publish
Before launching a new page, ask whether it adds unique value or duplicates something you already have indexed. If the answer is unclear, consolidate the content into an existing page instead of creating a new one.
Use noindex strategically on low-value pages
Faceted navigation, internal search results, and parameter-heavy URLs should carry a noindex tag so Google doesn't waste crawl budget evaluating them. This keeps your budget focused on pages that matter.
Monitor canonical tags across your site
Canonical mismatches are one of the top causes of "crawled not indexed."
Run periodic audits to confirm your declared canonicals match what Google selects, especially after site migrations or template changes.
Prioritize internal linking for key pages
Pages with strong internal link support signal importance to Google. Make sure your most valuable pages receive contextual links from related content.
Keep your sitemap clean
Only include URLs you want indexed in your XML sitemap. Remove redirects, noindexed pages, and low-value URLs so Google's crawl budget goes to pages that deserve it.
When "Request Indexing" helps vs. when it wastes your quota
The Request Indexing button in URL Inspection has a daily quota. It's not unlimited, and spamming it does nothing for pages Google has already evaluated and rejected.
Use it for pages where you've made a meaningful change: you've consolidated thin content, fixed a canonical mismatch, or removed a conflicting noindex tag. The request tells Google "something changed, please look again."
If nothing changed, you're just asking Google to re-reject the same page.
Do not use Request Indexing on brand-new URLs that show "Discovered – currently not indexed." Those pages haven't been crawled yet. Requesting indexing for them can work, but burning your quota on URLs that Google would naturally get to within days is poor resource management. Save your quota for pages where you've actually fixed something.
How to measure recovery in the page indexing report
The status flipping from "Crawled not indexed" to "Indexed" is the obvious win. But don't stop there.
Impressions are the real confirmation
A page can technically be indexed and still generate zero impressions.
Check the Performance report for the specific URL. Impressions appearing for your target queries confirm Google is actually serving the page.
Zero impressions doesn't always mean the page isn't indexed, either. Sometimes a page is indexed but ranking so far down that no one sees it. If you're seeing impressions climb while clicks stay flat, that's a different diagnostic problem. Understanding the gap between rising impressions and stagnant clicks helps you separate indexing wins from ranking problems.
Tracking status changes over time
The Page Indexing report updates on its own schedule. After submitting fixes, check back weekly rather than daily. Look for the URL count in the "Not indexed" bucket to decrease and the "Indexed" bucket to increase.
For larger sites, track this at the pattern level. Did your /blog/ URLs improve as a group? Did faceted URLs stay excluded (as they should)?
Pages that decay back out of the index after initial recovery often signal deeper content or authority issues. Monitoring for content decay in Search Console catches those regressions before they compound.
ClickFlow's GSC workflow tracks indexation against impressions automatically, flagging pages that flip status or lose visibility. The plan runs and handles the monitoring so you're not manually pulling these reports every week.
Frequently asked questions
How do you fix crawled but not indexed?
Prioritize URLs that actually need to rank, then improve your page so it is clearly unique and valuable compared to what Google already has indexed. After you make a significant change, give Google time to recrawl and re-evaluate before escalating with a limited indexing request.
What does "not indexed" mean?
It means Google is aware of your URL but has not added it to the searchable index, so it is unlikely to appear in search results. A URL can be crawled successfully and still be excluded from indexing.
What's the difference between crawling and indexing?
Crawling is Google fetching and reading your URL. Indexing is Google choosing to store it and make it eligible to show in search results. A page can be crawled without being indexed if Google decides it does not add enough value.
How do you resolve an indexing issue?
Start by confirming your page is eligible to be indexed, then make it more competitive by improving its originality and usefulness relative to existing indexed pages. Once changes are live, monitor outcomes in Search Console and escalate only when your page still does not move after a reasonable reprocessing window.
How do I prioritize which "crawled not indexed" URLs to work on first?
Sort by business impact. Start with pages tied to revenue or core topics, and deprioritize utility URLs that are not meant to capture search demand. A simple way to rank effort: high-intent pages and key category pages first, then supporting content, then everything else.
Can a page be indexed but still get no impressions, and what should I do next?
Yes, indexing only makes your page eligible to rank. It does not guarantee visibility. If it is indexed but still gets no impressions, focus on search demand and competitiveness. Validate whether your page targets a query Google actually shows results for and whether your page matches that intent.
How should I handle multi-location or similar pages to avoid index bloat while still ranking locally?
Create distinct local value on pages you want indexed, such as unique service details and locally relevant proof, and avoid spinning near-duplicates at scale. For locations that cannot be differentiated, consolidate into stronger hub pages and use internal linking to route users and crawlers efficiently.
Fix the pages that matter, leave the rest alone
Every "crawled not indexed" URL does not deserve your attention.
The operators who waste the most time are the ones trying to get every single URL indexed, including pages that have no business ranking.
Start with the URLs that serve a real search intent and carry business value. Run the triage checklist once. Fix the obvious blockers. Then give Google time to respond before reaching for the Request Indexing button again.
The distinction between a page Google hasn't visited and a page Google visited and rejected is the entire diagnostic. Get that right, and you'll stop solving the wrong problem.
Stop checking manually every week
If you're managing more than a handful of URLs, manual monitoring in the Page Indexing report doesn't scale.
ClickFlow connects directly to your Search Console data and watches for indexation shifts alongside impression and click trends, so you catch problems when they start rather than weeks later.
The plan covers the workflow end to end.