The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

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

No Organization or Organization subtype was found in Schema.org structured data. No WebSite entity was found in Schema.org structured data. Missing identity field(s): Organization.name, Organization.url, WebSite.name, WebSite.url. 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.

No JSON-LD, Microdata, or RDFa structured data was found.

Structured data gives agents explicit entities, relationships, and page meaning that are harder to infer reliably from visual layout alone.

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.

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.

CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

Semantic HTML is incomplete: expected exactly one visible main landmark, found 0; invalid h1 structure (visible h1 count 13); skipped or empty headings; 29 links missing accessible names; 6 image alt text quality issues.

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

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

No named author or publisher identity could be extracted.

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

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.

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

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways, lists for grouped facts or steps, FAQ or question-answer section where appropriate, typed JSON-LD structured data.

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 natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were detected. No list or table answer format 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 answer evidence or trust signals: author, publisher, freshnessDate, 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.

Missing source or trust signals: authorOrOwner, freshnessDate, 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.

Missing AIO trust signals: author, publisher, freshnessDate.

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.

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.

7 image(s) are missing width/height attributes.

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.

Expected exactly one h1, found 13. 11 section(s) may benefit from clearer answer-first openings. Heading outline issues were detected.

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.