IndexNow: verify your site before sending changed URLs
A careful key-file workflow with receipts that do not pretend to be indexing proof.
Notify a change that really exists
IndexNow is a protocol for notifying participating search engines about changed URLs. The useful unit is a page that was added, updated or removed. Sending an unchanged inventory every few minutes is not a substitute for a publishing workflow. Publish your change first, check the public response and only then send the notification.
The ownership key links the submission to a website you control. In Noor Indexer’s beta, you host the key in a text file at the root of the exact HTTPS origin. For example, a key named example-key-2026 would be available as /example-key-2026.txt and the file would contain that exact key. Use your own generated key rather than copying this illustrative value.
Keep hostname scope precise
A key file on one hostname does not automatically prove control of every other hostname. Check the exact origin you plan to submit, including any www prefix or subdomain. If your site redirects to another hostname, verify the final destination and use consistent addresses. The beta deliberately limits a submission to one HTTPS origin and 20 unique URLs.
Open the verification file as a public visitor. It must return the key text, rather than an HTML layout, login screen or application fallback. Some single-page applications return their homepage for every unknown path; that can make a missing text file appear superficially successful. Verify the response body as well as the status.
Read the response honestly
A successful notification response means the engine accepted the request at that stage. A 202 response means key validation is pending. Neither establishes that the URL has been crawled, indexed or ranked. Store the engine status, the URLs and the time separately from any indexing evidence you later obtain.
If a request is rejected, inspect key availability, host matching, URL scope and any engine quota response. Do not rotate keys repeatedly without understanding the failure. A key that is inaccessible because of routing will remain inaccessible under a different filename unless the deployment problem is corrected.
Fit notification into publishing
A useful release checklist has four stages: deploy the page, confirm its public response, update internal discovery routes, then notify supported engines. For removed pages, ensure the URL returns the intended removal response rather than a misleading successful page. Keep notifications tied to real content events so the record remains meaningful.
Google Search Console is a separate system. Do not label an IndexNow receipt as a Google indexing request. Noor Indexer keeps the notification response visible and leaves Google status unknown in this beta. That separation makes the dashboard more useful: it shows what happened without inventing the next event.
Technical references
Primary documentation checked for this launch. Examples are illustrative unless explicitly described otherwise.
Continue reading
06What Search Console URL Inspection can actually tell you
Separate the indexed version, live eligibility and a request to revisit.
RSS or sitemap: which should your publication maintain?
Keep both when they serve readers and discovery, using one content source.