Googlebot downloaded this site's sitemap 1.1 seconds after it was submitted, and discovered all five URLs immediately. It has since fetched the sitemap three times, every time in under 1.2 seconds — and has fetched none of the pages.
That gap is the whole point of this page. Discovery and crawling are separate events, and Search Console's API says so explicitly — a URL can sit in "Discovered – currently not indexed" having never once been requested by Googlebot.
Most writing about indexing delays is either advice or anecdote. This is a timestamped log of a single new domain with zero backlinks, taken from the API rather than from a screenshot, published whether the result is interesting or not. n = 1. It is a case, not a study.
| When (UTC) | Event | Source |
|---|---|---|
| 30 Jul 2026 | Domain registered. No prior registration history, no inbound links, no traffic. | registrar |
| 31 Jul 03:13:23.890 | Sitemap submitted (5 URLs) via the Search Console Sitemaps API | lastSubmitted |
| 31 Jul 03:13:25.035 | Sitemap downloaded by Google — 1.145 s later. 0 errors, 0 warnings, isPending=false | lastDownloaded |
| 31 Jul 03:20:45.117 | Sitemap re-submitted after a page was added | lastSubmitted |
| 31 Jul 03:20:45.573 | Downloaded again — 0.456 s later | lastDownloaded |
| 31 Jul 03:2x | All 5 URLs report Discovered – currently not indexed, with the sitemap as the only referring URL | URL Inspection API |
| 31 Jul 03:5x | This page is published and reads URL is unknown to Google — the state before discovery, recorded as reading 1 | URL Inspection API |
| 31 Jul 03:56:13.651 | Sitemap re-submitted, now listing 6 URLs | lastSubmitted |
| 31 Jul 03:56:14.393 | Downloaded — 0.742 s later. Third fetch, third sub-second response | lastDownloaded |
| — | First fetch of any page: not yet observed. | URL Inspection API |
Here is the actual API response for one of the five URLs, unedited:
"indexStatusResult": {
"verdict": "NEUTRAL",
"coverageState": "Discovered - currently not indexed",
"robotsTxtState": "ROBOTS_TXT_STATE_UNSPECIFIED",
"indexingState": "INDEXING_STATE_UNSPECIFIED",
"pageFetchState": "PAGE_FETCH_STATE_UNSPECIFIED",
"sitemap": [ "https://mossbench.com/sitemap.xml" ],
"referringUrls": [ "https://mossbench.com/sitemap.xml" ],
"crawledAs": "CRAWLING_USER_AGENT_UNSPECIFIED"
}robotsTxtState, indexingState, pageFetchState
and crawledAs are all unspecified. Google is not
reporting that the fetch succeeded, or failed, or was blocked. It is reporting no
fetch at all. The URL is known — it came from the sitemap, and the sitemap is the
sole referringUrls entry, which is what zero backlinks looks like in
this API — but the page itself has not been requested.
This matters when you are diagnosing a site, because the same status string gets
attributed to causes that the API can rule out. If pageFetchState is
unspecified, the problem is not your robots.txt, not your response time, not your
rendering, and not your canonical tags — none of those have been reached yet.
Nothing about your page has been evaluated, because your page has not been read.
What this page does not tell you. One domain, one sitemap, one starting condition. It cannot tell you the average time to index, whether your site is slow, or whether any intervention works — for that you need many domains, and this is one. Nor does it predict what happens next here: the useful outcome may well be that these URLs are never indexed at all, and that result will be posted on this page in the same detail as any other.
Both figures come from the free Search Console API, not from the dashboard. The
sitemap timestamps are from
Sitemaps: get,
which returns lastSubmitted and lastDownloaded to the
millisecond — the web interface rounds these to a date and hides the gap entirely.
The per-URL fields are from
URL Inspection: index.inspect,
which is limited to 2,000 calls per day and 600 per minute per property.
The URL Inspection API reports what Search Console already knows. It does not request a crawl, and nothing on this page was retried, resubmitted or nudged between readings.
Every reading behind this page, as returned by the API: indexing-log-2026-07.json. New readings are appended, and corrections are noted in place rather than edited away.