Features
Find out what AI assistants can read, and what they cannot.
From one crawl of your site.
Grouped by the question you are trying to answer, not by what sounds impressive. Every feature here runs today — and each one tells you what it measured, so you can act on it without taking our word for it.
- 900 million
- people use ChatGPT every week
OpenAI, reported by TechCrunch, February 2026 - 68%
- of Google searches now end without a click to any website
Similarweb, June 2026 - 20%
- of searches show an AI Overview, and click-through drops by close to 60% when they do
Similarweb, via Search Engine Land, June 2026
Every figure above links to its source and carries the date it was measured. We have seen these same numbers quoted on rival pages with no source and no date, and one of them was a year out of date.
Can AI engines read you?
Before an answer engine can cite you, it has to fetch you, render you and find something worth quoting.
AI crawler access
We check robots.txt against fifteen named AI crawlers, including OAI-SearchBot, PerplexityBot and Claude-SearchBot, and name the ones you block.
Read moreRendering gate
We fetch your page as raw HTML and again in a real browser, then compare. Content that exists only after JavaScript runs is content most AI crawlers never see.
Read moreStructured data values
Most schema validators tell you the markup parses. We check whether the fields inside it actually contain anything an answer engine can quote.
Read moreCitation drivers
Three things make a page quotable to an answer engine: a concrete number, a date it can trust, and language that commits. We check all three.
Read moreEntity consistency
Answer engines need to know the company on your site is the one on your Google profile. We check whether that identity is machine readable and consistent.
Read more
Audit the site itself
43 technical and on-page checks that run against every page we crawl.
- 24 of 24 implemented
Technical audit
Twenty four technical checks covering sitemaps, robots, canonicals, redirects, broken links, indexability, Core Web Vitals and JavaScript rendering.
Read more - 17 of 17 implemented
On-page audit
Seventeen on-page checks across titles, meta descriptions, heading hierarchy, internal and external links, images, canonicals and social cards.
Read more - Depth, duplicates and freshness, checked on every page
Content audit
Six content checks covering depth, semantic keywords, topic clusters, readability scoring, duplicate detection and freshness.
Read more
Never ship a bad claim
A registry that tracks where every claim came from, and a gate that refuses to publish without it.
Claim registry
Every claim about your business gets a state and a source. Claims move unproven to asserted to verified, and the transitions are enforced in code.
Read moreValidation gate
Seven validators run before anything ships and six of them block: unproven claims, unsourced numbers, fabricated quotes, missing AI disclosure and more.
Read moreGap reporting
When a check cannot answer something, it records a gap with the reason and what would fill it, rather than reporting a pass it did not earn.
Read more
Connect and scale
Live answer engine data, Google connections, and isolation that holds when you run many clients.
- Six engines, live answers
AI engine tracking
We run real prompts against six consumer answer engines and record whether you were mentioned, where in the answer, in what tone, and which sources were cited.
Read more - OAuth connection, real API reads
Search Console and GA4
Connect Search Console and Google Analytics 4 so ranking and traffic data sit next to the audit findings instead of in another tab.
Read more - Tenant id is the first argument, always
Client workspaces
Every client is a tenant. Isolation is enforced by the shape of the code, not by remembering to filter, and a record belonging to another client answers 404.
Read more - AES-256-GCM, per client key via HKDF
Credential vault
Client credentials are encrypted with AES-256-GCM under a per-client key. No endpoint returns a plaintext secret, including to you.
Read more
Someone else wrote the checklist. Here are our answers.
These twenty-one criteria are not ours. They are the buyer checklist published by a competitor in February 2026, which we have answered line by line, including the seven where the answer is no or not yet.
11 yes · 6 partly · 4 no
- Model coverageyes
Six engines, every plan, no add-on pricing
- Brand monitoringyes
Mentions and citations per engine, with sample size
- Citation trackingyes
Which sources an answer quoted, and whether you were one
- Competitive benchmarkingyes
Share of voice against the brands you name
- Site auditingyes
51 SEO checks and 31 citability checks, catalogued publicly
- AI bot trackingyes
15 named crawlers checked against your robots.txt
- Website mappingyes
Findings carry the pages they affect
- Multi-brand and agency useyes
One workspace per client, isolated by construction
- Security and access controlyes
Per-tenant credential vault, AES-256-GCM, write only
- API accessyes
On the Scale plan
- Search Console and GA4yes
Connect your own, no data purchase
- Reporting and data exportpartly
Reports in product. No CSV export yet.
- Self-service setuppartly
Sign-in works. Attaching a new account is still done by hand.
- Ease of usepartly
Judge this yourself. Run the free audit before you believe us.
- Content optimizationpartly
We tell you what to fix. We do not edit your pages.
- Data filteringpartly
Filter by engine and severity. Not by persona or funnel stage.
- Automated insightspartly
Findings are ranked worst first. No weekly digest yet.
- Content generationby design
We do not write your content. A tool that audits claims should not invent them.
- Content delivery to agentsby design
We do not serve a separate page to crawlers. That is cloaking with better branding.
- AI search volume and trendsby design
We report what engines answered, not estimated search volume.
- AI referral trackingby design
Not built. It needs your CDN logs and we do not ask for them yet.
Four of these are a flat no and we are not planning two of them. A tool that exists to check whether your claims are provable should not generate your content, and it should not serve a different page to a crawler than it serves to a person.
Run a free audit instead of reading about it