Agentic Web Census

August 2026by Omitsis

English

Domain suffix · August 2026

Are .lv sites ready for AI agents?

.lv scores 11.8%, indistinguishable from the web overall once the confidence margin of ±18.74 is taken into account.

Poor11.8%

AWCS

What the AWCS is, and how it is measured

Measured on 8 pages, 100.0% of which carried the agentic category, with a confidence margin of ±18.74.

= −3.2
AWCS over 4 months

14.4%11.8%

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=8 · coverage 100.0% · margin ±18.74 pp.

53% of the score
Read on its full scale

Poor12.5%

Read: 4 months, no significant change= −12.5 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=8 · coverage 100.0% · margin ±18.74 pp.

27% of the score
Guide on its full scale

Poor12.5%

Guide: 4 months, no significant change= +4.2 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=8 · coverage 100.0% · margin ±18.74 pp.

20% of the score
Act on its full scale

Poor12.5%

Act: 4 months, no significant change= +12.5 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=8 · coverage 100.0% · margin ±18.74 pp.

multiplies the rest
Reachable on its full scale

Excellent94.1%

Reachable: 4 months, no significant change= −2.0 pp
All sites
All sites: 19.9%
19.9%
.lv
.lv: 11.8%
11.8%
00.250.500.751.0
.lv against the web overall. The scale is always 0–1.

What else we measure here

12.5%
Sites with an AI crawler policy

Sites with an AI crawler policy

Sample
n=8
Coverage
100.0%
94.1%
Agents that can reach the site

Agents that can reach the site

Sample
n=8
Coverage
100.0%
12.5%
Pages an agent can parse

Pages an agent can parse

Sample
n=8
Coverage
100.0%
12.5%
Sites serving an llms.txt

Sites serving an llms.txt

Sample
n=8
Coverage
100.0%
12.5%
Sites with a valid llms.txt

Sites with a valid llms.txt

Sample
n=8
Coverage
100.0%
1
Sites exposing tools

Sites exposing tools

Sample
n=8
Coverage
100.0%

How this was measured