Яндекс.Метрика

Yandex 360 (Messenger): is the website ready for AI agents

360.yandex.ru·checked November 11, 2026
55.9out of 100
Has issues

Agents read the site but miss some important things.

Paste the task into Claude Code, Cursor or another agent with access to the site’s code.

  • Agent access: 89
  • Discoverability: 59
  • Content for models: 14
  • AI bot rules: 50
  • API and protocols: 48

Fix these first

First, what gets in agents’ way the most.

  1. 01

    The site serves Markdown when an agent asks

    Failed

    When the homepage is requested with “Accept: text/markdown”, return Markdown with “Content-Type: text/markdown” and “Vary: Accept”. Keep serving HTML for ordinary requests.

    An agent can ask for a page in Markdown instead of HTML and spend far less of its budget on markup.

    Markdown for agents →
    ›What the site returned
    URL
    https://360.yandex.ru/
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://360.yandex.ru/"
  2. 02

    Pages have Markdown versions

    Failed

    Serve a Markdown version of pages at the URL ending in .md and reference it with <link rel="alternate" type="text/markdown"> on the page itself.

    The same page at a URL ending in .md: clean text with no menus or scripts.

    Markdown for agents →
    ›What the site returned
    URL
    https://360.yandex.ru/index.md
    Response code
    404

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://360.yandex.ru/index.md"
  3. 03

    An API description (OpenAPI) is published

    Failed

    Publish an OpenAPI file (openapi.json or openapi.yaml) at a public URL and link to it from the docs.

    A file listing every API method in a machine format. An agent builds requests from it.

    API and MCP →
    ›What the site returned
    URL
    https://yandex.ru/openapi.json
    Response code
    404

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://yandex.ru/openapi.json"
  4. 04

    An MCP server exists

    Failed

    Publish an MCP server and state its address in the docs, or put a server card at /.well-known/mcp/server-card.json.

    MCP is a way to plug a product into Claude, ChatGPT and other assistants as a set of ready-made tools.

    API and MCP →
    ›What the site returned
    URL
    https://360.yandex.ru/.well-known/mcp/server-card.json/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/.well-known/mcp/server-card.json/"
  5. 05

    ChatGPT and Claude get the same page people do

    Failed

    Allow the ChatGPT-User and Claude-User user agents in your bot protection and server settings: they must get the same page a browser does.

    We open the homepage the way the ChatGPT and Claude agents do. If site protection answers them with a refusal or a CAPTCHA, a person never notices, and the agent leaves with nothing.

    Access without CAPTCHA or JS →
    ›What the site returned
    URL
    https://360.yandex.ru/
    Response code
    200
    Headers
    vary: Accept-Encoding
    content-type: text/html; charset=utf-8
    Found
    found: ChatGPT-User, Claude-User

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
Other issues17
  1. 06

    Company or product markup is present

    Failed

    Add JSON-LD markup of type Organization or SoftwareApplication with name and url to the homepage.

    JSON-LD is company data in a machine format: name, site URL, product type.

    sitemap and JSON-LD →
    ›What the site returned
    URL
    https://360.yandex.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
  2. 07

    llms.txt exists

    Failed

    Put an llms.txt in Markdown at the site root: a top-level heading with the product name, a short description and a list of links to key pages. The links must resolve.

    A short file for language models: what the product is and where the key pages are.

    llms.txt →
    ›What the site returned
    URL
    https://360.yandex.ru/llms.txt/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://360.yandex.ru/llms.txt/"
  3. 08

    robots.txt has rules for AI bots

    Failed

    Add separate User-agent groups for AI bots to robots.txt: GPTBot, ClaudeBot, OAI-SearchBot, PerplexityBot, YandexAdditional. Naming two is enough.

    AI bots are listed by name. Whether you allow or block them, it shows the choice was made.

    robots.txt for AI →
    ›What the site returned
    URL
    https://360.yandex.ru/robots.txt
    Response code
    200

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/robots.txt"
  4. 09

    Alice AI robots are allowed

    Partial

    Add a group to robots.txt with “User-agent: YandexAdditional” and “User-agent: YandexAdditionalBot” and an “Allow: /” rule.

    The YandexAdditional robots bring a site into Alice AI answers. Best to allow them with a rule of their own.

    robots.txt for AI →
    ›What the site returned
    URL
    https://360.yandex.ru/robots.txt
    Response code
    200

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/robots.txt"
  5. 10

    llms-full.txt exists

    Failed

    Put an llms-full.txt at the site root with the full text of the site or docs in Markdown.

    The full text of the site or docs in one file. An agent reads it in a single request.

    llms.txt →
    ›What the site returned
    URL
    https://360.yandex.ru/llms-full.txt/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://360.yandex.ru/llms-full.txt/"
  6. 11

    Content use is declared

    Failed

    Add a “Content-Signal: search=yes, ai-input=yes, ai-train=yes” line to robots.txt. Choose yes or no for each value yourself.

    The Content-Signal line says whether your text may be used for search, AI answers and model training.

    robots.txt for AI →
    ›What the site returned
    URL
    https://360.yandex.ru/robots.txt
    Response code
    200

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/robots.txt"
  7. 12

    Company markup has a description and contacts

    Failed

    Add description, logo and contactPoint (address, email or telephone also work) to your Organization JSON-LD.

    The description, logo and contacts in the markup let an assistant confirm this is a real company before recommending it.

    sitemap and JSON-LD →
    ›What the site returned
    URL
    https://360.yandex.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
  8. 13

    Pricing is available in Markdown

    Failed

    Serve the pricing page in Markdown: at the page URL ending in .md or at /pricing.md. The file must contain prices.

    An agent comparing products reads pricing most easily from a plain text file.

    Markdown for agents →
    ›What the site returned
    URL
    https://360.yandex.ru/premium-plans.md/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/premium-plans.md/"
  9. 14

    The homepage links to API docs

    Partial

    Link to your API docs from the homepage, for example in the footer or a developers menu.

    When asked to set up an integration, an agent looks for docs starting from the homepage.

    sitemap and JSON-LD →
    ›What the site returned
    URL
    https://360.yandex.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
  10. 15

    The site points agents to its machine-readable files

    Partial

    Add a Link header or a <link> tag on the homepage pointing to llms.txt, the page’s Markdown version (rel="alternate" type="text/markdown") or the API description (rel="service-desc").

    Links in the response header or page code lead to llms.txt, a Markdown version or an API description.

    Markdown for agents →
    ›What the site returned
    URL
    https://360.yandex.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
  11. 16

    An agent can find how to sign in

    Partial

    Publish /.well-known/oauth-authorization-server (or /.well-known/openid-configuration) as JSON with an issuer field and the authorization endpoints.

    A service file with OAuth endpoints. Without it an agent needs a person to explain where to get a token.

    API and MCP →
    ›What the site returned
    URL
    https://360.yandex.ru/.well-known/oauth-authorization-server/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/.well-known/oauth-authorization-server/"
  12. 17

    An API catalog exists

    Failed

    Publish /.well-known/api-catalog as application/linkset+json with links to your API descriptions (RFC 9727).

    One file at a standard URL linking to all of the company’s APIs and their descriptions.

    API and MCP →
    ›What the site returned
    URL
    https://360.yandex.ru/.well-known/api-catalog/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/.well-known/api-catalog/"
  13. 18

    Agent skills are published

    Failed

    Publish /.well-known/agent-skills/index.json with a list of skills in the skills field.

    Ready-made instructions for how an agent does common tasks in the product.

    API and MCP →
    ›What the site returned
    URL
    https://360.yandex.ru/.well-known/agent-skills/index.json/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/.well-known/agent-skills/index.json/"
  14. 19

    The API says which server grants access

    Failed

    Publish /.well-known/oauth-protected-resource as JSON with a resource field on the API domain (RFC 9728).

    A service file: which authorization server issues tokens for this API.

    API and MCP →
    ›What the site returned
    URL
    https://360.yandex.ru/.well-known/oauth-protected-resource/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/.well-known/oauth-protected-resource/"
  15. 20

    Markup links to official profiles

    Failed

    Add a sameAs field to your JSON-LD with links to official profiles: GitHub, social networks, app stores.

    sameAs links to GitHub, social networks and app stores. They tell an assistant that mentions elsewhere are about you.

    sitemap and JSON-LD →
    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    sameAs links: 0

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
  16. 21

    About, contact and policy pages are linked from the homepage

    Partial

    Link to the About, Contact and privacy policy pages from the homepage, for example in the footer.

    An agent checks these pages to make sure the site can be trusted.

    sitemap and JSON-LD →
    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    found: contacts, privacy

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
  17. 22

    An agent-to-agent card exists

    Failed

    Publish /.well-known/agent-card.json in the A2A format: JSON with a name field, a description and the agent’s URL.

    A file in the A2A standard: who you are, what you can do and how another agent reaches you.

    API and MCP →
    ›What the site returned
    URL
    https://360.yandex.ru/.well-known/agent-card.json/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/.well-known/agent-card.json/"
What already works16

  • Homepage opens without a CAPTCHA

    ›What the site returned
    URL
    https://360.yandex.ru/
    Response code
    200
    Headers
    vary: Accept-Encoding
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • Text is visible without JavaScript

    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    words of text: 1,289

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • Prices are visible without JavaScript

    ›What the site returned
    URL
    https://360.yandex.ru/premium-plans/?from=360_landing
    Response code
    200
    Headers
    vary: Accept-Encoding
    content-type: text/html; charset=utf-8
    Found
    snippet: , Телемост и другие сервисы с минимальным местом и рекламой 0 ₽/мес Место на Диске 5 ГБ Уже ваш Только

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/premium-plans/?from=360_landing"

  • A missing page returns 404

    ›What the site returned
    URL
    https://360.yandex.ru/agent-readiness-check-7fc7d2fa11/
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/agent-readiness-check-7fc7d2fa11/"

  • A short path from http to https

    ›What the site returned
    URL
    https://360.yandex.ru/
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding
    Found
    redirects: 1

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • The homepage is light and fast

    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    page size, KB: 660
    response time, s: 1.018

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • robots.txt exists

    ›What the site returned
    URL
    https://360.yandex.ru/robots.txt
    Response code
    200

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/robots.txt"

  • A sitemap exists

    ›What the site returned
    URL
    https://360.yandex.ru/sitemap.xml/
    Response code
    200
    Headers
    content-type: application/xml; charset=utf-8
    vary: Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/sitemap.xml/"

  • Homepage metadata is filled in

    ›What the site returned
    URL
    https://360.yandex.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • A clear heading structure

    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    H1 headings: 1
    H2 headings: 8
    has <main>: yes

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • Agents and AI search are allowed

    ›What the site returned
    URL
    https://360.yandex.ru/robots.txt
    Response code
    200

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/robots.txt"

  • Open API docs or an MCP server exist

    ›What the site returned
    URL
    https://yandex.ru/dev/api360
    Response code
    200
    Headers
    vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers
    content-type: text/html;charset=utf-8
    Found
    API markers: 6

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://yandex.ru/dev/api360"

  • The homepage is not hidden from search

    ›What the site returned
    URL
    https://360.yandex.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • Homepage text fits an agent’s memory

    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    tokens, approx.: 3,467

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • Content starts near the top of the page

    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    text before the heading, %: 0

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"

  • Page preview data is filled in

    ›What the site returned
    URL
    https://360.yandex.ru/
    Found
    found: og:title, og:description, og:image, og:type

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://360.yandex.ru/"
Not scored8

These checks do not apply to the site and do not lower the score.

  • The API reports errors in a machine format
  • llms.txt is structured well enough to navigate
  • The Markdown version has a header with page data
  • The MCP server answers a connection
  • MCP tools have descriptions
  • An access refusal says where to sign in
  • There is a guide for how an agent gets access
  • A catalog of AI interfaces exists

Check your own site

Paste the address and get the same breakdown in half a minute.

Check a site →

Other checked sites