Pages not indexed? Fix your index coverage issues

If your pages not indexed count keeps climbing in the Page indexing report, the fix depends entirely on which status Google assigns. According to Google's Search Console documentation, an unindexed URL falls into a small set of states, and the two that trap the most legitimate content are Discovered - currently not indexed and Crawled - currently not indexed. They look similar in the interface but they are opposite problems: one means Google has not bothered to fetch the page yet, the other means Google fetched it and decided it was not worth keeping. Treat them the same way and you will waste weeks. This guide separates the two, gives you a status-to-action table you will not find in most single-status write-ups, and walks the technical and editorial fixes in the order that resolves them fastest.

What does Discovered - currently not indexed actually mean?

It means Google knows the URL exists but has chosen not to crawl it yet. Discovery succeeded, crawling was skipped.

Google usually learns about the URL from your sitemap or an internal link, then puts it in a queue. When Google's systems predict the page is low priority, it can sit in that queue for weeks. As Search Engine Land explains, this is often a crawl-scheduling and site-authority signal rather than a verdict on the individual page, because Google has not read the content yet. Two levers move it: give Google a stronger reason to crawl (more internal links from important pages, inclusion in a lean sitemap) and reduce competing low-value URLs that eat your crawl allocation. This is where crawl budget optimization and a tidy log-file analysis earn their keep on larger sites.

What does Crawled - currently not indexed mean, and why is it worse?

It means Google fetched the page, evaluated it, and chose to leave it out of the index. This is the more serious of the two states because Google has already formed an opinion.

The usual culprits are thin or duplicate content, weak topical differentiation, and a lack of trust signals. Onely's analysis frames it plainly: Google saw the page and judged it not valuable or unique enough to store. On the July 16, 2026 Search Off the Record episode, Google's John Mueller said that when Google's systems have serious doubts about a site's overall quality, they crawl less and index less, and he named undifferentiated AI-generated content as a live trigger for those doubts (reported here). So a rising Crawled - currently not indexed count is often a site-wide quality tell, not a per-page accident. Fixing it means addressing duplicate content and lifting the page above the threshold Google is willing to store.

Discovered vs Crawled not indexed: which fix applies?

Use the URL Inspection tool to read the exact status, then match it to the root cause and the action. This side-by-side view is the information-gain element most articles skip, because they cover only one status in isolation.

Read the status first, then act. Sending an improve-the-content fix at a Discovered URL, or a build-more-links fix at a low-quality Crawled URL, wastes effort on the wrong lever.

How do I confirm the real reason with the URL Inspection tool?

Open the URL in Search Console's inspection tool and run a live test. It shows the current status, the canonical Google chose, whether the page is blocked, and the rendered HTML Google sees.

Check four things in order. First, is a noindex present in the meta robots tag or HTTP header. Second, does robots.txt block the path (a blocked URL cannot be crawled and can still be indexed without content, which is its own problem). Third, does Google's chosen canonical match your declared canonical, because a mismatch signals duplication. Fourth, does the rendered HTML contain your main content, since JavaScript that fails to render can leave Google with a near-empty page. Our Google Search Console guide walks these panels in detail, and the broader technical SEO checklist covers the crawl and render layers behind them.

Do sitemaps and internal links really move unindexed pages?

Yes, but they do different jobs. A sitemap is a discovery and priority hint, not an indexing command. Internal links are the stronger authority signal.

Mueller has been explicit that Google treats sitemaps as discovery and priority signals rather than instructions, and that when a sitemap fills with low-value, duplicate, or blocked URLs, Google starts trusting it less. So the highest-leverage sitemap move is subtraction: list only canonical, indexable, valuable URLs. On the linking side, a page that no important page links to is effectively invisible in your architecture. Add contextual links from your strongest hubs and reduce orphan pages so authority flows to the URLs you want indexed. This is exactly the payoff of a deliberate topical authority cluster structure, where hub pages feed crawl signals to their supporting articles.

Is crawl budget the reason my pages are not indexed?

For most sites, no. Crawl budget is widely over-blamed. Mueller has said crawl budget is over-rated and that most sites never need to worry about it.

Per Google's large-site crawl guidance, crawl budget only becomes a real constraint for sites in the range of roughly a million or more URLs, or sites that publish very large volumes daily. If you run a few hundred or a few thousand pages and content is stuck at Discovered, the bottleneck is almost always priority and authority, not a hard crawl ceiling. The exception is when your own site wastes the budget it has: infinite faceted URLs, session parameters, and endless pagination can drown your real pages. Controlling those with faceted navigation rules and clean URL structure frees crawling for the pages that matter.

How do I fix Crawled - currently not indexed for good?

Raise the page above Google's storage threshold or remove it. There is no request-indexing shortcut for a page Google already judged and rejected.

• Consolidate duplicates. If several pages cover the same intent, merge them into one stronger URL and redirect the rest, which concentrates signals instead of splitting them.
• Add genuine depth. Answer the query more completely than the pages that do rank, with specifics, examples, and first-hand detail that generic or AI-spun text lacks.
• Strengthen trust. Clear authorship, sources, and evidence matter, and they matter more on YMYL topics where Google's bar is highest.
• Prune what cannot be saved. Thin tag archives and near-empty pages are better removed or consolidated than defended. A structured content pruning audit lifts site-wide quality signals, which is exactly what Mueller described as the lever behind crawl and index decisions.

After a real improvement, use URL Inspection to request indexing once. Requesting repeatedly without changing the page does nothing.

How long should indexing take, and when should I worry?

There is no fixed timer. A page can be indexed within hours or sit for weeks depending on site authority, internal linking, and quality signals. Google itself declines to give a guaranteed timeframe.

A practical rule: for an established site with solid internal links, a genuinely useful new page that stays Discovered or Crawled not indexed for more than a few weeks is signaling a problem, not just slow scheduling. Rule out the mechanical blockers first (noindex, robots.txt, canonical conflicts, broken render), then treat persistent Discovered states as a priority and authority issue and persistent Crawled states as a quality issue. Note that indexing is also not permanent: pages can drop out later if quality signals fall, which is why ongoing pruning and internal linking matter more than a one-time push. Disclosure: this article is written by the team behind Sorank, which is why we lean on Search Console data rather than guesswork for these calls.

Frequently asked questions

Related guides