Scanning live. A first-ever scan of a domain runs against the site and takes about ten seconds.
0.0s elapsedAgentSpeed tests how easily automated agents can discover, understand, and act on linkvue.uk. The score weights five categories of machine-readability; the ticks on the arc are the 36 individual checks behind it.
Send this to whoever edits the site. The link shows the score and grade as a preview card, and it stays current: it re-reads the latest scan rather than freezing today’s number.
Checks tagged “emerging” are 2026 agent-protocol standards most of the web hasn’t adopted yet. Adopting early is an edge, not a defect.
Visible text is 8.1% of HTML weight (4609/57090 bytes). 60% of the document is inline script, 32% is markup.
Show me exactly what to doOf everything your server sends for this page, very little is actual readable text. The rest is code, styling, and markup wrapper. Agents fetched a lot of bytes and found few words.
Agents work with retrieval budgets. A page that is 2% text either gets skimmed (and mis-summarised) or skipped. More signal per byte means more of your actual message survives into the agent’s summary.
Get it in your inbox now, plus a heads-up whenever linkvue.uk’s agent-readiness score changes. Free, unsubscribe anytime.
Prefer we just watch it for you? Monitor rescans weekly and emails what changed, $29/mo. Start monitoring →
Weakest on this scan: actionability, 67/100 — the actions this page offers people are hard for an agent to find or complete.
This graded your homepage. Your pricing, docs, and checkout live on other pages: the ones assistants actually quote when they recommend you. A 73/100 here means agents are already missing things on the page you polish most. The $29 Deep Scan grades your homepage plus up to 10 more pages we discover, against all 37 checks, then emails a PDF with every failing check and its exact fix, ranked by what costs you the most visibility. One-time, delivered in minutes, no subscription.
Right now, only you know this score. Your buyers ask AI before they buy, and certification is how you show them, and anyone comparing you to a competitor, that assistants can actually read, quote, and use your site.
Sites under 70 can’t buy this at any price. That’s what makes displaying it mean something.
Embed this badge on your site. It links back to this live scan and updates on every rescan.
<a href="https://agentspeed.com/scan/linkvue.uk"><img src="https://agentspeed.com/badge/linkvue.uk" alt="AgentSpeed agent-readiness score" height="56"></a>Get this report by email, then a heads-up when linkvue.uk’s agent-readiness actually changes: a check regressing, or the composite dropping.
Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.
Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.
This score says whether an AI agent could read linkvue.uk. AI traffic analytics says whether one actually came, and which pages turned it away.
This domain's score moved 68 → 73 since 2026-08-18. Themes update, deploys land, robots files change — scores drift with no announcement. AgentSpeed can watch this domain and alert you when a check regresses.
Run reports like this for every client: white-label PDFs and weekly monitoring for up to 15 domains, $149/mo. AgentSpeed for Agencies →
This score is a measurement of machine-readability for automated agents under the published rubric 2026.10.4. AgentSpeed does not assess security, legitimacy, privacy, or financial trust.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
JSON-LD declares 1 price(s) (0), but the served HTML shows no price at all. An agent reading the page sees a price humans never see, or the visible price only renders via JavaScript. Either way the two channels disagree.
Show me exactly what to doYour page declares one price in its machine-readable data (JSON-LD) and shows a different price to human eyes. We extracted both from the same page load and they don’t agree.
An assistant quoting your declared price tells the customer a number that isn’t what they’ll see at checkout. That is the fastest way to lose a sale an agent sent you, and repeated mismatches teach assistants to stop quoting your structured data at all.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
Show me exactly what to doContent-Signal is a newer robots.txt directive (pushed by Cloudflare) that lets you state a granular AI policy: for example "don’t train on my content, but summarising it in answers is fine". Classic robots.txt only offers all-or-nothing per crawler; this adds the middle ground. We looked for a Content-Signal line in your robots.txt and response headers and found none.
Without a granular signal, crawlers infer your intent from blunt allow/block rules, and sites often block more than they mean to just to avoid training use. A declared signal lets you keep answer visibility (summaries, citations) while opting out of what you object to. This is an emerging standard: honoring is voluntary and adoption is early, which is why it is flagged as emerging and weighs little.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
One prompt covering the fixes above that have a step-by-step plan, in the same priority order, with the same guardrails.
#25 of 52 tracked SaaS domains
This scan shows whether an agent can read the site. One free probe asks a real assistant a real buying question and records who it cited.