Debug "Discovered, currently not indexed" — the actual root causes

"Discovered, currently not indexed" is Google's polite way of saying: we know your URL exists, we've decided not to crawl it yet, and we may never get to it. It's the saddest status in Search Console because nothing is technically broken — Google has just decided your page isn't worth the bandwidth.

What "discovered" actually means

Google found the URL — usually from your sitemap or an internal link — and queued it for crawling. The queue is prioritized by perceived value. If your domain is new, your site has low authority, or the URL looks like duplicate/thin content, the queue may take weeks or months to advance. For some URLs, it never does.

The diagnostic checklist

1. Run the URL through the Status tab (URL Inspection API). Look at the "coverage state" and "crawl reason" fields.
2. Run the Indexability Audit. Specifically check: word count, canonical tag, internal link count, robots.txt rules, page speed (LCP), and structured data.
3. Confirm the URL is in your sitemap — sitemap inclusion is a stronger discovery signal than a single internal link.
4. Check for index-bloat: if your sitemap contains thousands of low-quality URLs, Google may downgrade trust in the whole sitemap.
5. Look for canonicalization conflicts: is your URL self-canonical or pointing elsewhere?

The most common actual cause: thin content

Google's threshold for "worth indexing" keeps creeping up. Pages under 300 words with little unique content (think tag pages, paginated archives, author profiles) increasingly land in Discovered-not-indexed. The fix isn't a Indexing API push — it's making the page substantive enough that Google's quality classifier flips. Then push.

Second most common: site authority

New domains and low-authority sites get less crawl budget. If you launched 6 months ago and have a flat backlink profile, the Indexing API helps but won't override Google's lukewarm interest. Build internal links, get a few quality external links, then push.

When Indexing API actually fixes it

• URLs Google discovered weeks ago that are stuck in queue.
• URLs that recently changed (you fixed the thin content issue, added internal links, etc.).
• URLs on a healthy domain that should index but got deprioritized for unclear reasons.

When it won't

• URLs Google has crawled and explicitly chosen not to index ("Crawled, currently not indexed" — different status).
• URLs with noindex meta tags or robots.txt blocks.
• URLs that 404, redirect, or return errors.
• URLs Google considers duplicates of a different canonical.