Agent-readiness report, Software and SaaS
Is Webscore agent-ready?
No class of agent can use Webscore today: they cannot read it, call it as a tool or extract its content.
webscore.dev, last scanned 2 days ago, on 08.10.2026
Agent classes working
0/3
Score history
▼ 33 scans since 01.10.2026
- 4
- Blocking agents
- 10
- Weak spots
- 12/26
- Checks passed
What costs Webscore the most
0 of 3 agent classes work
- ✕Answer engines & research agents
- ✕MCP tool-callers
- ✕Summarisers & knowledge agents
- ✕
Content is buried in boilerplate
A model summarising the page quotes navigation and cookie banners instead of the content.
Blocker - ✕
No heading hierarchy
Retrieval chunks the page badly, so the passage a model quotes lacks its context.
Blocker - ✕
Pages are empty without JavaScript
Agents that read HTML and do not run scripts see a blank page.
Blocker - ✕
No MCP endpoint to call
Tool-calling assistants have no function to call, so they can only scrape.
Blocker - ✕
No stated policy for automated access
Cautious platforms will not act on the site without an explicit permission signal.
Improvement
✓12 checks passed, 9 more to fix+−
Free dashboard
Track webscore.dev and watch it climb.
Weekly re-scans, the fix for every gap above, and the rank moves of your rivals.
- 14 optimization suggestions, ready today
- Weekly re-scan with alerts on every change
- Rank and rival moves in one view
Your dashboard
We email you a sign-in link and add webscore.dev to your dashboard.
- Re-scan weekly
- Fixes listed
- Rivals tracked
Check a rival
5 domains free, unlimited with a plan.
Machine interfaces
Webscore exposes 4 of 8 interfaces agents look for: AI crawler access, Bot user-agent handling, llms.txt, Organisation markup.
Locked
All 8 interfaces and 26 checks for webscore.dev
See which interface is missing, what each check looked for, and what to change to pass it. Free account, no card.
View detailed signalsE-commerce & product feeds
Measured separately, not part of the public score or rank
Add-on score
35/100
- 5
- Blocking agents
- 4
- Weak spots
- 3/12
- Checks passed
- ✕
Products have no structured data
Agents cannot tell what is for sale, so the catalogue is invisible to them.
- ✕
Not on Qomvia Market
Agents using Qomvia cannot get an agent price or a payable order from this shop.
- ✕
Products have no stable identifiers
Agents cannot match your product to the same product elsewhere, so it drops out of comparisons.
- ✕
No product feed for agents to ingest
Agent platforms cannot load the catalogue in one request, so coverage stays partial.
- !Autonomous shopping agents
- ✕Feed & API integrators
- !Price-comparison & monitoring bots
- !Agent payment protocols
- ✓Catalogue access100%
- ✕Product data legibility18%
- ✕Agent-commerce protocols20%
- !Checkout traversability60%
The seal
Not yet certified
webscore.dev is in progress: Partly readable. Not yet good enough to display a public mark. Reach 60/100 to earn Agent-Readable and display it on your site.
Preview of Agent-Readable, greyed out until webscore.dev scores 60/100. There is no embed code until it is earned.
- Agent-Ready Champion90+
- Agent-Ready75+
- Agent-Readable60+
- In Progress40+, dashboard only
Webscore and AI agents: common questions
Is Webscore readable by AI agents?+−
Webscore (webscore.dev) scores 57 out of 100 for agent readiness, grade D, measured 2 days ago, on 08.10.2026. 0 of 3 agent classes we test can use the site, and 4 checks currently block agents outright.
What stops agents from using webscore.dev?+−
The heaviest problems are: Content is buried in boilerplate; No heading hierarchy; Pages are empty without JavaScript; No MCP endpoint to call; No stated policy for automated access. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report.
How is the Webscore agent-readiness score calculated?+−
Qomvia fetches public pages of webscore.dev as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100. E-commerce & product feeds checks are scored separately (35/100) and do not affect the public score or rank.
How often is this score updated?+−
Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from 2 days ago, on 08.10.2026.
Compare and keep reading
Scores are computed from public HTTP responses only. We never submit forms, never attempt a purchase and never bypass a bot challenge. Disagree with a result? Request a correction or opt this domain out.