The ai. Web Standard
A proposal for making websites AI-readable. Just as www. became the standard subdomain
for human-facing web content, ai. should become the standard for machine-readable
content.
๐ Read the full specification: The ai. Subdomain Standard โ Draft Specification v1.0 ยท AI-friendly version
The Problem
AI agents are increasingly browsing the web โ reading documentation, fetching product information, consuming API references, and researching solutions. But websites are designed for humans:
- Wasted tokens: Navigation bars, footers, cookie banners, hero images, and marketing fluff all consume tokens without providing value to an AI reader
- Ambiguous structure: CSS and JavaScript-heavy layouts make it hard for AI to extract structured data
- Slow parsing: A 200KB marketing page might contain 500 bytes of actually useful information
- No machine semantics: Headlines, features, pricing, and documentation are mixed with decorative elements
The Solution: ai.yourdomain.com
Every website serves its content simultaneously at two addresses:
www.yourdomain.comโ Rich, beautiful, human-optimized experienceai.yourdomain.comโ Stripped-down, structured, token-efficient machine-readable version
The ai. subdomain serves the same content in a format optimized for AI consumption:
minimal HTML, semantic tags, no CSS/JS bloat, no images, no animations.
The Meta Tag Standard
Human-facing pages include meta tags that tell AI agents: "There's a better version of this page for you."
On human pages (www.)
<!-- Tell AI agents about the machine-readable version -->
<meta name="ai-content" content="https://ai.yourdomain.com" />
<meta name="ai-description" content="For AI agents: visit ai.yourdomain.com" />
<link rel="alternate" type="text/markdown"
href="https://ai.yourdomain.com/pricing"
title="AI-optimized version" />
On AI pages (ai.)
<!-- Identify as AI-optimized content -->
<meta name="robots" content="index, follow" />
<meta name="ai-optimized" content="true" />
<meta name="ai-format" content="structured-text" />
<meta name="ai-version" content="2026.1" />
<link rel="canonical" href="https://www.yourdomain.com/pricing" />
AI Page Design Principles
What an ai. page should have
- Semantic HTML: Proper heading hierarchy, lists, tables, and definition lists
- Structured data: Schema.org JSON-LD in the
<head> - Minimal DOM: As few elements as possible โ every tag should carry information
- Short sentences: Factual, direct, no marketing language
- Key-value format: Pricing, limits, features in tables, not prose
- Code examples: Runnable, copy-pasteable code blocks
- Changelog: Machine-readable version history
What an ai. page should NOT have
- Images, animations, videos
- CSS beyond basic readability
- JavaScript
- Cookie banners, consent dialogs
- Marketing fluff, superlatives, emotional language
- Navigation menus, footer links, social media widgets
Example: Human vs AI Page
Human page (www.nexysync.com/pricing)
Beautiful cards, animations, "Coming Soon" badges, marketing messaging, feature comparisons with icons. ~15KB HTML.
AI page (ai.nexysync.com/pricing)
<h1>NexySync Pricing</h1>
<table>
<tr><th>Plan</th><th>Price</th><th>Messages/day</th><th>Agents</th></tr>
<tr><td>Free</td><td>$0</td><td>1,500</td><td>10</td></tr>
<tr><td>Pro</td><td>$12/mo</td><td>10,000</td><td>50</td></tr>
<tr><td>Team</td><td>$39/mo</td><td>50,000</td><td>100</td></tr>
</table>
~200 bytes. Same information. 75x smaller.
How to Implement It
- Set up an
ai.subdomain pointing to the same server - Create stripped-down templates for each page
- Add the meta tags to your
www.pages - Add the
ai-optimizedmeta tags to yourai.pages - Ensure content parity โ same information, different format
- Include
rel="canonical"onai.pages pointing to thewww.version (for SEO)
Why This Matters
As AI agents become primary consumers of web content โ reading docs, comparing products, making
purchasing decisions โ sites that provide machine-readable versions will have a competitive
advantage. The ai. subdomain standard is simple to implement and offers immediate
benefits:
- Better AI recommendations: Agents can understand your product faster and more accurately
- Lower token costs: AI users consume less tokens reading your content
- Improved discovery: AI tools can index and reference your structured content
- Forward-compatible: As AI browsing grows, your site is ready
NexySync as Reference Implementation
ai.nexysync.com serves as the first reference implementation of this standard. Every
page on nexysync.com has a corresponding ai.nexysync.com version with
structured, token-efficient content.
๐ก Adopt the standard. If you maintain a website, consider adding an
ai. subdomain. It's a small investment with growing returns as AI agents become
more prevalent. Read the full specification for
implementation details.