Website Specification map

Standards translated into implementation responsibilities

The canonical standard is specification.website. This page explains how agents should implement each category inside this repo.

Foundations

Stable pages, titles, descriptions, canonicals, favicon, social image, and clear route ownership.

SEO

Sitemap, robots, canonical URLs, unique metadata, one H1, internal links, schema, and crawl evidence.

Accessibility

Semantic landmarks, skip link, focus styles, contrast, keyboard-safe controls, and no clipped mobile text.

Security

Static host headers, security.txt, no secrets, no unsafe external scripts by default.

Well-Known URIs

security.txt plus only relevant well-known endpoints.

Agent Readiness

llms.txt, llms-full.txt, schemamap.xml, schema JSON endpoints, file-map.json, qa-contract.json, examples.json, contract-registry.json, site-studies.json, seo-aeo-evaluation.json, source-traceability.json, site-type-playbooks.json, page-patterns.json, page-pattern-fixtures.json, conversion-copy.json, offer-ecosystem.json, infrastructure-decisions.json, browser-visual-qa.json, crawl-evidence.json, design-system-contracts.json, aeo-geo-context.json, why-explanations.json, real-site-comparisons.json, handoff-reports.json.

Performance

Static output, minimal JavaScript, stable dimensions, local assets, and crawlable HTML-first pages.

Privacy

Privacy page placeholder, no analytics by default, source separation, no private data in public outputs.

Resilience

404 page, direct internal links, no internal redirects, route tests, and crawl evidence.

Internationalisation

html lang, locale config, and documented future hreflang expansion point.