Summary
AI-Ready Web is the UAIX program for websites that need to remain excellent for humans while becoming reliable for AI systems. It defines how to make pages accessible, content discoverable, APIs deterministic, capability claims bounded, delegation auditable, privacy preserved, and future standards adoption honest.
Agent implementation contract
When a user sends an agent to this AI-Ready Web guidance, the assignment is to apply the strategy to the user’s target site, repository, or publication package. Treat UAIX as the reference standard and checklist. Do not copy UAIX page content into the target site, do not create a page about UAIX guidance, and do not publish an “AI-Ready Web” explainer unless the user explicitly asks for that output.
The expected target-site evidence set is concrete: public manifest, .well-known discovery, route inventory, readiness result, robots.txt, sitemap, llms.txt, structured data, visible support boundaries, targeted checks, and package or root-file output when publication is requested.
| Agent step | Do the real implementation | Do not do this |
|---|---|---|
| Resolve the target | Identify the target domain, repo root, public routes, build system, CMS, deployment package, root-file output path, and current evidence before editing. | Assume UAIX.org is the target site, summarize this page, or make a new guidance page because this page was provided as a reference. |
| Audit the existing site | Check human HTML, headings, metadata, canonical URLs, robots, sitemaps, schema, .well-known files, llms files, APIs, route inventories, readiness records, accessibility, privacy, and support boundaries. | Skip the target-site audit and only restate AEO/GEO/SEO definitions. |
| Implement improvements | Update the target site’s pages, navigation, structured data, discovery files, route inventory, readiness records, public evidence, AEO/GEO/SEO copy, no-op guidance, review paths, and publish-package root files where the audit shows gaps. | Keyword-stuff, cloak, add hidden bot-only text, inject prompts for models, fabricate citations, or create synthetic doorway pages. |
| Verify and package | Run the site’s targeted checks, record changed files and routes, name skipped checks and blockers, and provide the requested root files, root ZIP, or publish package when the user asks for deployable output. | Claim readiness, certification, endorsement, ranking gains, live publication, or agent authority without evidence. |
Scope
The program complements UAI-1. UAI-1 is the portable public exchange, evidence, memory, trust-declaration, and handoff layer. HTTP APIs and OpenAPI describe route-level interfaces. MCP describes model/tool/resource integration in compatible host environments. A2A or other protocols may handle agent discovery, delegation, and task coordination when a site actually implements them. AI-Ready Web records how those layers fit together without merging them.
Operating principles
- Human-first, agent-compatible: do not sacrifice people, accessibility, or clarity for bots.
- Stable standards before speculative protocols: label every mechanism by maturity.
- Evidence over assertion: current support requires page copy, machine artifact, test, and release evidence.
- Least privilege and no-op safety: agents should use the lowest safe route and stop when unsupported.
- Vendor neutrality: the program should work across browsers, frameworks, runtimes, and agent vendors.
- One source of truth: human pages, manifests, schemas, examples, validators, and release notes must agree.
AEO/GEO: do the right thing
SEO means Search Engine Optimization. AEO means Answer Engine Optimization. GEO means Generative Engine Optimization. UAIX treats SEO/AEO/GEO as one public-interest publishing discipline: make pages useful for humans first, then make answers easy to find, verify, quote, compare, and route back to source evidence without hiding content from humans or trying to manipulate model output.
| Do | Do not | Why it matters |
|---|---|---|
| Write direct answer sections with stable headings, plain definitions, examples, limitations, dates when needed, and links to canonical evidence. | Stuff repeated keywords, publish AI-only doorway copy, or hide facts from the human page while showing them to bots. | Answer engines and generative systems need the same trustworthy source that a human reviewer can inspect. |
| Expose provenance: author or owner, last-reviewed state, primary source links, schema IDs, route IDs, checksums, release notes, and review paths where relevant. | Invent authority, cite stale reports as current truth, or use structured data that says more than the visible page supports. | Good AEO/GEO makes answers citable and correctable instead of merely extractable. |
| Use semantic HTML, accessible names, lists, tables, definitions, FAQ-style sections when helpful, JSON-LD where accurate, sitemaps, well-known manifests, and optional llms files that agree with canonical pages. | Treat llms.txt, schema markup, hidden prompts, or synthetic summaries as replacements for clear public content. | Machine-readable layers should reinforce the public page, not become a parallel truth surface. |
| State support boundaries, no-op behavior, unsafe-action handling, and human review routes beside claims. | Imply that AI visibility grants permission to scrape, authenticate, post, mutate data, validate credentials, certify safety, or bypass local policy. | Responsible AEO/GEO helps agents stop safely when the request exceeds public authority. |
| Keep content fresh through release notes, route inventories, readiness results, localization checks, and drift audits. | Chase model-specific hacks, fake citations, auto-generated pages with no review, or unverifiable ranking promises. | The durable win is a better web: accurate pages, stable routes, transparent evidence, and fewer hallucinated answers. |
Term pages
Seven-volume program
Current maturity model
| Status | Use it for | Examples | UAIX rule |
|---|---|---|---|
| Stable baseline | Requirements that should be implemented before any agent-specific claim. | WCAG 2.2, semantic HTML, HTTP semantics, robots.txt, sitemap, JSON Schema, OpenAPI, Problem Details, Trace Context, JSON-LD. | May be required language when relevant and tested. |
| Current optional | Useful capabilities with real implementations but environment-specific adoption. | MCP in compatible hosts, A2A where supported, signed non-human principal flows, structured alternate representations. | Label as supported only when the local implementation has public evidence. |
| Proposal or community convention | Helpful discovery or policy signals that are not formal web standards. | AEO/GEO terminology, llms.txt, markdown mirrors, agent preference files, TDMRep-style rights signals. | Use as advisory signals and never as the only source of authority. |
| Research track | Ideas to monitor without current support claims. | WebMCP/browser-native tool declarations, DNS-based agent discovery, autonomous agent commerce credentials beyond published APIs. | Keep in roadmap language until specifications, implementations, tests, and release evidence exist. |
| Unsupported | Claims UAIX must not imply. | Hosted runtime execution, automatic repository writes, hidden credential validation, certification, endorsement, safety proof, consciousness proof. | Block or rewrite the claim. |
Machine-readable files
- Requirement registry JSONStable ARW requirement identifiers, tests, evidence, and anti-patterns.
- Maturity register JSONCurrent stable, configuration-specific, proposal, research, and unsupported mechanisms.
- Route inventory JSONSource/live audit facts, publication boundary, and route exposure plan.
- AI-Ready site manifest schemaPortable declaration for discovery, capabilities, policies, evidence, and support boundaries.
- AI-Ready site manifest exampleConcrete UAIX-flavored example without claiming hosted runtime execution.
- Readiness result schemaAssessment result model for automated checks plus manual review evidence.
- Readiness result exampleExample scoring packet with warnings, blockers, and no certification claim.
Support boundary
AI-Ready Web records are public guidance, schemas, examples, and review evidence. They do not authorize scraping, bypass local policy, validate credentials, grant tools, execute workflows, certify vendors, endorse agents, prove safety, or prove consciousness. Unsupported actions should return no-op plus human review.