Skip to content
SearchSee plans and prices

"Discovered - currently not indexed" on WordPress: Google has not fetched the page yet

"Discovered - currently not indexed" means Google knows the address and has not fetched it. The help page explains the usual case as load: Google expected the crawl to overload the site and rescheduled it. The last crawl date is empty because there has not been one.

By
WP Ministry
Published

In short

  • Google found the address and has not crawled it. The help page's usual explanation is load on the site, not a judgment of the page.
  • The last crawl date is empty because there has not been a crawl. That is how the report shows the difference from "Crawled - currently not indexed".
  • A long list of filter, sort and archive addresses is the kind of pile Google's help describes. A page you wrote and linked is a different case.
  • Nothing on the site can force the crawl. Asking again does not change a crawl Google put off to spare the server.
  • Check that the server is answering and that you are not blocking Google before you treat the status as a fault.
  • The status is Google's to clear. A sandbox cannot make Search Console print it.

"Discovered - currently not indexed" means Google knows the address and has not fetched it. The Page indexing report's help gives the usual reason in one sentence: Google wanted to crawl the URL, expected that crawl to overload the site, and rescheduled it. The last crawl date is empty because there has not been a crawl. The help page does not call this a judgment of the page's quality.

"Crawled - currently not indexed" is the next status. There Google has fetched the address and chosen not to index it. A row under "Discovered" has not been read yet.

What Google says, and what it does not say

The status sits under "Not indexed", which the help introduces as pages that are not indexed but not necessarily because of an error. Read the description before treating the count as a fault.

Three things on the same help page set what you can and cannot do:

  • The delay is Google's scheduling. The help explains it as a crawl Google wanted to make and then put off, because it expected the fetch to overload the site. No setting on the site starts that crawl. The report's Source value, on the same page, says whether a reason is probably something you can fix.
  • A large non-indexed count is often duplicates. The help says that when non-indexed pages outnumber indexed ones, a common reason is a large number of duplicate pages, including ones that only change a sort or a filter. Those addresses should not all be indexed.
  • The examples are a sample. The report shows example addresses, not a promise that every such address is listed.

Google's page on HTTP status codes adds a limit that matters here: a 2xx response does not guarantee indexing even after a fetch. A page that has not been fetched yet is further from the index than one that has.

What usually fills the list on WordPress

A default WordPress publishes more addresses than the pages you wrote. Feeds, author and date archives, and the second page of a list all answer on their own. A store adds a sorted or filtered address for many combinations of the same products. What a default WordPress serves that can sit under "Crawled" is the same set of addresses, one step earlier: Google has heard of them, often from a link or from the sitemap, and has not fetched them.

WordPress's own sitemap and its canonical links are recorded on what WordPress does with no SEO plugin. Archives that print no canonical link are the ones Google has to sort out for itself. Filter addresses on a store are covered in WooCommerce filter URLs in Google.

A page you wrote, linked from the rest of the site, and listed in the sitemap can still land here. The help's explanation is still the load, not a mistake in that page. New pages are the subject of how long a new WordPress site takes to show up.

What will not clear it

  • Requesting indexing. Google has already found the address and delayed the crawl, because it expected the fetch to overload the site. The help for this status does not describe a new request as the way to clear it. A second request does not raise the server's capacity.
  • A plugin that "forces" indexing. Google's technical requirements, as the no-plugin guide quotes them, say indexing is not guaranteed. A tag cannot make a delayed crawl happen.
  • Marking the page noindex to tidy the report. The address then moves to the reason for a noindex. It is still not indexed.

If the pages you care about are fetched and then sit under "Crawled - currently not indexed", follow that page. The decision there is about the page Google read, not about a crawl it has not made.

A WordPress SEO audit is the job when the list is long, the pages you want are in it, and the server-side checks above are already done. The audit reads the report against the site. It does not decide what Google indexes.

What causes it

  • Google put the crawl off to avoid overloading the site

    Common

    The Page indexing report's help says Google found the page and had not crawled it yet, typically because the crawl was expected to overload the site, so Google rescheduled it. That is why the last crawl date is empty.

    Fix: Sort the examples before you change anything

  • The site offers a large number of addresses that repeat one another

    Common

    The same help page says a site with more non-indexed than indexed pages often has many duplicates, including addresses that only sort or filter the same collection. Google still has to discover them before it can decide they are duplicates.

    Fix: Sort the examples before you change anything

  • The server is slow, down or refusing Google

    Sometimes

    The report's notes on server errors say an overloaded host, timeouts, or a firewall that treats Googlebot as an attack can keep Google from fetching pages it already knows. A live test can succeed later, because a server error can be brief.

    Fix: Check that the server can answer Google

How to fix it

Sort the examples before you change anything

  • Easy
  • No risk
  • About 15 minutes
  1. Step 1: Open the examples

    In the Page indexing report, select "Discovered - currently not indexed". Note that the last crawl date is empty. That is the sign Google gives for this reason.

  2. Step 2: Separate pages you wrote from addresses the site makes

    Set aside feeds, numbered list pages, author and date archives, and addresses that only add a sort or a filter. Those are the pile the help page describes. What remains is the pages you want found.

  3. Step 3: Leave the pile

    Do not block those addresses in robots.txt to shrink the count. A block is reported under Blocked by robots.txt instead, and Google's help says a robots.txt rule does not reliably keep a page out of the index. The robots.txt tester shows which rule matches an address.

For the addresses you set aside, "not indexed yet" is the state the help page describes. Nothing on the site needs to change for Google to be allowed to fetch them later.

Check that the server can answer Google

  • Easy
  • No risk
  • About 15 minutes

The help page's notes on server errors are the checks that belong with a crawl that was put off for load.

  1. Step 1: Inspect one address you care about

    In the URL Inspection tool, run the live test on a page you wrote that is in the list. The help says a live test can succeed when an earlier crawl failed, because a server error can be brief. "Page fetch" should be successful, and "Crawl allowed?" should not be "No".

  2. Step 2: Read Crawl Stats

    The same help page points at host availability in the Crawl Stats report. A host that is down or overloaded while Google is fetching is the case it tells you to take to the host.

  3. Step 3: Look for a block you did not mean

    The help lists a firewall, a denial-of-service rule, or a setting that treats Googlebot's rate as an attack. Googlebot asks more often than a person, so a rule written for attacks can stop it. If the firewall is the host's, the help says to ask the host. Do not answer Googlebot with a block to slow it down. The help says that to change how often Googlebot crawls, you can request a crawl-rate change, and that hosting providers can verify ownership of their IP addresses to enable it.

The page indexing check reads one address from outside: the status, any noindex, and the canonical link. It does not show this Search Console status. It shows what your server answers today.

When to get help

When pages you wrote and linked stay in this list for a long time, or the Crawl Stats report shows the host failing while Google tries to fetch, and you cannot see a block or an overloaded server yourself. Sorting a long list into pages you want and addresses WordPress made is a short job for someone who reads the report often.

Common questions

Is "Discovered - currently not indexed" a penalty?

No. The help page files it under reasons that are not necessarily errors, and it explains the usual case as Google protecting your server from a crawl it expected to be heavy. It does not describe the status as a spam action or as a judgment that the page is poor.

Why is there no last crawl date?

Because Google has not crawled the address. The help page says that empty date is why the report looks the way it does for this reason. An address that has been crawled and left out is Crawled - currently not indexed.

Should I remove these URLs from my sitemap?

Remove an address only if you do not want it crawled. Feeds and filtered duplicates are not the pages you want found. A page you want found should stay. Which sitemap WordPress serves is the file a default site submits.

How long until Google crawls it?

The help page does not give a number of days. It says the crawl was rescheduled. A new site's wait is a different question, covered in a new WordPress site that is not on Google yet.

More on this subject

Would you rather we fixed it?

SEO audit is $249. A written audit, each finding with its source, and up to 2 hours of fixes done and tested again.

More about this work: WordPress SEO audit

May we measure how this site is used?

A yes notes the pages of this visit and loads Google Analytics. A no keeps and loads nothing. See the cookies page.

If you say yes, we note the pages you look at during this visit and load Google Analytics. If you say no, nothing is kept and nothing is loaded. The site works the same either way. The cookies page has the details.