Capability / Schema.org
Schema.org for places, visits and travel offers
A heritage site has an address. A Saturday guided visit has a date and meeting point. Its ticket offer has a price and booking conditions. These are connected pieces of information, each describing something different.
Schema.org provides a shared vocabulary for expressing those distinctions in structured data that software can read.
Tamaga helps tourism organizations decide what to describe, connect it appropriately and generate public markup from information they can maintain.
Describe the things your visitors need to understand
Consider a fictional heritage site offering guided visits. Its website explains the place, introduces the organizer and lists particular visits.
A useful model could distinguish:
| What the visitor encounters | What the structured representation describes |
|---|---|
| The heritage site | The place being visited, with its relevant public details. |
| A scheduled guided visit | An Event, where appropriate, connected to its location, date and organizer. |
| A ticket offer | The commercial offer associated with the visit, including the published price and booking destination. |
| The organizing association | The organization responsible for the activity. |
Schema.org supports relationships between an Event, its location, organizer and offers. The appropriate representation depends on what the page actually describes. Event specification, Offer specification
The aim is to make those relationships explicit while preserving the distinctions a visitor relies on.
Keep the conditions with the information
Suppose the French page describes a visit conducted in English. Translating the page changes the language of the explanation; it does not change the language of the visit.
A similar distinction applies to booking. A published ticket offer, an enquiry form and confirmed availability convey different information. We check which statements the source supports before choosing their public representation.
Some conditions need a clear written explanation. We retain them in the visible content and use suitable structured properties where they express the intended meaning.
When a date, meeting point or condition changes, the maintained record, affected pages and generated markup need to be reviewed together.
Place: the heritage site.
Guided visit: a scheduled activity at that site.
Offer: the price and booking conditions for that visit.
Illustrative fictional example. The site, visit and offer are distinct connected records; an offer does not confirm a booking.
What we review and implement
-
Step 1: Review the existing information and output
We inspect representative pages, their underlying records and the structured data already being generated. This includes identifying useful existing work, conflicting descriptions and information that has no clear maintenance owner.
-
Step 2: Define the appropriate entities and relationships
We choose suitable types and properties, identify the thing each record describes and establish its public identity. We also determine which information is appropriate for publication and which remains private.
If the underlying information needs organizing across several uses, Travel knowledge graphs explains that wider modeling work.
-
Step 3: Generate markup from maintained records
Where the platform supports it, public JSON-LD can be generated from approved content, fields and relationships. The mapping should make it clear where each value comes from and how it changes when the source is updated.
-
Step 4: Check the rendered result and its upkeep
We inspect the generated pages and relevant language versions. Checks cover the vocabulary’s meaning, relationships, visible content, publication boundaries and the requirements of the intended consumer.
The implementation outputs are a documented mapping, generated structured data, verification findings and an agreed way to maintain the result.
Choose the Drupal approach around the existing site
For Drupal projects, two approaches can serve different starting points:
- Schema.org Metatag extends Metatag to generate JSON-LD from an existing content model.
- Schema.org Blueprints uses Schema.org definitions to help build and maintain the content model itself.
The Blueprints maintainer identifies this distinction between mapping an existing model and building a standardized model. It does not establish an automatic requirement to migrate an existing website. Maintainer’s explanation
We first assess the records, relationships and editorial workflows worth retaining. The Drupal capability explains how that model connects with publishing and practical working tools.
Understand what the checks establish
A successful implementation needs several kinds of checks:
- Syntax: can the structured data be parsed?
- Meaning: do the selected types, properties and relationships describe the intended things accurately?
- Consumer requirements: does the page meet the documented requirements of a particular search feature or other intended use?
Google requires structured data to represent the page’s content accurately. Correct markup does not guarantee that a rich result will appear. A general Schema.org model and eligibility for a particular Google feature therefore need separate checks. Google’s structured-data guidelines
For the reasoning behind this approach, read why Schema.org represents maintained knowledge. The briefing develops that argument through a hospitality example.
Start with a representative page
Bring a page describing a place, visit, itinerary or offer, together with the information used to maintain it. Explain what visitors need to understand and which external service or search feature you want to support.
We can discuss the existing representation, the useful corrections and an implementation scope that your organization can maintain.