Skip to content
HN On Hacker News ↗

The Website Specification

▲ 559 points 221 comments by k1m 3mo ago HN discussion ↗

Pangram verdict · v3.3

We believe that this document is fully AI-generated

99 %

AI likelihood · overall

AI
0% human-written 100% AI-generated
SEGMENTS · HUMAN 0 of 2
SEGMENTS · AI 2 of 2
WORD COUNT 339
PEAK AI % 99% · §2
Analyzed
May 31
backend: pangram/v3.3
Segments scanned
2 windows
avg 170 words each
Distribution
0 / 100%
human / AI fraction
Verdict
AI
Pangram v3.3

Article text · 339 words · 2 segments analyzed

Human AI-generated
§1 AI · 99%

What a good website does. A platform-agnostic specification of the technical features every decent website should have — from <title> to /.well-known/security.txt, from WCAG contrast to llms.txt. Written for humans and agents. Categories Ten areas, mapped to widely-accepted standards. All topics → Foundations 14 The HTML, head, and document basics every page needs. SEO 13 Search visibility — robots.txt, sitemaps, canonicals, structured data. Accessibility 20 WCAG-aligned rules so people of all abilities can use the site. Security 12 Headers, transport, and policies that keep visitors safe. Well-Known URIs 9 Standard, agreed-upon paths under /.well-known/. Agent Readiness 18 Things that make a site legible to AI agents and crawlers. Performance 19 Core Web Vitals, caching, images, fonts, network behaviour. Privacy 6 Consent, signals, and respecting visitor choice. Resilience 5 Graceful failure — error pages, offline, redirects. Internationalisation 12 Language, locale, direction, and translated content. Standards, not opinions Each topic links back to the source standard — WHATWG, W3C, IETF RFCs, WCAG, MDN, and the organisations defining the modern web. Platform agnostic Whether you ship WordPress, Drupal, TYPO3, Next.js, Astro, Hugo, a Django app, or plain HTML, the spec is the spec. Implementation hints follow it, not the other way round. Built in the open Every page has an Edit on GitHub link. PRs welcome. Sources credited on every page. Let your agent query the spec. The whole spec is available as an open MCP server — read-only, no auth — plus a published Agent Skill that teaches any compatible agent when and how to use it. Per-page Markdown is available via /llms.txt and Accept: text/markdown on any spec URL.

§2 AI · 99%

{ "mcpServers": { "specification-website": { "transport": "http", "url": "https://mcp.specification.website/mcp" } } } How to use this site 01 Audit Run through the checklist. Each item is a “does the site do this — yes or no.” 02 Learn Click into any item for what it is, why it matters, and how to implement it. 03 Improve Found a gap, a stale fact, or a missing topic? Open a PR. Sources required.