When an agent needs the short audit response
Choose the compact audit response for scores, counts, and a short attention list; use the full response when the next step needs findings and fixes.
Blog
Deep dives into AI agent readability, machine-readable signals, and how to make your site discoverable by retrieval-augmented systems.
Choose the compact audit response for scores, counts, and a short attention list; use the full response when the next step needs findings and fixes.
Archive
Choose a MachineRead preset or refine supported check families with Custom scope while keeping the Essentials scoring frame consistent.
Understand why strict agent readiness has its own probe count and why changing audit scope can change the percentage without changing the site.
Read benchmark bars with their preset, denominator, and snapshot date so a peer comparison answers the question you intended to ask.
Keep product and offer metadata consistent with the visible sale, and distinguish catalog discovery from a tested checkout or payment flow.
Compare RSS, Atom, and JSON Feed entries with the pages they announce to find missing updates, stale links, and misleading dates.
Use auth.md to explain agent registration, human approval steps, and the route to authoritative metadata. Keep credentials and access decisions elsewhere.
Compare OAuth, OIDC, and protected-resource metadata with the intended issuer and endpoints before testing an authorization flow.
Separate WebMCP discovery documents from browser tool registration, and use an authorized browser test to check the advertised interaction.
Clear descriptions and accessible package files help supporting clients find an Agent Skill. Check the instructions and helper code before using them.
An A2A Agent Card describes a service's identity, capabilities, and interfaces. Check the advertised service as well as the document.
Connect an MCP client to MachineRead's read-only audit tools, request a website audit, and inspect the results without confusing discovery with tool execution.
Read Wikipedia and Wikidata matches with name collisions, cached results, and limited search coverage in mind. A match still needs inspection.
A small-looking page can still return slow, heavy HTML. MachineRead checks structural performance clues, while browser measurements answer what visitors experience.
Track down stale names and URLs across page titles, share cards, and JSON-LD without mistaking consistent metadata for verified identity.
Find accidental noindex rules and restrictive snippet settings in page HTML and response headers, and distinguish them from deliberate publishing choices.
Inspect the landmarks, links, labels, and form controls a client receives before JavaScript runs, then test the interactions separately.
Search discovery checks public signals related to reachability, initial HTML content, and declared modification dates.
A plain HTTP fetch can reveal whether public HTML is available before a client executes JavaScript. It cannot predict every crawler's behavior.
A sitemap publishes URLs and optional modification dates for crawlers. It can support discovery, but it does not guarantee crawling or indexing.
robots.txt expresses crawl directives for named user agents. AI-related rules should reflect a deliberate, reviewed policy.
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.
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.
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.
RFC 9727 defines a well-known URI for an API catalog expressed as a linkset. It gives supporting clients a predictable discovery path.
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.
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.
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.
MachineRead audits a public website for observable AI agent and search-readiness signals across 14 check groups and 60 checked points.