How AgentScore works: what's behind the 100 points
AgentScore gives your website one number out of 100 for how well AI agents can get in, read your pages and find their way around. A single number is only useful if you trust it, so here is exactly how it's worked out: the four categories, how each check earns points, which pages the scanner visits, and what it doesn't score yet.
Four categories, 100 points
Every check belongs to one of four categories. Each category has a fixed number of points, set by how much it matters to an AI agent trying to do something for a customer.
| Category | Points | The question it answers |
|---|---|---|
| Access | 25 | Can AI agents get in, past robots.txt, bot protection and challenges? |
| Readability | 25 | Can they understand your pages without guessing? |
| Navigability | 20 | Can they find and use the buttons, links and forms they need? |
| Task completion | 30 | Can an AI agent actually finish a real task, such as reaching checkout? |
The background to these categories is in our guide to agent readiness. This post is about the mechanics.
How a check earns points
Each check ends in one of four results:
- Pass earns the check's full weight.
- Warning earns half. Something works, but agents will stumble on it.
- Fail earns nothing.
- Not tested is left out of the sum entirely. It never counts against you.
Within a category, checks carry different weights, because some problems stop an agent cold and others only slow it down. A category's score is its points multiplied by the share of weight you earned among the checks that could be tested. If Readability's tested checks are worth 17 in total and you earn 13.5 of them, you get 25 × 13.5 ÷ 17, or 19.9 out of 25.
The overall score adds up the categories that could be tested and scales the result to 100. So if Task completion wasn't tested and you scored 20 for Access, 17 for Readability and 11 for Navigability, your AgentScore is 48 out of a possible 70, which is 69.
Most checks are rule-based rather than judged by an AI model, so the same site gets the same score from one scan to the next. When it moves, something on the site changed.
What the bands mean
| Score | Band | What we tell you |
|---|---|---|
| 80 and up | Good | AI agents can use this site well. |
| 60 to 79 | Fair | AI agents can mostly use this site, but some things get in their way. |
| 40 to 59 | Weak | AI agents will struggle on this site. |
| Below 40 | Poor | Most AI agents will fail on this site. |
The one-line verdict at the top of a report also names your biggest issue: the failed check with the highest weight.
The checks, by category
Here is what each category looks at today. The weight is how much the check counts inside its category.
Access
- Bot protection lets AI agents through (weight 4). We request your home page as five AI agents and as a normal browser, and compare. If any agent is blocked or challenged while the browser gets through, it fails. If an agent gets less than half the browser's text, it's a warning.
- robots.txt lets AI assistants and search agents in (3). Blocking one or two assistants or AI search agents is a warning; three or more is a fail. Blocked training crawlers are reported but not scored.
- AI agents can open your product, pricing and cart pages (3).
- AI agents aren't blocked or shown a CAPTCHA at the cart and checkout (3).
- No CAPTCHA or challenge on arrival (2).
- Shoppers can check out without an account (2).
- llms.txt guide for AI (1), Agents can use your site through MCP or WebMCP (1) and Agents can check out through an agentic commerce protocol (1). These are newer standards, so a missing one is a warning, never a fail.
Readability
- Content loads without JavaScript (4): how much of the page's text is in the HTML before scripts run.
- Structured data describes your business and products (3) and Product pages give price and stock in a form agents can read (3).
- Clear page title, description, and headings (2), Valid sitemap (2) and Prices are in the page HTML (2).
- Images have text descriptions (1).
Navigability
- Buttons and links have names (4) and Pop-ups and banners can be dismissed by agents (4).
- Agents can find and press your add-to-cart or sign-up button (3) and Cart and checkout fields are labelled for agents (3).
- Form fields are labelled (2), Page has main and navigation landmarks (2), Clickable things are real buttons and links (2) and Key pages are linked from the home page (2).
Weights can change between scoring versions as we learn what trips agents up. Every report records the scoring version it used, so you can compare like with like.
What the scanner visits
AgentScore reads public pages only. It never adds anything to a cart, submits a form, signs up or places an order. In one scan it looks at:
- Your home page, three ways: as a browser sees it before JavaScript runs, rendered in a real browser, and as five AI agents (ChatGPT-User, Claude-User, Perplexity-User, OAI-SearchBot and Googlebot).
- Your robots.txt, sitemap and llms.txt, plus the well-known addresses where sites describe an MCP server or an agentic commerce profile.
- Up to three key pages: a product page, a pricing page and the cart. It looks for them the way an agent would, in the links on your home page first, then in your sitemap, then at common addresses such as
/pricingand/cart. Each is fetched as a browser and as an AI assistant, and product and pricing pages are rendered in a browser too. - Your checkout, found from the link on the cart page or at
/checkout, fetched as a browser and as three AI assistants.
Requests under the scanner's own name are signed so you can verify them. The requests that imitate AI agents are not, on purpose. We explain why in Why our scanner sometimes wears other agents' names. How it identifies itself and how to opt out are on the AgentScore bot page.
What isn't scored yet
Task completion. The automated scan doesn't run an AI agent through a task yet, so "An AI agent completes a real task" shows as not tested and your score covers Access, Readability and Navigability. In the Ghost Agent Labs app, Ghost Agent tests already send real AI agents through your journeys. Their results don't feed into AgentScore yet.
Store-only checks on other sites. Guest checkout, checkout fields, product data and agentic commerce only apply to stores. If we find no products or cart, they're marked not tested.
Anything behind a full cart. Many checkouts only open with items in the cart. Because the scanner never adds any, those checks often say "not tested" rather than guess.
Your choice on training crawlers. Blocking AI training is a business decision, not a readiness problem, so it costs no points.
How to use your score
- Read the verdict and the biggest issue first. It's the highest-weight failure.
- Fix failures before warnings, and Access before everything else: if agents can't get in, nothing else matters.
- Hand each finding to the right person. Most Access problems belong to whoever runs your CDN or bot protection; most Navigability problems belong to developers.
- Rescan after each fix. In the Ghost Agent Labs app you can rescan whenever you like. The free AgentScore page reuses a domain's result for 24 hours, so repeated requests don't hit your site again.
Then go beyond the score: set up tests of your key journeys with AI agents, so you know when a release breaks them.