The API catalog endpoint did not return HTTP 2xx.

API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.

OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=utf-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.

OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.

No specific User-agent rules found for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.

Explicit AI bot rules reduce ambiguity for crawler operators and make training, indexing, or retrieval access policy auditable.

No Content Signal found in robots.txt

Content Signal provides a machine-readable way to communicate AI usage preferences where participating crawlers look for policy.

Content-Security-Policy is missing or incomplete.

Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.

Frame protection is missing or incomplete.

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking risk.

llms.txt was not found at the expected path.

llms.txt gives language-model clients a concise, curated summary of important site context and links before they crawl broadly.

Referrer-Policy is missing or incomplete.

Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.

Semantic HTML is incomplete: missing <main> landmark; missing <nav> landmark; missing <footer> landmark; invalid h1 (found 2); skipped heading levels; 2 links missing accessible names; 0/3 applicable form inputs have autocomplete attributes (3 missing).

Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.

Web Bot Auth request signing was not found at the expected path.

Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.

No high-value schema types (e.g. Article, Product, Service) were found.

High-value schema types tell agents whether a page is an article, product, event, service, or other actionable content type.

No JSON-LD blocks found.

JSON-LD is a low-friction structured data format that agents can extract without interpreting page presentation or microdata markup.

No useful agent discovery Link headers were found.

Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.

MCP Server Card was not found at the expected path.

MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.

mcp.json was not found at the expected path.

MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.

Neither Organization nor WebSite schema types were found in JSON-LD.

Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.

WebMCP manifest was not found at the expected path.

A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.

Content freshness signals are incomplete: missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.

Freshness signals help agents decide whether content is current enough to cite, summarize, or compare against newer sources.

A2A Agent Card was not found at the expected path.

A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.

Agent Skills index was not found at the expected path.

An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.

agent.json was not found at the expected path.

agent.json is an emerging machine-readable manifest for declaring what a website does, how agents authenticate, and which actions or protocols are available.

agents.json was not found at the expected path.

agents.json gives clients a simple directory of agent-facing capabilities and contacts when a site chooses to advertise them.

No DNS-AID entrypoint records were found under _agents.

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata, while DNSSEC can authenticate the discovery zone.

WebMCP declarative annotations need fixes.

WebMCP can expose page context and actions directly through the browser, giving agents safer structured hooks than screen scraping alone.

No JSON-LD structured data was detected.

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Missing AIO trust signals: author, publisher, freshnessDate, policyLinks.

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Missing AIO trust signals: author, publisher, freshnessDate, policyLinks.

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema, clear definition sentence using "is", "means", or "refers to" where natural, JSON-LD structured data.

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

10 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

No question-led h2 sections or FAQ pattern was detected.

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Title/H1 terms missing from description: meritech, leaders, inmarkets.

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

No substantial explanatory paragraphs were found.

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Entity or definition gaps: meritech, leaders, inmarkets.

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

10 section(s) may benefit from a clearer opening answer; this is optional for feature/card sections.

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Missing likely AI Overview intent sections: what, how, benefits, cost, compare.

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.