Перейти до основного вмісту
Рівень 1

Сайту потрібні виправлення

Сайт знаходиться в пошуку, але не пройдено перевірок: 11. Це заважає AI-агентам зрозуміти і використовувати сайт. Нижче — що зробити в першу чергу.

https://api.starveri.net/
  • 58
    Видимість для AI
    1/5 перевірок
  • 29
    Доступність контенту
    0/4 перевірок
  • 29
    Правила для AI-ботів
    0/3 перевірок
  • 0
    Технічні протоколи
    0/6 перевірок
  • Електронна комерція
    Не перевірено

Що зробити в першу чергу

ВажливоПомилка

Markdown content negotiation

Add content negotiation in the route or middleware: render clean page text for Markdown requests while keeping HTML for browsers.

ВажливоЧастково

AI bot rules

Add dedicated `User-agent` groups or a wildcard policy with `Allow`/`Disallow`; verify it does not accidentally block required SEO crawlers.

ВажливоЧастково

llms.txt

Create a short agent-facing index: a single H1 title, a one-line blockquote summary right after it, `##` sections that list key URLs as `[name](url): note`, prefer Markdown (`.md`) link targets, and serve the file with `Content-Type: text/markdown`.

ВажливоЧастково

robots.txt availability

Create or update `/robots.txt`: add rules for generic and AI crawler user agents, include an absolute sitemap URL, and serve it as `text/plain`.

ВажливоЧастково

Server-rendered content availability

Enable SSR/SSG or a server-side fallback for public pages; do not leave an empty app root as the only source of content.

Зони сайту

  • Видимість для AI

    58

    1 пройдено · 3 частково · 1 помилок

    Можна відкластиЧастково

    Canonical and metadata

    Populate metadata in the layout/template for each public page; do not rely only on client-side head updates. Point each page's canonical at its own clean URL (consolidating tracking/variant query parameters), keep `og:url` consistent with that canonical, add all four required `og:*` properties, and remove `noindex` from pages that should be available to agents.

    СередньоЧастково

    Generic structured data

    Add server-rendered JSON-LD in the `<head>` or body template; use `Article`, `WebPage`, `Organization`, `FAQPage`, `BreadcrumbList`, or another appropriate Schema.org type and keep `og:title`, `og:description`, and `og:url` populated.

    СередньоПомилка

    Discovery Link headers

    Add `Link` headers at the web server or application response layer; use absolute URLs and correct `rel`/`type` parameters.

    ВажливоЧастково

    robots.txt availability

    Create or update `/robots.txt`: add rules for generic and AI crawler user agents, include an absolute sitemap URL, and serve it as `text/plain`.

  • Доступність контенту

    29

    0 пройдено · 2 частково · 2 помилок

    СередньоПомилка

    llms-full.txt

    Publish the full public content as one Markdown file: an H1 title, a blockquote summary right after it, then `##`/`###` sections of complete text (overview, important pages, usage limits) and no private data. Serve it with an explicit `Content-Type: text/markdown` (or `text/plain`) and `Vary: Accept`, and keep a companion `/llms.txt` index next to it. Do not trim the file just for size — a large valid document passes the check.

    ВажливоЧастково

    llms.txt

    Create a short agent-facing index: a single H1 title, a one-line blockquote summary right after it, `##` sections that list key URLs as `[name](url): note`, prefer Markdown (`.md`) link targets, and serve the file with `Content-Type: text/markdown`.

    ВажливоПомилка

    Markdown content negotiation

    Add content negotiation in the route or middleware: render clean page text for Markdown requests while keeping HTML for browsers.

    ВажливоЧастково

    Server-rendered content availability

    Enable SSR/SSG or a server-side fallback for public pages; do not leave an empty app root as the only source of content.

  • Правила для AI-ботів

    29

    0 пройдено · 1 частково · 2 помилок

    ВажливоЧастково

    AI bot rules

    Add dedicated `User-agent` groups or a wildcard policy with `Allow`/`Disallow`; verify it does not accidentally block required SEO crawlers.

    СередньоПомилка

    Content usage policy signals

    Add consistent policy headers/meta/link rels pointing to usage terms; do not encode legal guarantees in code.

    Можна відкластиПомилка

    Rate-limit hints

    Configure rate-limit middleware/edge rules and return clear headers for 429 or controlled throttling.

  • Технічні протоколи

    0

    0 пройдено · 0 частково · 6 помилок

    СередньоПомилка

    A2A/WebMCP readiness

    Publish agent card/WebMCP JSON only for capabilities that truly exist; add docs links and tests for JSON validation.

    СередньоПомилка

    Agent Skills index

    Create index JSON for public skills, add schema validation, and use stable URLs for skill files or documentation.

    СередньоПомилка

    API Catalog discovery

    Publish API catalog JSON, add links to OpenAPI/JSON Schema documents and a `Link` header; do not include private or internal endpoints.

    СередньоПомилка

    MCP Server Card

    Publish MCP discovery JSON at `/.well-known/mcp` or an MCP Server Card path; when using another URL, add a root `Link` header with `rel="mcp-server-card"`. List only public endpoints and do not expose private tools.

    СередньоПомилка

    OAuth authorization server metadata

    Enable the standard OAuth/OIDC discovery endpoint in the provider or proxy; verify HTTPS URLs, issuer consistency, PKCE `S256`, scopes, and cache headers.

    СередньоПомилка

    OAuth protected resource metadata

    Add well-known JSON for the protected resource, list authorization server URLs, and verify linked server metadata includes PKCE `S256`/scopes without exposing internal resources.

  • Електронна комерція

    Не перевірено