Latest entry
Signals that help crawlers find updated public content
Search discovery checks public signals related to reachability, initial HTML content, and declared modification dates.
search-discoveryaudit-pillardeep-dive
Blog
MachineRead Blog
Deep dives into AI agent readability, machine-readable signals, and how to make your site discoverable by retrieval-augmented systems.
Archive
Earlier entries
What a non-browser request can actually read
A plain HTTP fetch can reveal whether public HTML is available before a client executes JavaScript. It cannot predict every crawler's behavior.
bot-accessaudit-pillardeep-dive
A sitemap is a map, not an indexing guarantee
A sitemap publishes URLs and optional modification dates for crawlers. It can support discovery, but it does not guarantee crawling or indexing.
sitemapseodeep-dive
robots.txt is a public crawler policy
robots.txt expresses crawl directives for named user agents. AI-related rules should reflect a deliberate, reviewed policy.
robots-txtseodeep-dive
Publishing page facts with Schema.org JSON-LD
JSON-LD can publish page facts in structured fields. It reduces ambiguity for supporting clients but does not determine how they will use the data.
schema-orgjson-lddeep-dive
Choosing one public URL for a page
A canonical tag expresses a preferred URL for duplicate or closely related pages. It can help search systems consolidate signals but does not dictate their behavior.
canonicalseodeep-dive
How an OpenAPI document makes an API easier to inspect
An OpenAPI document describes an HTTP API in a machine-readable form. It can help a supporting client construct requests, but it does not authorize or validate their use.
openapiagent-surfacesdeep-dive
A standard route to an API's public description
RFC 9727 defines a well-known URI for an API catalog expressed as a linkset. It gives supporting clients a predictable discovery path.
api-catalogagent-surfacesdeep-dive
llms.txt is optional, not a visibility shortcut
llms.txt is a proposed discovery file for language-model tools. A MachineRead result describes the response and basic shape, not client support or use.
llms-txtagent-surfacesdeep-dive
What an AI catalog can tell a supporting client
An AI catalog can state what a service does and where its machine-readable surfaces live. The format is early, so the audit gives it limited weight.
ai-catalogagent-surfacesdeep-dive
Why Agents Need to Read Your Site
Agent retrieval depends on what a client can fetch and parse. A page that renders for people may expose less to a non-browser client.
ai-agentsdiscoveryretrieval
Launching MachineRead
MachineRead audits a public website for observable AI agent and search-readiness signals across 13 check groups and 56 checked points.
launchproductai-readiness