The Ultimate TouristTrip
Schema Generator
Sell tours and experiences with rich, bookable-looking search results. TouristTrip schema surfaces itinerary, duration, and pricing for travel and experience marketplaces.
Magic Build
Paste your URL below and our AI will automatically fill the TouristTrip fields for you.
Configuration
Live GeneratorWhy use TouristTrip?
Sell tours and experiences with rich, bookable-looking search results. TouristTrip schema surfaces itinerary, duration, and pricing for travel and experience marketplaces.This type is officially supported by major search engines for enhancing search listing appearance.
Output Panel
Want to automate this?
Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.
Launch AI GeneratorWhat is TouristTrip Schema?
Sell tours and experiences with rich, bookable-looking search results. TouristTrip schema surfaces itinerary, duration, and pricing for travel and experience marketplaces.
Google uses TouristTrip structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.
Why Add TouristTrip Structured Data?
Appear in Rich Results
Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.
Boost Click-Through Rate
Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.
Feed AI Search Engines
AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.
How to Implement TouristTrip JSON-LD
Generate
Use the form above to fill in your details and generate valid TouristTrip JSON-LD markup in seconds.
Copy
Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.
Deploy
Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.
Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.
Properties You Can Include
TouristTrip schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.
| Property | Description | Expected Type | Status |
|---|---|---|---|
| additionalType | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide. | Text, URL | Optional |
| alternateName | An alias for the item. | Text | Optional |
| arrivalTime | The expected arrival time. | DateTime, Time | Optional |
| departureTime | The expected departure time. | DateTime, Time | Optional |
| description | A description of the item. | Text, TextObject | Optional |
| disambiguatingDescription | A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation. | Text | Optional |
| identifier | The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details. | PropertyValue, Text, URL | Optional |
| image | An image of the item. This can be a URL or a fully described ImageObject. | ImageObject, URL | Recommended |
| itinerary | Destination(s) ( Place ) that make up a trip. For a trip where destination order is important use ItemList to specify that order (see examples). | ItemList, Place | Optional |
| mainEntityOfPage | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details. | CreativeWork, URL | Optional |
| name | The name of the item. | Text | Required |
| offers | An offer to provide this item—for example, an offer to sell a product, rent the DVD of a movie, perform a service, or give away tickets to an event. Use businessFunction to indicate the kind of transaction offered, i.e. sell, lease, etc. This property can also be used to describe a Demand. While this property is listed as expected on a number of common types, it can be used in others. In that case, using a second type, such as Product or a subtype of Product, can clarify the nature of the offer. | Demand, Offer | Optional |
| owner | A person or organization who owns this Thing. | Organization, Person | Optional |
| partOfTrip | Identifies that this Trip is a subTrip of another Trip. For example Day 1, Day 2, etc. of a multi-day trip. | Trip | Optional |
| potentialAction | Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role. | Action | Optional |
| provider | The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller. | Organization, Person | Optional |
| sameAs | URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website. | URL | Optional |
| subjectOf | A CreativeWork or Event about this Thing. | CreativeWork, Event | Optional |
| subTrip | Identifies a Trip that is a subTrip of this Trip. For example Day 1, Day 2, etc. of a multi-day trip. | Trip | Optional |
| touristType | Attraction suitable for type(s) of tourist. E.g. children, visitors from a particular country, etc. | Audience, Text | Optional |
Example TouristTrip JSON-LD
Here's what valid TouristTrip structured data looks like with sample values filled in. Use the generator above to replace these with your own data.
{
"@context": "https://schema.org",
"@type": "TouristTrip",
"name": "Example TouristTrip",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page",
"additionalType": "Example additionalType",
"alternateName": "Example alternateName",
"arrivalTime": "2026-08-01T10:00:00-05:00",
"departureTime": "2026-08-01T10:00:00-05:00",
"description": "A sample description for this TouristTrip."
}Validate Your TouristTrip Schema
Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.
Check your TouristTrip schema for errors and Rich Result eligibility