Agent experience

Learn how the extension checks whether AI agents can understand a page's structure, find useful content and operate its controls.

These checks read the rendered page in your browser, the way an agent driving it would. They look at how much of the page is text, whether it fits an agent’s context window, whether its metadata and outline make sense, whether the business behind it looks real, and whether its controls and form fields can be found and operated.

Most of these checks need the page open in the active tab. When the extension cannot read the page, they report Unmeasured rather than guessing.

Agent experience carries a weight of 1 in the overall score. A page built to accessibility standards passes most of it, which is agent readiness, but not evidence of work done specifically for agents.

Checks in this category

  • Content efficiency
    Agents prioritise readable text, so a page that is mostly markup costs them more to read.
  • Page token budget
    A page that does not fit an agent's context window gets truncated, so some of its content may be missed.
  • Metadata completeness
    The title, description and canonical URL are how an agent sums up a page and spots duplicates before reading it.
  • Trust anchor pages
    Agents check about, contact and privacy pages to decide whether a business is real.
  • Document structure
    Landmarks and an unbroken heading order are how an agent builds a map of the page before acting on it.
  • Native interactive controls
    A div with a click handler is invisible to an agent driving the page by keyboard or accessibility tree.
  • Accessible names on controls
    An agent picks controls by their names, so it will struggle to use buttons that have none.
  • Form control labelling
    Agents use field labels to fill in forms. Without them, they have to guess.
  • Accessibility-tree injection safety
    Instruction-shaped text in aria-labels and alt text is read by an agent as part of the page, and can be used to steer it.
  • Emerging checkPagination signals
    rel="next" and rel="prev" links let an agent work through a paginated archive instead of stopping at page one.