Why Is My Page Not Indexed? Diagnosing Crawled vs Discovered, and the Fix

You publish a page, wait a week, search for it with site:yourdomain.com/the-url, and nothing comes back. The page is live and loads fine, yet the search engine acts as if it doesn't exist. A page that isn't indexed can't rank at all — and the reason is almost never the one people assume, so the fix is almost never rewriting the page or buying links.

The takeaway up front: "not indexed" is a diagnosis, not a single problem. Google's reporting splits the most common cases into two distinct states — Crawled, currently not indexed and Discovered, currently not indexed — with nearly opposite causes and fixes. Confuse them and you'll spend days on the wrong repair. Read the exact status first; the wording is the diagnosis.

Indexing is a separate step from crawling

A search engine has to find your URL, crawl it, index it, and only then rank it — and a page can stall at any stage. Indexing is the step where otherwise-fine pages quietly get stuck; the full pipeline is in how search rankings work.

The key insight: being crawled does not guarantee being indexed. Search engines fetch far more pages than they keep. Indexing is a judgment call — is this page worth storing and serving? — and "no" is a normal answer for thin, duplicate, or low-value URLs. The question isn't only "can the engine reach my page?" but "has it decided my page earns a slot?"

Read the exact status in Search Console first

Don't guess. Run URL Inspection in Google Search Console on the specific URL, or open Pages → "Why pages aren't indexed." The status string it returns is the most useful signal you have. The two that trip people up most:

• Discovered — currently not indexed. Google knows the URL exists (from a sitemap or a link) but hasn't crawled it yet — a priority problem, often a sign Google is rationing crawl effort on your site.
• Crawled — currently not indexed. Google fetched the page and chose not to index it — a value judgment, not a technical block.

Those look almost identical in a dashboard and mean very different things; everything below hinges on which one you see. The remaining statuses — "Excluded by 'noindex' tag," "Duplicate, Google chose a different canonical," "Soft 404" — name their cause directly, which is why reading the literal status beats theorizing.

"Discovered — currently not indexed": a crawl-priority problem

Here the page was never fetched — Google found the URL and parked it in a queue it hasn't reached. That usually traces to one of these:

• Crawl budget rationing. On large or slow sites, Google limits how much it fetches. If your server is sluggish or you have tens of thousands of low-value URLs (faceted filters, session-ID parameters), the important pages wait behind the junk.
• Weak internal linking. A page buried deep, or linked from nowhere, signals low importance. Crawlers prioritize pages that are well-linked from pages they already value.
• Server strain or errors. Timeouts and 5xx responses make Google back off and crawl less.

The fixes target priority, not content:

1. Link to the page from somewhere that matters — a relevant hub, category page, or popular existing article. An internal link is the strongest "this is worth crawling" signal you can send for free.
2. Trim crawl waste. Block or canonicalize the low-value parameter and filter URLs so crawl effort flows to real pages.
3. Keep your sitemap clean — only canonical, indexable URLs, no redirects or 404s.
4. Fix server speed and errors so the crawler isn't throttling itself. Requesting indexing can nudge one URL, but won't fix the underlying priority at scale.

"Crawled — currently not indexed": a value problem

This is the harder, more common, and more misunderstood case. Google fetched the page and decided it wasn't worth a slot. No technical block is involved, so re-requesting indexing usually does nothing — you're asking the engine to reconsider a verdict it reached on the merits. Typical reasons:

• Thin or duplicative content. It restates what other pages (yours or others') already say. Tag pages, near-empty product variants, boilerplate listicles, and near-copies of another URL are classic offenders — Google keeps the stronger version and skips the rest.
• Low perceived value or trust on new or low-authority sites — the engine is conservative about what it stores until a site proves itself.
• No real demand. Some pages answer a question nobody searches, so indexing them gains the engine nothing.

The fix is editorial, not technical:

1. Make the page substantively better than the alternatives — original detail, a clearer answer, something a searcher can't get from what's already indexed. "Worth storing" is the bar.
2. Consolidate near-duplicates. Merge thin pages into one strong page and redirect the rest, instead of asking the index to hold five weak versions.
3. Prune or noindex pages that shouldn't compete (low-value tag archives, internal search results). Removing dead weight raises the average quality of what's left.
4. Strengthen internal links so the page reads as a valued part of the site, not an orphan. Only then request indexing — once the page deserves a slot, the nudge has something to act on.

Rule out the simple blockers before anything else

A surprising share of "won't index" panics are a one-line technical mistake. Check these before assuming a crawl-priority or quality problem:

• A stray <meta name="robots" content="noindex"> (or X-Robots-Tag header) left on by a theme, plugin, or staging config.
• A Disallow in robots.txt blocking the path. (The trap: robots.txt blocks crawling, so Google may never even see a noindex on a blocked page — un-disallow it so the directive can be read.)
• A canonical tag pointing at a different URL, telling Google to index that one instead.
• The page returning a non-200 status (404, 410, redirect, or 5xx) to the crawler even though it looks fine in your browser.

If any of these is the culprit, no content work helps until it's cleared — which is why the order is always: rule out blockers first, then read the exact status, then apply the matching fix.

FAQ

How long should I wait before worrying a page isn't indexed?

Days to a couple of weeks is normal, especially for new or low-authority sites — indexing isn't instant and isn't guaranteed. If a page still isn't indexed after that, inspect it in Search Console rather than waiting longer; the status string tells you whether it's a crawl-priority issue, a quality verdict, or a simple blocker like a noindex tag.

Does requesting indexing force Google to index my page?

No. "Request indexing" asks Google to re-crawl and re-evaluate sooner; it doesn't override the engine's judgment. If the page is Crawled, currently not indexed because it was deemed low value, re-requesting won't change the outcome until you've improved the page. It's a useful nudge for a genuinely indexable page, not a workaround.

Can a page rank without being indexed?

No — indexing is a prerequisite for ranking. A page that isn't in the index can't appear for any query, however strong its content or backlinks. That's why an indexing problem is worth fixing before you invest in on-page work or link building for that page.

Next step

Before you touch the content, the layout, or your link budget, open Search Console and run URL Inspection on the page that won't index. Read the literal status, then apply the matching fix: a stray noindex or robots.txt block, a crawl-priority problem, or a page that simply didn't earn its slot. The diagnosis lives in that one status string — get it right, and you stop fixing the wrong thing. For tools to track where your pages actually stand, visit sbranker.com.