Crawled — currently not indexed is the most confusing state in Search Console: Google fetched the page, then chose not to put it in the index. It is not an error, and there is no “Validate Fix” button. The page is competing for a slot and losing on quality.
Fastest fix: before touching anything, inspect the live URL (the URL Inspection tool is fresher than the Page indexing report and often already shows the page as indexed). If it really is excluded, the only durable fix is to make the page clearly more useful than what is already ranking, then add real internal links to it. Requesting indexing alone almost never moves this status.
What the status actually means
Open Search Console → Indexing → Pages → “Why pages aren’t indexed” and click Crawled - currently not indexed. This means:
- ✅ Google knows the URL exists
- ✅ Googlebot fetched the page successfully (200 OK, no
noindex, not blocked by robots.txt) - ❌ Google decided not yet to add it to the index
Google’s own help text reads: “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.” In plain terms: the page passed the technical bar but failed the value bar.
This is different from Discovered - currently not indexed, where Google knows the URL but has not crawled it yet (usually a crawl-budget or scheduling issue). Causes and fixes differ — make sure you are reading the right status before you start.
First: confirm it is actually excluded
The Page indexing report can lag the live index by days. Before you spend an afternoon fixing nothing:
- Paste the URL into the URL Inspection box at the top of Search Console.
- Read the live result. If it says
URL is on Google, the report is just stale — you are done. - If it says
URL is not on Googlewith reasonCrawled - currently not indexed, the exclusion is real. Continue below.
You can also sanity-check from the SERP: search site:yourdomain.com/your-exact-path. No result is consistent with exclusion; a result means it is indexed.
The real causes, in order of likelihood
| # | Cause | How to spot it | Bucket |
|---|---|---|---|
| 1 | Thin or “commodity” content | Under ~300 words, mostly images, or it says the same thing as dozens of pages already ranking | Quality |
| 2 | Orphan / sparse internal links | No indexed page links to it; only reachable via the sitemap | Authority |
| 3 | Near-duplicate of your own pages | Several pages target the same intent; Google indexes one and skips the rest | Quality |
| 4 | New-domain / new-section caution | Brand-new domain or section; Google is conservative for the first 1–3 months | Time |
| 5 | Canonical points elsewhere | The page’s canonical tag names a different URL, so Google indexes that one instead | Technical |
As of June 2026 the bar on cause 1 is higher than it was a year ago. The March 2026 core update (rolled out March 27 to April 8, 2026) leaned hard on “commodity content” — pages that are technically fine but easily replaceable and add nothing beyond what is already indexed. They get crawled and then dropped. The update did not ban AI-generated text; it targeted content produced at scale without real editorial oversight, while pages where a human added first-hand expertise, examples, and judgment held up. If a page was previously indexed and slipped into this status after late March 2026, suspect a sitewide quality reassessment, not a single-page bug.
Shortest fix path
Work top-down; stop as soon as the live URL inspection flips to indexed.
- Fix the technical blockers first (fast, days to recover). Confirm the page returns
200, has nonoindex, is not disallowed inrobots.txt, and its canonical points to itself unless you genuinely want another URL indexed. Re-inspect the live URL after each change. - Make the page meaningfully better than the competition (the durable fix). Add original substance: specifics, numbers, a worked example, an FAQ, your own screenshots. Aim for content a competitor could not copy-paste. Word count is a symptom, not the goal — 800+ useful words usually beats 300 thin ones, but padding does nothing.
- Add 2–5 internal links from already-indexed pages that get traffic, using descriptive anchor text (not “click here”). Links from your homepage, category hubs, and closely related articles pass the most signal. An orphan page rarely gets indexed.
- De-duplicate. If two of your pages chase the same query, merge them or 301 the weaker one into the stronger.
- Optionally request a re-crawl. In URL Inspection, click
Test Live URLfirst; if the live test fails, the request will fail too and you waste a daily slot. If it passes, clickRequest Indexingonce after the improvements ship. The manual request quota is roughly 10–12 URLs per day per property (as of June 2026; tied to the verified property, not your account), and the button greys out for ~24 hours once you hit it. Per Google, requesting is not required and doing it without real changes “rarely works” — it only nudges the queue. - Wait. Technical fixes can clear in days; content-quality recovery typically takes 1–4 weeks, sometimes longer if it is tied to a core update. Do not re-request daily; that does nothing.
How to confirm it’s fixed
- Re-run URL Inspection on the live URL; you want
URL is on Google. - Confirm with
site:yourdomain.com/your-exact-pathin Google Search. - In the Page indexing report, the URL drops out of the
Crawled - currently not indexedlist on the next report refresh (allow a few days of lag).
FAQ
Should I just keep clicking “Request Indexing”? No. Google explicitly says “no need to resubmit this URL for crawling,” and re-requesting without changing the page does not change the quality decision. You also can’t spam it: manual requests are capped at roughly 10–12 URLs per day per property (as of June 2026), and the button greys out for about a day once you hit the limit. Improve the page first; request once, if at all.
It says crawled-not-indexed but the page shows up in site: search. Which is right?
The live site: result and live URL Inspection win. The Page indexing report can be days stale, so a page can be indexed while still listed under this status. Verify live before fixing anything.
How long until it gets indexed after I improve it?
Technical fixes (removing noindex, fixing a canonical) often recover within days of a re-crawl. Content-quality and internal-link improvements usually take 1–4 weeks, and longer if the drop coincided with a core update.
My whole site dropped into this status after a core update — what now? Treat it as a sitewide quality signal, not 500 separate bugs. Prioritize your best pages, cut or merge thin/duplicate ones, strengthen internal linking, and improve first-hand value. Recovery generally happens over the following weeks to the next update cycle.
Is “Crawled — currently not indexed” the same as “Discovered — currently not indexed”?
No. Crawled means Google fetched it and declined (a value decision). Discovered means Google has not fetched it yet (a crawl-budget/scheduling decision). The Discovered fix focuses on crawl budget and server response time, not content quality.
Related
- Discovered — currently not indexed (the other status)
- Sitemap submitted but no indexing
- Search Console shows “Not indexed”
- Site not on Google after launch
External references: Google Page indexing report (official) and the URL Inspection tool docs.