JnK Plugins
‘Crawled — Currently Not Indexed’: What It Means and How to Fix It
Few Google Search Console statuses cause as much quiet panic as “Crawled — currently not indexed.” You open the Page indexing report, see dozens of posts in that bucket, and conclude something is broken. Here’s the uncomfortable truth we learned firsthand — we watched our own new site go through exactly this in its first month: nothing is technically wrong. Google visited your page, read it in full, and chose not to index it. That distinction changes everything about how you fix it, and it’s why the usual reflexes — resubmitting the sitemap, hammering Request Indexing — mostly don’t work here.
This post stays tightly scoped to this one GSC status (and its close cousin, “Discovered — currently not indexed”): what it actually means, which fixes genuinely move pages out of it, and when it’s fine to just leave it alone. If your problem is broader — your whole site isn’t showing up, or you suspect a noindex tag or robots.txt issue — we’ve covered the full troubleshooting checklist in our guide to Google not indexing your WordPress site. Start there if you haven’t ruled out the technical basics; come back here once you’re sure the only thing between your page and the index is Google’s opinion of it.
What “Crawled — currently not indexed” actually means
Read the status literally. Crawled: Googlebot fetched the page successfully — no 404, no server error, no robots.txt block, no noindex tag. Currently not indexed: after evaluating what it fetched, Google decided the page doesn’t earn a spot in the index right now. The word “currently” is doing real work — Google explicitly says these pages may be indexed later without you doing anything.
In other words, this is a quality and priority signal, not an error. Google’s index is a curated subset of the web, not a complete archive, and the bar for inclusion keeps rising. When a crawled page doesn’t make the cut, Google is effectively saying one of three things:
- “This page doesn’t add enough unique value.” It’s thin, it substantially duplicates something already indexed, or it answers a question the index already answers a thousand times over.
- “Your site hasn’t earned enough trust yet for us to index everything.” Very common on new domains — Google indexes a slice of your content first and watches how it performs.
- “Nothing on your own site tells us this page matters.” The page has few or no links from your other indexed pages, so your own structure is voting against it.
How it differs from “Discovered — currently not indexed”
These two statuses look similar and get conflated constantly, but they describe different problems. Discovered — currently not indexed means Google knows the URL exists (from your sitemap or a link) but hasn’t crawled it yet — usually a crawl-budget or crawl-scheduling issue on a low-priority URL. Crawled — currently not indexed means the crawl already happened and the page was evaluated and passed over — a quality/priority judgment.
The practical difference: “Discovered” pages often resolve on their own as your crawl budget grows. “Crawled” pages have already had their audition — something about the page, or your site’s overall standing, needs to change before Google reconsiders.
Why Request Indexing usually doesn’t fix this one
The Request Indexing button in the URL Inspection tool asks Google to crawl the page again soon. But crawling was never the problem — Google already crawled it and declined to index it. Requesting indexing on one of these pages typically just gets you a fresh crawl followed by the same decision. We tried it on our own early posts; the pages bounced right back into the same bucket.
The button is worth pressing exactly once after you’ve meaningfully changed something — rewritten the content, added links to it from strong pages, consolidated it with a sibling post. Used that way, it shortens the wait for re-evaluation. Used as a repeated ritual on an unchanged page, it does nothing.
Fixes that genuinely work
1. Add links to the page from your indexed pages (the highest-leverage fix)
If we could only recommend one action, it’s this. A page with no links from the rest of your site is telling Google, in the language it reads most fluently, that even you don’t think it’s important. Go to two or three already-indexed, reasonably strong pages and add natural, contextual links pointing at the stuck page. In our experience — and in most published case studies on this status — this moves pages into the index more reliably than any content tweak.
Start by finding the pages with zero inbound links at all; our walkthrough on finding orphaned pages in WordPress shows how to surface them, and orphans are heavily overrepresented in this GSC bucket. Doing the links by hand works fine on a small site. On a bigger one, tooling helps — full disclosure: our own free plugin, JnK Linkweave, adds contextual links between related posts automatically, and clearing our orphaned posts with it was part of how we dug our own site out of this status. To survey the whole tooling landscape, see our roundup of the best plugins for linking your posts together.
2. Improve the page’s depth and uniqueness
Reread the stuck page and ask the brutal question: if this page vanished, would anyone searching Google lose anything? If it’s a 400-word summary of a topic with fifty better treatments already indexed, no amount of resubmitting will help. Add what only you can add — original data, screenshots of your actual process, a firsthand test, a strong opinion. Expand thin sections; delete filler. Google doesn’t need another page on the topic; it needs a better one.
3. Consolidate thin and overlapping pages
Five weak posts circling the same topic often serve you worse than one strong post. If several pages in this bucket overlap heavily, merge them into your best URL and 301-redirect the others to it. You lose nothing — the pages weren’t indexed anyway — and the surviving page inherits the combined substance. It also improves Google’s assessment of your site overall, which matters because indexing decisions are partly sitewide.
4. Confirm the page is in your sitemap
This won’t fix a quality judgment by itself, but a page missing from your XML sitemap is another small vote against its importance. Make sure your SEO plugin includes the page’s post type in the sitemap and that the sitemap is submitted in Search Console. It’s a five-minute check; do it and move on.
5. Earn external signals
A link or two from another indexed site — a relevant forum answer, a guest post, a mention in a niche newsletter — tells Google the page matters to someone beyond you. For new domains especially, a handful of legitimate external links raises the sitewide trust that governs how much of your content Google will index. Don’t buy links; one honest mention beats fifty spammy ones.
6. Sometimes, just wait
If your domain is under six months old and your content is genuinely good, patience is a real strategy. New sites get indexed incrementally as Google builds confidence. Our own site launched with most posts stuck in this status; the majority moved into the index over the following weeks as we kept publishing and cross-linking, with no page-level intervention on many of them.
Realistic timelines
After a meaningful change plus one Request Indexing, expect re-evaluation within days to a couple of weeks — not hours. For new domains riding it out, think four to twelve weeks for the bulk of good content to be picked up. If a page has sat in this status for three-plus months after you’ve improved and linked it, take the hint: it needs a bigger rethink or consolidation.
When this status is completely fine to ignore
Not everything deserves to be indexed, and Google skipping some URLs is healthy. Don’t burn time on:
- Feed URLs (
/feed/) — RSS endpoints have no business in the index. - Tag, date, and thin category archives — auto-generated lists with no unique content.
- Parameter and pagination URLs (
?replytocom=,/page/7/) — duplicates or near-duplicates by design. - Attachment and utility pages — media pages, cart/checkout, login, thank-you pages.
If most of your “Crawled — currently not indexed” URLs fall into these buckets, your report is basically clean. Only the pages you actually want to rank deserve the fixes above.
Quick reference: common GSC page-indexing statuses
| GSC status | Severity | What to do |
|---|---|---|
| Crawled — currently not indexed | Medium (quality/priority signal) | Improve or consolidate content, link to it from indexed pages, then request indexing once |
| Discovered — currently not indexed | Low–medium (crawl scheduling) | Usually wait; improve site speed and link the page from crawled pages |
| Excluded by ‘noindex’ tag | High if unintentional | Check your SEO plugin and page settings; remove the tag if the page should rank |
| Blocked by robots.txt | High if unintentional | Edit robots.txt to allow crawling of pages you want indexed |
| Not found (404) | High if the page should exist | Restore the page or 301-redirect the URL to its replacement |
| Alternate page with proper canonical tag | None (working as intended) | Nothing — Google is honoring your canonical choice |
| Duplicate without user-selected canonical | Medium | Set explicit canonicals or consolidate the duplicate pages |
The mindset shift that makes this status manageable: it’s Google giving you feedback, not throwing an error. Treat the affected pages as a to-do list ranked by how much you care about each URL, fix the ones that matter with better content and stronger links from your own site, and let the rest go. That’s what we did — and the report thinned out month by month.
Frequently asked questions
Is “Crawled — currently not indexed” an error I need to fix?
No. It is not a technical error — Google successfully crawled the page and chose not to index it, which is a quality and priority judgment. Fix it only for pages you genuinely want to rank, by improving the content and linking to the page from your indexed pages. For feeds, tag archives, and parameter URLs, the status is normal and safe to ignore.
How long does it take for a page to leave “Crawled — currently not indexed”?
After you meaningfully improve a page and request indexing once, re-evaluation typically takes a few days to a couple of weeks. On new domains, expect four to twelve weeks for most good content to be indexed as Google builds trust in the site. A page still stuck three months after real improvements is a candidate for a rewrite or consolidation.
Does clicking Request Indexing fix “Crawled — currently not indexed”?
Usually not. The button only triggers another crawl, and crawling was never the problem — Google already crawled the page and declined to index it. Press it once after you have actually changed something, such as rewriting the content or adding links to the page from strong indexed pages. Repeatedly resubmitting an unchanged page does nothing.
