FAQ

Inside the diagnostic: a sample excerpt of an AI visibility report

What exactly do you get for a ¥19,800 diagnostic? This page opens up the deliverable of Negency's AI search visibility diagnostic package — the scorecard, the itemised findings list and the 90-day roadmap, at delivery granularity. Sample figures come from the published median profile of our 30-company going-global benchmark, not from any real client; a real engagement measures your own domain and three competitors, item by item.

Figure 01 · Sample scorecard: median profile of the 30-company benchmark

  1. 00

    Total score

    Median of 30; mean 80.1; range 55–98; 7 sites above 90, 6 below 70

    80/100 Sample — not a client report
  2. 01

    Crawlability

    Can AI crawlers get in and get around? 21 sites at full marks; strongest dimension

    91.1/100
  3. 02

    Performance

    Do load and rendering slow down crawlers and visitors?

    87.3/100
  4. 03

    Trust signals

    Are entity facts, contacts and third-party profiles consistent and checkable?

    82.1/100
  5. 04

    Entity structure

    Can a machine read, unambiguously, who you are, what you sell and who it is for?

    71.1/100
  6. 05

    Machine readability

    Structured data, llms files and semantic markup; weakest dimension, only 2 sites at full marks

    69.2/100 Weakest dimension · median 68.5 · only 2 at full marks
This is a sample, not a client report: every figure comes from the Negency Flagship Report 2026 (Issue 1) 30-site public measurement. In your report, every point comes from page-by-page measurement of your own domain. Sample basis: 30 Chinese exporters' global website home domains, single-day sample on 30 October 2026; the report measures website technical visibility only, not brand mention rates in AI answers.

First, the honest part: this is a sample, not a client report

A diagnostic report exposes a client's real weaknesses — we never showcase a real one. Every figure here comes from Negency's published flagship study, the AI Search Visibility Report for Chinese Companies Going Global (2026, first edition): 30 Chinese exporters' global website home domains; Negency AI visibility audit engine, around 30 signals, five categories; single-day sample, 30 October 2026. The report measures website technical visibility only, not brand mention rates in AI answers. The "median profile" scorecard below follows part one of a real diagnostic report exactly — for your company, every number comes from measuring your own domain page by page.

Sample 1: the scorecard (median profile, 30-company benchmark)

Total: 80 / 100 (median of 30; mean 80.1; range 55–98; 7 sites above 90, 6 below 70)

Crawlability: 91.1 (mean of 30) — can AI crawlers get in and get around? 21 sites at full marks, the strongest dimension

Performance: 87.3 — do load and rendering slow down crawlers and visitors?

Trust signals: 82.1 — are entity facts, contacts and third-party profiles consistent and checkable?

Entity structure: 71.1 — can a machine read, unambiguously, who you are, what you sell, who it is for?

Machine readability: 69.2 (mean; median 68.5) — structured data, llms files, semantic markup; the weakest dimension, only 2 sites at full marks

A scorecard shows the bottleneck dimension — not a total to celebrate or mourn. The median profile says most companies spend in the wrong place: plenty of content, while machine readability and entity structure drag. Two statistics matter: median 80 and mean 80.1 sit close, so the distribution is roughly symmetric; machine readability's mean (69.2) and median (68.5) are close too — the weakness is broad.

Sample 2: what an itemised finding looks like

Every finding carries four things: problem, evidence, impact, fix. The three most frequent across the 30 companies, in the real format:

Problem: no JSON-LD structured data anywhere on the site (17 of 30). Evidence: source-level check of the homepage and core product pages — no Organization, FAQPage or Product markup. Impact: engines guess your entity and product facts from prose — guesses drift descriptions and lose citations. Fix: add Organization plus the four core markup types, word-consistent with visible text. Specification: Schema.org Organization and Google's structured-data introduction.

Problem: H1 missing or not unique (13 of 30). Evidence: the crawl inventory lists every page's H1 text. Impact: several topics compete on one page; engines cannot tell which passage to quote — Q&A content suffers most. Fix: one H1 per page, aligned with the question the page answers.

Problem: sitemap problems (15 of 30). Evidence: item-by-item check of sitemap reachability and contents — dead addresses submitted, core pages omitted, conflicts with robots rules. Impact: crawlers take wrong turns or miss key pages; new content enters the index slowly. Fix: rebuild the sitemap against the real page inventory; confirm robots is not blocking the sitemap itself.

Sample 3: the 90-day roadmap skeleton

Month 1 · Technical and entity layer: clear crawl blockers, add structured data, unify facts and profiles — get machines reading you right first. Acceptance: audit scores rise; AI crawler visits and success rates rise in server logs.

Month 2 · Content and Q&A layer: publish question-shaped content from buyer questions; category definition and comparison pages go live for "what is it" and "how to choose". Acceptance: Q&A content indexed and appearing in the citation sources of relevant answers.

Month 3 · Mentions and re-measurement: work third-party mentions and directory profiles, re-measure on the same basis, set next quarter's priorities. Acceptance: sampling on a fixed question set and one method shows a trend, grounding next quarter's investment.

What a real diagnostic adds

  • Raw measurements and evidence for your own domain, page by page — not a benchmark;
  • A same-method comparison table against three competitors you name;
  • A prioritised fix list (what first, why, expected impact);
  • A walkthrough call covering the report item by item.

Fixed price RMB 19,800, no per-page or per-finding surcharges. Before ordering, run the free AI visibility audit for a rough picture; the diagnostic package page lists the full deliverables.

How to use this sample

Take this sample to any GEO provider and ask: does your deliverable look like this — scorecard with item-by-item evidence, findings with fixes, roadmap with acceptance criteria? A provider that cannot answer mostly delivers a monthly "work summary". The full vetting script: the 12 due-diligence questions.

Related questions: What does an AI visibility audit actually check? A complete checklist; How much does GEO cost? How is it usually priced?; What is GEO (Generative Engine Optimization)?

Related questions

How is GEO different from SEO?

SEO optimises a page's rank in a list of links, aiming for clicks. GEO (Generative Engine Optimization) optimises how discoverable, understandable, trustworthy and citable a company is inside AI-generated answers — the goal is to be in the answer itself. They share technical foundations (crawlability, structured data, content quality), but GEO additionally requires governed entity facts, a machine-readable surface (llms.txt, Markdown mirrors) and a third-party mention ecosystem. A site that ranks well is not automatically visible to AI: engines cite the companies whose facts they can fetch, parse and verify. The concrete differences sit in four dimensions — goal, object, content structure and evaluation — compared item by item in the body below.

How can Chinese companies going global build AI search visibility?

For Chinese companies going global, the visibility gap is rarely content volume — it is the machine-readable surface. Our audit of 30 Chinese outbound companies found machine-readability the weakest category (69.2/100 average): 17 had no JSON-LD on the homepage, 15 had a missing or thin sitemap, 13 had a missing or duplicated H1. The path has four steps: audit bot reachability and machine-readability first; govern entity facts so Chinese and English statements agree; publish question-shaped content built on real overseas buyer questions; then earn third-party mentions (media, communities, partners) and verify with periodic resampling against a fixed question set.

What should a corporate website change for the AI search era?

Five changes. (1) Bot reachability: robots.txt explicitly allows AI crawlers and live fetches are not stopped by firewalls or challenge pages. (2) A machine-readable surface: an llms.txt fact file (optional aid), a complete sitemap, Markdown versions of core pages (optional). (3) Entity structure: JSON-LD naming entity types such as Organization, clean title/H1 discipline, hreflang pairing on bilingual sites. (4) Question-shaped content: pages organised around buyer questions, short answers first, FAQ schema attached. (5) Measurability: analytics that separate human and bot traffic and attribute AI-referred inquiries. Negency's own site was rebuilt to exactly this standard, and the public audit tool scores against it.

What is llms.txt, and should every company website have one?

llms.txt is a plain-text brief at the site root written for AI systems: who the company is, what it does, where the core pages live, and the canonical facts and definitions. It does not by itself raise citation rates — in Ahrefs' May 2026 study of 137,210 domains, 97% of published llms.txt files received zero requests that month, so its direct effect is near zero — but it is the cheapest fact-governance move available: one file anchors a single version of the truth that crawlers can rely on. Verdict: worth adding, useless alone; it works as part of entity-fact governance, structured data and question-shaped content. Negency's llms.txt is a full fact bible: company definition, offering boundaries, sourced cases and citation rules.

What should an enterprise prepare before deploying AI agents?

Four preparations, and we advise against starting without any of them. (1) Scenario selection: pilot on a workflow that is frequent, comparatively rule-clear and verifiable — not the most glamorous one. (2) Knowledge and data foundations: govern the knowledge base first (deduplication, versioning, permissions); a dirty knowledge base only scales errors. (3) Governance design: permission boundaries, human approval points and audit logs decided before launch, not after. (4) A measurement baseline: record the manual process's time and error rates before the pilot, or value can never be proven afterwards. Negency's method is a small controlled pilot, verified before scaling, with governance as a design input rather than a patch.