Inside the free dashboard
These screenshots show a demo account captured before the switch to free accounts. See current limits on the free features page.
Turn on sitemap watching to submit changes automatically and receive alerts when a key file stops working.
Your sites, watched without you
Each project is one host, its IndexNow key and its sitemap. Once auto-submit is on, the sitemap is re-read on a schedule and anything new or changed is submitted for you. The third project here is the reason this exists. Its key file started returning 404, so submissions stopped, and rather than continuing to report success, the dashboard says which project is broken, why, and that nothing has gone out since. The watcher repeats the key check on each daily run.
A record of what was actually sent
Every submission, with the URL count, where it came from (sitemap watch, the API, or
the web form), whether the key was verified at the time, and how many engines accepted it.
Note the third row: 2/4 engines and
key unverified. Bing and Yandex returned
202 for the same broken key that Naver and
Seznam rejected with 403: the split this
whole product is built around, visible in your own history. Exportable as CSV.
Where you stand, at a glance
Daily URL usage, project limits, and how long delivery history is kept.
Setting one up takes a minute
Host, key, sitemap. Leave the sitemap blank and it is discovered the way a crawler would
: robots.txt Sitemap: lines first, then the
conventional paths. Choose the global endpoint, which forwards to every participant, or pick
engines individually. The key file is fetched and verified before the project accepts anything.
Keys you can tell apart
Name a key per use (one for CI, one for a client report, one for your own scripts) and see when each was last used. Revoke one without disturbing the others.