SEO·AEO·GEO

For hosting companies, CMS vendors, website builders and SEO platforms

AI search checks for your platform

Your customers are starting to ask whether ChatGPT, Google's AI answers, Claude and Perplexity can find their site. Most can't tell, and many are blocked by a robots.txt rule or a firewall setting they never chose. Our engine answers that per page, with the evidence and the exact fix. We're looking for a few platforms to build the API with.

Become a design partner

Where it fits

Hosting dashboards

An "AI search access" card per site: which AI crawlers your customer's robots.txt and firewall let in, and what to change.

CMS and site builders

A pre-publish or post-deploy check that the page's text is in the HTML, nothing blocks the answer engines, and no snippet control hides it.

Deploy and CI pipelines

Audit the preview URL, compare with the last good result, and return pass, warn or fail with the regressions listed.

SEO and agency platforms

Add AI-crawler access, firewall probes and evidence-graded fixes next to the rankings and backlinks you already show.

What the engine checks

  • robots.txt for 31 AI crawlers, matched by exact token as RFC 9309 and Google's parser do, for the page being audited.
  • Live requests as the AI search crawlers, compared with a browser request, to catch firewall, CDN and bot-challenge refusals. We say plainly that a user-agent request is a simulation, not the crawler's own IP.
  • The raw HTML: how much of the content arrives without JavaScript, and whether what came back is the page or a challenge.
  • Indexability and snippet controls: noindex, nosnippet, max-snippet, canonical and status code.
  • Every finding with its evidence, the fix, where it belongs and a command to verify it. Each check carries an evidence grade, and the scoring model is versioned, so a change in a result can be traced to the site or to the model.

The method behind it: our study of AI crawler access on the top 5,000 websites and the pre-registered GEO Lab experiment.

What exists today, and what doesn't yet

  • Live now: the web audit, JSON exports, an MCP server with audit_url and get_report, and an embeddable, white-label audit widget on the Agency plan.
  • Built with design partners: a versioned REST API with organisation keys, usage metering, batch audits and regression checks against a baseline. We'll shape the schema around your integration, not the other way round.
  • Not offered yet: an uptime SLA, compliance certifications or a public price list for API volume. We'd rather tell you that now than in procurement.

How a pilot works

  1. You send a sample of sites you're allowed to check, or we start with public ones you pick.
  2. We return the full results for each, so your team can judge accuracy before anything is integrated.
  3. Together we agree the one endpoint and the one screen it will power first.
  4. Pricing follows your volume and how you show it to customers: wholesale per site, a platform fee, or both.

Become a design partner

Tell us what you run and where the check would show up. A founder reads every message.

Tell us about your platform

Your email is used only to reply. See our privacy policy.