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

Loop: is the website ready for AI agents

loop.ru·checked November 11, 2026
68.5out 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: 100
  • Discoverability: 81
  • Content for models: 42
  • AI bot rules: 64
  • API and protocols: 41

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.

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, 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://loop.ru/"
  2. 02

    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
    Response code
    404

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://developers.loop.ru/openapi.json"
  3. 03

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/.well-known/mcp/server-card.json"
  4. 04

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, 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://loop.ru/llms.txt"
  5. 05

    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.

    ›What the site returned
    Response code
    200

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/robots.txt"
Other issues16
  1. 06

    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.

    ›What the site returned
    Response code
    200

    Repeat the check yourself

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

    The site points agents to its machine-readable files

    Failed

    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.

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  3. 08

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, 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://loop.ru/llms-full.txt"
  4. 09

    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.

    ›What the site returned
    Response code
    200

    Repeat the check yourself

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

    An agent can find how to sign in

    Failed

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/.well-known/oauth-authorization-server"
  6. 11

    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.

    ›What the site returned
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/pricing.md"
  7. 12

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

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

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

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

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

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

    Page preview data is filled in

    Partial

    Add og:title, og:description, og:image and og:type tags to the homepage <head>.

    Title, description, image and page type (Open Graph). An assistant uses them when it shows a link to you.

    ›What the site returned
    Found
    found: og:title, og:description

    Repeat the check yourself

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

    Company markup has a description and contacts

    Partial

    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.

    ›What the site returned
    Found
    found: contact

    Repeat the check yourself

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

    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.

    ›What the site returned
    Found
    found: contacts, privacy

    Repeat the check yourself

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

    The Markdown version has a header with page data

    Failed

    Start the page’s Markdown version with a block between “---” lines containing title, description and url fields.

    Title, description and URL at the top of the file. An agent learns what the document is without parsing the text.

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://developers.loop.ru/index.md"
  14. 19

    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
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/.well-known/agent-card.json"
  15. 20

    There is a guide for how an agent gets access

    Failed

    Put an auth.md file at the site root with step-by-step instructions for how an agent gets a key or token.

    An auth.md file walks an agent through getting a key or token without a person’s help.

    API and MCP →
    ›What the site returned
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

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

    A catalog of AI interfaces exists

    Failed

    Publish /.well-known/ai-catalog.json as JSON listing your MCP servers and other interfaces for agents.

    One file at a standard URL listing the company’s MCP servers and other interfaces for agents.

    API and MCP →
    ›What the site returned
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/.well-known/ai-catalog.json"
What already works27
  • Homepage opens without a CAPTCHA

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Text is visible without JavaScript

    ›What the site returned
    Found
    words of text: 387

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Prices are visible without JavaScript

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
    Found
    snippet: доступных тарифов Плата за месяц За год скидка 20 % Базовый 0 ₽ Бесплатный тариф для небольших команд и

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/pricing/"
  • A missing page returns 404

    ›What the site returned
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/agent-readiness-check-0afde12e8d/"
  • A short path from http to https

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, 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://loop.ru/"
  • The homepage is light and fast

    ›What the site returned
    Found
    page size, KB: 226
    response time, s: 0.528

    Repeat the check yourself

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

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/plain; 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://loop.ru/robots.txt"
  • A sitemap exists

    ›What the site returned
    Response code
    200
    Headers
    content-type: application/xml
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/sitemap.xml"
  • Homepage metadata is filled in

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Company or product markup is present

    ›What the site returned
    Found
    JSON-LD types: Answer, FAQPage, Organization, Question, SoftwareApplication, WebSite

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • The homepage links to API docs

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Pages have Markdown versions

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/markdown; 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://developers.loop.ru/index.md"
  • A clear heading structure

    ›What the site returned
    Found
    H1 headings: 1
    H2 headings: 10
    has <main>: yes

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Agents and AI search are allowed

    ›What the site returned
    Response code
    200

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/robots.txt"
  • Open API docs or an MCP server exist

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/html
    Found
    API markers: 18

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://developers.loop.ru/"
  • The homepage is not hidden from search

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Homepage text fits an agent’s memory

    ›What the site returned
    Found
    tokens, approx.: 1,115

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Content starts near the top of the page

    ›What the site returned
    Found
    text before the heading, %: 10

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • ChatGPT and Claude get the same page people do

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Markup links to official profiles

    ›What the site returned
    Found
    sameAs links: 3

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • AI search gets the same page people do

    ›What the site returned
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • The sitemap carries update dates

    ›What the site returned
    Response code
    200
    Headers
    content-type: application/xml
    vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
    Found
    share, %: 80

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/sitemap.xml"
  • Prices are in the markup

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/pricing/"
  • Questions and answers are marked up

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Images have text descriptions

    ›What the site returned
    Found
    share, %: 100

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • The page does not forbid quoting its text

    ›What the site returned

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://loop.ru/"
  • Pricing and docs are not closed to agents

    ›What the site returned
    Response code
    200

    Repeat the check yourself

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

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 MCP server answers a connection
  • MCP tools have descriptions
  • An access refusal says where to sign in
  • The site does not forbid using its text in AI answers

Check your own site

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

Check a site →