How to Fix “Discovered – Currently Not Indexed” in Google Search Console

Seeing “Discovered – currently not indexed” in Google Search Console? Learn what it means for your WordPress site and how to get those pages crawled and indexed.

You published a great post, submitted your sitemap, and waited. Days later you open Google Search Console, check the Pages report, and find your URL sitting under a status called “Discovered – currently not indexed.” Google knows the page exists. It just… has not looked at it. And until it does, that page cannot rank for anything.

This is one of the most misunderstood statuses in Search Console, and it worries WordPress owners more than almost any other. The good news is that it is rarely a penalty and rarely permanent. It is Google telling you something specific about how it sees your site — and once you understand what, you can usually fix it. Here is what “Discovered – currently not indexed” actually means and how to get those pages crawled and indexed.

💡 Quick Answer: What This Status Means and What to Do

  • What it means: Google has found the URL (usually via your sitemap or internal links) but has chosen not to crawl it yet. The page has not been indexed because Googlebot never fetched it.
  • Most common causes: a new or low-authority site, thin or duplicate content, weak internal linking, or crawl budget being spent on low-value URLs.
  • The fix: strengthen the page (content and internal links), improve overall site quality and crawlability, then use the URL Inspection tool to request indexing — and give it time.

“Discovered” vs “Crawled” – Know the Difference

These two statuses look similar but point to different problems, so identify yours first:

  • Discovered – currently not indexed: Google found the URL but has not fetched it at all. This is usually about crawl priority — Google is not convinced the page is worth the crawl yet.
  • Crawled – currently not indexed: Google did fetch the page but decided not to index it. This is usually a quality or duplication judgement about the page itself.

This guide focuses on “Discovered,” but many of the same fixes help both, because both come down to the same root question in Google’s eyes: is this page, on this site, worth indexing?

Why Google Discovers a Page But Does Not Crawl It

Googlebot does not crawl every URL the instant it finds it. It allocates a limited “crawl budget” to each site based on how much it trusts and values that site. When a page sits in “Discovered,” one or more of these is usually true:

  • Your site is new or low-authority. Fresh domains get a small crawl budget until they build a track record. This is the single most common reason and it eases with time.
  • The page looks thin or templated. If the content is short or resembles many other pages, Google deprioritises it.
  • Weak internal linking. If few or no pages link to the URL, Google reads it as unimportant. Orphan pages get stuck here constantly.
  • Crawl budget wasted elsewhere. Endless tag archives, paginated pages, search-result URLs, and parameter variations can soak up crawl budget that should go to real content.
  • Server or speed issues. If your host responds slowly or with errors, Googlebot backs off to avoid overloading it.

Step 1: Rule Out the Simple Blockers

Before improving content, confirm you are not accidentally telling Google to stay away. In Search Console, run the URL through the URL Inspection tool (the search bar at the top) and check:

  • Is it blocked by robots.txt? A stray disallow rule can stop crawling entirely. You can build a clean, correct file with our robots.txt generator for WordPress.
  • Is there a “noindex” tag? Check that the page is not set to noindex in your SEO plugin, and that WordPress’ Settings → Reading → “Discourage search engines” box is unchecked.
  • Is the canonical pointing elsewhere? If the page’s canonical URL points to a different page, Google will index that one instead.
  • Is it actually in your sitemap? Confirm the URL appears in your XML sitemap and that the sitemap is submitted under Sitemaps in Search Console.

Step 2: Strengthen the Page Itself

If nothing is blocking it, the next job is to make the page obviously worth crawling. Give Google a reason:

  • Add real depth. Expand thin posts so they genuinely and completely answer the query, with specifics, examples, and detail a templated page would not have.
  • Make it distinct. If several of your pages target near-identical topics, merge them or differentiate them clearly so none look like duplicates.
  • Link to it from strong pages. Add internal links from your homepage, popular posts, or cornerstone content. This is the fastest signal you control — it tells Google the page matters and gives Googlebot a path to it.
  • Use descriptive anchor text. Link with text that describes the target page, not “click here,” so Google understands what the page is about before it even crawls.

Step 3: Improve Site-Wide Crawlability

“Discovered” is often a whole-site signal, not a single-page one. Raising overall quality lifts every stuck URL:

  • Trim low-value URLs. Consider setting thin tag or author archives to noindex so crawl budget flows to real content instead of near-empty pages.
  • Fix broken links and redirect chains. These waste crawl budget and frustrate Googlebot.
  • Speed up your site. A faster server and lighter pages let Googlebot crawl more per visit. Good caching and a decent host make a real difference.
  • Keep publishing quality content. A site that regularly ships genuinely useful posts earns a bigger crawl budget over time.

Step 4: Request Indexing (the Right Way)

Once the page is genuinely improved and well linked, give Google a nudge:

  1. In Search Console, paste the URL into the URL Inspection tool at the top.
  2. Click Request Indexing. This adds the URL to a priority crawl queue.
  3. Do this once per page. Repeatedly requesting the same URL does not speed it up — it just adds noise.

Requesting indexing is a nudge, not a command. If the underlying reasons are unaddressed, Google may still hold off. Fix the cause first, then request — that combination is what actually works.

How Long Should You Wait?

Patience is genuinely part of the fix. On an established site a page may move from “Discovered” to indexed within days. On a new site it can take several weeks, sometimes longer, no matter what you do — Google is still learning to trust the domain. As long as you have ruled out technical blockers and the content is strong, the usual prescription is: improve, request once, and wait. Re-check the Pages report every week or two rather than obsessing daily.

If a large share of your site is stuck, or pages that used to be indexed have dropped out, that points to a bigger crawlability or quality issue worth a proper audit. Our free WordPress consultation is a good place to start, and our WordPress care plans cover technical SEO health as part of keeping a site fast and crawlable. And if you have recently moved things around, double-check nothing broke by making sure your other site systems are still working too.

Frequently Asked Questions

Is “Discovered – currently not indexed” a penalty?

No. It is a crawl-priority status, not a manual action or penalty. Google simply has not decided the page is worth crawling yet. Improve the page and your site’s overall signals and it usually resolves on its own.

Will requesting indexing every day help?

No. Request it once after you have improved the page. Spamming the button does not raise your priority and can look like a low-quality signal. Fixing the underlying cause is what moves the needle.

Should I noindex tag and archive pages?

Often, yes. If your tag, author, or date archives are thin and duplicate your posts, noindexing them focuses crawl budget on the content you actually want ranked. Keep archives indexed only where they add unique value.

About the author

zaibbteam

WordPress developer sharing practical fixes, tutorials, and website improvement tips.

View all guides