Free Hotel Schema Generatorschema.org/Hotel JSON-LD in 30 seconds

Fill out the form, copy the JSON-LD, paste it into your<head>. Output is clean — no [TODO] placeholders, no leaky defaults. Runs entirely in your browser; nothing is sent to a server.

Identity

Sub-type *

Hotel name *

Alternate name (optional)

Description (150–300 chars works best)

Location & contact

Hotel website URL *

Primary language

Country *

Street address

City

Postal code

Latitude

Longitude

Google Maps URL (hasMap)

Telephone (E.164 ideally)

Categorization

Star rating (1–5)

Price range (e.g. $$, $$$$) — leave blank if unsure

Number of rooms

Pets allowed

Check-in time (HH:MM)

Check-out time (HH:MM)

Currency accepted

Payment methods

Images

One https:// URL per line. The first one is treated as primary.

Amenities

Core

Wellness

Access & parking

Extras

Click an amenity to cycle through Skip → Yes → No → Skip. Amenities marked “Skip” are omitted from the output entirely — no placeholders.

`sameAs` — cross-references

Where else this hotel is listed. Google Maps + at least one OTA is the highest-leverage combination — that’s where AI assistants converge.

Add these — every AI assistant cross-references them:

Aggregate rating (opt-in)

Only enable if you display first-party reviews on the page. Aggregating third-party scores (TripAdvisor, Booking.com) can trigger Google manual actions. If unsure, leave this off.

Rooms (HotelRoom schemas)

One entry per room category.

Restaurant

One Restaurant schema for the on-site restaurant.

Spa / Wellness (HealthAndBeautyBusiness)

One schema for the spa, with treatments listed.

Treatments

Events / Meetings (EventVenue)

Event spaces and packages.

Packages

FAQ Page

Question/answer pairs visible on the page.

Schema completeness

0/7 required · 1/16 recommended

Score reflects schema.org/Hotel completeness, not content quality.

Missing required

name
description
address
telephone
url
image
geo

Missing recommended (boosts AI visibility)

@id
starRating
email
aggregateRating
priceRange
checkinTime
checkoutTime
numberOfRooms
petsAllowed
sameAs
hasMap
review
currenciesAccepted
paymentAccepted
alternateName

sameAs — Add a Google Maps URL and at least one OTA listing (Booking.com / TripAdvisor) — that is where the AI cross-references converge.

JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Hotel",
      "@id": "/#hotel",
      "name": "",
      "url": "",
      "amenityFeature": [
        {
          "@type": "LocationFeatureSpecification",
          "name": "Free Wi-Fi",
          "value": true
        }
      ]
    },
    {
      "@type": "WebSite",
      "@id": "/#website",
      "url": "/",
      "name": "",
      "publisher": {
        "@id": "/#hotel"
      },
      "inLanguage": "en"
    }
  ]
}
</script>

What is hotel schema and why AI search needs it

Schema.org is a vocabulary for describing things on the web in a way machines can parse. For hotels, the relevant types areHotel,HotelRoom,Restaurant,HealthAndBeautyBusiness (for spas),EventVenue, andFAQPage. The standard way to publish them is JSON-LD — a single<script type="application/ld+json">block per page.

Why it matters for AI search

AI assistants don’t read your beautiful homepage hero. They parse the structured data and cross-reference it against Google Maps, OTAs, and review sites. From our research:

ChatGPT pulls from 5+ providers and uses entity linking to reconcile names — structured identity makes you reconcilable.
Claude almost always calls Google Places and reads reviews verbatim. Your Google Maps presence + on-site schema agree → higher trust.
36.3% of 121,425 hotels we scanned have no schema at all, and 41% use the wrong type. Most hotels are invisible to AI for this reason alone.

What this generator gets right

Most schema generators emit"value": "[TODO]"placeholders inside the JSON, hoping someone fills them in later. They never do. We omit properties without input entirely — the output is paste-and-deploy clean. Other things we got right per our study of 121K hotel sites:

One @graph per page, not 17 separate <script> tags.
Stable @id URIs ({baseUrl}/#hotel) so cross-page schemas reference the same entity.
paymentAccepted as an array, not a comma-joined string. addressCountry required, no defaults.aggregateRating opt-in, with the first-party-reviews-only caveat.
sameAs populated with the OTA and Google Maps URLs that AI assistants actually cross-reference.

What it does NOT do

It does not audit your existing schema (paid version coming).
It does not crawl your site or generate per-URL graphs (paid version coming).
It does not validate the output against Google’s rich-results constraints — use the Google Rich Results Test to verify before deploying.

Want the deeper version?

For a multi-page audit of an existing hotel website (crawls all pages, checks AI-bot access, generates per-URL recommendations), we’re prepping a paid version. Get in touch if you want it run on a portfolio.