top of page
Glossy 3D 48PEGASUS Logo.png

Design · R7

The Agent-Readable Website

How to test whether AI assistants can identify your business, services, and next steps

A website passes an agent-readability test when a web-enabled assistant can correctly identify the business, explain what it offers and where, and point a customer to a verified next step. A brand mention alone does not meet that standard. An answer can name the right business and still invent a price, confuse service areas, cite the wrong company, or send the customer to an obsolete intake form. This paper separates three questions: can the assistant read a page when given its address, can it find the right business without that address, and can it guide a customer to the right next step? The protocol uses a dated register of verified facts, five representative prompts, repeated clean-session runs, and independent checks of each material claim and destination. Report known-site tests separately from unbranded discovery. Log omissions, unsupported assertions, broken destinations, and appropriate abstentions. Treat a fabricated price or wrong payment destination as a critical failure even if the overall score improves. Start by making the official pages accurate, accessible, and internally consistent. Test the published site, not a preview. Then use controlled retesting to learn where changes worked. Structured data and optional machine-readable files can support specific uses, but none substitutes for reliable public content or guarantees assistant retrieval, citations, recommendations, or traffic.

Co-authored by Jonathan G. Browning, Founder & CEO of 48PEGASUS

Published November 19, 2026 · Version 1.0

Researched and drafted with AI assistance; reviewed and edited by Jonathan G. Browning.

Download the PDF →

Contents

  • Overview
  • Sources and notices

Chapters

Related service

View the related service →

Questions about this paper? Call 1-615-970-8316.

Download the PDF →

Browse: White Papers · Reports · Downloads

bottom of page