"Crawled, currently not indexed" is the Search Console status that generates the most confusion, because it sounds like an error and isn’t one. Google found your page, read it, and decided not to file it. That’s not a bug report. It’s a quality verdict, and it’s fixable once you read it that way.
Google isn’t failing to index your page. It’s declining to, and the difference tells you exactly what to fix.
What the status actually means
Google’s index is not a directory of everything; it’s a curated library with limited shelf space per site. When a crawled page stays unindexed, Google is saying the page didn’t clear the value bar relative to what’s already indexed, yours and everyone else’s. Google’s own explanation of how Search works is blunt about this: crawling and indexing are never guaranteed.
The four usual causes, in order of likelihood
1. Thin or near-duplicate content
Pages with a couple hundred words, tag archives, near-identical service pages for different towns, filtered product URLs, Google sees them as shelf-fillers. The test is brutal but useful: if this page vanished, would anyone notice? If not, Google already made that call.
2. Orphaned or weakly linked pages
Internal links are how Google reads importance. A page reachable only through the sitemap, with no links from your navigation or related content, is telling Google you don’t consider it important either. Every page worth indexing should be linked from at least two or three relevant pages.
3. Site-wide quality dilution
Hundreds of thin pages don’t just fail individually. They drag the site’s overall quality signal down, which makes Google stingier with your good pages. This is why pruning weak content often gets other pages indexed within weeks.
4. New site, low trust
Young domains get a small indexing budget. Pages that would index instantly on an established site sit in the queue for weeks. The fix is time plus the other three fixes.
The fix process
First, decide page by page: improve, consolidate, or remove. Improve pages that deserve to exist: expand them with genuinely useful detail, not padding. Consolidate near-duplicates into one strong page with redirects from the old URLs. Remove (or noindex) the shelf-fillers entirely; a smaller, denser site indexes better than a bloated one.
Second, wire internal links. Add contextual links from your strongest indexed pages to the ones stuck in the queue. This alone un-sticks a surprising share of "crawled, not indexed" pages, because it directly answers Google’s importance question.
Third, request indexing in Search Console after improving, not before. Requesting indexing on an unchanged page just re-runs the same verdict. And expect the re-evaluation to take days to weeks; this system rewards patience over button-mashing.
Crawled, currently not indexed vs the other statuses
It is worth being precise, because the fix depends on it. Crawled: currently not indexed means Google fetched the page, read it, and decided not to put it in the index. That is different from Discovered, currently not indexed, where it has not been fetched at all, and different again from a noindex, which is you telling it to stay out.
So this is a judgement, not an error. There is nothing technically broken to repair, which is why re-submitting the URL, pinging the sitemap and rebuilding the site change nothing. The page has to become worth indexing.
The causes, in the order they usually turn out to be true
| Cause | How to check it | What to do |
|---|---|---|
| Thin or near-duplicate | Is there anything on it that is not on three other pages of yours? | Merge it into the stronger page and redirect, or give it something only it can say |
| Nothing links to it | Search your own site for the URL. If only the sitemap knows about it, that is the problem | Link it from at least three relevant pages, with the topic as the anchor text |
| Competing with your own page | Two URLs aimed at the same query | Pick one, redirect the other. Google already picked one; this is just you agreeing |
| Low site-wide trust | Is it only new pages, or everything? | Nothing page-level will fix it. This is a whole-site problem, age, links, and published depth |
| Crawl budget spent on rubbish | Crawl stats: how many requests go to filters, tags, search and parameter URLs? | Block the rubbish in robots.txt so the budget reaches the pages that matter |
| It is genuinely new | Published in the last few weeks on a small site | Nothing. Give it time |
The test that settles it
Take a distinctive sentence from the page (fifteen words, something nobody else would write) and search it in quotes. If Google returns your page, it is indexed and the report is stale. If it returns nothing, it genuinely is not, and the table above is where to start.
Then use URL Inspection → Test live URL and read the rendered HTML, not the source. If your content only appears after JavaScript runs and the rendered view is empty, you have a rendering problem wearing an indexing problem’s clothes, and no amount of content work will fix it.
While you are there, check the page returns a plain 200. Redirects, soft 404s and server errors are a different problem with different fixes, and Google’s notes on how HTTP status codes affect Search explain how each one is treated.
How long it takes once you have fixed it
Longer than anyone wants. Requesting indexing puts the URL in a priority queue, not at the front of it, and the request is re-evaluated against the same judgement that excluded it. On a small site expect days to a few weeks after a genuine improvement; on a new site, longer. Requesting indexing repeatedly does not help and the daily quota exists for that reason.
The one thing that reliably shortens it is internal links from pages Google already crawls often, usually your home page, your main service pages and your most recent posts. A new page linked from three of those gets looked at again much sooner than one sitting alone in the sitemap. That is the same mechanism behind the internal linking mistake that buries good content, and why new pages take months to get indexed in the first place.
If a whole section of your site is sitting in this report rather than a page or two, that is a structural problem rather than a content one, start here instead.
When it’s a structural problem
If large batches of legitimate pages stay unindexed for months, the issue is usually architecture: weak internal linking, template-generated near-duplicates, or a site Google has classified as low-trust. That’s a build problem more than a content problem, the kind of thing that gets engineered out when a site is structured properly from the start, and the kind of thing worth catching in a regular maintenance review before it compounds for a year.
Getting indexed is only the first half. A page that ranks still has to turn visitors into customers, and that is where many small business sites fall down next. Why your clinic website isn’t booking appointments and why restaurants lose money to delivery apps are two examples of that second problem.
