Short answer: a travel website needs Organization (sitewide identity), LocalBusiness or TravelAgency (for a physical office), Service (for each service page), Article (for guides) and BreadcrumbList (for navigation context), all as JSON-LD. FAQPage is still a valid schema.org type but Google no longer shows FAQ rich results at all, so add it for machine-readability, not for stars in the listing. Validate everything with the Rich Results Test and the Schema.org validator before shipping.
What schema markup does and does not do
Schema markup (structured data) is machine-readable JSON you embed in a page so search engines can identify entities and facts without guessing from prose. Google's structured data documentation (Google Search Central) is explicit on two points: structured data is not a ranking factor by itself, and marked-up content must be visible to users and match what the markup claims. Its real value on a travel site is entity clarity - connecting your website, your Google Business Profile and your brand into one consistent identity - plus eligibility for the rich result types Google still supports, such as breadcrumbs and review snippets where genuinely applicable.
Google recommends JSON-LD as the preferred format. Put each block in a <script type="application/ld+json"> tag in the page head or body; never mark up content the page does not show.
The types that matter for travel sites
| Schema type | Where to use it | Why |
|---|---|---|
| Organization | Every page (usually in the site template) | Establishes the brand entity: legal name, logo, contacts, social profiles. Feeds knowledge panels. |
| LocalBusiness / TravelAgency | Location and contact pages | Connects the site to a physical office and to your Google Business Profile. TravelAgency is a schema.org subtype of LocalBusiness. |
| Service | Each service page | Describes what you sell and the area you serve. No rich result, but strong entity clarity. |
| Article | Guides and blog posts | Declares headline, author, dates. Supports how your content appears in Search and Discover. |
| BreadcrumbList | Every page below the home page | Google can show the breadcrumb trail in the listing instead of a raw URL. |
| FAQPage | Pages with genuine Q&A content | Still valid schema.org, but Google no longer shows FAQ rich results (see below). |
Types like Flight, Trip and TouristTrip exist on schema.org but currently drive no Google rich result for an agency site; add them only if you have a data feed use for them. Focus effort on the six above and on the page quality itself - see our guide to SEO for travel agencies for where schema fits in the bigger picture.
Organization: your sitewide identity
One Organization block, emitted on every page from your template, keeps the entity consistent:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Globitude Travels & Tech",
"url": "https://www.example.com/",
"logo": "https://www.example.com/assets/logo.png",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+91-88128-00000",
"contactType": "customer service",
"availableLanguage": ["en", "hi"]
},
"sameAs": [
"https://www.linkedin.com/company/example",
"https://www.instagram.com/example"
]
}Use your registered legal or trading name exactly as it appears on your website footer and your business profile. The sameAs array should list only profiles you control.
LocalBusiness and TravelAgency
On your contact or location page, use the TravelAgency subtype so the entity is categorised correctly:
{
"@context": "https://schema.org",
"@type": "TravelAgency",
"name": "Globitude Travels & Tech",
"image": "https://www.example.com/assets/office.jpg",
"address": {
"@type": "PostalAddress",
"streetAddress": "Two Horizon Center, Golf Course Road",
"addressLocality": "Gurugram",
"addressRegion": "Haryana",
"postalCode": "122002",
"addressCountry": "IN"
},
"telephone": "+91-88128-00000",
"url": "https://www.example.com/",
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "10:00",
"closes": "18:30"
}]
}The address, phone and hours must match your Google Business Profile character for character - mismatched NAP data undermines the local entity you are trying to build. Our guide to Google Business Profile for travel agencies covers the profile side.
Service pages
Each service page - visa assistance, corporate travel, portal development, whatever you sell - gets a Service block naming the service, the provider and the area served:
{
"@context": "https://schema.org",
"@type": "Service",
"serviceType": "Travel website development",
"provider": { "@type": "Organization", "name": "Globitude Travels & Tech" },
"areaServed": ["IN", "AE", "US", "GB"],
"url": "https://www.example.com/travel-website-development/",
"description": "Design and development of booking-ready travel agency websites."
}Service markup produces no rich result in Google today, so keep it lean and accurate rather than stuffing it with keywords. Do not add aggregateRating unless the page visibly shows genuine, verifiable reviews collected on your own site - self-serving review markup is restricted under Google's review snippet guidelines.
Article and BreadcrumbList
Guides should carry Article markup with real authorship and dates:
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Schema markup for travel websites",
"author": { "@type": "Organization", "name": "Globitude Editorial Team" },
"datePublished": "2026-08-24",
"dateModified": "2026-08-24",
"publisher": { "@type": "Organization", "name": "Globitude Travels & Tech" }
}BreadcrumbList mirrors your visible breadcrumb trail (Home, Guides, this page) with itemListElement entries in order. It remains one of the few universally supported rich results and helps every listing on the site, which is why a well-built travel website emits it from the template automatically rather than page by page.
FAQPage: what changed
This is the area where most advice online is out of date. In August 2023, Google announced (Search Central blog, "Changes to HowTo and FAQ rich results") that FAQ rich results would only be shown for well-known, authoritative government and health websites. In 2026 Google went further: FAQ rich results no longer appear in Search at all, and the FAQ search appearance and its Search Console report have been retired.
Practical consequences: do not add FAQPage markup expecting expandable Q&A in your listing - that reward is gone for everyone. FAQPage remains a valid schema.org type, existing markup does no harm, and clearly structured question-and-answer content remains valuable for users and for how language models and answer engines read your pages. Write the FAQ for the reader; treat the markup as optional metadata.
Validation workflow
- Test each template with Google's Rich Results Test, which checks eligibility for Google rich result types.
- Run the same code through the Schema.org Markup Validator, which checks general schema.org correctness beyond Google's subset.
- After deployment, watch the enhancements and structured data reports in Google Search Console for errors and warnings at scale.
- Re-validate whenever the template changes - a broken JSON comma silently kills every block on the page.
- Keep markup and visible content in sync; markup for content users cannot see violates Google's structured data policies.
If your pages are generated by a portal platform, bake the markup into the templates during portal development rather than retrofitting page by page, and confirm the output on a staging URL before go-live. Schema is one part of conversion-ready pages - our guide to travel website conversion optimisation covers the rest of the page.
This article is general information about travel technology and online marketing. It is not legal, tax or financial advice, and advertising platform policies change often. Check the current policy documents and take professional advice for your own situation.