Agentic Web CensusCheck your site
EN

Census report · July 2026

The web reaches 19.9% in July, and for the first time a real number of sites expose tools an agent can call: 7,395 of them.

This is July 2026, frozen. The index went up against June 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 159,678 pages, 95.6% of which carried the agentic category, with a confidence margin of ±0.13.

▲ +2.5
AWCS over 3 months

15.2%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=158,168 · coverage 95.3% · margin ±0.13 pp.

53% of the score
Read on its full scale

Weak32.2%

Read: 5 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=158,165 · coverage 95.3% · margin ±0.13 pp.

27% of the score
Guide on its full scale

Poor14.8%

Guide: 5 months, up▲ +0.9 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=158,176 · coverage 95.3% · margin ±0.13 pp.

20% of the score
Act on its full scale

Very poor4.6%

Act: 5 months, up▲ +0.2 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=166,024 · coverage 100.0% · margin ±0.13 pp.

multiplies the rest
Reachable on its full scale

Excellent95.5%

Reachable: 5 months, no significant change= −0.1 pp

Every figure of the month

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

FigureJuly 2026Pages
AWCS19.9%159,678
Pages an agent can parse30.3%159,679
Agents that can reach the site96.0%167,055
Sites with a valid llms.txt13.6%159,678
Sites exposing tools7,395159,693
Sites serving an llms.txt34.1%159,678
Sites with an AI crawler policy10.2%167,055
Layout stability87.7%159,693
Forms an agent can fill98.7%7,395
Valid tool schemas96.2%7,395
Google's category score57.2%159,663

The two ends

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

EndTechnologyAWCSPages
HighestSeal Subscriptions65.7%101
HighestShopPad Infinite Options64.4%125
HighestAmerican Express64.3%3,141
HighestMastercard63.5%3,527
HighestVisa63.5%3,534
LowestSubstack0.0%245
LowestLoja Integrada0.1%168
LowestShoptet1.3%141
LowestMediaWiki1.4%232
LowestShopline1.4%129

The data behind this report

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

figures passed to the model: 29
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-09-24, 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.com/report/2026-07.json
shellThe aggregate of July 2026, exactly as the site read it.