A Guide To Adding Hotel Schema To Your Website (2026 Edition)

Hotel schema is structured data, written in JSON-LD using the Hotel type from schema.org (currently version 30.1, released September 16, 2026), that tells search engines and AI assistants exactly what your property is, where it is, what it offers, and what a stay costs. Done right, it models three objects: the LodgingBusiness (your hotel), the Accommodation (your rooms), and the Offer (your rates). It will not raise your rankings, Google says so plainly, and it will not get you into Google Hotels, which runs on Hotel Center feeds. What it does do is feed accurate, machine-readable facts to Google’s knowledge panel, Bing and Copilot, and the growing share of travelers (25% in 2026, up from 15% in 2025, per Deloitte) who plan trips with generative AI. This guide covers which types and properties to use, a complete example you can adapt, the review-markup mistake that gets hotels flagged, and how to validate everything before it goes live.

We first published this guide in September 2022. Back then, the pitch was simple: add schema, earn star ratings and rich snippets on the results page, out-shine the OTAs. Since then, Google has retired the FAQ rich result (though not, as we explain below, the case for FAQ markup), pruned a dozen other structured data types, and put AI Overviews and AI Mode on top of the results page. Schema.org added VacationRental, plus proper bed and occupancy properties for rooms. And the reason to bother has shifted from “win a rich snippet” to “make sure the machines describing your hotel get the facts right.” So we rebuilt the guide from scratch. Every section below reflects how things work in 2026, and where the 2022 advice no longer holds, we say so.

Here is the roadmap:

1. What hotel schema is (and what changed since 2022)
2. Why it still matters in the age of AI search
3. The three core objects: hotel, accommodation, offer
4. Which schema types and properties a hotel should use
5. A complete hotel JSON-LD example
6. Review markup: the trap most hotels fall into
7. What hotel schema will not do for you
8. How to add it to your site
9. How to test, monitor, and maintain it

1. What is hotel schema, and what changed since 2022?

What is structured data, in plain English?

Structured data is a block of code on your page that labels your content so a machine can read it without guessing. A human sees “Check-in from 3 PM” in a paragraph; a crawler sees "checkinTime": "15:00" and knows precisely what it means. The shared vocabulary for those labels is schema.org, a project backed by Google, Microsoft, Yahoo, and Yandex, and the recommended way to write it is JSON-LD, a small script block that lives in your page’s <head> or body and never touches what visitors see.

For a hotel, the relevant slice of that vocabulary starts at Hotel, which inherits from LodgingBusiness, which inherits from LocalBusiness, which inherits from both Organization and Place. That double parentage matters: it is why a single Hotel object can carry a phone number and a brand (organization things) and also coordinates and opening hours (place things).

What has changed in hotel schema since our 2022 guide?

Four things changed, and two of them undo advice we gave last time.

• The vocabulary got better for rooms: schema.org version 16.0 (May 2023) added bed and occupancy to Accommodation and introduced VacationRental as a subtype of LodgingBusiness. Version 28.0 (September 2024) added hasMemberProgram, which is the first clean way to describe a loyalty program.
• The FAQ rich result is gone, the markup is not: Google restricted the FAQ rich result to government and health sites in August 2023, then removed it from Search entirely on May 7, 2026. So the expandable Q&A under your listing is not coming back. But FAQPage markup on a real FAQ page still describes your content in exactly the question-and-answer shape that AI Overviews and People Also Ask draw from, and we still recommend it there. What we no longer recommend is a plugin stamping it on every page.
• Google pruned its rich results list: in June 2025 it announced it was phasing out seven structured data types (Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, Vehicle Listing), and the sitelinks search box went in late 2024. None were hotel features, but the signal is clear: Google only keeps rich results people use.
• The testing tools changed: the old Structured Data Testing Tool we linked in 2022 was shut down in August 2021 (yes, we were already behind). Today you use Google’s Rich Results Test and schema.org’s Schema Markup Validator, and they answer different questions. More on that in section 9.

The bigger shift is in the audience. In 2022, your markup was read by one crawler that decided whether to show a star rating. In 2026, it is read by Google’s knowledge graph, by Bing’s index (which feeds Copilot and other assistants that lean on Bing for web results), and by whatever assistant a traveler happens to ask “find me a pet-friendly hotel near the convention center under $250.” The facts you publish are the facts that get repeated.

2. Why does hotel schema still matter in the age of AI search?

Do AI search engines actually use schema markup?

Microsoft says yes, and Google says it is not required but does not hurt. At SMX Munich in March 2025, Bing’s Fabrice Canel confirmed that Microsoft’s LLMs use schema markup to help understand web content, which matters because Bing’s index is what Copilot answers from. Google’s own guidance on AI features is more restrained: “There’s also no special schema.org structured data that you need to add” to appear in AI Overviews or AI Mode, and structured data should simply “match the visible text on the page.” Read those two statements together and you get the practical position for 2026: schema is not a ticket into AI answers, but it is one of the cleanest ways to make sure the answer about your hotel is correct.

That accuracy problem is not hypothetical. An AI assistant summarizing your property is pulling from your site, your Google Business Profile, OTA listings, and review sites, and where they disagree, it picks one. Structured data on your own domain is the one source you fully control. If it says check-out is at 11:00 and pets are allowed, that is a strong, unambiguous vote.

How much has the results page changed for hotel searches?

A lot, and mostly in ways that reduce clicks. Pew Research Center found in July 2025 that users clicked a traditional result on just 8% of visits to pages with an AI summary, versus 15% without one (Google has disputed the methodology, so treat the exact numbers as directional). Ahrefs’ April 2025 study of 300,000 keywords found the presence of an AI Overview correlated with a 34.5% lower click-through rate for the top-ranking page. And according to Semrush data, the share of queries triggering an AI Overview went from 6.5% in January 2025 to nearly 25% in July before settling under 16% by November.

Meanwhile, travelers are moving upstream of the results page entirely. Deloitte’s 2026 summer travel survey found 25% of travelers now use generative AI to plan trips, up from 15% a year earlier, and 36% of millennials. Those travelers never see your title tag. They see whatever the model says about you, and if you want it saying “book direct,” the groundwork is in our hotel SEO strategy for AI search in 2026.

3. What are the three core objects of hotel schema?

How does schema.org model a hotel?

Schema.org’s own hotel documentation defines three core objects, and the whole discipline of hotel markup is keeping them straight:

• The lodging business: “essentially the place and local business that houses the actual units of the establishment.” That is your Hotel (or Resort, Motel, Hostel, BedAndBreakfast, VacationRental, or Campground). It carries the address, the star rating, check-in and check-out times, and property-wide amenities.
• The accommodation: “the actually relevant units of the establishment,” meaning hotel rooms, suites, apartments, meeting rooms, camping pitches. Each is an Accommodation subtype, most often HotelRoom or Suite, with its own beds, occupancy, floor size, and amenities.
• The offer: “an offer to let a hotel room … for a particular amount of money and for a given type of usage.” Price, currency, and availability live here, never on the hotel or the room itself. This is the rule people break most.

The relationship runs one way: the hotel containsPlace the rooms, and each room carries offers. Schema.org’s documentation shows rooms typed as both HotelRoom and Product ("@type": ["HotelRoom", "Product"]) so that an Offer can attach cleanly. If you remember nothing else from this guide: rates belong to offers. Phrasing, as ever, is everything.

4. Which schema types and properties should a hotel use?

Which type should my property be?

Use the most specific LodgingBusiness subtype that describes you, because a more specific type inherits everything from its parents and adds precision. A full-service property is a Hotel. A destination property with recreation is a Resort. Schema.org also defines Motel, Hostel (“cheap accommodation, often in shared dormitories”), BedAndBreakfast, Campground, and, since 2023, VacationRental, “a kind of lodging business that focuses on renting single properties for limited time.” If you run a boutique inn, Hotel is fine. Do not invent types; the validator will reject them, and the schema.org list is more complete than most people expect.

Which properties matter most on the hotel object?

Start with the properties Google’s LocalBusiness documentation requires (name and address) and recommends (geo, telephone, url, openingHoursSpecification, priceRange), then add the lodging-specific ones defined on LodgingBusiness. Here is the checklist we use:

Two notes on that table. First, starRating is the official classification (the one on the plaque by the door), not your Google review score; review scores go in aggregateRating, and section 6 explains why you should be careful there. Second, address and telephone must match your Google Business Profile character for character. Consistency across your site, your profile, and your OTA listings is what lets machines confidently merge them into one entity. If you are still deciding what belongs on the site itself, our list of hotel website features you can’t skip pairs well with this one.

Which properties matter on the room object?

Each HotelRoom or Suite should carry name, bed (a BedDetails object with typeOfBed and numberOfBeds), occupancy (a QuantitativeValue), floorSize, its own amenityFeature list, and image. Add numberOfBedrooms and numberOfBathroomsTotal for suites and apartments. Then attach an offers block with price, priceCurrency, and availability. Keep the offer honest: use your published from-rate, and update it when the rate changes. Markup that says $199 next to a page that says $249 is the kind of mismatch Google’s policies explicitly prohibit (“Don’t mark up content that is not visible to readers of the page”).

5. What does a complete hotel JSON-LD example look like?

Can I see the whole thing in one block?

Yes. The example below is written against the current schema.org vocabulary (run it through the validator in section 9 after you edit it); swap in your own details and drop it into the <head> of your homepage (and a trimmed version, with the relevant room only, on each room page).

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Hotel",
  "name": "The Harbor Line Hotel",
  "url": "https://www.harborlinehotel.example/",
  "image": "https://www.harborlinehotel.example/images/exterior.jpg",
  "telephone": "+1-312-555-0142",
  "priceRange": "$$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "410 N Harbor Drive",
    "addressLocality": "Chicago",
    "addressRegion": "IL",
    "postalCode": "60611",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 41.8916,
    "longitude": -87.6153
  },
  "starRating": {
    "@type": "Rating",
    "ratingValue": "4",
    "author": { "@type": "Organization", "name": "AAA" }
  },
  "checkinTime": "15:00",
  "checkoutTime": "11:00",
  "petsAllowed": true,
  "numberOfRooms": 212,
  "availableLanguage": ["en", "es"],
  "amenityFeature": [
    { "@type": "LocationFeatureSpecification", "name": "Free Wi-Fi", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "Indoor pool", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "EV charging", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "On-site parking", "value": true }
  ],
  "sameAs": [
    "https://www.instagram.com/harborlinehotel",
    "https://maps.google.com/?cid=1234567890"
  ],
  "containsPlace": [
    {
      "@type": ["HotelRoom", "Product"],
      "name": "Harbor View King",
      "image": "https://www.harborlinehotel.example/images/harbor-view-king.jpg",
      "bed": { "@type": "BedDetails", "typeOfBed": "King", "numberOfBeds": 1 },
      "occupancy": { "@type": "QuantitativeValue", "maxValue": 2 },
      "floorSize": { "@type": "QuantitativeValue", "value": 38, "unitCode": "MTK" },
      "amenityFeature": [
        { "@type": "LocationFeatureSpecification", "name": "Lake view", "value": true },
        { "@type": "LocationFeatureSpecification", "name": "Air conditioning", "value": true }
      ],
      "offers": {
        "@type": "Offer",
        "price": "249.00",
        "priceCurrency": "USD",
        "availability": "https://schema.org/InStock",
        "url": "https://www.harborlinehotel.example/rooms/harbor-view-king/"
      }
    }
  ]
}
</script>

A few things to notice. The star rating names the organization that awarded it, which is what separates a classification from a boast. Every amenity is a named LocationFeatureSpecification, not a free-text list, so a machine can filter on “EV charging” without parsing prose. The room is typed as both HotelRoom and Product, following schema.org’s own hotel examples, so the Offer attaches cleanly. And the price sits on the offer, where it belongs. If your property has a restaurant, spa, or event space, add them as nested Restaurant, HealthClub, or EventVenue objects under containsPlace as well; each is a real schema.org type with its own hours and phone.

6. How should hotels handle review schema?

Can I mark up my own guest reviews for star ratings in search?

No, not if you want a rich result, and doing it anyway can cost you. Google’s review snippet guidelines (updated September 2026) state: “If the entity that’s being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature.” A Hotel is a LocalBusiness. Your reviews about you, on your site, are self-serving by Google’s definition, whether you typed them into the JSON-LD yourself or a third-party widget injected them. The same rule applies to an aggregateRating built from your own guest surveys.

In 2022 we warned that misusing review markup could trigger a structured data penalty. That is still true, and the consequence is spelled out in Google’s policies: a structured data manual action “means that a page loses eligibility for appearance as a rich result.” So the honest play is this:

• Keep starRating: your official classification, with its author, is legitimate and useful.
• Skip self-hosted aggregateRating for rich results: you may include it as plain data if it is accurate and visible on the page, but do not expect stars in the SERP, and do not fake the scale.
• Let the review platforms do the reviewing: your Google Business Profile, TripAdvisor, and the OTAs will show ratings in their own surfaces. Link to them with sameAs so the entity is unmistakable.
• Never mark up reviews of things you don’t control: a “review” of the neighborhood or a nearby attraction is not a review of your business and just muddies the entity.

7. What will hotel schema not do for you?

Does schema markup improve rankings?

No. Google’s John Mueller put it flatly in April 2025: “Structured data won’t make your site rank better.” It is used for displaying search features, and using extra schema.org types beyond Google’s supported list “won’t cause problems, but you’re unlikely to see any visible change from it in Google Search.” We said something similar in 2022, and it remains the single most common misunderstanding we hear from hotel owners. Schema is a clarity investment, not a ranking lever.

Will hotel schema get me into Google Hotels or free booking links?

No, and this is the confusion we most want to clear up. The hotel results on Google Search and Maps, including free booking links and Hotel Ads, are fed by Google Hotel Center: a rate and availability feed, usually delivered through your booking engine or channel manager. Google even publishes its own proprietary lodging feed format, which is not schema.org markup, despite the shared word. On-page Hotel markup and a Hotel Center feed are two separate systems. You want both. They do not substitute for each other.

Is there a dedicated hotel rich result?

Not for hotels, no. Google’s structured data gallery (updated June 2026) lists a “Vacation rental” feature for individual rental properties, plus general features hotels can use: Local business (the knowledge panel), Organization (logo and legal details), Breadcrumb, Event, Video, and Image metadata. What you should not chase anymore: the FAQ rich result (gone since May 2026), HowTo (gone since 2023), and the sitelinks search box (gone since late 2024). Any plugin promising “FAQ rich snippets” is selling 2021.

Should a hotel still use FAQ schema?

Yes, on pages that are FAQs, and nowhere else. The rich result was the visible reward, but it was never the only use. A well-built FAQ page, with real guest questions (“Is parking included?”, “Can I check in early?”), direct one-paragraph answers, and matching FAQPage markup, gives search engines and AI assistants each question and answer as a clean, labeled pair. That is the shape AI Overviews, AI Mode, and the People Also Ask box are built to lift from, and in our experience it is one of the more dependable ways for a hotel to get cited for the practical questions guests actually ask. Google’s guidance is that no special markup is required for AI features, so treat this as clarity rather than a trick. The rule is the same as for everything else in this guide: mark up what is visibly there. A single FAQ page with twelve honest answers is an asset; FAQPage on a room page with two manufactured questions is spam, and it was spam in 2022 too.

The FAQ page is not the only place the format earns its keep. We also close long articles and detailed pages (a meetings and events page, a wedding package, a guide like this one) with a short Key Takeaways block written as questions and answers, and mark it up as FAQPage when the questions stand on their own. The test is simple: would a person skimming this page be glad the summary is there? If yes, it belongs, schema or no schema; a reader who scrolls to the bottom gets the answers, and an assistant gets the same answers in a labeled form. If the only reason to add it is the markup, leave it out. That is how the Key Takeaways at the end of this post came to be, and it is why they read as plain answers rather than a keyword list.

8. How do I add schema to my hotel website?

Which method should I use to implement it?

JSON-LD in a script tag, added through whichever layer of your stack you control. The right route depends on your setup:

• WordPress: most major SEO plugins (Yoast SEO, Rank Math, and dedicated tools like Schema Pro) can output LocalBusiness or Hotel markup from a settings screen. Check the generated code: many default to LocalBusiness and omit checkinTime, starRating, and rooms entirely. Use a custom JSON-LD block for anything the plugin cannot express.
• Hotel-specific CMS or booking engine templates: ask your vendor what schema they output and whether you can edit it. Many booking engines inject their own Hotel object; a second one from your CMS creates two conflicting entities on one page. One hotel object per page, please.
• Custom or headless sites: generate the JSON-LD from the same data source that renders the page (your property management or content system), so rates and amenities cannot drift out of sync with visible content.
• Google Tag Manager: works in a pinch, but Google has to execute JavaScript to see it, and it is easy to lose track of. Treat it as a stopgap, not a home.

Whichever route you take, mirror your Google Business Profile. Same name, same address format, same phone, same categories. Then link the two with sameAs. If your property is part of a group or a soft brand, add brand and parentOrganization so the chain relationship is explicit; for a single independent hotel, leave them out.

Where on the site does each object belong?

The full Hotel object belongs on the homepage. Room pages get a HotelRoom (or Suite) object with its offers, referencing the hotel with containedInPlace. Your restaurant page gets a Restaurant. Wedding and meetings pages can use EventVenue, and specific happenings (a New Year’s dinner, a jazz series) can use Event, which is still a live Google rich result. Blog posts get Article, and your FAQ page gets FAQPage. The pattern is one primary entity per page, described once, matching what a visitor reads. Structured data is also one of the quieter wins in voice search optimization, because an assistant answering “what time is check-out at the Harbor Line” prefers a labeled fact to a paragraph.

9. How do I test, monitor, and maintain hotel schema?

Which tool should I use to validate it?

Both of them, because they check different things. The Schema Markup Validator tells you whether your JSON-LD is syntactically valid against the full schema.org vocabulary, including hotel-only properties like checkinTime and bed that Google does not surface. Google’s Rich Results Test tells you only whether the page is eligible for a Google rich result, so it will happily ignore your room markup while flagging a missing address. Run the validator first for correctness, then the Rich Results Test for eligibility. Google’s old Structured Data Markup Helper still exists for point-and-click generation, but it has no idea what a hotel is, so we do not recommend starting there.

How do I know it is working after launch?

Watch the enhancement reports in Google Search Console. Google’s rich result reports show “structured data (and its validity) found on your site,” split into valid items, items with warnings, and critical errors, with a note that they show “a sample of detected items” rather than every one. Check them after any template change. Beyond Search Console, the honest test in 2026 is to ask: type your hotel’s name into Google’s AI Mode, Copilot, and ChatGPT with a question your guests ask (check-in time, parking, pet policy) and see whether the answer matches your markup. When it does not, your structured data is the fastest lever you own to correct it.

What maintenance does schema need?

Quarterly, at minimum. Rates change, amenities change, a pool closes for renovation, a restaurant gets a new name. Every one of those is a markup edit, and stale markup is worse than none because it actively misinforms. Put schema on the same checklist as your Google Business Profile updates, and re-run both validators whenever your web team ships a new template. If you already produce a steady stream of content, repurposing it across pages is a natural moment to check the markup on each one.

Final thoughts

In 2022, hotel schema was a tactic for winning a little more real estate on the results page. In 2026, it is closer to plumbing: the unglamorous layer that makes sure Google’s knowledge panel, Bing and Copilot, and every AI trip planner describe your property accurately, with your own URL attached. It will not lift your rankings, and it will not replace a Hotel Center feed. It will make you legible to machines at exactly the moment more travelers are letting machines do the shortlisting. Model the three objects, keep the rates on the offers, leave the self-serving stars alone, validate twice, and revisit it every quarter. Right? Right.

Want a hotel website that search engines and AI assistants both understand? Contact Phrasing to audit your existing markup or build it properly from the ground up.

Key Takeaways

What is hotel schema markup?

Hotel schema is JSON-LD structured data using schema.org’s Hotel type (a subtype of LodgingBusiness) that labels your property’s name, address, coordinates, check-in and check-out times, star rating, amenities, rooms, and rates so search engines and AI assistants can read them without guessing. Schema.org is currently at version 30.1 (September 2026), and the hotel vocabulary has been stable since bed, occupancy, and VacationRental were added in 2023.

Does hotel schema help with AI search?

Microsoft has confirmed that Bing and Copilot’s language models use schema markup to understand pages, while Google says no special structured data is required for AI Overviews or AI Mode. The practical value is accuracy: with 25% of travelers using generative AI to plan trips in 2026 (Deloitte), structured data on your own domain is the clearest signal you control about what your hotel offers.

What are the three core objects in hotel schema?

Schema.org models a hotel as a lodging business (the property), one or more accommodations (the rooms and suites), and offers (the rates). The hotel lists rooms with containsPlace, each room is typed as HotelRoom and Product, and price, currency, and availability live only on the Offer.

Can a hotel mark up its own reviews for star ratings?

Not for a rich result. Google’s review snippet guidelines make LocalBusiness and Organization pages ineligible for review stars when the business controls the reviews, and a manual action removes rich-result eligibility. Use starRating for your official classification and let Google Business Profile and review platforms display guest ratings.

Does hotel schema get a property into Google Hotels?

No. Google Hotels, free booking links, and Hotel Ads run on Google Hotel Center feeds delivered through a booking engine or channel manager, using Google’s own lodging feed format. On-page schema.org markup is a separate system, and a hotel should have both.