IndexNow checks you can run yourself
Three checks, and all of them are about the same thing: whether the parts you control are in the state the protocol expects. None of them tells you anything about indexing, because no check can.
What the IndexNow checks look at
- The key and its file name
The key and the file name that serves it have to agree exactly, and a mismatch between them is invisible until an engine tries to read the file — a common way to spend an afternoon. Generating the pair together, rather than typing either by hand, prevents the disagreement outright.
- What the hostname returns
Fetching the key file from your hostname the way an engine would shows what actually comes back: the file, a redirect, or a page rather than plain text. Those are exactly the failure shapes on key not found, and the check has a page of its own.
- What the engine answers
A single address, submitted and read back, separates a submission problem from everything else you might be investigating. What an accepted submission does and does not mean is set out under what an accepted submission means, and it is less than most people assume.
What no IndexNow check can tell you
One boundary, and it applies to all three.
No check here reports whether a page was indexed, when it will be, or whether an engine intends to. Submission is an announcement that an address changed, and the decisions that follow it are the engine's, made on its own criteria and never reported back. A check claiming otherwise would be inventing an answer.
What these do instead is confirm the half you control: that the key is correct and reachable, and that a submission is accepted rather than rejected. When something is wrong, that half is where it almost always is, and troubleshooting sorts the rest by symptom rather than by response code.
A clean result from all three means your side is correct, not that anything has happened at the engine, and those are different kinds of good news. What the key itself proves, and why it is public by design, is set out under the key file.
FAQ
Do these checks need an account?
No. Everything they look at is public by design: the key file is served openly from your hostname, and a submission is answered by the engine's own endpoint. Checking either involves only what is already served publicly, which is the same thing an engine reads.
Does a clean check mean my page will be indexed?
No. A clean result means your side is correct: the key is right and reachable, and the submission was accepted. Whether a page is then crawled, indexed or ranked is the engine’s decision, made on its own criteria, and no check here reports it.
Which IndexNow check should I run first?
The key file, because most rejections are about the key. Request it the way an engine does: over HTTPS, at /<key>.txt on the exact hostname, without following redirects, and from outside your network. The key checker sets out the four answers that request can return and what each one means.