What a GEO KAMI report looks like
This is a real scan of geokami.com, refreshed once a week. Nothing here was written for the occasion: it is the same 37 checks and the same scoring every customer gets.
Overall score
geokami.com
Scanned 2026-09-19
34 of 37 checks passed
Most agents can already read this site. The rows that are not green are the ones still worth closing.
Score by category
Whether an agent can find the site at all — robots.txt, sitemap, security.txt and DNS records.
Whether an agent can fetch the content it found, in a form it can parse — llms.txt, markdown, canonical URLs.
Whether crawlers and AI bots are told what they may do, and whether that intent is machine-readable.
Whether the site publishes the machine-readable cards agents look for — MCP, A2A, OAuth, OpenAPI.
Whether the meaning of the content survives the trip — structured data, reviews, provenance, languages.
Whether the site is served over HTTPS with headers that keep tampering out.
Whether an agent could pay or transact — the emerging payment and commerce protocols.
All 37 checks
Grouped by category. Every check is shown with the result it was judged on.
How to read this
Every check runs on every scan and is scored out of its own maximum. A check can pass and still give away points — that is what the score out of the maximum measures, and why those rows read as Partial rather than Pass.
Discoverability30/35
- robots.txt10/10 · Pass
robots.txt exists with valid format
What it checks: Publish /robots.txt with clear crawl rules
- sitemap.xml10/10 · Pass
sitemap.xml exists and is valid
What it checks: Publish /sitemap.xml listing all pages
- security.txt10/10 · Pass
security.txt exists with valid contacts
What it checks: Publish /.well-known/security.txt
- DNS-AID Records0/5 · Fail
DNS-AID records not found (failed after 0 retries)
What it checks: Publish DNS-AID records for agent discovery
Content Accessibility40/55
- llms.txt Presence5/5 · Pass
llms.txt exists with content summary
What it checks: Pass llms.txt Presence
- llms.txt Quality10/15 · Partial
llms.txt content quality is high
What it checks: Ensure /llms.txt provides comprehensive AI guidance
- Markdown Negotiation0/10 · Fail
No markdown negotiation support (failed after 0 retries)
What it checks: Support Content-Type: text/markdown negotiation
- .md Page Variant5/5 · Pass
.md variant found
What it checks: Provide .md variants of key pages
- Open Graph / Meta Tags10/10 · Pass
Rich meta tags present
What it checks: Add OG tags, description, and Twitter Card meta tags
- Canonical URL5/5 · Pass
Canonical URL properly set
What it checks: Add <link rel="canonical"> to all pages
- Link Headers (RFC 8288)5/5 · Pass
Agent-discovery Link headers found
What it checks: Include Link headers for agent discovery
Bot Access Control15/25
- AI Bot Rules0/10 · Fail
No AI bot rules found (failed after 0 retries)
What it checks: Add AI-specific rules to robots.txt
- AI Privacy Compliance5/5 · Pass
AI privacy compliance measures found
What it checks: Publish AI training opt-out policy
- Web Bot Auth5/5 · Pass
Web Bot Auth JWKS found
What it checks: Publish JWKS for bot identity verification
- Content Signals5/5 · Pass
Content-Signal directives found
What it checks: Declare AI content usage preferences in robots.txt
Protocol Discovery52/55
- MCP Server Card5/5 · Pass
MCP Card found
What it checks: Publish MCP Server Card at /.well-known/mcp/server-card.json
- MCP Endpoint Validation5/5 · Pass
MCP configuration validated
What it checks: Validate MCP endpoint structure
- A2A Agent Card4/5 · Partial
A2A Card found
What it checks: Publish A2A agent card
- A2A Card Validation3/5 · Partial
A2A configuration validated
What it checks: Validate A2A card structure
- Agent Skills5/5 · Pass
Agent skills manifest found
What it checks: Publish agent skills index at /.well-known/agent-skills/index.json
- OAuth Discovery5/5 · Pass
OAuth configuration found
What it checks: Configure OAuth discovery endpoint
- OpenAPI Spec5/5 · Pass
OpenAPI spec found
What it checks: Publish OpenAPI specification
- API Catalog (RFC 9727)5/5 · Pass
API Catalog found
What it checks: Publish API catalog for automated discovery
- OAuth Protected Resource (RFC 9728)5/5 · Pass
OAuth Protected Resource metadata found
What it checks: Publish OAuth Protected Resource metadata
- Auth.md5/5 · Pass
auth.md found
What it checks: Publish auth.md for agent registration
- WebMCP5/5 · Pass
WebMCP implementation detected
What it checks: Implement WebMCP to expose tools via browser
AI Readability30/30
- JSON-LD Structured Data15/15 · Pass
3 JSON-LD snippet(s) found with 3 high-value Schema.org type(s)
What it checks: Add JSON-LD structured data markup
- Review/Rating Data5/5 · Pass
Reviews and/or ratings found (8 detected, 2 aggregate)
What it checks: Add review/rating structured data
- Content Authenticity5/5 · Pass
Content authenticity indicators found (4/8)
What it checks: Add C2PA and content provenance signals
- Multilingual Ready5/5 · Pass
Multilingual readiness features found (3/6)
What it checks: Add hreflang and multilingual support
Security & UX15/15
- Basic Security Check5/5 · Pass
Site uses HTTPS
What it checks: Use HTTPS for all pages
- HSTS Configuration Check5/5 · Pass
HSTS header present
What it checks: Add Strict-Transport-Security header
- Error Page Check5/5 · Pass
Custom 404 page detected
What it checks: Create custom 404 error page
Commerce20/20
- x402 Payment Protocol5/5 · Pass
x402 protocol detected
What it checks: Implement x402 payment protocol
- ACP Protocol5/5 · Pass
ACP protocol found
What it checks: Publish ACP protocol configuration
- Universal Commerce Protocol5/5 · Pass
UCP protocol detected
What it checks: Enable content payments via UCP
- Machine Payment Protocol5/5 · Pass
MPP protocol detected
What it checks: Support MPP for agent-native payments
See this for your own domain
Sign in, verify your domain, and run the same 37 checks on your own site.
Start free