Agentic Web Census

August 2026by Omitsis

English

Census report · August 2026

The web reaches 19.9% on the Agentic Web Census Score in August, and the step clears its own margin.

This is August 2026, frozen. The index went up against July 2026, by more than the margin allows us to call a wobble.

What moved it

Poor19.9%

AWCS

What the AWCS is, and how it is measured

Measured on 14,373 pages, 95.8% of which carried the agentic category, with a confidence margin of ±0.44.

▲ +0.8
AWCS over 4 months

14.3%19.9%

Read

What Read measures

Lighthouse builds the accessibility tree an agent would traverse and scores the page pass or fail. The denominator is only the pages the audit could evaluate: a notApplicable or an error is excluded rather than counted as a failure, and the fraction that could be evaluated is published beside it as the coverage.

n=14,374 · coverage 95.8% · margin ±0.44 pp.

53% of the score
Read on its full scale

Weak30.4%

Read: 4 months, up▲ +1.3 pp
Guide

What Guide measures

The llms-txt audit passing: a file is served AND Lighthouse considers it valid. The denominator is every sampled page, so this is a fraction of the whole web and not of the sites that have a file. This is the figure the index uses, because a broken file does not guide an agent.

n=14,373 · coverage 95.8% · margin ±0.44 pp.

27% of the score
Guide on its full scale

Poor13.1%

Guide: 4 months, no significant change= +0.1 pp
Act

What Act measures

A count, not a percentage: how many sampled sites register WebMCP tools that an agent can call. It is the audit that defines the Act dimension — the other two WebMCP audits measure how good those tools are, not whether they exist.

n=14,374 · coverage 95.8% · margin ±0.44 pp.

20% of the score
Act on its full scale

Very poor5.1%

Act: 4 months, up▲ +0.6 pp
Reachable

What Reachable measures

Read from the robots.txt of the sampled sites: of the AI agents we track, how many are NOT disallowed. Gradual and not a yes or no — turning away one agent out of seventeen is not the same as turning away all of them. A site with no robots.txt blocks nobody, so it counts as fully reachable: that is a measurement, not a gap. This is the only figure that MULTIPLIES the index instead of adding to it, because it is a precondition: if an agent cannot fetch the page, nothing else about the page matters. One caveat we would rather state than hide: a blanket Disallow under User-agent: * is not counted, because the corpus-wide measurement cannot see it either, and we would rather be consistent than clever.

n=15,009 · coverage 100.0% · margin ±0.43 pp.

multiplies the rest
Reachable on its full scale

Excellent96.0%

Reachable: 4 months, no significant change= −0.2 pp

Every figure of the month

Each one with the sample it was measured on and the margin that comes with it.

FigureAugust 2026PagesMargin
AWCS19.9%14,373±0.44
Pages an agent can parse30.4%14,374±0.44 pp
Agents that can reach the site96.0%15,009±0.43 pp
Sites with a valid llms.txt13.1%14,373±0.44 pp
Sites exposing tools73514,374±64 sites
Sites serving an llms.txt34.0%14,373±0.44 pp
Sites with an AI crawler policy9.6%15,009±0.43 pp
Layout stability88.6%14,370±0.44
Forms an agent can fill98.4%735±1.95 pp
Valid tool schemas98.8%735±1.95 pp
Google's category score57.3%14,369±0.44

What moved

366 segments moved by more than their margin, and 2,124 were compared and did not move. 693 appear for the first time, which is not a movement from zero — it is a debut.

SegmentMonth beforeAugust 2026Movement
Squeezely0.0%100.0%▲ +100.0
Chili Piper0.0%80.0%▲ +80.0
ConvertFlow0.0%80.0%▲ +80.0
Advanced Custom Fields 680.0%0.0%▼ −80.0
web-vitals 30.0%80.0%▲ +80.0
a3 Lazy Load 10.0%80.0%▲ +80.0
.lat28.2%100.0%▲ +71.8
AMP for WordPress0.0%71.1%▲ +71.1
Qualified8.9%80.0%▲ +71.1
.org.sa66.7%0.0%▼ −66.7
Three.js 1840.0%62.2%▲ +62.2
Albacross0.0%53.3%▲ +53.3
Ambassador53.3%0.0%▼ −53.3
Apple MapKit JS0.0%53.3%▲ +53.3
Avada Size Chart46.7%100.0%▲ +53.3
Baidu Maps0.0%53.3%▲ +53.3
Bold Upsell100.0%46.7%▼ −53.3
Comm1000.0%53.3%▲ +53.3
Commanders Act TagCommander0.0%53.3%▲ +53.3
Contenido53.3%0.0%▼ −53.3

The two ends

The five highest and the five lowest technologies of the month, by index.

EndTechnologyAWCSPages
HighestSegmentStream100.0%1
HighestVerifyPass100.0%1
HighestBeeketing100.0%1
HighestCustomily100.0%1
HighestAvada Size Chart100.0%1
LowestCreateJS0.0%1
LowestSite Search 3600.0%2
LowestThemeZee Poseidon0.0%1
LowestGroupBy0.0%1
LowestAtlassian Confluence0.0%1

The data behind this report

How this report is written, and which parts a model may touch

figures passed to the model: 835
numbers it may write: only those, or their roundings
if it writes any other: the build FAILS and nothing is published
the contractThe rule is executable and not a promise: lib/prose.ts rejects a number nobody passed in, and thirteen tests hold it there.
Everything on this page is calculated — the figures, the deltas, the tables, the records and this note. The headline, the "what moved it" and the advice were written by claude-opus-5 on 2026-08-23, from the figures above and nothing else: no database access, nothing to compute. The text is stored in the repository and validated again at build time, so a number nobody passed in stops the build instead of reaching this page.Every figure here comes from a sample, not from counting every site — so it carries a margin: how much it could move if we had happened to sample different pages. A figure measured on a thousand pages has a wide margin; one measured on a hundred thousand has a narrow one. It matters for one thing: two figures that differ by less than the wider of their margins are not one above the other, they are tied. That is why nothing here has a position number.

Every figure above, as a file. A report you cannot check is an opinion.

curl -O https://agenticwebcensus.drupal.omitsisdev.com/report/2026-08.json
shellThe aggregate of August 2026, exactly as the site read it.