Response is not valid 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.

Response is not valid JSON.

OAuth and OIDC discovery let agents find authorization, token, and key endpoints programmatically instead of relying on human documentation.

Response is not valid JSON.

Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.

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.

OpenAPI YAML document did not match the expected shape. Content-Type "text/html" 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.

Response is not valid JSON.

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

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.

HSTS header is missing or incomplete.

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

Content-Type "text/html" 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.

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; invalid h1 (found 3); skipped heading levels; 7 links missing accessible names; missing alt text on >10% of images.

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

No structured data (JSON-LD, Microdata, or RDFa) found on page.

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

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.

Content-Type "text/html" 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.

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

Response is not valid JSON.

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

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.

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.

FAQ content was detected but no FAQPage schema was found.

FAQPage schema lets agents extract visible question-and-answer content cleanly and avoid guessing which text is an answer.

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.

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.

robots.txt was found but could not be parsed as valid.

robots.txt gives crawlers and agents a standard place to read crawl permissions, disallowed paths, and sitemap locations before requesting site content.

No valid XML sitemap found at checked locations: https://beyondgames.co/sitemap.xml, https://beyondgames.co/sitemap_index.xml, https://beyondgames.co/sitemap-index.xml.

Sitemaps help crawlers and agents discover canonical URLs, updated pages, and deeper content that may not be obvious from the homepage navigation.

Response is not valid JSON.

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

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.

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.

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.

llms.txt response did not match the expected shape. Content-Type "text/html" is not Markdown or text/plain; missing h1 title (e.g. # Site Name).

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

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

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.

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

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

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

Canonical tag is missing.

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

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

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

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