Discovery is everything for tour businesses. Almost none have the schema for it.
When travelers ask AI for food tours, wine tours, or walking tours in your city, TouristAttraction and TouristTrip schema determines whether your experience appears in the answer. Most tour operators depend entirely on TripAdvisor. Direct AI visibility changes that.
Your tours are invisible to the AI that recommends things to do.
Tour operators are among the most search-dependent businesses that exist. They have no physical storefront and depend on search discovery. "Things to do in [city]" and "food tours near me" are among the most AI-Overview-heavy query types in travel. The tour operators in those recommendations are not necessarily the best, they are the ones with the best-structured websites.
The TouristAttraction and TouristTrip schema types are designed specifically for this use case. They include duration, touristType, and itinerary, properties that AI systems use to match a tour to a specific traveler. "Best food tour in New Orleans for couples" requires touristType and duration to be answered precisely.
The dependency on TripAdvisor is a vulnerability. TripAdvisor appears in AI recommendations as a citation source, not as a direct booking interface. A tour operator that owns their direct AI visibility reduces this dependency and captures customers before they reach TripAdvisor at all.
Where tour operator sites usually lose clarity
Tour schema requirements that AI systems need.
TouristTrip schema must declare duration, itinerary, and tourist type. Without these properties, AI systems cannot match a tour to a specific travel request.
- vPrimary type: TouristAttraction and TouristTrip
- vduration in ISO 8601 format (PT3H)
- vtouristType and availableLanguage
- vitinerary with structured stops
- vEvent schema for scheduled departures
{
"@context": "https://schema.org",
"@type": "TouristTrip",
"name": "New Orleans French Quarter Food Tour",
"duration": "PT3H",
"touristType": "Foodies and couples",
"availableLanguage": "English",
"itinerary": {
"@type": "ItemList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"item": {
"@type": "TouristAttraction",
"name": "Central Grocery - Muffuletta Origin"
}
},
{
"@type": "ListItem",
"position": 2,
"item": {
"@type": "TouristAttraction",
"name": "Cafe Du Monde - Beignets and Chicory Coffee"
}
}
]
}
}The 3 gaps present on most tour operator sites.
No TouristAttraction schema
Tours are much harder for AI systems to classify because the business is not declared with a tour-specific entity type.
No Event schema
AI cannot surface scheduled departure times or availability in responses.
duration missing
AI cannot answer how long the tour lasts, reducing recommendation accuracy.
Common questions for tour operators.
Each distinct tour type benefits from its own TouristTrip entity with separate duration, touristType, and itinerary. This is included in the Full Setup scope for operators with multiple tour types.
The core TouristAttraction and TouristTrip schema can remain year-round. Event schema for specific departure times should be updated seasonally, which is handled during maintenance.
No. These are separate booking platforms with their own schemas. VERIS optimizes your own website's direct AI search visibility so customers find you before aggregators.
Find out if AI is recommending your tours or your competitors'.
The audit checks schema, AI crawler access, llms.txt, public discovery signals, and itinerary visibility. Free.