An IndexNow checker examines the verification file used to demonstrate control of a website when sending IndexNow notifications. Screpy checks whether the file is reachable, readable as UTF-8 and consistent with the key you supply. This is a setup inspection: it does not submit a page to a search engine or test whether an earlier notification was accepted.
Enter the origin and verification key
Use the website origin, such as https://example.com/, without a page path, query or fragment. Enter the IndexNow verification key, using 8–128 letters, digits or dashes. With no custom location, the expected file is /{key}.txt at that origin. The IndexNow documentation explains verification-file hosting and key-location rules.
You must publish the file on your own website; running this checker does not create or upload it. Its text should contain the exact key. The form saves the site origin for reuse, but not the key or custom file URL. The report masks the file path and excludes the supplied key.
Check a custom location deliberately
Open the optional location field if you publish the key file elsewhere. The URL must have the same scheme and host as the submitted origin, with no query or fragment. A file under a directory limits the applicable URL scope to that location's directory; review the displayed scope rather than assuming it covers the entire site.
At most three same-origin redirects are followed and reported as warnings. A redirect to another hostname or scheme is not treated as verified setup. Use the intended published origin and inspect the response separately with HTTP Headers Checker if the location is unclear.
Read unknown checks separately from failed checks
The download is limited to 16 KiB of wire and decoded data, with a six-second fetch and a 12-second analysis deadline. A 404 or 410 records a missing file; blocked, timed-out, incomplete or oversized responses leave unverified fields unknown. An unavailable response is not proof that the key is wrong.
The comparison can remove a UTF-8 byte-order mark and one terminal newline, but it reports that normalization as a warning. Extra text or a different key does not match. Review the source and bounded JSON report before changing your configuration. No chart is needed: the three checks describe distinct facts, not an indexing score.
Keep setup verification separate from indexing
A matching file does not establish that a search engine accepted a submission, crawled a page or indexed it. This tool sends no IndexNow notification and does not request Google indexing. For other questions, use Sitemap Checker to inspect sitemap files or Noindex Checker to review a page's noindex directives. Each report has its own scope.