Buyer questions
The 18 buyer questions and 2 brand checks we ask AI about online appointment scheduling.
Open the questionsYou also get the pages the engines actually cited in your category, each one typed — your own, a competitor's, an editorial list, a community thread, a directory — and the ones cited for your questions that never mention you.
Two different failures look the same from outside: an engine reads your pages and still recommends somebody else, or it never read them. The $19 Check answers both in one report: 20 questions, asked 3 times on 5 engines: 300 answers, every prompt printed word for word, plus a reachability check of 6 of your own pages. No sign-up, no call, and nothing renews.
The Check is $19, once, and the report is yours to keep. It tells you which pages to fix.
Pro ($49/month) runs one monthly benchmark of the same 20 questions plus 3 weekly pulses, writes each fix as a block to copy into your site, whatever it is built on, and shows what moved after each one.
A real delivery: the report, the buyer questions and the Fix package, as a customer gets them.
Measured Oct 18, 2026. TidyCal is not a Kovmere customer.
The 18 buyer questions and 2 brand checks we ask AI about online appointment scheduling.
Open the questionsWho AI recommends instead of TidyCal, question by question, and the pages it cites.
Read the report12 fixes, 2 optional technical files and 1 check from one Pro month, in the order to make them.
Open the Fix packageAnswers come from five search APIs — OpenAI, Perplexity, Gemini, Google AI Overviews, and Claude — and each report prints the model it used. These are search API measurements, not results from consumer apps: not the consumer ChatGPT or Perplexity apps, whose answers also depend on memory, location and personalisation. Google AI Overviews is read through DataForSEO, a search-data provider: for each question it returns the AI Overview Google shows in its results. An API sample is reproducible: it carries no personalisation, no memory and no location, and the identical questions can be re-asked thirty days later and compared.
Reachability, per engine. Each engine's checks come from that engine's own published crawler documentation, and each says whether its rule is official (the engine documents it), observed (we measured it) or inferred. Every page is fetched twice — once with the engine's real crawler user-agent, once as a browser — so a firewall that answers one and refuses the other shows up. A crawler-user-agent fetch shows what a crawler would receive; it is not proof that the engine crawled the page, and the report says so beside the result. How we measure.
Before anything about content, there is a yes-or-no question: could the engine get the page.
The engine's own published crawler rules: robots rules for its named crawler, a fetch with its real crawler user-agent next to a browser fetch, main content that only appears after JavaScript, noindex, and ChatGPT's observed 4 MB fetch limit.
A firewall that answers a browser and refuses a bot looks healthy in your own browser. Fetching both ways in the same second shows the difference, and the report prints the refusal itself — the status code and what came back.
A crawler fetch shows what a crawler would receive. It is not proof that the engine crawled the page, and the report says so.
A failing check names the page, the engine and the rule, with the exact command to re-run the fetch yourself. It is a ticket for whoever owns your site, not a score.
20 questions, asked 3 times on 5 engines: 300 answers; every page the engines cited, reachability for 6 of your pages, up to 3 evidence-supported, ready-to-use fixes, and a fix list ordered by what the closest page is missing. You pay once, no sign-up is needed, and the report is yours to keep at its own link.