420 requirements. Nothing left to interpret.
Before we wrote the agentic layer we wrote the specification for it: a 42-page build document covering every requirement a site must satisfy to be found, understood, quoted and used — by a browser, a crawler, a retriever and an agent.
It is deliberately complete rather than novel. Items Themixify already implements sit alongside items nobody implements, so the document stays a valid specification for a theme built from zero.
42
Pages
46
Sections
420+
Individual requirements
Ten parts, forty-six sections
Every requirement carries a stated implementation method and a priority, so a developer can start building from it without a single research task.
Foundations — crawl, index, architecture
- Document head & HTML contract
- Crawlability, robots & indexation
- Canonicalisation & duplicate control
- URL architecture & site structure
- XML sitemaps & discovery surfaces
- Instant indexing & push protocols
On-page, semantics & link architecture
- Titles, meta & SERP snippet control
- Semantic HTML & heading architecture
- Internal linking & link equity
- Pagination, facets & archives
- International SEO, i18n & RTL
- Feeds & syndication
Structured data & entity modelling
- The core schema graph
- Content-type schemas — the full matrix
- Entity & knowledge-graph optimization
- Speakable, voice & assistant surfaces
Media, performance & access
- Image SEO & delivery
- Video, audio & embeds
- Core Web Vitals engineering
- Caching, edge & delivery
- Mobile, responsive & input
- Accessibility as ranking substrate
Content, authority & trust
- E-E-A-T, authorship & trust
- Content quality, freshness & decay
- Engagement & UX signals
AEO — Answer Engine Optimization
- Snippet & direct-answer engineering
- Question coverage & PAA capture
- Answer-ready formatting primitives
GEO — Generative Engine Optimization
- Retrievability & chunk design
- Citation-worthiness signals
- AI crawler policy & licensing
- Brand entity & off-site consensus
The agentic layer
- llms.txt & the machine manifest family
- Machine-readable content surfaces
- Agent capability manifests & MCP
- Agentic actions & transactions
- Agent identity, auth & rate control
- Provenance, attribution & C2PA
Vertical surfaces
- Local & multi-location SEO
- E-commerce & product SEO
- News, Discover & publisher SEO
- Programmatic & long-tail surfaces
Operations, governance & launch
- Measurement, telemetry & consoles
- In-theme auditing & editor workflow
- Security, privacy & compliance
- Code standards, compatibility & launch
The theme is the implementation
You could hand this document to a developer and build it yourself. It would take months, and you would still be maintaining it. Or you could install the version that is already finished.