Product tour

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.

01

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.

Three projects listed in the dashboard: two with a green "key verified" badge, and one showing "key mismatch" with the message "Key file returned 404. Nothing has been submitted for this project since."
02

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.

A list of recent submissions showing host, URL count, source, time, key verification state, and how many engines accepted each one.
03

Where you stand, at a glance

Daily URL usage, project limits, and how long delivery history is kept.

Three cards showing URLs submitted today against the daily allowance, projects used against the plan limit, and the history retention period.
04

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.

The add-project form with fields for host, IndexNow key and sitemap URL, checkboxes to choose engines, and a checkbox to watch the sitemap and submit changes automatically.
05

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.

Three API keys listed with individual names (Client reporting (read-only), CI deploy hook, and Production) each showing when it was last used, with revoke buttons.

Start with a free account

Open dashboard See usage limits

Questions

Are these real screenshots?

Yes. Every image is the actual dashboard rendered by the actual code, captured from a signed-in session against a real database. The account is fictional (the hosts are under the example.com, example.org and example.net domains reserved by RFC 2606 for exactly this purpose) but the interface, the states and the data flow are all genuine. Nothing here is a mockup or an illustration.

Why does one of the projects look broken?

A key file returning 404 can stop submissions from being honoured. The dashboard shows the failed check so you can fix it.

What does a free account include?

Daily sitemap checks, saved projects, delivery history, email alerts and API keys. Manual submission and the checkers are available without an account.