Agentic Web CensusCheck your site
EN

Trends · Pages an agent can parse

Pages an agent can parse across the web

Agents can parse the page structure. It has gone up since May 2026, and again last month. Both steps clear their margin.

Weak32.2%

Pages an agent can parse in September 2026

What the Pages an agent can parse in September 2026 is, and how it is measured

Measured on 158,168 pages, 95.3% of which carried the agentic category, with a confidence margin of ±0.13 pp.

▲ +1.3 pp
Pages an agent can parse in September 2026 over 5 months

27.8%32.2%

32.6%27.4%Pages an agent can parse · May: 27.8%Pages an agent can parse · June: 29.4%Pages an agent can parse · July: 30.3%Pages an agent can parse · August: 30.9%Pages an agent can parse · September: 32.2%Pages an agent can parseMayJuneJulyAugustSeptember
Pages an agent can parse, May 2026 to September 2026, one measurement a month. The last step was a real rise.

What this measures

Who moved

How to read these figures

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.
SegmentAugust 2026September 2026Movement
.pm30.9%78.9%▲ +48.0 pp
SoundManager23.1%66.6%▲ +43.5 pp
Plausible80.5%45.1%▼ −35.4 pp
AngularJS 125.1%57.6%▲ +32.5 pp
AngularJS25.6%55.4%▲ +29.8 pp
.click97.5%68.9%▼ −28.5 pp
Elasticsearch39.0%66.5%▲ +27.5 pp
Axeptio44.9%18.0%▼ −26.9 pp
Loadable-Components32.6%54.8%▲ +22.2 pp
Angular 1827.5%48.3%▲ +20.8 pp
Crisp Live Chat21.6%42.3%▲ +20.7 pp
Vercel Speed Insights 139.2%58.3%▲ +19.1 pp
Intercom21.4%39.8%▲ +18.4 pp
Browser-Update.org 326.2%43.7%▲ +17.5 pp
Bootstrap 114.0%31.3%▲ +17.3 pp

How to move it on your own site

1 · Read

53% of the score

An agent can build a usable picture of your page from its markup.

This is the precondition for everything else. An agent that cannot tell your navigation from your footer, or find the button that submits a form, cannot do anything on your site — however welcome it is. It is also the dimension most sites fail, and the one that carries the most weight of the three that add up.

What to do

  1. Use real landmarks: one <main>, a <nav>, a <header> and a <footer>. A page of nested <div>s has no structure to read.
  2. Give every control an accessible name. A button whose only content is an icon is an unnamed button, and an agent cannot guess what it does.
  3. Label every form field, and connect the label to its input. Placeholder text is not a label — it disappears when you type.
  4. Keep headings in order and use them for structure, not for size. An <h4> chosen because it looked right breaks the outline.
  5. Do not hide meaning in colour or position alone: an agent reads neither.
<body>
  <header><nav aria-label="Sections">…</nav></header>
  <main>
    <h1>Blue running shoes</h1>
    <form action="/basket" method="post">
      <label for="size">Size</label>
      <select id="size" name="size">…</select>
      <button type="submit">Add to basket</button>
    </form>
  </main>
  <footer>…</footer>
</body>
htmlLandmarks, a labelled field and a named button: the three things an agent looks for.

The largest of the four, and the one that pays twice: everything here also fixes accessibility for people using screen readers.