Web Almanac

In everyday web and SEO conversation, "the Almanac" almost always means the Web Almanac, HTTP Archive's annual State of the Web report. A quick note on the word first: an almanac in general is a reference book of facts and figures, often issued yearly, and in software a document called an almanac occasionally means a knowledge base or reference set. But among people who build and optimize websites, the Web Almanac is the definite and defensible sense, so that is the one this entry treats. HTTP Archive is a long-running, community-run project that has tracked how the web is built since 2010, testing millions of sites every month and storing the results in a public dataset. Each year it distills that data into the Web Almanac — a set of chapters, written by volunteer experts, covering aspects of page content, user experience, publishing, and distribution.

What makes the Almanac useful is the marriage of scale and interpretation. On one side is the raw evidence: measurements from millions of real websites, gathered with tools that inspect page structure, performance, and markup, not opinions or small surveys. On the other side is the expertise of the web community, whose volunteers turn those numbers into readable chapters that explain what is happening and why it matters. A performance chapter might report how many sites hit good Core Web Vitals; an SEO chapter might track how widely structured data or canonical tags are used; a markup chapter might show which HTML elements dominate. Because the same measurements repeat year after year, the Almanac also shows direction — whether an adoption curve is rising or a bad practice is fading — which makes it a shared reference point rather than one team's snapshot.

It is worth contrasting the Web Almanac with the industry benchmarks marketers see more often, because they answer different questions. A typical vendor benchmark reports averages from that vendor's own customers or panel — say, the email open rate across accounts on one platform. It is useful but partial, shaped by who uses that tool and how the vendor defines each metric. The Web Almanac instead measures the public web at large, using an open methodology and a public dataset anyone can inspect or query, and it focuses on how sites are built rather than on campaign outcomes. So a vendor benchmark tells you how your open rate compares to a platform's clients, while the Almanac tells you how common a given technical practice is across the web as a whole. Both are benchmarks; one is a market slice, the other a broad, transparent census of construction.

That difference shapes how to use each. Read a vendor benchmark with its sampling in mind, because the population is the vendor's users, not the world. Read the Almanac as a wide, methodical baseline for technical decisions — what share of sites use a feature, how performance is trending, whether a practice you rely on is common or fringe — and appreciate that its methodology and data are open, so its claims can be checked rather than taken on faith. It is not a substitute for measuring your own site, and it will not tell you what to do for your particular audience. But when you want a credible, non-commercial picture of the state of the web to calibrate against, the Almanac is a stronger reference than any single vendor's numbers, precisely because it looks at the whole field with methods laid bare.

Use the Almanac to calibrate, not to copy. When you want to know whether a technical practice — a markup pattern, a performance target, an SEO tactic — is standard, emerging, or already stale across the web, the relevant chapter gives you a broad, data-backed answer to weigh against your own measurements. Read the methodology so you understand what was measured and how, because the framing matters as much as the number. Track a metric across editions rather than fixating on one year, since the trend is usually more instructive than a single figure. And treat the chapters as expert interpretation you can learn from, following the analysis and the caveats the authors raise, not just the headline statistics. Cited well, an Almanac finding is a defensible, checkable fact rather than an unsourced claim.

The pitfalls are mostly about overreach. The Web Almanac describes what the web at large does, which is not the same as what is right for your audience, so do not turn a population statistic into a rule for your site — that many sites do something does not make it correct for you. Do not confuse it with a marketing-outcome benchmark; it measures how sites are built, not how campaigns perform, and using it to set a conversion or open-rate target is a category error. And be careful with the ambiguous word: if you mean a different "almanac" — a general reference volume, or some product's internal knowledge base — say so plainly, because in a web or SEO context readers will assume the HTTP Archive report. Used within its lane, the Almanac is one of the most trustworthy public references on the state of the web.

The Web Almanac — HTTP Archive's annual State of the Web report since 2019 — pairs crawl data from millions of sites with community-written chapters, and is the default sense of "almanac" in web and SEO usage.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where web almanac is a core concern: