AI-Ready Website Checklist.
A rigorous pre-launch engineering checklist for developers, software architects, and technical leads building modern websites structured for AI retrieval, answer engines, and autonomous agents.
Strict Semantic HTML5 Structure (<main>, <article>, <section>)
Replace generic `<div>` soup with landmark HTML5 elements. Ensure the primary page content lives exclusively within `<main>` and discrete articles within `<article>`.
<main id="main">
<article className="prose">
<h1>Direct Topic Headline</h1>
</article>
</main>Hierarchical Heading Architecture (H1 -> H2 -> H3)
Exactly one `<h1>` per page matching the document entity. Section headers strictly nested without skipping levels (e.g. no jumping from H1 directly to H4).
Tabular Data in Semantic <table> Elements
Structure comparative data, price matrices, and specifications using semantic `<table>`, `<thead>`, `<th>`, and `<tbody>` rather than CSS flex/grid divs.
<table> <thead><tr><th>Tier</th><th>Deliverable</th></tr></thead> <tbody><tr><td>DIP Beacon</td><td>AI Tracking</td></tr></tbody> </table>
Descriptive Microcopy & Accessible Image Alt Attributes
All technical diagrams, workflow graphics, and UI previews must have complete, context-rich `alt="..."` descriptions and caption text.
Top-Level @graph Array Unification
Unify all isolated `<script type="application/ld+json">` tags into a single root `@graph` network connecting Organization, WebSite, WebPage, and BreadcrumbList.
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Organization", "@id": "https://example.com/#org" },
{ "@type": "WebSite", "@id": "https://example.com/#site", "publisher": { "@id": "https://example.com/#org" } }
]
}Explicit @id URI Anchoring on All Entities
Assign unambiguous `#entity` fragment identifiers to all core nodes (e.g. `https://example.com/#organization`, `https://example.com/#primary-clinic`).
Comprehensive sameAs Cross-Verification Nodes
Include verified links to official corporate registries (ACRA, Singapore government directories, LinkedIn company pages, Google Maps CID).
ISO 8601 Date Formatting & dateModified Headers
Use complete ISO 8601 format (`YYYY-MM-DD` or `YYYY-MM-DDTHH:MM:SS+08:00`) for `datePublished` and `dateModified` in Article/TechArticle schema.
Server-Side Rendering (SSR) / Static Site Generation (SSG)
Deliver pre-rendered HTML on first byte. Avoid client-only client rendering (CSR) where content is injected after JavaScript execution.
Time to First Byte (TTFB) < 300ms on Singapore Edge
Serve static assets and cached HTML via edge CDN (Vercel, Cloudflare) with TTFB consistently below 300ms from Singapore nodes.
Explicit AI Crawler Directives in robots.txt
Declare explicit `User-agent: GPTBot`, `ClaudeBot`, and `PerplexityBot` rules with `Allow: /` for indexable paths.
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: /
Automated XML Sitemap with Priority & lastmod Flags
Maintain an automated `sitemap.xml` generated at build time with valid `<lastmod>` timestamps matching content git commit history.
Direct Answer In First 30% of DOM
Place direct, factual summaries (40–60 words) immediately beneath primary topic H2 headings before explanatory background.
Factual Claim Backing with Citation Sources
Ground statistical claims, regulatory rules, and clinical facts with linked source citations to government registries (MOH, HSA, ACRA) or RFCs.
Deterministic FAQ Schema Pairing with On-Page Q&A
Ensure every question-answer pair listed in on-page accordions has an exact 1:1 match inside the `FAQPage` schema `mainEntity` array.
Mobile Touch Targets & Core Web Vitals Compliance
Zero layout shift (CLS < 0.05), Largest Contentful Paint (LCP < 2.0s), and touch target minimums (48x48px) on mobile viewports.
Root /llms.txt Machine Context File
Deploy a root-level `/llms.txt` markdown file providing LLMs with concise company context, key service endpoints, and documentation under 2,500 tokens.
Secondary /llms-full.txt Extended Dataset
Deploy an extended `/llms-full.txt` containing full research transcripts, case study datasets, and technical documentation.
Machine-Readable Open Graph & Twitter Meta Tags
Deploy complete `og:title`, `og:description`, `og:image` (1200x630px), `og:locale` (`en_SG`), and `twitter:card` tags on every page.
Deterministic Error Handlers & 404 Header Validation
Custom 404 page must return HTTP status 404 Not Found (never HTTP 200 soft-404) and link back to core site navigation.
Need Help Implementing This Technical Architecture?
Infinitus works directly with engineering teams and enterprise brands to build end-to-end JSON-LD knowledge graphs, SSR infrastructure, and machine discovery endpoints.