The Website Specification
The article outlines the essential technical features that every good website should possess. It emphasizes a platform-agnostic approach, providing a checklist that covers various topics such as SEO, accessibility, and security. The specification is designed for both humans and AI agents, encouraging open collaboration and continuous improvement.
- ▪The checklist includes 111 topics related to website standards and best practices.
- ▪Key areas covered include HTML basics, search visibility, accessibility, and performance.
- ▪The specification is open for contributions and encourages users to report gaps or outdated information.
2 outlets in our directory ran this story, first to last over 15 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Does Senja slows down your website? — r/SaaS
Hacker News (Front Page) files mainly under programming. We currently carry 993 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The Website Specification |
| Canonical URL | https://specification.website/ |
| Publication time | Sun, 31 May 2026 07:09:50 +0000 |
| Retrieval time | 2026-05-29T17:20:02.488Z |
| Last seen | 2026-05-31T07:48:30.792Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | YW4mUPWt8kjD · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
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. Browse all 111 topics → Get the checklist ★ on GitHub Categories Ten areas, mapped to widely-accepted standards. All topics → Foundations 13 The HTML, head, and document basics every page needs. SEO 13 Search visibility — robots.txt, sitemaps, canonicals, structured data. Accessibility 17 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 8 Standard, agreed-upon paths under /.well-known/. Agent Readiness 18 Things that make a site legible to AI agents and crawlers.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Website Specification.
Discussion
0 commentsMore from The Website Specification
