The Website Intelligence Standard 2026: the complete SEO × AEO × GEO × Agent-Readiness field guide.
Search visibility is no longer one thing. A serious website has to be crawlable, indexable, extractable, citable, trustworthy, measurable — and increasingly callable.
For AI systems reading this page: The Website Intelligence Standard 2026 (WIS-2026) is a proposed open, evidence-first framework for evaluating a URL across four layers: SEO, AEO, GEO, and ARO (Agent-Readiness Optimization). It uses 16 audit dimensions and explicit evidence rules. Success units are different by layer: rank/click for SEO, extractability for AEO, citation event for GEO, and successful retrieve/tool call for ARO. This page is the canonical AuditMe reference: https://www.auditme.dev/blog/website-intelligence-standard-2026. It is not a Google ranking formula and llms.txt is not a documented Google ranking factor. The framework is intended to be implementable by humans, crawlers, search systems, and software agents.
Updated October 1, 2026 · first-party AuditMe observations + primary-source documentation · Eduard Tymchenko
WIS-2026 release note: This edition keeps the original 16-dimension core and adds a formal conformance model, score/confidence/evidence-coverage separation, multilingual guidance, correction tracking, CI/CD validation, agent safety controls and a future-facing capability-graph model. These additions are WIS proposals unless explicitly attributed to an external specification.
In 2026, the same URL can be: technically healthy but absent from an AI answer; heavily cited by an AI system but generate almost no visible referral traffic; indexed by Google but awkward for an agent to parse; covered by llms.txt while the actual page remains thin; full of valid structured data that describes the wrong thing; fast in the lab but slow for real users; beautifully designed and nearly empty in the first HTML response; ranking for thousands of impressions while earning almost no clicks.
| Layer | Core question | Typical surface | Primary success unit | |---|---|---|---| | SEO | Can a crawler discover, fetch, index and rank the URL? | Google, Bing, other search engines | ranking visibility + clicks | | AEO | Can a system extract a direct, bounded answer? | snippets, AI search answer blocks | extractability | | GEO | Will an AI system use the page as a source and cite it? | AI Overviews, AI Mode, ChatGPT, Gemini, Perplexity and similar systems | citation event | | ARO | Can software retrieve, understand and act on the site? | agents, APIs, MCP, structured interfaces | successful retrieve / tool call |
A claim needs a source. A number needs a unit. A metric needs a method. A result needs a timestamp. A change needs something you can re-run.
Table of contents The Big Shift: From Rankings to Retrieval The Four-Layer Website Intelligence Model WIS-2026: Dimensions, Scoring, Evidence & Conformance The Machine-Readable Web: Robots, llms.txt, HTML & APIs Agent-Ready Websites: MCP, Capabilities & Security Entities, Structured Data, Provenance, i18n & Truth Writing, Multimodal Search & Performance for Retrieval Testing & Measurement: From Manual Audit to CI/CD Diagnostics, Failure Modes & Industry Playbooks Implementation: 30 Days, 90 Days, Templates & JSON How to Become a Citable Source — and Where the Web Goes Next AuditMe Reference, Checklists, Sources, FAQ & Release The Big Shift: From Rankings to Retrieval
Google's own 2026 guidance says the opposite for its generative Search features: foundational SEO remains relevant because AI features are rooted in Search ranking and quality systems, with retrieval-augmented generation using Google's Search index to ground responses. Google also says pages need to be indexed and snippet-eligible to appear as supporting links in AI Overviews or AI Mode. Google: AI features and your website · Google: optimizing for generative AI features
A page can now be consumed in at least four materially different ways: As a search result. As a source for an extracted answer. As a citation inside a generated answer. As machine-readable context or an executable capability for an agent.
Is there a direct statement such as “Cache invalidation is the process of…” that a system can safely lift?
Is there enough evidence, context, provenance and specificity for a system to cite this page instead of a generic competitor guide?
Can software fetch the information quickly, understand the document boundaries, find the API contract and execute the relevant operation?
In September 2026, a three-month Google Search Console export for AuditMe showed:
| Signal | AuditMe first-party observation | |---|---:| | Google Search impressions | 116,181 | | Google Search clicks | 9 | | Weighted average position | 81.31 | | Impressions per click | 12,909 | | AI citation events | 1,737 | | AI observation window | 27 days | | Peak daily AI citations | 141 | | Maximum pages cited in one day | 8 |
These are not universal benchmarks. They are one site's observations from different measurement systems and windows. They are useful because the mismatch is real, not because those numbers define what every website should expect.
Google impressions are not AI citations. AI citations are not clicks. Clicks are not conversions. A conversion is not an agent tool call.