Google has rewritten the “Crawled - currently not indexed” entry in its Page indexing report documentation. It now says plainly that Google doesn’t index every page, that this message is common and that it doesn’t have to mean there is a problem.
Barry Schwartz covered the change on November 3, 2026 on Search Engine Roundtable. I checked the current wording in Google’s documentation. Use the English page: on November 4 the Polish translation still showed the old text.
What changed in the documentation
The old entry was two sentences long. As quoted by Search Engine Roundtable, it said Google had crawled the page but not indexed it, that the page may or may not be indexed in the future, and that there was no need to resubmit the URL for crawling.
The new entry has three parts:
- Google doesn’t index all pages across the web, so this status is common and doesn’t necessarily point to a problem.
- If you see it on pages you care about, use the URL Inspection tool and other tools to find out whether something on your site is holding those pages back, for example whether you have blocked them from Google’s crawlers.
- If you have fully diagnosed the issue and suspect an indexing bug affecting your whole site, use the form for reporting indexing issues.
Two things are gone: the “may or may not” about future indexing and the note that you don’t need to resubmit the URL. So the new text promises nothing about later indexing.
What the status means in practice
The status says only that Googlebot fetched the page and Google did not put it in the index. The documentation gives no reason, so there is no “error code” to fix in one move. “Discovered - currently not indexed” means something else: Google knows the URL but hasn’t crawled it yet.
The diagnosis depends on which one you have:
- Discovered - currently not indexed: the documentation’s typical reason is that crawling was expected to overload the site, so Google rescheduled it. Google’s John Mueller adds that this status can also follow from concerns about site quality, because Google then crawls fewer pages.
- Crawled - currently not indexed: Google’s Martin Splitt says this can have all sorts of reasons. Content quality, duplication, weak links to the rest of the site or plain selection can all play a part.
Does it matter that quality isn’t mentioned?
Schwartz points out that the new entry doesn’t mention quality at all, although Google has talked about it in public. It did in the Search Off the Record episode “How to read the Indexing Report” from July 16, 2026. Splitt asked Mueller whether this status is often or only sometimes a sign of a quality issue. Mueller’s answer was sometimes: if Google’s systems are seriously worried about the quality of a whole site, they crawl and index fewer pages. He added that there is nothing to fix technically here. When Google isn’t indexing many of your pages and there is no technical reason, you need to step back and look at the site’s overall quality.
The documentation and Mueller don’t contradict each other: the documentation describes the status in general, and Mueller describes a specific pattern. I wouldn’t read the new text as saying quality stopped mattering. My conclusion is different: a few URLs in this status are normal, and it’s worth checking when the status covers important pages or when Google skips many pages for no technical reason.
The share of unindexed pages doesn’t settle anything on its own. In the same episode Splitt says he has seen healthy sites with a million unindexed pages and half a million indexed, and Mueller says about 5% of the pages in Google’s developer documentation are indexed, including all the important ones.
What this looks like on my sites
I checked this status in Search Console for a few of my own sites. The data comes from reports last updated on October 23, 2026.
On uper.pl the status covers 179 URLs, the largest entry in the table of reasons.
The Page indexing report for uper.pl: 179 URLs under Crawled - currently not indexed.
The list of examples looks less alarming than the number, because 105 of the 179 URLs aren’t pages at all but image versions from /.netlify/images. It also has sitemap-index.xml, rss.xml and tag pages, next to regular articles. Only those articles need a closer look.
Examples from uper.pl: next to articles, Google crawled image URLs that don’t need to be in the index.
On catalog.polo.blue the status covered about 3,000 URLs in August and only 443 by the end of September. The report shows no validation in progress, and I don’t know exactly what caused the drop. It does show that the status isn’t final.
catalog.polo.blue: URLs in this status fell from about 3,000 to 443.
On spoko.space the status covers 127 URLs. A validation started on September 5 failed on September 15, which fits Splitt’s remark in the podcast that this button sets the wrong expectations.
How to handle this status on your site
The steps below are my own conclusions, not Google’s instructions.
1. Split URLs into important and unimportant
The report often lists URLs that shouldn’t be in the index anyway: filter parameters, pagination, tag archives, print versions. Leaving them out is usually the intended result, so there is nothing to “fix”.
2. Check the basics on important pages
Following the documentation’s advice, use URL Inspection to check:
- whether the page is blocked in robots.txt or by
noindex, - which URL Google chose as canonical,
- whether Googlebot sees the content after rendering,
- whether the page returns the correct status code.
I cover this in more detail in my guides to Google Search Console and analyzing sitemap.xml for indexing.
3. If the basics are fine, look at the page as a whole
Mueller suggests looking at the site through the eyes of someone who isn’t involved with it. Splitt adds a question about value: if others cover the same topic just as well, why would Google add your version to the index? Mueller also says quality isn’t just the text but the full experience on the page, so it matters whether ads, pop-ups and filler get in the way of the content.
I’d add two questions of my own: is this another version of a text you already have on the site, and do internal links lead to this page? For more context, see the articles on semantic selectivity in Google indexing and E-E-A-T.
4. Don’t keep resubmitting URLs
The old entry said outright that you didn’t need to resubmit the URL. The new one doesn’t repeat this, but the logic still holds: Google knows about the page because it crawled it, so the problem lies elsewhere.
What is still unknown
- Google gives no threshold at which this status becomes a sign of a problem. Splitt goes further and says the ratio of indexed to unindexed pages isn’t a quality measure.
- The documentation doesn’t explain whether or when a page with this status will be indexed. Mueller says only that when quality is the concern, Google will take another look once it’s happy with the site.
- The documentation’s wording changed. Nothing suggests Google changed how it classifies pages in the report.
Summary
The new entry is clearer than the old one: Google admits it doesn’t index everything and takes away the pressure to fix every URL in the report. Important pages still need a technical check, and when Google skips many pages for no clear reason, what’s left is work on the quality of the whole site.
Frequently Asked Questions
Is "Crawled - currently not indexed" an error?
Not necessarily. According to the Google documentation it is a common message that does not necessarily indicate an issue that needs attention, because Google does not index all pages across the web. Look into it when it affects important pages.
Should I resubmit the URL for indexing?
The old documentation said outright that there was no need to resubmit such URLs. The page has already been crawled, so Google knows about it. Instead of submitting it again, check it in URL Inspection and assess its content.
How is "Crawled" different from "Discovered - currently not indexed"?
With "Discovered", Google knows the URL but has not crawled it yet, typically because it expected the crawl to overload the site. With "Crawled", the page was fetched but Google did not put it in the index. According to John Mueller, both statuses can also follow from concerns about site quality.
Can this status point to a content quality problem?
Sometimes. John Mueller said that when Google systems are seriously worried about the quality of a site, they index fewer pages. That applies to a pattern across many pages with no technical cause, not to individual URLs.
When should I use the form for reporting indexing issues?
According to the documentation, only after a full diagnosis, when you suspect an indexing bug affecting your whole site. It is not for reporting individual pages.
Sources
- Search Engine Roundtable: Google Updates Crawled - Currently Not Indexed Details https://www.seroundtable.com/google-updates-crawled-currently-not-indexed-42450.html
- Google Search Console Help: Page indexing report https://support.google.com/webmasters/answer/7440203?hl=en
- Search Off the Record: How to read the Indexing Report (transcript) https://search-off-the-record.libsyn.com/how-to-read-the-indexing-report-transcript
- Search Engine Roundtable: Google On Discovered vs Crawled Not Indexed Quality Issues & AI-Generated Content https://www.seroundtable.com/google-crawled-not-indexed-quality-ai-content-41701.html