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.

No MCP server card was found at current, transitional, or linked discovery paths.

MCP server cards give agents a stable, public pre-connection discovery surface for server identity, remote transports, protocol compatibility, and safe routing without guessing endpoints.

No WebMCP surface was found to probe.

WebMCP gives agents structured page and browser tool hints so they can understand actions without relying only on screen scraping.

No explicit User-agent rules were found for major AI crawler tokens.

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.

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

/llms.txt was not found or could not be fetched.

llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.

Applicable editorial content has no usable author, creator, publisher, visible byline, or HTML attribution signal.

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Best candidate returned Content-Type "text/html; charset=utf-8" instead of text/markdown.

Markdown representations give agents a cleaner page form while preserving normal HTML for browsers and cache-safe representation handling.

Referrer-Policy header is missing.

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

No A2A Agent Card was found at the current, legacy, or fallback discovery paths.

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

No Agent Skills discovery index was found at the canonical or legacy path.

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

No Wildcard-style agents.json file was found.

Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.

No Content-Usage or Content-Signal declarations were found.

Content usage preference signals communicate intended downstream AI use separately from robots.txt crawl permission. They can express training and search preferences for compliant systems without replacing access-control rules.

No DNS-AID HTTPS/SVCB records were found under _agents.

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

No RSL declarations were found.

Really Simple Licensing is an emerging rights-expression layer for communicating content usage and licensing terms separately from robots.txt crawl permission.

No TDMRep declaration was found at /.well-known/tdmrep.json.

TDMRep is a W3C Community Group protocol and IANA-registered well-known URI for declaring text and data mining reservation policy on applicable content.

Applicable HTML response is missing an enforcing Content-Security-Policy header.

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

No valid X-Frame-Options fallback is present.

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

No WebSite entity was found in Schema.org structured data. WebSite.publisher is missing. Organization schema is missing logo and sameAs or public contact evidence.

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

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

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Missing source or trust signals: authorOrOwner, freshnessDate, sourceLinks, entityLinks.

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

No evidence-backed, citation-length explanatory paragraph was found.

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Missing answer evidence or trust signals: author, publisher, freshnessDate, sources, sameAs.

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

27 section(s) bury or omit a concise opening answer.

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

The sitemap lists page or child sitemap URLs outside the scanned origin host.

Sitemaps help crawlers and agents discover canonical URLs, update timestamps, and deeper content that may not be obvious from homepage navigation alone.

No natural question headings were detected. No visible FAQ or Q&A pattern was detected.

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Missing or weak extraction signals: summary or key takeaways, FAQ or question-answer section where appropriate.

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Semantic HTML is incomplete: 2 form controls missing labels; 0/1 applicable personal-data inputs have valid autocomplete attributes (1 missing).

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

Canonical does not self-reference the scanned page.

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

One or more same-origin active resources observed by Chrome did not emit X-Content-Type-Options: nosniff.

X-Content-Type-Options tells browsers to trust declared media types instead of sniffing content, reducing the risk that mislabeled files execute as active content.

HSTS is valid, but includeSubDomains is absent.

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade, SSL-stripping, and mixed-transport risk for repeat users.

27 section(s) bury or omit a concise opening answer.

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.