The five groups, itemised
The audit checks five groups of signals, every item traced to a specific page and problem — never just a total. Group by group: what is checked, how it is judged, what failure looks like.
Crawler reachability
What is checked: does robots.txt allow the major AI crawlers, does a complete sitemap exist without dead links, do pages return healthy codes. How it is judged: AI crawlers are simulated against the homepage and core pages, not just configuration. Typical failure: robots allows the crawler while the CDN or WAF blocks its IP ranges; or the 200 is really a challenge page.
Machine-readable surface
What is checked: is there an llms.txt fact file, do core pages have Markdown versions, is body text extractable from raw HTML. How it is judged: raw HTML is checked for the body text itself; a missing llms.txt is a warning, not a failure — an optional aid, not a requirement. Typical failure: body text script-rendered, source holding only container tags; or llms.txt contradicting the website's facts.
Entity facts
What is checked: are name, business, audience and contact details marked up in JSON-LD, and consistent between the website and third-party platforms. How it is judged: markup is reconciled against the visible page text and cross-checked against major directories. Typical failure: no JSON-LD at all; or a founding year in the markup differing from the About page.
Content structure
What is checked: is content organised around real customer questions, does each page lead with a quotable short answer, is the heading hierarchy clean. How it is judged: core pages are sampled: a definition within the first three sentences, each H1 unique and on-topic, paragraphs leading with the answer. Typical failure: one H1 shared across the site, or an H1 stating a slogan instead of a topic; a concept page opening with the motto and no definition in three sentences.
Citation readiness
What is checked: do cases and numbers carry public, attributed sources. How it is judged: key figures and case claims are checked for a clickable public source and a date. Typical failure: "industry-leading" and "significant growth" with no figures or sources; or figures attributed only to unverifiable "internal data".
A real reference point
We sampled 30 Chinese companies' global websites with the same method: mean total 80.1/100, median 80 (range 55–98), 7 above 90 and 6 below 70 — but the machine-readable surface was weakest (average 69.2, median 68.5): 17 of 30 lacked JSON-LD, 15 had sitemap problems, 13 had malformed H1 headings, 10 scored below 70 on both machine readability and entity structure. (Sampling note: the sample is the global homepages of 30 Chinese exporter websites, measured in a single-day sweep on 30 October 2026 with the Negency audit engine — about 30 signals in five groups. The report measures technical visibility only — whether AI can reach and read the site — not brand mention rates in AI answers.)
Scope matters: the audit measures technical visibility — whether AI can reach and read a website — not brand mention rates in AI answers. A high technical score only proves you hold the entry ticket.
The audit runs on this site: no registration for the score; the full report arrives by email.
How an audit runs, step by step
- Intake: submit the domain and confirm scope — languages, target markets, the engines that matter;
- Automated crawl: AI crawlers are simulated against the homepage and core pages, recording allow/deny status, response codes and body-text extraction;
- Five-dimension scoring: every deduction maps to a specific page and problem, never just a total;
- Readout: start with the weakest dimension and entry-ticket issues before content and citation issues — in the wrong order, budget goes to the wrong fixes;
- Fix and re-test: remediate by priority, then re-run the same instrument. Score movement and mentions are recorded separately: the score is a process metric, mentions are the outcome metric.
After the audit: the improvement path, in priority order
- Priority 1 — the entry ticket: allow AI crawlers, repair the sitemap, ensure core pages return clean responses with extractable body text — without entry, everything else is zero;
- Priority 2 — being understood: add JSON-LD entity markup, fix H1 and heading hierarchy, give core pages a quotable short answer;
- Priority 3 — being trusted: align entity wording across website and third-party platforms, attach public sources to cases and numbers;
- Ongoing — being cited: publish question-shaped content, build third-party mentions, re-sample a fixed question set regularly.
For a formal, evidence-backed diagnostic after the self-check, the diagnostic sample excerpt shows the deliverable format and granularity.