Skip to main content
Level 1

Your site needs fixes

The site is reachable, but 11 checks failed and are blocking AI agents from understanding and using it. The fixes below should be done first.

https://api.starveri.net/
  • 65
    AI visibility
    2/5 checks
  • 29
    Content accessibility
    0/4 checks
  • 29
    AI bot rules
    0/3 checks
  • 0
    Technical protocols
    0/6 checks
  • E-commerce
    Not checked

What to do first

ImportantFail

Markdown content negotiation

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

ImportantPartial

AI bot rules

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

ImportantPartial

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`.

ImportantPartial

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`.

ImportantPartial

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.

Site health

  • AI visibility

    65

    2 pass · 2 partial · 1 fail

    Can waitPartial

    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.

    MediumFail

    Discovery Link headers

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

    ImportantPartial

    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`.

  • Content accessibility

    29

    0 pass · 2 partial · 2 fail

    MediumFail

    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.

    ImportantPartial

    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`.

    ImportantFail

    Markdown content negotiation

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

    ImportantPartial

    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 bot rules

    29

    0 pass · 1 partial · 2 fail

    ImportantPartial

    AI bot rules

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

    MediumFail

    Content usage policy signals

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

    Can waitFail

    Rate-limit hints

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

  • Technical protocols

    0

    0 pass · 0 partial · 6 fail

    MediumFail

    A2A/WebMCP readiness

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

    MediumFail

    Agent Skills index

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

    MediumFail

    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.

    MediumFail

    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.

    MediumFail

    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.

    MediumFail

    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.

  • E-commerce

    Not checked