This guide is for owners whose site is already set up — Search Console connected, sitemap submitted, nothing obviously blocked — but who still have pages that won’t index. If you’re starting from scratch, our beginner guide on getting found by Google covers the foundations. Here we tackle the harder, more common situation past setup: pages stuck under “Crawled – currently not indexed,” “Discovered – currently not indexed” and similar, where the cause is rarely a simple block and more often crawl budget, duplication or — increasingly in 2026 — quality. We’ll read the report properly and fix the specific reason each page is stuck.
The single biggest mistake is guessing at fixes instead of reading what Google already told you. In Search Console, the Page Indexing report (under Indexing then Pages) groups your not-indexed pages by reason, and each reason points to a different fix. Learn what the common ones actually mean before changing anything:
Use the URL Inspection tool on any specific page for its exact status and the reason. Match each cluster of pages to its cause, and you have a prioritised fix list instead of a guess.
Deal with the unambiguous ones first because they’re fast. Pages marked blocked by robots.txt point back to a disallow rule you can remove if the page should be public. Pages excluded by a noindex tag have an instruction — often a leftover from development or a misconfigured plugin setting — telling Google to stay out; find and remove it where it shouldn’t be. Redirect and 404 statuses mean the URL doesn’t resolve to indexable content; fix the link or the redirect target. Use URL Inspection to confirm Google sees the corrected version, then request indexing for the important ones. These are the “easy” recoveries — but on a maintained site they’re usually the minority.
This is the big one in 2026, and it’s the one owners resist because the fix isn’t a setting. When Google has crawled a page and declined to index it, it’s usually saying the page isn’t worth a place in the index: too thin, too similar to other pages, or offering nothing a searcher needs. Google has become markedly pickier about what earns indexing, evaluating content quality before granting shelf space.
The fix is to make the page genuinely worth indexing. Thin pages — a few lines of text, a near-empty category, an auto-generated tag archive — either need substantial, useful content added or should be removed or deliberately noindexed so they stop diluting your site. Near-duplicate pages (several pages saying almost the same thing, or product variants with identical descriptions) should be consolidated into one strong page or differentiated meaningfully. And every page you do want indexed should answer a real need clearly and completely.
A practical way to judge each stuck page: ask what a searcher would gain from it that they can’t get from another page on your site or a competitor’s. If the honest answer is “nothing much,” that’s why it’s not indexed, and the options are to make it substantially better or to let it go. This is uncomfortable because it often means admitting that pages you created — perhaps to chase a keyword, or because a template generated them — aren’t actually useful. But indexing is not a participation prize; Google is allocating limited index space, and a smaller site of strong pages consistently outperforms a large site padded with weak ones. Counterintuitively, removing or noindexing hundreds of thin pages frequently raises how much of the rest gets indexed, because it stops diluting the site’s overall perceived quality and frees crawl budget for the pages that deserve it. Be honest: if a page exists only to target a keyword and offers nothing more, Google’s judgement is probably correct, and your effort is better spent strengthening fewer, better pages than forcing weak ones in.
If you have a large site and see many pages stuck at “Discovered – not indexed,” crawl budget is likely in play. Google only fetches a certain number of URLs from your site in a given window, and that number is set by two things: how fast and reliably your server responds (crawl capacity — a slow or error-prone server makes Google back off), and how much Google actually wants your content (crawl demand — driven by your site’s perceived importance and how often it changes). If the budget you do have is spent on low-value URLs — faceted-search and filter combinations, session parameters, endless thin archives, duplicates — your genuinely important pages sit waiting in the queue, which is exactly what “Discovered – not indexed” at scale is telling you.
Reclaim the budget by stopping Google wasting it. Use robots.txt to keep crawlers out of admin areas, internal search results and parameter-driven duplicate URLs. Noindex or remove low-value pages like empty tag archives and filtered variants so Google stops re-crawling them. Make sure your important pages are well linked internally so Google can reach them easily, and that your sitemap lists only the canonical pages you actually want indexed — never URLs you’ve blocked or noindexed, which sends contradictory signals. A fast, responsive server also raises how much Google is willing to crawl. The goal is simple: point Google’s limited attention at the pages that matter.
Mixed signals cause their own indexing problems and duplication. Your sitemap, your canonical tags and your internal links should all agree on which version of a page is the real one. If your sitemap pushes a URL your site treats as a variant of another, or your internal links point at a different version than your canonical names, Google has to guess — and often indexes something other than what you intended, or nothing. Pick the canonical version of each page, make the sitemap list only those, point internal links at them, and ensure the canonical tag on each page agrees. Consistency here resolves a surprising share of “duplicate” and “wrong page indexed” statuses. A Site Audit surfaces conflicting signals and broken internal links across the site.
After fixing a cause, use URL Inspection to confirm Google now sees the page as indexable, then request indexing for your priority pages — but use it sparingly and only once the underlying problem is fixed, because requesting indexing on a page that’s still thin or blocked does nothing. Then watch the Page Indexing report over the following weeks: indexing isn’t instant, and a genuinely improved page can take days to a few weeks to move into the indexed group as Google re-crawls and re-evaluates. Track whether the count of indexed pages is rising and whether your fixed clusters are shrinking. Re-run a Site Audit periodically to catch new issues before they pile up.
An owner finds 180 pages under “Crawled – currently not indexed” and assumes it’s a technical fault. URL Inspection shows the pages are reachable and unblocked — Google simply chose not to index them. Looking closely, most are near-identical: auto-generated tag archives and thin location pages with a sentence each. The cause is quality and duplication, not a setting. The owner noindexes the tag archives, consolidates the thin location pages into a handful of genuinely detailed ones, and removes a batch of empty pages entirely. They tidy the sitemap to list only the real, canonical pages and block the internal-search URLs that were eating crawl budget. Over the next few weeks the indexed count climbs as Google re-crawls and the remaining, stronger pages earn their place — while the junk that was dragging the site down is gone. Nothing was “broken”; the site was asking Google to index pages that didn’t deserve it.
The recurring ones: assuming “not indexed” is always technical when it’s often quality. Forcing thin or duplicate pages instead of improving, consolidating or removing them. Letting auto-generated archives and filter URLs eat crawl budget. A sitemap that contradicts your canonicals or lists blocked pages. Spamming “request indexing” without fixing the cause. And expecting instant results, then changing more things before the first fix had time to take.
Google visited the page but chose not to store it, usually a quality or duplication judgement rather than a technical fault. The fix is to make the page genuinely more useful and unique, or to consolidate or remove it if it isn’t.
“Discovered” means Google knows the page exists but hasn’t crawled it yet, often a crawl-budget or priority signal. “Crawled” means it has visited and decided not to index it, usually a quality or duplicate issue.
Most often because Google judged them not worth indexing: thin, duplicate or low-value. Improve, consolidate or remove weak pages, and focus on fewer, stronger ones.
It’s how many URLs Google will fetch from your site in a window. It matters on larger sites: if low-value URLs eat the budget, important pages wait. Block junk, remove thin pages, and link your important pages well.
Yes, but only after fixing the underlying cause, and sparingly. Requesting indexing on a page that’s still thin, duplicate or blocked won’t help.
Days to a few weeks, as Google re-crawls and re-evaluates. Watch the Page Indexing report for the indexed count rising and your problem clusters shrinking, rather than changing more things too soon.