Discovered — currently not indexed

“Discovered — currently not indexed” means Google knows your URL exists but has not crawled it yet. It found the address — in your sitemap, or through a link — added it to the queue, and then chose not to spend a crawl on it for now. Nothing about your page’s content has been judged, because Google has not read it. This is a prioritization decision about your whole site, not a verdict on the one page.

Discovered is not the same as crawled

The two statuses sit next to each other in the Page indexing report and get treated as one problem. They are not. Crawled — currently not indexed means Google fetched the page, read it, and decided not to index it — a quality judgment you address by improving the page. Discovered means Google never fetched it at all. The page could be excellent; Google has not looked. That difference decides everything you do next: there is no point rewriting a page Google has not read.

Why Google leaves a URL discovered

Crawling costs Google money, so it rations attention across the whole web and across your site. A URL sits in the discovered state when Google has decided the site does not yet justify the crawl. The usual reasons, in rough order of how often they are the real one:

1. The domain is too new or too weak

A new site with few links has almost no crawl priority. Google discovers URLs from the sitemap, queues them, and works through them slowly because nothing signals that the site is worth prioritizing. This is the most common cause on small and recent sites, and the least satisfying, because the fix is partly time.

2. Too many low-value URLs competing for budget

If the site generates large numbers of thin or near-duplicate URLs — filter combinations, tag archives, session parameters — Google spends its limited crawl on those and starves the pages you care about. The queue is shared, and padding it with pages nobody searches for makes every page wait longer.

3. The URL is weakly linked or orphaned

Google infers importance from internal links. A URL reachable only from the sitemap, or buried five clicks deep, reads as low priority. A URL linked from the homepage or a well-linked hub reads as important and gets crawled sooner. This is the lever you actually control, and the one most worth pulling.

4. The server was slow when Google visited

Google watches how quickly your server responds and backs off if crawling seems to strain it. A consistently slow response time lowers your crawl rate, which lengthens the discovered queue.

What actually moves a URL from discovered to indexed

In the order that produces results:

Link to it from your strongest pages. The homepage is almost always the most-crawled, most-trusted page on a small site. A URL linked directly from it is discovered and crawled far faster than one that only appears in the sitemap. Add real, contextual links from your homepage and your best-performing pages to the URLs stuck in the queue. On a small site this single change clears most of the discovered list.

Cut the thin URLs competing for budget. Consolidate or control faceted and parameter URLs so Google is not spending its crawl on pages that will never be indexed anyway. Fewer, better URLs are crawled more completely.

Request indexing for the few that matter. In Search Console, use URL Inspection then Request Indexing on your most important stuck URLs. This works for a handful of pages, not hundreds — it is a nudge, not a pipeline. Use it on the pages that earn revenue, not the whole list.

Earn a few external links. A single link from a relevant site raises the whole domain’s crawl priority, which shortens the queue for every discovered URL at once. On a new domain this matters more than any on-page change.

Then give it time. Once the links are in place, crawling catches up over days to a few weeks. Note the date you made the change and judge it in a month, not a day.

What does not work

Resubmitting the sitemap repeatedly does nothing — Google already has the URLs; that is what “discovered” means. Requesting indexing on hundreds of URLs does not scale and can look like a signal to ignore. Adding more pages while pages are already stuck makes the queue longer, not shorter. And there is no meta tag or canonical trick that promotes a URL up the crawl queue — the queue is about site-level trust, which those tags do not change.

Does “discovered — currently not indexed” hurt your SEO?

Not directly. It is not a penalty, and it does not lower the rankings of the pages you already have indexed. A discovered URL simply is not in the index yet, so its only real cost is the traffic it cannot earn while it waits — an opportunity cost, not a punishment. The status describes a crawl decision, not a quality strike against the site.

The caveat is scale. One or two discovered URLs on an otherwise healthy site are normal and safe to ignore. A large and growing discovered count is worth acting on — not because the label harms you, but because it is usually a symptom of the thing that does: a site Google has decided is not yet worth crawling in full. Fix the cause — internal links and crawl budget, above — and the symptom clears with it.

If your site is on WordPress

WordPress produces this status more than most platforms for one structural reason: out of the box it generates a large number of thin, auto-created URLs — tag archives, category and author pages, date-based archives, and a separate “attachment” page for every image you upload. Each is a real URL in your sitemap competing for the same crawl budget as your actual content, which is reason 2 above at industrial scale.

The fix is to stop feeding the queue pages nobody searches for. In Yoast SEO or Rank Math, set the tag, author, date and attachment archives you do not need to noindex (attachment pages should also redirect to the media file itself), and keep only the taxonomy archives that genuinely serve readers. That alone often halves the number of URLs Google has to work through, which shortens the queue for the posts and pages you actually care about. It is the same principle as everywhere else here — fewer, better URLs get crawled more completely — WordPress just makes the cleanup more necessary.

Check the mechanics first

Before assuming it is an authority problem, rule out the boring causes. Confirm the URL is actually indexable — a stray noindex or a canonical pointing elsewhere will keep a page out regardless of crawl priority — and that it is present and correct in your sitemap. Then run a full site check to find the thin pages and broken links quietly draining the crawl budget the stuck URLs are waiting on.

For the wider picture of which report statuses are genuine problems and which are Google working normally, the Page indexing report reference covers the full list.