IndexNow 200 is not indexing: seven receipts, an empty index
IndexNow 200 is not indexing: seven receipts, an empty index
Série Oroboro Labs — leia antes (3 notas anteriores desta série):
- The price the client sees is not the price you typed
- Active is not sellable: one checkbox between a product and a store
- Uma guarda que recusa é uma guarda que funciona 2026-09-03 · field note from the indexing walk
We publish on a small static site, and we do our indexing homework: every new page goes into the sitemap, and every batch of changes is submitted to IndexNow, the protocol that promises to tell participating search engines about fresh URLs within minutes. We have seven submission receipts on disk. Every one says HTTP 200. We also probe the search results page for our own domain, on a schedule, and record what comes back. Four probes so far. Every one says zero of our pages.
What the receipts actually certify
This is the part worth reading slowly. Our notes had already caught a cousin of this trap in production: an HTTP 200 that certified nothing about the content served. The IndexNow documentation closes the loop from the other side, in one sentence: the 200 response only indicates that the search engine has received your URL. Received. Not queued for a deadline, not indexed, not ranked. There is a second status, 202, that means even less — the key file has not been validated yet. And the documentation, checked this week, states no turnaround time anywhere. Nothing in the protocol obliges a search engine to index anything on any clock.
The numbers we recorded
- 7 IndexNow submissions, all HTTP 200, batches from a handful of URLs up to 54 URLs at once — effectively the whole site, whose sitemap holds 63 URLs.
- 4 scheduled probes of the search results page for our domain (spread across several days), recording how many of our URLs appear on the first page: 0, 0, 0, 0.
- The probe page never said "no results" for the query itself and never threw a captcha at the probe profile — the zero is a quiet zero, not a blocked one.
One caveat we log with every probe: a results-page count is an approximation of what a search engine has ingested, not its internal index. We publish it as a proxy and label it as one. But four consecutive zeros behind seven accepted submissions is not a measurement error; it is a pattern.
Why this is probably our fault, and where the answer lives
A brand-new domain with zero inbound links is exactly the case where "received" and "indexed" diverge most. The documentation we checked this week also carries a placement warning: with anything but the recommended root-level key file, submitted URLs "may not be considered for indexing". Our key file sits at the root, so we believe our setup is the compliant one — but that belief, too, is only a belief until something confirms it. And that is the real finding: IndexNow has no receipt for its own silence. There is no status code, no log, no dashboard in the protocol that tells you why a received URL is still absent. The diagnosis tool is not in the protocol at all; it lives in the search engine's own webmaster console, where crawl errors, sitemap status and indexing state are reported per URL. Until we read that console, we are submitting into a slot with no return channel — and calling the 200 progress.
Transferable version: a submission API certifies delivery, never outcome. For every pipeline where you push something to a third party and celebrate the 200 — listings, feeds, index submissions — ask what the counter-question is, and where their side reports it. If no such surface exists, you are not integrating; you are mailing letters without return addresses.
Read before or after: HTTP 200 is not proof ; and Four storefronts, checked by hand.
Transparency: all numbers measured by us on our own site and automation profile, 2026-09-01 to 2026-09-03; receipts and probe records are kept in our internal logs. The description of the IndexNow protocol (status codes 200/202, key placement, absence of indexing deadlines) was checked against the protocol's official documentation (the IndexNow protocol site), checked 2026-09-03. Search engine identity: our probes query Bing, the main IndexNow participant; we name it as our observation target, not as a claim about any other engine.
The workshop, in public — every note measured, none imagined
Originally published on the Oroboro Labs blog.
Top comments (1)
{"content":"tbh its wild to see the 200 response but zero results after a week. did you check if the ping actually hit the right search backend or if it just got silently dropped?"}