“Crawled – currently not indexed” means Googlebot fetched your page, found nothing blocking it, and decided not to add it to Google’s index — at least for now. It isn’t an error, and it isn’t a penalty. It’s a quality-and-priority decision: Google looked at the page and judged it wasn’t worth storing yet. The fix is rarely technical. It usually means making the page more worth indexing, merging it into a stronger page, or accepting that it shouldn’t be indexed at all. Resubmitting an unchanged page almost never helps.
This guide explains what the status means, when you can safely ignore it, how to diagnose it, and a fix for each common cause.

What the Status Actually Means
You’ll find it in Google Search Console under Indexing → Pages, in the “Why pages aren’t indexed” list. Google’s own description is short: the page was crawled but not indexed, it may or may not be indexed in the future, and you don’t need to resubmit it.
It helps to compare it with the statuses it’s often confused with:
| Status | What happened | What it usually points to |
|---|---|---|
| Crawled – currently not indexed | Google fetched the page, then chose not to index it | Content value, duplication, weak internal links, canonical conflicts |
| Discovered – currently not indexed | Google knows the URL but hasn’t fetched it yet | Crawl capacity, server speed, too many low-value URLs |
| Excluded by ‘noindex’ tag | Google fetched it and obeyed your noindex directive | A deliberate or accidental noindex tag |
| Duplicate / alternate page with proper canonical | Google chose a different URL as the main version | Canonical signals working as intended |
The key difference: “Discovered” stops before the crawl, so crawl-budget fixes help there. “Crawled” stops after it, so crawl budget is rarely the issue. If a page shows “Crawled – currently not indexed,” there is no noindex tag and no robots.txt block in the way — those have their own separate statuses. (If you’re mixing up robots.txt blocking and noindex, our robots.txt vs. llms.txt guide covers the difference.)
Should You Worry? When to Ignore It
Not every page on a site deserves a place in Google’s index, and plenty of sites carry hundreds of these URLs without any problem. You can usually ignore the status when:
- The URLs are ones you don’t want indexed anyway — tag archives, filtered or parameter URLs, internal search results, thank-you pages, and thin utility pages
- It affects only a handful of URLs on an otherwise healthy site
- The page was published very recently and hasn’t had time to earn links or signals
Pay attention when:
- Your important pages are affected — services, products, cornerstone articles
- The count is large or growing, especially across entire sections or templates
- Most of a new site’s pages sit in this status, which suggests Google isn’t yet convinced the site is worth indexing at scale
Mass occurrences deserve extra attention. According to coverage of a July 2026 episode of Google’s Search Off the Record podcast, John Mueller said that when Google’s systems have serious doubts about a site’s overall quality, they reduce both crawling and indexing, which can show up as these statuses at scale. Treat that as a reminder that a large pile of “crawled, not indexed” URLs is sometimes a site-wide quality signal, not a series of unrelated page problems.
How to Diagnose It in Six Steps
- Export the list. In Search Console, open the “Crawled – currently not indexed” report and export the URLs.
- Group by pattern, not by URL. Sort them by template, folder, or URL type. Fixing a pattern — say, all product-variant pages — is far more effective than fixing URLs one at a time.
- Sort into “should be indexed” and “shouldn’t.” Decide which groups you genuinely want in search. Everything else can be left alone, consolidated, or removed.
- Inspect a sample of key pages. Use the URL Inspection tool and check the rendered HTML. If the main content only appears after JavaScript runs, Google may be seeing a thin page.
- Check Google’s chosen canonical. URL Inspection shows which URL Google picked as canonical. If it differs from yours, there may be a duplication or canonical conflict.
- Compare with pages that are indexed. What do your indexed pages have that these lack — more depth, more internal links, more unique value? Also you can checkout the full technical SEO guide.
Common Causes and Their Fixes
| Cause | Typical symptom | Fix |
|---|---|---|
| Thin or shallow content | Short pages that restate what’s elsewhere. | Expand with unique, useful information, or merge into a stronger page. |
| Duplicate or near-duplicate pages | Templated pages differing only by a name or city. | Consolidate with 301 redirects or canonical tags; differentiate what must stay. |
| Weak internal linking | Page reachable only via the sitemap or deep pagination. | Add contextual links from relevant, already-indexed pages. |
| Content missing from rendered HTML | Page looks fine in a browser, thin in URL Inspection. | Serve important content in the initial HTML or fix rendering. |
| Canonical or sitemap conflicts | Google’s chosen canonical differs from yours. | Align canonicals, redirects, and sitemap URLs. |
| Search-intent mismatch | Page doesn’t answer what the query actually wants. | Rework the page around the real intent. |
| Low-value URL bloat | Thousands of parameter or archive URLs. | Reduce them with noindex, canonicals, or removal. |
| Site-wide quality or trust doubts | Many pages across many templates affected. | Improve overall quality, prune weak content, build real authority over time. Check on-page SEO guide. |
A Practical Fix Workflow
- Prioritize pages by business value. Fix the ten pages that matter before the thousand that don’t.
- Improve or consolidate. Strengthen valuable pages, and merge near-duplicates into one authoritative version with proper redirects.
- Remove or noindex what has no value. Delete genuinely useless pages or mark them noindex so they stop diluting the site.
- Strengthen internal links to the pages you want indexed, using descriptive anchor text from related, indexed pages.
- Clean up your sitemap. It should list only canonical, indexable URLs. Our guide to fixing sitemap errors on WordPress covers the common problems. Or you can checkout also common XML sitemap errors.
- Request indexing only after meaningful changes. Use URL Inspection’s Request Indexing for your most important improved pages, not as a bulk or repeated action.
- Wait and monitor. Check back in a few weeks and watch the trend rather than individual URLs.
What Doesn’t Work
- Repeatedly clicking “Request Indexing” on an unchanged page. Google has already seen it and made its call.
- Resubmitting the sitemap again and again. The sitemap isn’t the problem — the page evaluation is.
- Third-party “indexing” tools or pingers. They can prompt a crawl, but they can’t override a decision about content quality.
- Publishing more thin pages. More low-value URLs make a site-wide quality problem worse, not better.
How Long Does It Take?
There’s no fixed timeline. Improved pages are typically recrawled and re-evaluated over days to weeks, but the status can resolve gradually as quality and internal-link signals improve, or persist indefinitely for pages Google continues to judge low-value. No one can force a page into the index, and anyone who guarantees it is overpromising.
When to Get Help
Fixing this yourself is realistic for a few pages. Outside help tends to pay off when:
- Hundreds or thousands of URLs are affected and you can’t tell which patterns matter
- You’ve fixed content and links and nothing changes, which often points to a deeper canonical, rendering, or site-wide quality issue
- A migration or redesign preceded the drop in indexed pages
- Indexing problems overlap with sitemap, robots.txt, or redirect issues
Our Google indexing issues service starts with diagnosis — grouping affected URLs by pattern, checking rendering and canonicals, and cross-referencing Search Console — before recommending fixes. We can’t promise any page will be indexed, but we can find out what’s actually in the way.

Checklist: Fixing “Crawled – Currently Not Indexed”
- Affected URLs exported and grouped by pattern
- Pages split into “should be indexed” and “shouldn’t”
- Sample pages inspected for rendering and canonical selection
- Thin and near-duplicate pages improved, merged, or removed
- Internal links added to every page you want indexed
- Sitemap lists only canonical, indexable URLs
- Indexing requested only for meaningfully improved key pages
- Trend monitored over weeks, not days
Frequently Asked Questions
Is “Crawled – currently not indexed” a penalty?
- No. It means Google crawled the page and chose not to index it for now, which is a normal prioritization decision. It becomes a concern when it affects important pages or appears at scale.
Does the status mean my page has an error?
- No. It isn’t a technical error, and a noindex tag or robots.txt block would appear under a different status. It’s about whether the page seems worth indexing.
How is it different from “Discovered – currently not indexed”?
- With “Discovered,” Google knows the URL exists but hasn’t crawled it, which usually points to crawl capacity or weak internal links. With “Crawled,” Google has fetched the page and decided against indexing it, which usually points to content value or duplication.
Should I keep requesting indexing?
- Not for unchanged pages. Improve the page, strengthen its internal links, then request indexing once. Repeated requests don’t change Google’s evaluation.
Will it fix itself?
- Sometimes. Pages can be indexed later as the site’s quality and link signals improve, but others may stay excluded indefinitely, which is fine for pages that shouldn’t be indexed anyway.
Final Thought
“Crawled – currently not indexed” feels like a technical failure, but it’s really Google asking a question: why should this page be in the index? Answer it with better content, clearer signals, and stronger internal links on the pages that matter — and let the rest go. Fix patterns, not individual URLs, and judge progress over weeks. Avail a free indexing review from there.
