Tour Operator Stack
Tour operator pages with TravelAgency + TouristTrip context, FAQs, and breadcrumb navigation.
When to use this stack
- Tour operator landing pages with trip offerings
- Guided tour pages with itineraries and pricing
- Pages where FAQs clarify inclusions, cancellations, and logistics
What is included
Anchors the tour operator’s identity, contact info, and services.
Describes the tour itinerary, duration, and destination.
Answers questions about inclusions, refunds, and meeting points.
Provides navigation context to the tour page.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- address.addressLocality
- address.addressRegion
- address.streetAddress
- description
- itemListElement[].name
- itinerary.name
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- telephone
- touristType
- url
Recommended properties
- endDate
- geo.latitude
- geo.longitude
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- offers.price
- offers.priceCurrency
- priceRange
- sameAs[]
- startDate
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "TravelAgency",
"@id": "https://www.example.com/tours#agency",
"name": "Cascade Trail Tours",
"url": "https://www.example.com/tours",
"telephone": "+1-206-555-0130",
"image": "https://www.example.com/images/cascade-tours.webp",
"address": {
"@type": "PostalAddress",
"streetAddress": "450 Pine St",
"addressLocality": "Seattle",
"addressRegion": "WA",
"postalCode": "98101",
"addressCountry": "US"
},
"priceRange": "$$"
},
{
"@context": "https://schema.org",
"@type": "TouristTrip",
"@id": "https://www.example.com/tours/alpine-lakes#trip",
"name": "Alpine Lakes Day Tour",
"description": "Guided day trip to three alpine lakes with hiking and lunch included.",
"touristType": "Adventure Travelers",
"itinerary": [
{
"@type": "ItemList",
"name": "Day Tour Itinerary",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Departure from downtown Seattle" },
{ "@type": "ListItem", "position": 2, "name": "Hike and lake visit" },
{ "@type": "ListItem", "position": 3, "name": "Lunch at the trailhead" }
]
}
],
"offers": {
"@type": "Offer",
"price": "149.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/tours/alpine-lakes#book"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is included?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Transportation, guide, lunch, and park entry fees are included."
}
},
{
"@type": "Question",
"name": "Where is the meeting point?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We meet at 8:00 AM at 450 Pine St, Seattle. Exact details are sent after booking."
}
},
{
"@type": "Question",
"name": "What is the cancellation policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Full refunds are available up to 48 hours before departure."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Tours", "item": "https://www.example.com/tours" },
{ "@type": "ListItem", "position": 3, "name": "Alpine Lakes", "item": "https://www.example.com/tours/alpine-lakes" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Should I include multiple trips?
Yes. Include one TouristTrip per tour listing if multiple tours appear on the page.
What if pricing varies by date?
Use offers.url to point to the pricing selector and keep visible ranges aligned with the Offer.