Discovered — Currently Not Indexed: What Actually Fixes It on WordPress

Discovered — currently not indexed means Google knows the URL exists (it saw it in your sitemap or a link) but has chosen not to crawl it yet. On WordPress sites with thousands of listing pages this is a crawl-budget signal, not a penalty. The levers that matter are sitemap coverage, crawl accessibility and patience.

Quick answer

Fix the mechanical issues you control: make sure the URL is in a sitemap that serves 200 with an index, follow header, is not blocked by robots.txt, has no stray noindex, and is reachable by crawlers (check that wp-cron and your firewall agree). Then wait — Google paces discovery of large new content pools over weeks. Re-requesting indexing one URL at a time helps the pages you care about most, not the whole pool.

Why it happens

Sitemap coverage gaps. If your sitemap contains fewer URLs than you have published posts, Google's view of your inventory is smaller than yours. Compare the sitemap's URL count to your published-post count; mismatches of thousands are common after bulk imports.
Serving bugs upstream of the crawl. A noindex header on the sitemap (see the sitemap noindex fix), robots.txt asset blocks, or a blocked wp-cron all reduce Google's confidence before it even visits.
Crawl budget. Large WordPress sites (thousands of product or listing pages) get paced. New sites get paced more.
Content duplication. Thousands of near-identical template pages tell Google most of the pool adds nothing; it will sample slowly instead of indexing everything.

The DIY checks, in order

Count your sitemap URLs vs your published posts. Both numbers and the delta tell you the story.
Sample URLs from the sitemap: check for 200 responses, self-canonicals and index/follow headers.
Verify robots.txt does not block /wp-includes/ or /wp-content/ CSS/JS paths that Google needs to render.
Use the URL Inspection API in Search Console for per-URL verdicts on a sample.
Resubmit the sitemap, then give it weeks. Re-check the report, not the individual URLs, for the trend.

The Brambyl route

The sitemap coverage check compares sitemap URL count against your published-post count and flags mismatches; the sitemap dead-URLs check samples the sitemap for non-200s; the robots asset-block check catches the silent rendering blockers. Together they remove the mechanical reasons Google defers crawling. The waiting part stays yours — anyone promising same-day indexing of a 5,000-URL pool is selling something.

FAQ

How long does Discovered — currently not indexed take to clear?

For large inventories, expect weeks, not hours. Small sites with high-quality pages move faster. The verdict to watch is the trend in Search Console's Pages report.

Should I request indexing for every URL?

Search Console rate-limits bulk requests, and the queue is not your crawl budget. Request your priority pages; fix the mechanical issues for the pool.

Is Discovered the same as Crawled — not indexed?

Crawled — not indexed means Google looked and chose not to index; Discovered means it has not looked yet. Discovered is more likely to be crawl-budget or mechanical; Crawled is more likely a content-quality call.