Google says Crawled - currently not indexed may need no action

Google rewrote the “Crawled - currently not indexed” entry in its Page Indexing report documentation, and the replacement opens by calling the status common. Barry Schwartz, Search Engine Roundtable’s executive editor, reported the edit on November 3. The entry now says Google does not index all pages across the web, so the message is common for many sites and “doesn’t necessarily indicate an issue that needs attention.”

The old version, which Schwartz’s post reproduces, carried no diagnostic step at all: the page was crawled and not indexed, it may or may not be indexed in future, and there is no need to resubmit the URL for crawling. The new one adds a filter and an escalation path. For important pages showing the message, Google says to use the URL Inspection tool and other tools to check whether anything on the site is stopping those pages from appearing, “such as if you’ve blocked them from our crawlers.” The report an indexing issue form comes last, and only for someone who has finished diagnosing and suspects a complete, site-wide indexing bug.

Nothing in the new text mentions content quality. Schwartz calls that weird, noting that Google has pointed at quality as a cause for this status more than once. The likelier explanation is a change of purpose rather than a change of position: the entry is now a triage instruction instead of a list of causes, and the single cause it does name, crawler blocking, is the one a site owner can confirm in seconds. Anyone treating the omission as Google clearing thin pages of blame is reading a help-page edit as a ranking statement.

The word carrying the new entry is “important.” A bucket count on its own means very little on a large site, where most of what lands in it is URLs nobody meant to rank: parameter variants, internal search results, near-identical product pages. Google’s wording does not say that, but an instruction to inspect only important pages makes sense only if the rest of the bucket is expected to stay where it is.

That matters most when a big count has been presented as proof of a site-wide quality problem. Google’s own page now says the message is common and may need no action, so the argument worth having is about which URLs in the bucket should be ranking, not how many URLs are in it.

What to do

The edit changes nothing about how indexing works, so the job is sorting the bucket rather than shrinking it.

• Export the bucket from the Page Indexing report and split it in two: URLs that should be earning traffic, and everything else. Only the first list gets attention.
• Inspect those URLs one at a time. The fetched HTML is the place to start, since a page that renders fine in a browser can still reach Google nearly empty, and this bucket is rarely a crawl budget problem.
• Confirm the status is the one you think it is. Discovered - currently not indexed means Google never fetched the URL, which is a different investigation with different fixes.
• The line telling owners not to resubmit the URL is gone from the entry. Its removal is not an invitation to push a few thousand URLs through Request Indexing, because nothing in the new text promises that resubmitting changes the outcome.
• Leave the indexing issue form alone unless indexing has stopped across the whole site and causes on your end have already been ruled out. That is the bar the new wording sets.