Crawled, currently not indexed, and what Google is actually telling you.

First, separate it from "discovered"

These two statuses sit next to each other and mean opposite things, and treating them the same is the most common wasted effort here.

• Discovered, currently not indexed. Google knows the URL exists but has not fetched it. This is a crawling and discovery problem: not enough internal links pointing at it, buried too deep, or a large site where crawl capacity is being spent elsewhere.
• Crawled, currently not indexed. Google fetched the page, read the content, and chose not to index it. Discovery worked. The page was assessed and did not make the cut.

The five causes, in the order worth checking

1. The page has nothing that is not already elsewhere

The most common cause by a distance. Thin location pages spun from a template with the town name swapped, product variants differing by one attribute, tag archives listing the same three posts, or category descriptions repeated across a dozen pages. Google can index it, and has decided a near-identical page is already covering the query.

We have diagnosed this on a live site where the copy was machine spun: readable at a glance, hollow on the second read, produced to fill a template rather than answer a question. The full write-up of that diagnosis is in a strong domain ranking for nothing.

2. Nothing on the site treats the page as important

Internal links are how you tell Google which of your pages matter. A page reachable only from a sitemap, or from one link in a footer block that points at everything, is a page your own site is not vouching for.

The trap is over-correcting. A templated block linking to everything passes a thin, undirected share to each destination. On one site, cutting a 25 link block down to five chosen, relevant links did more for the target pages than any single one of the twenty-five had. Fewer links, each deliberate.

3. The site is spending its crawl allowance on rubbish

On a large site, Google allocates finite effort. If most of that is going into filter combinations, session parameters, calendar pages and endless faceted URLs, real pages queue behind them. This shows up as both statuses climbing together while the pages you care about sit unindexed.

The fix is upstream: stop generating and linking to URL combinations nobody needs, handle parameters, and keep the crawler on pages that can rank. This is architecture work rather than page-level work.

4. Duplicates across locales or domains

UK and US English versions of the same page are near duplicates by definition. Without correct hreflang and canonical handling, Google indexes one and leaves the other here. It looks like a content quality problem and is actually a declaration problem, which is why it is worth ruling out before rewriting anything. This is covered properly under international SEO.

5. It is genuinely new

A recently published page on a site without much authority can sit in this status for weeks and then index on its own. Before assuming a fault, check how long it has actually been live. Requesting indexing repeatedly does not speed this up and is not a fix for anything.

The honest part: sometimes the answer is to delete it

If a page exists because a template generated it rather than because someone needed it, the correct action is usually to remove it, not to improve it. A site with 400 pages where 120 are thin is not a site that needs 120 rewrites. It is a site that needs 120 fewer pages.

This is the advice people least want and it is frequently the cheapest. Consolidating ten thin pages into two good ones removes the duplication, concentrates the internal links, and gives Google something worth indexing, all in one move.

What does not work

• Requesting indexing over and over. It re-queues a fetch. Google already fetched it. The verdict was on the content.
• Adding words to hit a count. Padding a thin page makes it a longer thin page. Depth means covering what the query needs, not reaching a number someone quoted.
• Resubmitting the sitemap. Sitemaps aid discovery. This page was already discovered and crawled.
• Blaming crawl budget on a small site. If you have a few hundred pages, crawl capacity is not your constraint. Cause one is.

The checklist

• Confirm the status is "crawled" and not "discovered". They need different work.
• Read the page as a stranger. If it reads as filled rather than written, that is your answer.
• Count the internal links pointing at it, and check they come from relevant pages rather than a blanket block.
• On a large site, check what proportion of crawl is going into parameter and filter URLs.
• Rule out locale and cross-domain duplication before rewriting.
• Check the publish date before treating it as broken.
• Ask whether the page should exist at all. Often it should not.

Work in that order and most of these resolve into one of two outcomes: a page that deserved to exist and needed saying properly, or a page that never needed to exist. Both are fixable. Neither is fixed by resubmitting anything.