Field note · 19 September 2026
Crawled, currently not indexed: we changed nothing and Google indexed all ten.
On the evening of 17 September, ten of our pages sat in "Crawled, currently not indexed". By 19 September all ten were indexed, with no rewrite and no new crawl: every last-crawl timestamp predates our next change to those pages, so Google indexed the same version it had deferred two days earlier. On a young site, this state is often a place in the queue rather than a judgment on the content.
30 min · Fixed quote before we build · Projects from $2,500
How we measured it
The Index Coverage report in Search Console lags and rounds. Instead we ran the URL Inspection API over every URL in our sitemap, three times between 17 and 19 September 2026, and saved the raw coverage state and last-crawl time for each one. That gives a per-URL census rather than a chart, and it is the only way to watch individual pages change state.
What the three censuses showed
| State | 17 Sept, midday | 17 Sept, evening | 19 Sept |
|---|---|---|---|
| Submitted and indexed | 54 | 72 | 100 |
| Crawled, currently not indexed | 3 | 10 | 0 |
| Discovered, currently not indexed | 27 | 18 | 7 |
| URL is unknown to Google | 32 | 16 | 11 |
Every URL in the sitemap, inspected individually. 116 URLs at the first two censuses, 118 at the third.
27 pages were indexed between the evening of 17 September and 19 September, and none dropped out. The entire "Crawled, currently not indexed" group moved into the index. The trend held: by 22 September, 106 of our pages were indexed.
The ten pages, and the timestamps that matter
The usual advice for "Crawled, currently not indexed" is that Google looked at the page, judged it thin or duplicated, and declined. The fix, in that story, is to rewrite it. Our timestamps say something different.
| Page | Google last crawled | Next change we shipped |
|---|---|---|
| Two case studies | 17 Sept 16:14 UTC | 18 Sept 15:38 UTC |
| Four German service pages | 17 Sept 16:22 to 18 Sept 10:47 UTC | 18 Sept 21:48 UTC |
| Two Spanish service pages | 17 Sept 16:22 to 16:29 UTC | 18 Sept 21:48 UTC |
| One French and one English service page | 17 Sept 16:18 UTC | 18 Sept 21:48 UTC |
Every last-crawl time is earlier than the next edit to that page, so Google indexed the version it had already crawled.
Nothing was rewritten, no new links pointed to those pages, and Google did not fetch them again. The same version that was "Crawled, currently not indexed" on Thursday evening was "Submitted and indexed" on Saturday. For these ten pages the state meant the decision was pending, and the content passed as it stood.
The states are not a ladder
Movement between the earlier states ran in both directions. Between the evening of 17 September and 19 September, five URLs went from "URL is unknown to Google" to "Discovered, currently not indexed", and seven went the other way. On a new site, pages move in and out of Google's queue while it decides how much of the site to crawl.
- URL is unknown to Google: not in the index and not in the crawl queue, whatever your sitemap says.
- Discovered, currently not indexed: queued, not yet fetched. Usually a crawl-budget decision about the site, not about the page.
- Crawled, currently not indexed: fetched, decision deferred. On a young site, frequently temporary.
- Submitted and indexed: in the index. None of ours dropped out across the three censuses.
When the state is a real verdict
On an established site, "Crawled, currently not indexed" usually does mean Google saw the page and passed on it, most often because the page is thin or too close to another one. The last-crawl time tells you which case you are in.
Inspect the URL and compare its last-crawl time with your last meaningful change. If the crawl came first, Google has not seen the current version yet, and another rewrite only restarts the wait. If Google has crawled the current version and the page has stayed out for weeks, improve it: make it more useful than the pages that already rank, and link to it from pages Google already indexes.
We run this kind of measurement as part of our work, described on our AI automation agency page.
Questions, answered.
Does "Crawled, currently not indexed" mean my content is bad?
Not necessarily. It means Google fetched the page and has not yet made a decision. On an established site with thin pages it is usually a quality signal. On a new site it is often a matter of time: all ten of ours were indexed within two days, with no edit and no recrawl.
How do I check whether Google has seen my latest version?
Inspect the URL and read the last-crawl time, then compare it with when you last changed the page. If the crawl predates your change, Google has not judged the current version at all.
Is requesting indexing worth it?
It is free and the daily allowance is small, so spend it on pages that are genuinely unknown to Google rather than on ones already queued. It is not a substitute for the site being crawlable and worth crawling.
Why did some pages move from Discovered back to unknown?
Discovery is not permanent. On a new site, Google adds URLs to its queue and drops some again while it works out how much of the site to crawl. Seven of ours made that move between the last two censuses, while the number of indexed pages kept rising.
How often should I run a census like this?
Weekly is plenty once a site is established. On a site that is actively being built, every few days shows you which changes actually moved coverage and which did not.
Related services
Tell us what's slowing you down. We'll show you what to automate first.
Free · 30 min · Projects from $2,500
contact@aistrikeforce.com