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.

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

X-Content-Type-Options is missing or incomplete.

X-Content-Type-Options prevents browsers from treating mislabeled files as executable content, reducing content-sniffing attacks.

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.

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.

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-Type "text/html; charset=utf-8" does not indicate Markdown when requested with Accept: text/markdown.

Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.

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.

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.

Semantic HTML is incomplete: missing <main> landmark; missing <footer> landmark; 4 links missing accessible names.

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.

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.

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.

Content-Type "text/html; charset=utf-8" is not JSON, Markdown, or text/plain.

A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.

Response is not valid JSON.

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

Response is not valid JSON.

A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking 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.

Response is not valid JSON.

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

Response is not valid JSON.

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

Response is not valid JSON.

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

Missing AIO trust signals: author, publisher, freshnessDate.

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.

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.

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

Title/H1 terms missing from description: online, tests, technical, interviews, hire, next, generation, developer.

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

4 structured-data value(s) were not found in visible page text.

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

3 explanatory paragraph(s) could be stronger for citation or AI extraction.

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.

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.

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.

49 image(s) are missing width/height attributes. 5 possible modal/interstitial element(s) 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.

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

Entity or definition gaps: online, tests, technical, interviews, hire, next, generation, developer.

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