What we check
Six categories, weighted by booking impact
Everything an AI agent needs to find your tours, understand what they cost, and complete a booking — with tourism-specific checks no generic scanner runs.
20%
AI Content Discovery
If crawlers can't reach you, nothing else matters. We check robots.txt against all 13 major AI bots, your XML sitemap, and llms.txt — the curated front door for AI agents.
- robots.txt
- AI crawler directives
- XML sitemap
- llms.txt
- meta robots
25%tourism-first
Tour Data & Schema
Agents book from structured data, not adjectives. We validate JSON-LD for Product, TouristTrip, Event and TouristAttraction — and whether every offer carries a price, currency and availability.
- JSON-LD
- TouristTrip
- Offer & price
- aggregateRating
- BreadcrumbList
20%tourism-first
Agent Bookability
The headline question: could an agent act, not just read? We probe WebMCP, MCP discovery, A2A agent cards, OpenAPI — and whether 'Book now' is a real link in your HTML.
- WebMCP
- MCP discovery
- A2A agent card
- OpenAPI
- booking path
15%
Content & Semantics
Browser agents combine the DOM, accessibility tree and screenshots. We check server-rendered content, heading hierarchy, landmarks, alt text and link clarity.
- SSR
- headings
- landmarks
- alt text
- link text
10%
Trust & Security
HTTPS is the baseline. HSTS, CSP and strict headers form the trust layer agents require before transacting on your site.
- HTTPS
- HSTS
- CSP
- X-Frame-Options
- Referrer-Policy
10%
Local & Experience Signals
Tours happen somewhere. We check machine-readable meeting points, opening hours, phone and address, FAQ markup and share cards.
- GeoCoordinates
- opening hours
- NAP
- FAQPage
- Open Graph