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 yandex.ru. The score weights five categories of machine-readability; the ticks on the arc are the 37 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.
No reachable sitemap.xml. Publish one and reference it in robots.txt.
Show me exactly what to doA sitemap is a machine-readable list (sitemap.xml) of every page on your site. It is how crawlers find pages that aren’t linked from your homepage.
Agents discovering your site crawl outward from the pages they know. Without a sitemap, anything not linked from a top-level page (docs, older articles, product variants) may simply never be read, so it can’t be quoted or recommended.
Get it in your inbox now, plus a heads-up whenever yandex.ru’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 →
Generated, ready-to-ship files for the gaps above. Copy them, or download and drop them into your repo.
Weakest on this scan: readability, 20/100 — much of what this page shows people never survives into the text an agent actually reads.
This graded your homepage. Your pricing, docs, and checkout live on other pages: the ones assistants actually quote when they recommend you. A 36/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.
Embed this badge on your site. It links back to this live scan and updates on every rescan.
<a href="https://agentspeed.com/scan/yandex.ru"><img src="https://agentspeed.com/badge/yandex.ru" alt="AgentSpeed agent-readiness score" height="56"></a>Get this report by email, then a heads-up when yandex.ru’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 yandex.ru. AI traffic analytics says whether one actually came, and which pages turned it away.
Running AI agents of your own? AgentSpeed also monitors them in production: every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.
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.11.0. 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.
No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.
Show me exactly what to doA canonical tag is one line in your page’s HTML head that says "THIS is the official address of this page." Without it, yoursite.com/pricing, yoursite.com/pricing?utm_source=x, and www.yoursite.com/pricing all look like different pages with copied content.
When the same content lives at several addresses, agents split your page’s identity across the copies. They may cite a tracking-parameter URL, or treat the duplicates as a signal of low quality. The canonical tag merges them back into one.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
No non-empty <title>. Agents use it as the page label in citations and answers.
Show me exactly what to doThe <title> tag is the page’s name: the text in the browser tab. Yours is missing, empty, or generic (e.g. just "Home"), so machines have no usable name for this page.
The title is the single most-quoted identifier for a page; agents cite it verbatim when referencing you. A missing one gets replaced with a guess assembled from headings, which amounts to your page’s name being written by someone else.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.
Show me exactly what to doThe meta description is a one-sentence summary of the page that you control, embedded in the HTML head. Without it, machines compose their own summary from whatever text appears first, often cookie-notice or navigation boilerplate.
This is the sentence you get to write about yourself. Pages without one are summarised by autopilot, and the autopilot frequently leads with the least representative text on the page.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
Show me exactly what to doJSON-LD is a small block of structured facts (name, what you sell, prices) embedded invisibly in your page’s HTML, written in a vocabulary (schema.org) that machines share. Think of it as the machine-readable caption for the page humans see.
An agent reading prose has to guess which number is the price and which name is the brand. JSON-LD removes the guessing: typed facts it can quote directly. Pages without it get summarised from inference, which is where wrong prices and wrong names come from.
Page text too sparse to probe; agent has nothing to read.
Show me exactly what to doWe gave an AI model the visible text of your page and asked it two questions: what does this page offer, and what is the price or main action? It could not answer from what your page serves.
This is the same task a shopping assistant performs before recommending you. If a model reading your page can’t name your offer and how to act on it, an assistant answering a customer can’t either, and it routes the recommendation somewhere it can.
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.
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.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.