Knowledge base · AI Readiness
AI Web Check technical guides
Implementation-focused notes for AI Readiness, agentic discovery and AI-commerce. The guides explain what the checker can observe, what it cannot prove, and how to improve the underlying technical signal.
No single signal guarantees ranking, citation or agent selection. Optional protocols are clearly marked and do not reduce AI Readiness when absent.
Standard or specification
Schema.org structured data for AI-readable pages
How to publish explicit machine-readable entities and properties without duplicating formats or claiming that markup itself guarantees ranking, citation, or AI use.
Vendor documentation
AI crawlers and robots.txt: separate search, training, and user retrieval
How to distinguish crawl policy, search visibility, model-development controls, and user-triggered retrieval instead of treating every AI user-agent token as the same mechanism.
Standard or specification
XML sitemaps and public URL discovery
What a sitemap actually tells automated systems, why it is useful for discovery, and why it does not replace navigation, canonicalization, or page accessibility.
Standard or specification
Canonical URLs, robots meta, and X-Robots-Tag
How to separate preferred-URL signals, crawl policy, and indexing directives so canonical, sitemap, robots meta, and HTTP headers do not contradict each other.
Established web practice
Content without mandatory JavaScript execution
Why meaningful HTML in the initial response remains a strong technical baseline even when some search systems can render JavaScript.
Experimental practice
llms.txt and llms-full.txt: useful context without false promises
How to use the proposed llms.txt format as an additional machine-readable map without presenting it as a ranking factor, crawler directive, or mandatory web standard.
Experimental practice
WebMCP: page-level tools for browser agents
How browser pages can expose structured tools through document.modelContext, why this differs from a server API or MCP server, and why it does not affect AI Readiness scoring.
Standard or specification
Schema.org Product and Offer for AI-commerce
How to describe products, offers, price, currency, availability, identifiers, and variants without creating a machine-readable version that conflicts with the visible product page.
Experimental practice
Universal Commerce Protocol: publishing a commerce capability profile
How UCP discovery describes protocol version and commerce capabilities, and why a public profile must remain separate from authentication and transaction authority.
Standard or specification
A2A Agent Card: capability discovery without hidden authority
How an A2A Agent Card describes identity, interfaces, skills, and security requirements while keeping credentials and execution authority out of public discovery.
Standard or specification
OpenAPI as a machine-readable action contract
How OpenAPI helps software and agents understand HTTP operations without confusing interface description with permission to execute those operations.
Standard and security practice
Agent endpoint security: public discovery without excessive authority
A practical boundary between public capability metadata and protected execution: safe URLs, TLS, authentication, scoped authorization, least privilege, secrets, rate limits, and confirmation for irreversible actions.