Skip to content
MixTool

SEO & Websites

Discovered – Currently Not Indexed: Causes and Fixes

"Discovered – currently not indexed" means Google knows the URL but hasn't crawled it. Learn why it happens, how long it lasts and what gets pages indexed.

By MixTool Team3 min read

In Google Search Console's Pages report, "Discovered – currently not indexed" means Google knows the URL exists but hasn't crawled it yet. It isn't an error, and nothing is blocking the page. Google has simply put it in a queue and not got round to it.

On new sites, it's common for most pages to sit in this state for a while. Here's why it happens and what actually moves pages out of it.

What the status means

According to Google, a URL in this state was found, usually through a sitemap or a link, but crawling was postponed. Google often reschedules the crawl because it expected crawling to overload the site, but in practice the status also shows up when Google doesn't yet see the pages as a priority.

Compare it with the related status:

StatusWhat happenedWhat it usually means
Discovered – currently not indexedFound, not yet crawledLow crawl priority or limited crawl capacity
Crawled – currently not indexedCrawled, but Google chose not to index itGoogle didn't find the page valuable or distinct enough, for now

Neither status means the page is blocked. If a page were blocked, Search Console would say so, for example "Excluded by 'noindex' tag" or "Blocked by robots.txt".

Why Google isn't crawling your pages

Google decides how much to crawl a site partly based on how important it seems. A new site with few links from other websites gets a small crawl allowance, so a sitemap with hundreds of URLs can take weeks to work through.

Many pages look similar or thin

If the pages Google has already crawled are thin, duplicated or low-value, it becomes less eager to crawl the rest. Large numbers of near-identical pages, such as tag pages, filtered URLs or auto-generated content, are a common cause.

Pages are hard to reach

Pages that are only in the sitemap, with no internal links pointing to them, look unimportant to Google.

The server is slow or returns errors

When a server responds slowly or returns 5xx errors, Google crawls it more cautiously, which slows everything down.

How to fix it

1. Be patient with a new site

For a site that's a few weeks or months old, this status is normal. Most pages move on as Google's trust in the site grows. Don't panic and don't delete pages just because they're waiting.

Internal links are the strongest signal you control. Link new pages from your homepage, navigation, category pages and related articles. Google crawls those pages often and will follow the links.

3. Raise the overall quality of the site

Improve or remove thin, outdated or duplicate pages, or noindex the ones that have no search value. A smaller site of strong pages often gets crawled and indexed more completely than a big site of weak ones. Check pages with the SEO Score Checker to catch thin content and technical problems.

4. Keep your sitemap clean

Your sitemap should list only canonical, indexable pages that return 200, with accurate last-modified dates. Remove redirects, error pages and noindexed URLs. The Sitemap Validator checks the file against the sitemap rules and tests the first 50 URLs it lists.

5. Check server health

Make sure pages load quickly and don't return errors. In Search Console, Settings → Crawl stats shows response times and errors from Google's point of view. The Page Speed Checker helps find slow pages.

6. Request indexing for your most important pages

The URL Inspection tool's "Request indexing" button puts a single page in a priority queue. There's a limited daily quota, so use it for your most important new or updated pages, not for every URL.

Links from relevant, trusted sites tell Google your site matters, which increases how much it crawls. Listing your site in reputable directories in your field and creating content worth citing both help.

What not to do

  • Don't resubmit the same sitemap over and over. Google already knows about the URLs.
  • Don't use the Indexing API for ordinary pages. Google supports it only for job postings and livestream videos.
  • Don't pay for "instant indexing" services or bulk backlinks. They tend to create spammy links that can hurt the site.

How to check progress

Watch the Pages report in Search Console over a few weeks: the number of indexed pages should rise as pages leave the "Discovered" list. For a quick check on a single page, paste it into URL Inspection, or use the Google Index Checker. For a bigger list, the Index Status Checker checks up to 50 URLs at once for anything that would block indexing.

If you're not sure whether a page is blocked or just waiting, see why a website might not show up on Google for a full checklist.

Frequently asked questions

How long does "Discovered – currently not indexed" last?

There's no fixed time. On a new site it can last weeks or a few months. Internal links, a cleaner site and links from other websites usually shorten it.

Should I delete pages that are discovered but not indexed?

Not just for that reason. Delete or improve pages that are genuinely thin or duplicated. Useful pages that are simply waiting usually get indexed as the site gains trust.

Does requesting indexing fix it?

It can get a single important page crawled sooner, but there's a daily limit and it doesn't change how Google treats the rest of the site. Internal links and site quality matter more.

Is "Discovered – currently not indexed" a penalty?

No. It means Google hasn't crawled the page yet. Penalties appear separately, under Manual actions in Search Console.

Tools mentioned in this guide

Free, private and ready to use — no sign-up.