Hotel Schema Markup: The Complete 2026 Guide

Only 10.6% of hotel websites achieve a “good” schema implementation — defined as scoring 50 or above out of 100 on completeness. The median hotel schema score is 0 out of 100. These are not estimates; they come from a study of 121,425 hotel homepages conducted by Hotelrank in 2026 (Hotelrank Hotel Schema.org Adoption Study 2026). That means roughly 9 in 10 hotel websites are invisible to the machine layer of modern search — and the gap is costing them visibility in both Google and AI-powered travel discovery.

TL;DR: Only 10.6% of hotel websites have schema markup good enough to qualify for Google rich results. Adding Hotel, FAQPage, AggregateRating, and Restaurant schema makes your property machine-readable for Google, ChatGPT, Gemini, and Perplexity. FAQPage schema increases AI citation probability by approximately 28% (Waymarker internal data, 2026). This guide gives you the exact JSON-LD to deploy — and the traps to avoid.

Why Does Schema Markup Matter for AI Search, Not Just Google?

Schema markup is no longer just an SEO tool. Google AI Overviews now reaches 1.5 billion users per month (Google, 2025), and AI systems like ChatGPT, Gemini, and Perplexity increasingly parse structured data to build their responses. The difference is meaningful: AI systems that find structured data can extract check-in times, price ranges, star ratings, and amenities directly. Unstructured content requires interpretation — and interpretation introduces errors.

When a traveller asks an AI assistant “What time is check-in at The Midland Hotel?”, the answer comes from wherever the AI can find it most reliably. If your website has a checkInTime field in properly formatted JSON-LD, that answer is yours. If it doesn’t, the AI either skips you or makes an educated guess from your page copy.

Schema markup functions as a direct communication channel to AI systems. Unstructured prose is processed probabilistically; structured data fields are processed deterministically. Hotels with complete schema are, in effect, speaking the AI’s native language.

There is an important distinction worth understanding, however. Research published by searchVIU in December 2025 found that when AI chatbots retrieve a web page in real-time during a query, they extract information from the visible HTML — not from JSON-LD structured data (searchVIU, December 2025). All five AI systems tested in the study behaved this way. This means your schema doesn’t directly feed a chatbot answering a query right now.

What it does instead is equally important: it matters at indexing time. When GPTBot, GoogleBot, and other AI crawlers visit your site, they read your JSON-LD and use it to build their understanding of your property. That indexed understanding shapes what they know about you when a traveller query comes in later. Think of schema as speaking to the AI’s memory, not its live reading.

This also matters outside pure AI: Google AI Overviews, featured snippets, and knowledge panels are the first results most travellers see. Schema is what earns your property a place in those surfaces — before anyone clicks through to your website at all. Rich results drive results: Nestlé found an 82% higher click-through rate for pages that appeared as rich results versus standard listings. Rotten Tomatoes saw a 25% CTR increase for pages with structured data (Google Search Central). The same mechanism applies to hotel listings.

→ See our FAQ on AI search and hotel visibility.

What Are the 6 Schema Types Every Hotel Website Needs?

Schema markup is one of the five dimensions Waymarker audits across every hotel group — and it is consistently the lowest-scoring dimension in initial audits (Waymarker internal data, 2026). Most hotels are missing four or five of the six types below. Each one addresses a different part of how AI and search systems understand your property.

1. Hotel / LodgingBusiness (The Core Schema)

The Hotel type (a subtype of LodgingBusiness in the schema.org hierarchy) is the foundation. Without it, nothing else works as well. Required fields include: name, address, geo (latitude/longitude), starRating, priceRange, amenityFeature, numberOfRooms, checkInTime, checkOutTime, telephone, and url.

amenityFeature deserves particular attention. This is an array of LocationFeatureSpecification objects — each one a named feature with a true/false value. Gym, parking, pool, pet-friendly, air conditioning: list them all. AI systems use these to answer specific traveller questions without needing to read your amenities page.

One clarification that matters: the Hotelrank study found that of hotels which do have JSON-LD structured data, 41.1% are using the wrong schema type — typically Organisation or LocalBusiness instead of Hotel or LodgingBusiness. These hotels have gone to the effort of adding schema but are not getting the hospitality-specific benefits. If your site already has JSON-LD, check what type it declares before assuming the job is done.

2. FAQPage (The Highest-Impact Addition)

FAQPage schema encodes your most common guest questions directly into the page. Our data shows FAQPage schema increases AI citation probability by approximately 28% (Waymarker internal data, 2026). The reason is structural: AI systems are optimised to return direct answers to conversational questions. An FAQ schema block is, effectively, a pre-formatted bank of direct answers.

Good FAQ questions to encode: parking availability and cost, pet policy, distance to nearest airport or station, cancellation policy, accessibility features, and dining hours. Write the answers as you’d give them to a guest — clear, specific, and complete.

3. AggregateRating (Your Review Score)

AggregateRating tells search and AI systems your aggregated review score, review count, and rating scale. Google pulls this into star ratings in search results. AI systems use it to assess whether your property is recommended.

A critical restriction applies here, and it catches many hotels out: if the reviews displayed on your page are ones you control or collected yourself, the markup is ineligible for Google rich results. Google’s policy is clear — AggregateRating schema is only valid for rich result eligibility when it is sourced from third-party review platforms such as TripAdvisor, Booking.com, or Google reviews. Using it to mark up ratings you’ve curated yourself will not earn you a star rating in search, and could be treated as spam (Google Search Central).

The correct approach: pull your aggregate score from TripAdvisor or Booking.com, reference the source in the schema, and update it quarterly. Include reviewCount, ratingValue, bestRating, and a link to the third-party source.

Despite this being a well-documented requirement, the Hotelrank study found that 87.5% of hotels with JSON-LD are missing AggregateRating entirely — meaning those properties have locked their review scores inside third-party platforms, invisible to their own website’s structured data.

4. FoodEstablishment / Restaurant (For F&B Outlets)

If your hotel has a restaurant, bar, or café, each should have its own Restaurant or FoodEstablishment schema block. This is where you encode cuisine type, opening hours, price range, and whether reservations are accepted. AI systems frequently answer “does [hotel name] have a good restaurant?” queries — and this schema is what gives them the data to answer accurately.

Nest these blocks within your main Hotel schema using the containsPlace property, or add them as separate blocks on the restaurant’s own page.

BreadcrumbList schema maps your site’s navigation hierarchy in machine-readable form. It tells search systems where a page sits within your website — home > hotels > london > the-bloomsbury. This isn’t glamorous, but it improves how Google and AI systems understand your site structure and helps disambiguate properties within a group that has multiple locations.

Every property page and key landing page on your site should include a BreadcrumbList block.

6. Event (For Programming and Offers)

Event schema marks up specific happenings at your property: seasonal packages, pop-up dining, wellness retreats, live music nights. It is the most underused of the six types. When a traveller asks an AI assistant “what’s on at [hotel] this summer?”, Event schema is how your answer gets surfaced. It also powers Google’s event rich results, which appear separately from standard search listings.

→ See a full schema audit in a sample report.

How Do You Check Your Current Schema?

Two tools give you an immediate read on what your site currently declares. Google’s Rich Results Test shows which rich result types your page qualifies for and flags any errors in your markup. The Schema Markup Validator (schema.org’s own tool) gives a more complete picture, including warnings on fields that are present but incomplete.

In our initial audits, the most common finding is not broken schema — it’s absent schema. Most hotel websites return zero structured data errors in the Rich Results Test because they have no Hotel schema to test at all. Passing with zero errors on an empty result is not a win.

Run both tools on your homepage, your property pages, and your restaurant pages separately. They test individual URLs, not whole sites. A property group with ten hotels needs to test each property page individually, because the schema should differ per property — different address, different amenities, different staff.

→ See a full schema audit in a sample report.

What Are the Most Common Hotel Schema Mistakes?

Using Incorrect Schema Types

The Hotelrank study found 41.1% of hotels that do have JSON-LD are using the wrong type — typically Organisation or LocalBusiness instead of Hotel or LodgingBusiness. Always use Hotel (or LodgingBusiness for non-hotel accommodation) as your primary type. It inherits all LocalBusiness fields and adds the hospitality-specific ones that AI systems specifically look for.

Marking Up Your Own Reviews as AggregateRating

This is the most consequential mistake hotels make with AggregateRating schema. If your website shows guest reviews you’ve collected directly — via a booking engine, a review widget, or your own collection form — marking those up with AggregateRating makes you ineligible for Google rich result star ratings. Google requires that aggregated ratings marked up for rich results come from third-party review platforms. Using the field on self-sourced reviews is treated as manipulative markup and can result in the rich result being suppressed entirely.

The fix is straightforward: use your TripAdvisor or Booking.com aggregate score, note the source, and update quarterly.

Leaving Out Negative Amenity Features

A common instinct is to only list amenities your property has. Don’t. List the ones you lack as well, with value: false. “On-site Parking: false” is genuinely useful to a traveller — and to an AI system trying to answer “does [hotel] have parking?” accurately. A missing field is ambiguous; an explicit false is informative.

Encoding Outdated Review Scores

AggregateRating data goes stale. A rating of 4.2 from 340 reviews that was accurate 18 months ago is now wrong if you’ve received 300 more reviews since. Set a calendar reminder to update your schema quarterly at minimum. The Hotelrank study found 87.5% of hotels with JSON-LD are missing aggregateRating entirely — so simply having it, kept current, puts you well ahead of the field.

One Schema Block for the Whole Group

Hotel groups sometimes put a single Hotel schema block on their homepage representing the entire group. This doesn’t work. Each property needs its own schema block on its own page, with its specific address, coordinates, room count, and amenities. Group-level schema on the homepage should use Organization type, not Hotel.

Missing or Thin FAQPage Content

FAQPage schema with two or three questions is better than nothing, but it’s not enough. Aim for eight to twelve questions per property page, covering: check-in/out times, parking, transport, pets, accessibility, cancellation, dining, and any property-specific frequently asked questions. These questions map directly to what travellers ask AI assistants.

In Waymarker’s initial audits, the average hotel property page contains 1.4 schema types. The target for a well-optimised property page is 4-5 types. The gap between median and target is larger for hotel groups than for any other hospitality category we’ve assessed.

Frequently Asked Questions

Does hotel schema markup directly affect Google rankings?

Schema markup is not a direct ranking signal, but it strongly influences how your property appears in search results. Rich results — including star ratings, FAQ dropdowns, and event listings — come directly from structured data. Hotels with complete schema appear more prominently and earn higher click-through rates: Nestlé found an 82% higher CTR for rich results versus standard listings, and Rotten Tomatoes reported 25% higher CTR for pages with structured data (Google Search Central). Higher CTR feeds back into ranking signals over time.

How often should I update my Hotel schema?

Update your AggregateRating data quarterly, or whenever your review count changes significantly. Core hotel data — address, amenities, room count — should be updated immediately whenever it changes. FAQPage content should be reviewed every six months to ensure the answers are still accurate and the questions still reflect what guests ask.

Can I add schema markup without a developer?

For most hotel websites, yes. If your site runs on WordPress, plugins such as Rank Math or Yoast SEO provide schema editors that don’t require code. For custom-built sites, you’ll need to add the <script type="application/ld+json"> block to your page templates. The JSON-LD format is self-contained and doesn’t change your visible page content at all.

→ Waymarker provides ready-to-deploy JSON-LD as part of every audit.

What is the difference between JSON-LD, Microdata, and RDFa?

All three are valid ways to add schema markup, but JSON-LD is the recommended format. Google prefers it, it’s easier to maintain, and it sits in your page <head> rather than being mixed into your HTML markup. Microdata and RDFa embed attributes directly in your HTML elements — technically equivalent, but harder to manage and audit. If you’re starting from scratch, use JSON-LD.

Does schema markup help with ChatGPT and Perplexity, or only Google?

It’s more nuanced than a simple yes. Research by searchVIU in December 2025 found that AI chatbots retrieve visible HTML content when reading a page in real-time, not the JSON-LD (searchVIU, December 2025). However, when AI crawlers such as GPTBot index your site between queries, they do read structured data — and that indexed understanding shapes what AI systems know about your property when queries come in. Schema matters for AI discoverability, but through the indexing layer rather than direct retrieval.

→ See our FAQ on how AI platforms find and cite hotels.

Where to Start

Schema markup is one of the highest-impact improvements most hotel websites can make. The order of priority is clear: Hotel schema on every property page first, FAQPage next (highest direct impact on AI citation rates), then AggregateRating sourced from TripAdvisor or Booking.com, Restaurant schema if applicable, BreadcrumbList, and Event schema progressively.

The data picture is stark: 36.3% of hotel websites have zero structured data of any kind. Of those that do have JSON-LD, 41.1% are using the wrong schema type. Only 10.6% score well enough to qualify for rich results. If your hotel group is in the 89.4% majority, there is an immediate, concrete opportunity here that your competitors likely haven’t taken yet.

The challenge in practice isn’t understanding the schema types. It’s implementing them accurately across every property — with the correct amenity lists, up-to-date review scores, property-specific FAQ content, and the right type declarations. Schema with errors or incomplete fields performs worse than no schema in some cases. And for a hotel group with ten or twenty properties, the volume of detail work adds up quickly.

Schema markup is one of the five dimensions we assess in every Waymarker audit. It is consistently the lowest-scoring dimension in first audits — and almost always the quickest to improve. Every audit we produce includes ready-to-deploy JSON-LD specific to each property, built from your actual data, tested against Google’s Rich Results Test before we deliver it.

→ See what a full schema audit looks like.

If you’d like to know exactly where your hotel group stands across all five dimensions — schema, content depth, digital footprint, review health, and AI mention rates — the details are on our pricing page.