Table of Contents
- What Schema Markup Actually Does for a Destination Site
- FAQPage Schema: The Highest-Leverage Type for AI Citation
- TouristAttraction and TouristDestination: Building the Itinerary Layer
- Event Schema: Getting Festivals and Calendars Into Search and AI Answers
- Review and AggregateRating Schema: Building Trust Signals Correctly
- ItemList Schema for Attraction and Partner Directories
- Implementing Schema Without Creating New Problems
- Frequently Asked Questions
Most destination websites are running on almost no structured data. An audit of Australian DMO sites, attractions, and festival pages found near-zero use of tourism-specific schema: no TouristAttraction markup on major national park pages, no Event markup on festival homepages, and breadcrumbs as the only structured data present on most destination pages (Tourism Tribe, 2026). That gap is now a visibility problem in two directions at once: traditional search results and the AI answers that increasingly sit above them.
Schema is a short, plain-language label attached to each page, the same way a name tag tells a person at a conference who they are talking to before any conversation starts. Schema markup is JSON-LD code added to a page that tells search engines and AI systems exactly what the page is about (an attraction, an event, a multi-day itinerary, a review) rather than leaving them to infer it from prose. For destination marketers, five schema types do most of the work: FAQPage, TouristAttraction/TouristDestination, Event, Review/AggregateRating, and ItemList. Each is covered below, along with what it does for SEO and what it does for AI interpretation, which are no longer the same job.
Self-contained Q&A pairs written the way travelers ask AI assistants. Still read by AI Overviews, ChatGPT, and Perplexity even after Google retired the FAQ rich result.
AI CitationConnects a region page to its individual attractions via includesAttraction. Almost no DMOs use this today — the entity-clarity gap is wide open.
Entity ClarityOne dedicated leaf page per event, with accurate start/end dates. Calendar pages should link out, not carry the markup themselves.
Search + AIApply on bookable products, not on self-reviewed Organization or LocalBusiness pages, which Google will not display as star results.
Trust SignalsTurns "Things to Do" and partner directory pages into machine-readable sequences instead of unstructured prose.
Structured ListsOnly implement a schema type if you can fill it accurately and completely. A sparse, generic block is worse than no markup at all.
ImplementationWhat Schema Markup Actually Does for a Destination Site
Structured data is implemented in JSON-LD, a script block placed in a page’s <head> or immediately after the opening <body> tag. It does not change what a visitor sees on the page. It changes what a machine can extract from the page without guessing.
That distinction matters more in 2026 than it did two years ago. Google formally retired the FAQ rich result, the expandable question-and-answer accordion under a search listing, on May 7, 2026 (Quattr, 2026). Some destination marketers read that as a signal to drop FAQ schema. It is the opposite signal. AI systems including Google AI Overviews, ChatGPT, and Perplexity still parse FAQPage markup to identify clean question-and-answer pairs for citation; what disappeared was the visual snippet in classic search, not the underlying value to AI extraction (Quattr, 2026).
Not sure where your site stands on AI visibility today?
service audits how your destination’s structured data and content are performing across both traditional search and AI-generated answers.
FAQPage Schema: The Highest-Leverage Type for AI Citation
FAQPage schema marks up genuine question-and-answer content in a format schema.org and AI systems both recognize. Google’s own guidance is specific about scope and quality: add FAQ content because it is genuinely useful to the reader, keep it to a handful of questions that are actually relevant to that page, and avoid using it on purely promotional content (Quattr, 2026). Three to eight questions per page is the range most implementation guides converge on.
The format matters as much as the markup. An answer written for AI extraction needs to stand alone: no “as mentioned above,” no pronouns referring back to a paragraph the AI system did not also extract. Industry analysis of AI citation behavior found that FAQ-formatted content built this way earns citation rates roughly 2.5 to 2.7 times higher than unstructured equivalents on the same topic (Quattr, 2026).
For a destination page, this means writing FAQs the way a traveler actually types a question into an AI assistant, not the way a brochure would phrase a headline. “What is the best time of year to visit Asheville, North Carolina?” extracts cleanly. “What makes our destination special?” does not, because it invites a subjective answer with no fact for a machine to lift.
TouristAttraction and TouristDestination: Building the Itinerary Layer
Two schema.org types exist specifically for this industry, and almost nobody uses them: TouristDestination for the region or city itself, and TouristAttraction for the individual sites within it, connected through the includesAttraction property. Recent analysis of the schema landscape puts it directly: “Almost no DMOs use these types, so the entity-understanding opportunity is wide open” (JSON Schema App, 2026).
Neither type triggers a visible rich result in Google. Their value is entity comprehension: they tell an AI system unambiguously that this page describes a specific place, this other page describes a specific attraction within it, and the two are connected. For a multi-day itinerary, TouristTrip nests individual TouristAttraction stops in sequence, giving an AI trip planner a structured path rather than a paragraph to parse (JSON Schema App, 2026).
Practically, that means a destination’s city or region overview page is the natural home for TouristDestination, with each attraction, park, or landmark page carrying its own TouristAttraction markup and a link back to the parent destination. Tour and itinerary pages layer TouristTrip on top, referencing the same attraction pages rather than duplicating their details.
Rebuilding destination or attraction pages to support this kind of schema architecture?
team builds page templates around the entity relationships schema requires, not just around layout.
Event Schema: Getting Festivals and Calendars Into Search and AI Answers
Event schema tells search engines that a page is about a specific, dated occurrence rather than an evergreen topic. Google’s guidelines are precise about scope: each event needs its own unique URL, must specify accurate start and end dates, and the event experience is built for pages focused on a single event rather than pages listing a full calendar of many events (Google Search Central). A multi-day event needs both start and end dates marked up; a festival with several distinct performances needs a separate Event element for each one.
This is another area where destination sites are leaving visibility on the table. Even large, well-known festivals frequently carry no Event schema at all on their own homepages, meaning the date, venue, and ticket information a traveler needs is present in the page’s design but invisible to the systems trying to answer “what’s happening in [destination] this weekend” (Tourism Tribe, 2026).
For a DMO managing dozens of annual events, the practical fix is a dedicated leaf page per event, tagged with Event schema, rather than relying on a single events calendar page to carry the load. The calendar page can still exist for human browsing; it is simply not the page doing the structured-data work.
Review and AggregateRating Schema: Building Trust Signals Correctly
Review and AggregateRating schema can add star ratings to a destination’s or attraction’s search listing, but Google restricts how it can be used. Since 2019, Google has not displayed review-rich results for LocalBusiness or Organization schema types when the entity being reviewed controls the reviews about itself, whether those reviews are collected directly on the entity’s own site or embedded through a third-party widget (Google Search Central). A DMO adding a “review our destination” form to its own homepage and marking up the results with Organization schema will not see stars in search results, regardless of how genuine those reviews are.
The workaround is not to fabricate a workaround. It is to apply Review and AggregateRating schema at the level where it is legitimate: on Product-type listings for a bookable tour, ticketed attraction, or specific experience, where first-party reviews of that specific product are permitted (JSON Schema App, 2026). A destination’s own Google Business Profile remains the correct channel for aggregate destination-level reputation; that data does not require, or benefit from, review schema on the website itself.
ItemList Schema for Attraction and Partner Directories
Destination websites are full of lists that never get marked up as lists: “Things to Do,” partner attraction directories, neighborhood or district guides, accommodation roundups. ItemList schema turns a rendered list into a machine-readable sequence, pairing naturally with the other types above; an ItemList of attractions can reference the same TouristAttraction-marked pages used elsewhere on the site, rather than duplicating their details in a new format.
This is a lower-priority type than FAQPage, TouristAttraction, or Event for most destination sites, but it closes a specific gap: without it, a “Top 10 Things to Do” page reads to an AI system as unstructured prose, the exact format industry guidance identifies as the hardest for AI systems to extract reliably compared to a formatted list or table.
Implementing Schema Without Creating New Problems
Two rules keep schema work from backfiring. First, only implement a schema type where the page can actually support its required and recommended properties with accurate, current data; a generic, sparsely filled schema block is worse than no markup at all, because it signals low confidence to the systems reading it. Second, validate everything before publishing. Google’s Rich Results Test and the Schema.org Validator both check syntax; neither one checks whether the content matches what is actually on the page, so that review stays a manual step (Google Search Central).
Treat schema as living data, not a one-time project. Attractions change hours, festivals get new dates, and partner listings turn over. Every time a page’s underlying facts change, its schema needs a corresponding update, or it starts feeding outdated information to exactly the systems it was built to inform.
Already have schema in place but not confident it’s complete or current?
service includes structured data review as part of ongoing site upkeep, so schema doesn’t quietly go stale between redesigns.
Frequently Asked Questions
Q: What schema type should a DMO use for its main destination page?
TouristDestination is the type built specifically for a region or city overview page. It connects to individual attraction pages through the includesAttraction property, giving AI systems a clear map of what the destination contains.
Q: Does FAQ schema still matter if Google removed the FAQ rich result?
Yes. The visual accordion in classic search results is gone as of May 7, 2026, but AI systems including AI Overviews, ChatGPT, and Perplexity still read FAQPage markup to identify citable question-and-answer content.
Q: Can a destination website use a review schema to show star ratings for the destination itself?
Not through Organization or LocalBusiness schema if the destination controls the reviews being marked up; Google classifies that as self-serving and will not display the stars. Review schema is legitimate on specific bookable products, like a ticketed attraction or tour.
Q: Does Event schema help with a full events calendar page?
Not directly. Google’s event guidelines are built around single-event pages with their own URLs. A calendar page listing many events should link out to individual event pages that each carry their own Event markup.
Q: How much schema is enough for a destination site to start seeing results?
Fewer, fully completed schema types outperform many partially filled ones. Start with TouristDestination and TouristAttraction on core pages, FAQPage on any page with genuine Q&A content, and Event schema on individual event pages, then expand from there.
References
- Tourism Tribe. (2026). Schema Markup for Tourism: What Google Knows About Your Business. https://www.tourismtribe.com/schema-markup-tourism-what-google-knows/
- Quattr. (2026). FAQ Schema in 2026: What’s Confirmed, What’s Not & What to Do. https://www.quattr.com/blog/faq-schema-in-2026
- JSON Schema App. (2026). Travel & Tourism Schema Markup for Google & AI Search. https://jsonschemaapp.com/travel-tourism-schema-markup/
- Google Search Central. (n.d.). Event (Event) Structured Data. https://developers.google.com/search/docs/appearance/structured-data/event
- Google Search Central. (n.d.). Review Snippet (Review, AggregateRating) Structured Data. https://developers.google.com/search/docs/appearance/structured-data/review-snippet
- Schema.org. (n.d.). TouristAttraction. https://schema.org/TouristAttraction
