Publish
Put it where the engines already read.
A page nobody crawls changes nothing. Ondit publishes into a directory that eight AI crawlers are verified to reach, with structured data on every page, a sitemap and llms.txt that rebuild on deploy, and a badge that proves the backlink each week.
What it does
Reach, and proof of reach.
A directory built to be cited
Every entity, comparison and best-of page carries JSON-LD from one of six templates, a canonical URL, and hreflang for both languages. Answer engines get the page the way they want it.
Live in seconds
Publishing invalidates exactly the cached pages it touches — the page, the entities it names — and nothing else. Fifty thousand pages share one deployment because nothing is rebuilt on a schedule.
Your badge, your backlink
A live citation badge for your own site. Ondit probes the backlink weekly: a badge that quietly disappeared should stop counting before it is counted.
How it is built
What comes out
A public page at a stable URL, in the sitemap, in llms.txt, reachable by every engine's crawler.
What happens next
Fourteen days later, the same questions are asked again.
- Eight crawlers, checkedGPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, PerplexityBot, Googlebot and bingbot each fetch every page type in a scripted check that ships with the code.
- llms.txt says what is originalThe file the engines read says plainly which facts are sourced from elsewhere and which — the cross-product comparison, the dated weekly series, the citation measurements — exist only here.
- The sitemap is rebuilt, not scheduledEvery publish marks it dirty; a deploy rebuilds it and invalidates the cache the site serves it from, so a release that adds five hundred entities does not advertise the old file for an hour.
- Your own domain, on ProServe your pages from a subdomain you control. Planned for the third quarter; the plan tier is reserved for it.