Can the engines read your site at all — and who do they name instead of you?
Two different failures look identical from the outside. Either an engine can fetch your pages and still recommends somebody else, or it never fetched them. The $29 Check answers both in one report: up to 40 real buyer questions in your category, asked 3 times each through the OpenAI web-search API and the Perplexity Sonar API, every prompt printed verbatim — plus a page-by-page reachability check on 6 of your own pages. No account, no call.
- One-time, nothing renews
- No account created
- Back in about 20 minutes
Or start free, right here
Up to 10 questions, 3 runs, one engine, no account and no card — enough to see who the engines are naming in your category.
Free tells you who is being recommended. It does not tell you which pages were cited, whether the engines can fetch yours, or what to fix — that is the $29 Check. See what the Check adds.
The boring reason a site never gets named
Before anything about content, there is a question with a yes/no answer: could the engine retrieve the page.
Each engine's gates are built from that engine's own published crawler documentation, and each gate is tagged as official, observed or inferred so you can tell a documented rule from a measured one. Robots rules for that engine's named agent, a fetch with the real crawler user-agent placed next to a browser fetch, main content that only exists after JavaScript, noindex, and ChatGPT's observed 4 MB fetch ceiling.
A firewall that answers a browser and refuses a bot looks perfectly healthy in your own browser. Fetching both ways in the same second is the only way to see the difference, and the report prints the refusal itself — the status code and the body we got — beside the verdict.
A crawler-user-agent fetch shows what a crawler would receive. It is not proof that the engine crawled the page. We say that on the report, in the PDF and here, because the difference is the whole difference between a measurement and a guess.
A failing gate names the page, the engine and the rule it broke, with the exact command to re-run the fetch yourself. It is a ticket for whoever owns your site, not a score.
What we refuse to sell you
The limits are part of the product. If any of these is a dealbreaker, we would rather you knew before paying.
- Not schema, llms.txt, IndexNow or FAQ re-formatting. Controlled studies show no measurable effect on citations, so we don't grade them and we won't sell you work on them.
- Not a promise about rankings or citations. We report what the engines answered on the day we asked, with the range that goes with it. Engines change.
- Not bulk AI pages. A Fix Pack writes up to 5 pages, from facts you enter, on your domain, published only after you approve — and none at all where your own page already answers the question.
- Not a subscription unless you choose one. The $29 Check and the $99 Fix Pack are one-time. Nothing renews.
- Not a human reading your site. Nothing here is edited by a person or published on your behalf. One person builds and runs Kovmere; the rest is software, and the method is published.
What we sample, and why it is an API
Samples come from the OpenAI web-search API (the model id is printed on your report) and the Perplexity Sonar API — not the consumer ChatGPT or Perplexity apps, whose answers also depend on memory, location and personalisation.
That is the point, not an apology. An API sample is reproducible: it carries no personalisation, no memory and no location, it prints the model id and the search tool it used, and the identical frozen questions can be re-asked thirty days later and compared. A reading that depends on whose account asked it cannot be any of those things — which is exactly why the re-test means something here. How we measure.
$29, one report, about twenty minutes
Up to 40 buyer questions × 3 samples, the full page-verified source ledger, per-page reachability for 6 pages, and a fix list ordered by what the closest page is missing. One-time — nothing renews, and no account is created.