Lorixen.
EN

"Discovered, Currently Not Indexed": Why Google Has Not Even Crawled Your Page

Short answer: This label means Google has the address on its list, usually from your sitemap or a link, but has not yet requested the page. It is a different case from the "Crawled" variant, where Google did fetch the page and then passed on it. On a new or small site the cause is almost always low priority: little reason to visit, weak internal links, or a server that responds slowly. Improve the links to the page and the quality of the site, be patient for a few weeks, and request indexing only for the pages that matter most.

Which status is which

Search Console groups unindexed pages by the stage they stopped at. It helps to know the order: discovery, crawl, render, index decision.

  • Discovered: Google knows the address but has not fetched it. Nothing has been judged about your content yet.
  • Crawled: Google fetched it and held it back for now. That is a content or duplication question.

So the first status is about scheduling, not quality. Google decides how much to crawl on a site from how fast the server answers, how much it has found valuable before, and how many URLs the site offers. A site with two hundred new pages and no history will see some wait in line.

Owner questions, answered

How long is normal to wait?

On a fresh domain, expect anything from days to a number of weeks. A page that stays in this state for months deserves attention. Check the "last crawled" information in URL Inspection, which shows "N/A" if it has never been fetched.

Is my server the problem?

Possibly. If pages take several seconds to respond, or the host returns errors under light load, Google slows down so it does not overload you. Open the Crawl Stats report under Settings and read the average response time and any host status problems. Repeated server errors can cause a sharp fall in crawling.

Are my internal links too weak?

This is the most common cause on small sites. A page listed only in the sitemap, with no navigation link, looks unimportant. Add links to it from pages that already get visits: the homepage, a relevant service page, a category page. Use descriptive anchor text, not "click here".

Did I publish too many thin pages at once?

Bulk-generated pages, such as hundreds of near-identical location pages, make Google cautious about the whole batch. If the first pages it samples look repetitive, it may hold off on the rest. Fewer, more distinct pages recover faster than a large dump.

Is a plugin or setting hiding the page?

Check that nothing blocks the URL and that the sitemap contains only live, indexable addresses. Redirected, noindexed or deleted pages in a sitemap waste attention.

A practical order of work

  1. Confirm the page is live and indexable. Open it in a private window and check it returns 200, is not noindexed, and carries a self-referencing canonical.
  2. Inspect the URL. In URL Inspection, read "Discovered" and "Last crawl". Run the live test to prove Googlebot can fetch it.
  3. Add links. Place at least two internal links from established pages, ideally in the body copy where it makes sense for readers.
  4. Prune the sitemap. Remove URLs you do not want indexed, such as tag archives, parameter pages and thank-you pages, so the important ones stand out.
  5. Check speed and errors. Look at the Crawl Stats report. If response time is high, deal with hosting, caching or heavy plugins first.
  6. Request indexing selectively. Use the button in URL Inspection for your top few pages. It is a nudge, not a guarantee, and it has a daily limit, so do not use it for hundreds of URLs.
  7. Wait and recheck. Look again after two to three weeks, not the next morning.

What does not help

  • Submitting the same sitemap over and over.
  • Buying links or pinging services in the hope of speeding up a first visit.
  • Changing the page title repeatedly. The page has not been seen yet.
  • Resubmitting through the Indexing API. That tool is limited to specific page types such as job postings and livestreams.

What a healthy small site looks like

A tidy site with, say, forty pages usually sees most of them crawled within days of publishing, because every page is two clicks from the homepage and the server is quick. The "Discovered" queue grows when a site has more URLs than useful content: filtered category views, calendar pages, endless tag archives, or auto-created attachment pages. Treat the report as a prompt to ask which of those URLs deserve to exist.

Illustrative case: a Canadian bookkeeping firm publishes forty articles in one week on a two-month-old domain. Thirty stay in this status. The firm adds links from each service page to the two most relevant articles, trims the sitemap to the articles and service pages, and speeds up the host. Over the following weeks the queue shrinks without any repeated requests.

FAQ

Does this status affect other pages on my site?

Not directly, but a large pile of undiscovered or low-value URLs can reduce how eagerly Google crawls the rest, so tidy the list.

Should I delete pages that stay discovered for months?

If they have no purpose, yes, or merge them into a stronger page. If they matter, improve their links and content and wait.

Will social media shares get the page crawled?

Links from social platforms rarely help. Links from other websites and your own strong pages are better signals.

Is it the same as "URL is unknown to Google"?

No. That means Google has not even found the address. Discovered means it has found it but not visited.

If you are launching a site and want a clean structure that gets crawled quickly, send us a note on our enquiry page.

Sources

WhatsAppBook a call