Crawled – Currently Not Indexed: What It Means and How to Fix It
Of all the statuses in Google Search Console’s Page indexing report, crawled, currently not indexed is the one that generates the most confusion, because it describes a page that did everything right and still is not in the index. Googlebot found the URL. It fetched the page. Nothing blocked it, nothing errored. And then Google looked at what it had fetched and decided, for now, not to keep it. This post explains what the status actually means, why Google applies it, and what you can do that has a realistic chance of changing the outcome.
What “crawled – currently not indexed” actually means
Google’s own documentation for the Page indexing report describes the status plainly: the page was crawled by Google but not indexed, and it may or may not be indexed in the future. There is no need to resubmit the URL, Google says, because the decision was not caused by a delivery problem.
That last part is worth sitting with. Most indexing problems are mechanical. A noindex tag, a robots.txt block, a 404, a server error: these are switches you can flip, and when you flip them the problem goes away. Crawled, currently not indexed is not mechanical. It is a judgement. Google saw the page in full and declined, or deferred, the decision to index it.
The distinction matters because it changes what “fixing” looks like. You cannot fix a judgement by resubmitting harder. Something about the page, or about the site around it, has to give Google a reason to decide differently.
Why Google crawls a page and then declines to index it
Google does not publish a checklist for this status, but the patterns are consistent enough to name. In practice, pages land here for a handful of reasons.
The content is thin or templated. Pages generated at scale from a database, tag and archive pages, near-empty category pages, or short posts that restate what a hundred other pages already say. Google’s guidance on creating helpful content is the closest thing to an official explanation: pages made primarily to attract search engines rather than to help a person tend not to earn a place in the index.
The page duplicates something Google already has. If the page substantially overlaps another URL, on your site or elsewhere, Google may crawl it and conclude the index already contains the answer. This is a close cousin of a canonical problem; Google’s page on consolidating duplicate URLs explains how it picks one version among duplicates.
The site’s overall record is dragging the page down. Indexing decisions are not made on a page in isolation. A site where most previously crawled pages turned out to be thin teaches Google to expect thinness, and new pages inherit that expectation until the record improves.
The page is orphaned or nearly so. A URL that only a sitemap knows about, with no internal links pointing at it, gives Google very little evidence that the site itself considers the page important.
It is simply “not yet”. The status name includes the word currently for a reason. Google indexes on its own schedule, and some pages pass through this status on the way to being indexed with no intervention at all. We cover this and the other structural causes in more detail in six reasons Google declines to index a page that looks fine.
Diagnose before you change anything
Resist the urge to start editing immediately. A short diagnosis pass now saves a long stretch of guessing later.
Start with the URL Inspection tool in Search Console. Confirm the status is really crawled, currently not indexed and not its sibling, discovered, currently not indexed, which means Google has not fetched the page at all yet. Check the “Google-selected canonical” field: if Google chose a different URL as canonical, your problem is duplication, not quality.
Then look at the page the way a stranger would. Open it next to the pages on your site that are indexed and ask what the indexed ones have that this one lacks. Length is rarely the answer. Substance usually is: original information, a specific answer to a specific question, something a person would be glad to have landed on.
Finally, look at the page’s position in the site. How many clicks from the home page? How many internal links point to it, and from where? A page the site itself barely references is easy for Google to deprioritise.
The fixes, in the order worth trying them
1. Improve the page itself. This is the unglamorous fix and the one that works most often. Add the substance the indexed comparison pages have. Merge two thin pages into one useful page. If a page exists only to hold a keyword, either give it a real reason to exist or remove it and let its stronger sibling take the query.
2. Strengthen internal linking. Link to the page from your most established, most indexed pages, with descriptive anchor text. This is evidence Google can crawl: the site considers this page part of its structure, not an appendix.
3. Resolve duplication deliberately. If URL Inspection shows Google preferring another canonical, decide which URL you actually want indexed, point canonicals there consistently, and make the surviving page the one that deserves to survive.
4. Prune what you will not improve. If a section of the site is generating hundreds of crawled-not-indexed pages you have no intention of improving, consider noindexing or removing them. A smaller site with a higher proportion of index-worthy pages builds a better record than a large one padded with filler.
5. Then, and only then, request recrawling. Once the page has genuinely changed, ask Google to recrawl it. A recrawl request on an unchanged page invites the same judgement it received last time.
Verify the outcome, not the request
Here is the part most workflows skip. Requesting a recrawl is a submission event, and submission is not indexing. The request can be delivered perfectly and the page can remain out of the index, because Google was never obliged to keep what it crawled. That gap between the two events is the whole subject of submitted is not indexed, and it is exactly where crawled, currently not indexed lives.
So after you fix and resubmit, check the actual index on a schedule rather than assuming. The Search Console report updates at its own pace, and a green submission message tells you nothing about the decision. This is the specific problem AIndexify was built around: you submit the URLs, and the tool then checks each one against live Google results on a fixed schedule over the following week, reporting submitted and indexed as two separate events with the date the page was actually found in the index. If a page still shows as not indexed after a fix, you know the fix was not enough, and you know it from evidence rather than optimism.
What not to do
Do not resubmit the same unchanged page daily; Google has said resubmission is not the lever for this status. Do not assume the report is wrong; it lags, but it is rarely mistaken about the decision itself. And do not treat the status as permanent. Pages move out of it in both directions: into the index when the page or the site earns it, and out of Google’s attention entirely when nothing changes.
Crawled, currently not indexed is Google telling you the mechanics worked and the page did not persuade. The honest response is to make the page more persuasive, then watch what Google actually does. If you want that second part handled for you, submit your URLs and see where each page really stands, on evidence rather than a green tick.