AI search
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.
Read the full answer →AI search
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.
Read the full answer →AI search
Separate the crawlers by purpose before deciding: search-index crawlers (OAI-SearchBot, PerplexityBot) and user-triggered fetches (ChatGPT-User) decide whether you can appear in AI answers at all; training crawlers (GPTBot and peers) are a separate licensing choice — a company may allow search while declining training. For a website whose job is winning customers, explicitly allow at least the search and user agents: if they cannot fetch your pages, AI answers cannot cite you. Whether to allow training follows your own content-licensing policy. In our audit of 30 Chinese outbound companies, only 3 blocked all three major AI crawlers — and those three have capped their own visibility ceiling. Allowing is not exposure: keep admin paths closed, rate-limit by real IP against abuse, and declare training/search/input permissions separately via Content-Signal. Negency's own robots policy — allow everything, close only admin paths, rate-limit for protection — is public and reusable.
Read the full answer →AI search
An audit checks roughly 30 signals along one chain — can AI find you, read you and trust you — in five groups: crawler reachability (are bots allowed in, is the sitemap complete), machine-readable surface (llms.txt, Markdown versions, fetch success), entity facts (is company information structured and consistent everywhere), content structure (question-shaped organisation, heading hierarchy, short answers first) and citation readiness (do cases and numbers have public, checkable sources). Negency's free audit scores each group and points at specific pages and problems, not just a single total.
Read the full answer →AI search
Structured data is the 'fact sheet' machines read: it tells crawlers unambiguously which company an entity is, what a page is (an FAQ, a service, a report), and what the facts inside are. Its importance is asymmetrical — it does not buy you citations, but its absence causes a class of real failures: AI reads your facts wrong, merges you with a namesake company, or simply cannot parse your pages. In Negency's sample of 30 Chinese companies going global, 17 lacked JSON-LD entirely — the most common major gap in the whole machine-readable group.
Read the full answer →AI search
Do not start with complaints to the AI companies — the wrong fact almost always comes from a wrong or conflicting source the engine is reading. The fix order: find which page the wrong version lives on (often your own outdated page, a platform listing or Wikipedia); make one canonical, machine-readable version of the truth easy to find (llms.txt plus JSON-LD on the official site); correct the third-party sources in citation order; then verify by re-sampling the same questions over the following weeks. Vendor feedback channels exist but are slow — treat them as escalation, not the fix.
Read the full answer →