Crawled – Currently Not Indexed: Why Google Skips Your Pages (and How to Fix It)
“Crawled – currently not indexed” means Googlebot successfully fetched your page, read it, and then chose not to add it to the search index. It is not a crawl error, a penalty, or a broken link. It is a judgement. Google looked at the page and decided it was not worth storing — usually because of site-level trust, duplication, thin value, or a configuration mistake that makes the page look like a copy of something else.
That distinction matters, because it changes the fix completely. If this were a crawl error you would repair a link or a server response and move on. Because it is a judgement, no amount of resubmitting will change the outcome until the underlying reason changes. This guide covers what the status actually means, the eight causes behind almost every case, a diagnostic you can run in twenty minutes, and the one cause that almost nobody checks.
Crawled, discovered, indexed: what the three states mean
Google Search Console uses three statuses that sound similar and mean very different things. Getting them straight is the first step, because each points to a different problem.
If most of your pages sit in Discovered – currently not indexed, Google is rationing crawl attention. That is usually an authority and freshness problem. If they sit in Crawled – currently not indexed, Google has already spent the effort to read them and still said no. That is the harder signal, and the one this guide addresses.
The eight reasons Google crawls a page and skips it
Google does not publish a reason per URL, so diagnosis is a process of elimination. In practice almost every case falls into one of these eight buckets, roughly in order of how often they turn out to be the culprit.
Notice what is not on that list: page speed, meta description length, keyword density, and missing alt text. Those matter for ranking once a page is indexed. They are almost never why a page fails to be indexed at all. Chasing them is the single most common way people waste a month on this problem.
The cause almost nobody checks: your property is watching the wrong host
This one deserves its own section because it produces hundreds of “crawled – currently not indexed” rows, it survives every content fix you throw at it, and it is invisible unless you specifically look for it.
Google treats www.example.com and example.com as two different websites. If your Search Console property is registered to one host and your site actually serves from the other, Google will keep crawling URLs on the property’s host, keep finding that they redirect somewhere else, and keep declining to index them. The Pages report will show a large, flat number that never improves, and validation attempts will come back as Failed.
The fix is to add a Domain property rather than a URL-prefix property. A Domain property is verified with a DNS TXT record at your registrar, and it covers www and non-www, http and https, and every subdomain in a single property. Once it is verified, submit your sitemap again on the new property and give Google a week or two to recrawl. Keep the old property rather than deleting it — it is useful for watching the old URLs drain out of the index.
While you are there, make sure the sitemap you submit is the one your site actually serves. If an SEO plugin such as Rank Math is generating /sitemap_index.xml but your robots.txt advertises WordPress core’s /wp-sitemap.xml, you are sending crawlers through an unnecessary redirect and will see “Couldn’t fetch” errors in the Sitemaps report.
A 20-minute diagnostic you can run yourself
Work through these in order. Each step either clears a cause or identifies it, and the order is deliberate — there is no point tuning content if the plumbing is pointing at the wrong address.
Step six is worth dwelling on. Manual indexing requests are capped at roughly ten to twelve URLs per property per day, so you cannot submit your way out of a large backlog. What you can do is use a small batch as a test. If five genuinely good pages get indexed after a direct request, your crawl budget was the bottleneck and the path forward is authority and internal linking. If they still do not index, the assessment is happening at site level and no page-by-page work will shift it.
What actually fixes it
Once you know which cause you are dealing with, the remedies are reasonably well understood. They are also slower and less comfortable than most SEO advice suggests.
Publish less, not more
This is the counterintuitive one. If three hundred pages are sitting unindexed, adding fifty more does not help — it dilutes crawl budget further and reinforces whatever quality signal is holding the site back. Google assesses quality across everything you publish, which means weak pages actively cost you. Auditing what exists and deleting or consolidating the thin half is usually more effective than any amount of new content.
Consolidate near-duplicates
If you have eight articles covering overlapping ground, they compete with each other for the same queries and none of them reads as definitive. Merging them into one thorough piece and 301-redirecting the rest concentrates the signal. One strong page beats eight weak ones, both for indexing and for ranking in 2026.
Fix your internal linking
Orphan pages — those with no internal links pointing to them — tell Google you do not consider them important either. Every page worth indexing should be reachable from your navigation or from a hub page within two or three clicks. Category and pillar pages that genuinely describe and link to their contents do real work here, both for crawlers and for readers.
Earn external signals
Site-level trust is the hardest cause to address and the most common one at scale. There is no technical substitute for other reputable sites referencing yours. Directory submissions and bookmarking will not do it; genuine mentions, guest contributions to established publications, and original research or data that people cite will. This is slow work measured in months, and it is the reason an otherwise clean site can still struggle to get indexed.
What does not fix it
An equally useful list, because each of these consumes time that could go somewhere productive.
- Resubmitting the same URLs repeatedly. Google has already assessed them. Asking again returns the same verdict.
- Indexing APIs and third-party “instant index” services. Google’s Indexing API is officially limited to job postings and live-stream markup. Everything else is either ignored or risky.
- Rewriting meta descriptions. They influence click-through rate on results that already exist. They have no bearing on whether a page is indexed.
- Chasing a perfect PageSpeed score. Worth doing for users, but a slow page that offers something unique still gets indexed, and a fast page that offers nothing does not.
- Adding more schema to a thin page. Structured data describes content. It does not create value where there is none.
How long recovery takes
Expectations matter here, because the most common mistake after fixing the cause is concluding too early that the fix did not work.
The pattern to watch for is direction rather than speed. If the unindexed count is falling week on week, even slowly, the fix is working. If it has been completely flat for a month after a genuine change, something else is still wrong and it is worth going back to step one of the diagnostic.
A note on AI search
Indexing has become more consequential, not less, as AI answers have grown. An AI engine cannot cite a page it cannot find, and most generative answers draw from pages that are already indexed and ranking in conventional search. If you are working on appearing in AI Overviews or being quoted by ChatGPT and Perplexity, indexing is the prerequisite, not a parallel track. Fix it first, then worry about extractability, structured data and author attribution.
Where to start tomorrow
If you take one thing from this guide, make it the diagnostic order. Confirm the host, confirm the property matches, confirm the sitemap resolves, rule out a manual action, then test five strong pages. Those five checks take twenty minutes and will tell you whether you are facing a configuration fault you can fix this week or an authority problem that will take months.
Most people skip straight to rewriting content, because that feels like progress. It usually is not. The pages were never rejected for the reasons being fixed — and discovering that after a month of writing is a painful way to learn it.
For related reading, see our guides to on-page SEO elements that carry the most weight, learning SEO in simple steps, and 48 ways to increase website traffic. You can browse everything in the Technology section.
