Common agent-readiness gaps in a measured sample
Sources checked 2026-09-15
A prospecting sample of 567 company sites revealed recurring technical gaps. This guide explains the patterns while keeping the sample and scanner limitations visible.
Marketing sites are often strong for people and weak for agents, and the gaps are predictable. The evidence here is a scan of 567 company sites with one independent scanner between 28 June and 3 September 2026, which grew out of an earlier write-up of sixteen Finnish sites. The sample is a prospecting list and not a random draw, so read it as what recurred in the sites reviewed rather than as a count of the whole web. Of the 567 sites, 485 read Level 1 of 5, the floor an ordinary CMS reaches, and 74 read Level 0, below it.
Rendering
A site that builds its content with JavaScript returns an empty shell to any agent that does not run a browser, so for those clients the content never arrives in the first response. This is the gap that shows up first among the Level 0 sites, because a site with no content in the first response has nothing else to fall back on.
Discovery
No llms.txt and a thin or missing sitemap leave an agent with nothing to read but rendered pages. Among the 74 Level 0 sites, 68 have a first-fix note, and robots.txt appears in 45 of those notes and the sitemap in 38, with 29 naming both: a robots.txt the CMS shipped by default and a sitemap that is missing or never announced in it. Among the 439 Level 1 sites with a note, the sitemap appears in 102 and llms.txt in 99.
Content
Only HTML is offered, with no markdown form, so an agent spends its budget on markup and truncates the page. This is a cost problem rather than a discovery problem: the agent found the page, but reading it took more of its budget than the content was worth.
Data correctness
Capability is usually undeclared. The site may have an API or a useful action, but with no server card or OAuth discovery, an agent cannot find or use it. Among the 439 Level 1 sites with a note, robots.txt appears in 72, structured data in 49 and an MCP server in 35. Structured data is often missing too, so prices and facts are left for the agent to infer from layout instead of reading them from a declared source.
Verification
None of these gaps require a rebuild. The work is mostly at the edge and in a few small files, and the result shows up in a scanner on the next run against the version of the site that is live then. A site does not have to change its structure to become legible to agents, it has to publish what agents already look for and verify with a fresh scan that the fix landed.
turva.dev runs this exact review and reports each gap with a concrete fix. For an audit, contact info@turva.dev.
Frequently asked
What are the most common agent-readiness gaps on marketing sites?
Client-side rendering that returns an empty shell to non-browser agents, no llms.txt and a thin or missing sitemap, and HTML-only delivery with no markdown form. Capability is usually undeclared and structured data is often missing, so prices and facts are left for the agent to infer.
Are agent-readiness gaps hard to fix?
Not usually. The work is mostly at the edge and in a few small files, and the result shows up in a scanner on the next run. A site does not have to change its structure to become legible to agents, it has to publish what agents already look for.
Which gap costs a marketing site the most?
Client-side rendering that returns an empty shell to non-browser agents. Nothing else on the page can be read if the first response carries no content, and prices and facts are then left for the agent to infer.