--- language: en title: "Agent readability" description: "Agent readability describes the clarity of content and interfaces in the representations an agent uses to recognize information, relationships, and actions." canonical: "https://tropk.ai/en/resources/glossary/agent-readability" last_modified: "2026-10-12T16:10:40.807Z" --- # Agent readability Reviewed on 2026-10-07. ## What it means Agent readability, or agentic readability, describes how well an agent can interpret a page’s information, relationships, and actions in the representation it uses. This representation may include [HTML](/en/resources/glossary/html-the-web-s-markup-language), an accessibility tree, and a screenshot. An assessment should specify which agent and task it considers; readability is an operational criterion, not a standardized measure across platforms. ## Why it matters for marketing For marketing and content, the key is to keep the relationship between an offer and its terms clear, including when an agent reads the structure rather than the visual appearance. A button without a name or an option without a label can make it harder to understand the user journey. The team needs to assess the meaning the agent retrieves, as well as check whether the page looks organized. ## Example in practice Imagine an internet provider displaying three internet plans in cards. Visually, each button belongs to a plan; in the accessibility tree, they all appear simply as Choose, without enough context. The agent associates the button with the wrong plan. The team adjusts the names and groupings so the choice identifies precisely the plan the user requested. ## How to apply or check Inspect the HTML and accessibility tree of the elements involved in the task, comparing names, roles, and states with the screen. Check field labels, groupings, and result messages. Then see whether the agent identifies the correct offer under the same conditions. Record which representation it received to distinguish difficulty interpreting the content from lack of access to it. ## Important distinctions Plain text helps, but readability also involves structure and interaction. A readable document can describe an unavailable offer; an understandable interface may require authentication to proceed. Google’s documentation covers these representations and recommends semantic HTML and stability. These guidelines do not prove that models prefer a single format, nor do they guarantee a commercial recommendation or task completion. ## Sources and references - [Build agent-friendly websites]() — Google / web.dev ## Continue a leitura - [Machine-readable content]() - [Agent readiness]() - [JavaScript rendering]() ## About the author [Vinicius Pacheco]() Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content. --- [All pages in Markdown]()