Agent Analyzer
Point it at a page. It fetches the page the way an agent does, without running JavaScript, and checks the 35 items from the 56-point audit that a machine can verify. Each failure comes with the fix and a prompt you can hand to your own coding agent.
Scan a pageFree account. One page a week, and re-scans of the same page within 14 days are free. More pages from $10 for 20.
What the score is, and is not
The score measures agent readiness: whether an agent can reach the page, read it without a browser, tell what it is and who wrote it, and find it through robots.txt and the sitemap. It is not a prediction of whether AI answers will cite you. Nobody can honestly sell that number, and What Gets Cited explains why several popular tactics, llms.txt among them, have no evidence behind them. Every check in a report carries the same evidence rating so you can decide what is worth your time.
Clarity and Completeness, 30 of the 100 points, need a person to judge. The report hands off to the self-assessment with the verified items already ticked.
What it checks
36 scored checks, plus 7 for information only. The Agentic browsing checks are the audits in Google Lighthouse’s Agentic Browsing category, scored the way Lighthouse scores them: llms.txt, WebMCP tools, and ai-catalog.json count only if the site has them. Lighthouse runs a real browser and this scanner does not, so the accessibility and layout checks look for the same problems in the HTML rather than measuring them.
Agent accessibility
- Page is reachable by an automated fetcher
Retrievability comes before every other factor. A page an answer engine cannot fetch cannot be read, summarised or cited. Guidance
- Page is not marked noindex
A noindex directive in a meta tag or an X-Robots-Tag header removes the page from search indexes, and the AI search products built on them follow it. Guidance
- Content is in the HTML without JavaScript
Most AI crawlers do not execute JavaScript. Content that only appears after scripts run is invisible to them, however complete the page looks in a browser. Guidance
- Content is not behind a login or paywall
An agent without credentials reads whatever an anonymous visitor gets. Gated content cannot be retrieved, so it cannot be cited. Guidance
- Content images have alt text
A text-only reader gets nothing from an image without alt text. Information carried only by an image is lost when the page is converted to text. Guidance
- robots.txt is served
robots.txt is where crawlers look first for what they may fetch and where the sitemap is. A server error on it can make crawlers treat the whole site as off-limits. Guidance
- Search and AI search crawlers may fetch this page
AI answer products with citations fetch through their own search crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot). Blocking them, or blocking Googlebot and Bingbot, removes the page from those answers. Guidance
- Search and training crawlers decided separately
Being cited and being trained on are separate choices with separate crawlers. A site that has not named either leaves the decision to defaults, and an over-broad AI block can remove it from search too. Guidance
- XML sitemap is discoverable
A sitemap lists every page you want found, with dates. Crawlers use it to discover pages and to decide what to recrawl. Guidance
- Sitemap lists this page
A page missing from the sitemap depends on links alone to be discovered and recrawled. Guidance
- Sitemap lastmod dates look real
lastmod tells crawlers what changed. When every URL carries the same date, the dates are being stamped at build time and crawlers learn to ignore them. Guidance
Technical
- Server responds quickly
Crawlers and user-directed fetchers work to time budgets. A slow first byte risks a timeout before any content arrives. Guidance
- Title and meta description
The title and description are the summary a system reads before deciding whether the page answers the question. Guidance
- Self-referencing canonical URL
The canonical tells crawlers which URL is the page. A missing or wrong canonical splits signals across duplicates, or points them at a different page entirely. Guidance
- Open Graph tags with an image that resolves
Open Graph tags are the card a link becomes when it is shared or previewed, including in chat interfaces. A broken image URL produces a broken card. Guidance
- Mobile viewport declared
Pages without a device-width viewport render as shrunken desktop pages on phones, and mobile rendering is how search engines evaluate a page. Guidance
- JSON-LD in the server HTML
Structured data states facts about the page (what it is, who wrote it, when) in a form a machine does not have to infer. Its effect on AI citation specifically is contested, so treat it as clarity for machines rather than a ranking lever. Guidance
- Structured data says what the page is
Organization and WebSite markup describe the site. A page-level type such as Article, WebPage or Product describes this page, and is what carries its headline, dates, and author. Guidance
- Structured data parses and matches the page
Markup that fails to parse is ignored. Markup that disagrees with the visible page (a different headline, an author as a bare string) gives a machine two versions of the facts. Guidance
- BreadcrumbList is well formed
Breadcrumbs place the page in the site hierarchy. Positions must run 1, 2, 3 with no gaps or the list is invalid. Guidance
- FAQPage markup matches visible questions
FAQPage markup must describe questions a reader can see. Questions that exist only in the markup are the kind of mismatch the schema lesson warns against. Guidance
- HTTPS, with HTTP redirecting to it
HTTPS is a baseline trust and ranking signal. An HTTP version that serves content instead of redirecting creates a duplicate of every page. Guidance
Structure
- One H1 per page
The H1 is the document title once markup is stripped. One clear H1 tells a parser what the page is about; none or several leaves it guessing. Guidance
- Headings nest without skipping levels
Heading levels are the outline a text converter keeps. Skipped levels break the outline, so sections lose their relationship to each other. Guidance
- Semantic landmarks mark the content
main and article tell an extractor where the content starts and the navigation ends. Without them it has to guess what to keep. Guidance
Trust
- A named human author
A named person is something a reader, or a model, can check. "Admin" or "Team" gives nothing to verify. Guidance
- Author links to a page and profiles
An author page and sameAs links connect the name to a real, identifiable person, which is what lets the name carry any weight. Guidance
- Honest, machine-readable dates
Freshness is one of the better-supported citation factors, and a machine can only judge it from dates it can parse. Visible dates and structured-data dates should agree. Guidance
- Cites outside sources
Links to the sources behind a claim let a reader, or a system, check it. Whether the sources are primary still needs a human to judge. Guidance
- Organization and contact information
Knowing who publishes a page, and how to reach them, is part of judging whether to trust it. Guidance
Agentic browsing
- llms.txt
llms.txt is a proposed index of a site for language models. There is no evidence that major AI systems use it for citation, so its absence costs nothing. If you publish one, it is scored the way Google Lighthouse scores it: an H1 title, at least one link, and more than a few words. Guidance
- Forms annotated as WebMCP tools
Declarative WebMCP turns an ordinary form into a tool an agent can call, by adding toolname and tooldescription attributes. As in Lighthouse’s "WebMCP form coverage", a page earns the point when every form is annotated, and an unannotated form is reported without costing anything: WebMCP is in a Chrome origin trial. Guidance
- WebMCP form tools are complete
A form annotated for WebMCP becomes a tool schema: the form gives the tool its name and description, and each field becomes a parameter. Lighthouse’s "WebMCP schemas are valid" audit fails a tool with no name or description, or a required field with no name, and warns about fields with no name or description. Guidance
- Controls have names an agent can read
Browser agents read the accessibility tree, not the pixels: a button is whatever its accessible name says it is. Lighthouse’s "Accessibility tree is well-formed" audit runs a set of naming and ARIA rules for this reason. This check runs the subset of those rules that can be judged from the HTML without a browser. Guidance
- Images and embeds reserve their space
Agents that operate a page often click by position. If content moves after an image loads, the click lands on whatever moved into place. Lighthouse includes Cumulative Layout Shift in its Agentic Browsing category for this reason. Measuring layout shift needs a browser; this check looks for its commonest cause, media with no reserved size. Guidance
- AI catalog (ai-catalog.json) is valid
Agentic Resource Discovery (ARD) defines ai-catalog.json, a manifest listing the agents, MCP servers, and skills a site offers. Lighthouse validates it against the spec when a site publishes one. As there, having none costs nothing; publishing an invalid one does. Guidance
For information, never scored
Buy pages
Every account gets one page a week free. Pages beyond that are bought outright, not by subscription. They do not expire, and there is nothing to cancel.
20 pages
$10$0.50 a page
A site section, or one site checked a few times over a year.
100 pages
$30$0.30 a page
A whole small site, with room to re-check after the fixes ship.
500 pages
$100$0.20 a page
Several client sites, or a large one section by section.
Agency · 1,000 pages a month
$49/moFor people scanning client sites every month: 1,000 pages, site crawls and reports you can put your own name on. Each month’s pages are used before any pack you have bought, and expire at the end of the month rather than piling up. Cancel from your account at any time.
- A page only costs a credit if the Agent Analyzer could read it. Blocked, missing and broken pages are free.
- Re-scanning a page you scanned in the last 14 days is free, up to five times, so fixing and checking costs nothing.
- Your free weekly page is always used before a credit.
- Site crawls and reports you can put your own name on come with page credits.
When you are not charged
A scan only counts if the Agent Analyzer could read the page: an HTML response in the 200 range that is not a bot challenge. Blocked requests, error pages, timeouts, and non-HTML files cost nothing, and the report tells you what stopped it.
Your own coding agent can drive all of this over MCP: scan, fix, scan again. Connect the Agent Analyzer to your agent.
To see how well-known sites do on the same scan, read the State of Agent Readiness: 100 home pages, scored.
The Agent Analyzer identifies itself honestly and can be blocked like any crawler. How the Agent Analyzer fetches pages.