Schema Template Library
Starting points you can copy and paste for each type of page on your hotel website. Replace every with a real value before you publish.
New to this? Start with How to Build Hotel Schema (Hub & Spoke), which explains how the templates fit together. Come back to this page for the code once you know which template you need.
Note
Paste each block into Website → SEO → Extra Head Markup for the page it belongs to. Check the code in the Schema.org Validator before you publish.
- T1 — Homepage (Hotel — global schema)
- T2a — Rooms listing page (all room types on one page)
- T2b — Individual room page (one page per room type)
- T3 — Offers / Packages page
- T3b — Single offer / package page
- T4 — FAQ page
- T5 — Restaurant / Bar page
- T6 — Blog / Guides page
- T7 — Events page
- T8a — Apartment page (unit inside the hotel)
- T8b — ApartmentComplex hub (separate building)
- T9 — Contact page
- T10 — Nearby third-party facilities (parking)
- T11 — Meetings / Weddings venue page
- T12 — Spa / Wellness page
- T13 — Golf page
- Placeholder key
Shared frontmatter
All schema clipping files use this header:
---
title: ""
source: ""
author:
published:
created: 0
description: ""
tags:
- "clippings"
---
T1 — Homepage (Hotel — global schema)
Mode: Standalone. This block IS the hotel's master description. Add it in SEO → Extra Head Markup → Schema Item Types, and tick Disable Site Schema on the homepage. If you do not, the automatic Site Schema adds a second Hotel block, with a bare @id, beside it. (Leave Disable Site Schema unticked only if you are using the automatic block as the Hub instead of this markup.) See How to Build Hotel Schema (Hub & Spoke) for the site-wide method.
Notes:
@idmust end in/#hotelor/. Check the existing global block before you create a new one.parentOrganization: leave it out if the hotel has no parent group.amenityFeature: for the hotel as a whole only. Room amenities go onHotelRoomin T2.checkinTime/checkoutTimego here and ONLY here.
T2a — Rooms listing page (all room types on one page)
Use when: The site has one /rooms.htm or /accommodation.htm page that lists all room types together.
Disable Site Schema: ON. This removes the global Hotel block from this page.
Notes:
- Build from the Bookassist feed, not from the page HTML. Feed URL:
https://smart-01.bookassist.com/cms-tools/see-pricegroups/?hotel_id={ID}&guide_id={ID}&user_language=en- Leave out
validThroughif the feed's end date is3000-01-01.- Add another
ListItemblock for each extra room type.- For twin beds,
"bed"takes an array:[{"@type":"BedDetails","typeOfBed":"Single","numberOfBeds":2}].- Use
aboutto connect to the Hub, because this page is about the hotel's rooms.
T2b — Individual room page (one page per room type)
Use when: The site has a separate page for each room type (for example /double-room.htm, /suite.htm). Each page is about one room only, and its schema should say the same.
Disable Site Schema: ON. This removes the global Hotel block from this page.
Notes:
isPartOflinks this room to the Hotel Hub, because the room page is part of the hotel site.- Here
makesOffersits directly on theHotelRoom, not inside aCollectionPage. Use this when the page is about one room type.- For twin or multiple beds,
"bed"takes an array:[{"@type":"BedDetails","typeOfBed":"Single","numberOfBeds":2}].- Take the price and price group from the Bookassist feed, not from the page HTML.
- Leave out
validThroughif the feed's end date is3000-01-01.
T3 — Offers / Packages page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Notes:
- Remove all session and tracking tokens from booking URLs: no
bas=,cct=,_gl,_ga*.positionnumbers follow the order in which the offers appear on the page.
T3b — Single offer / package page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Use this for a page about one promotion (for example "Stay 3 Nights & Save 15%"). T3 is for a page that lists several offers. The main item is a single Offer, connected to the Hub with offeredBy.
Notes:
offeredBy→ Hub@idis the connection. Do not add a secondHotelblock.- Percentage-discount packages have no fixed price. Leave
priceout and keep onlypriceCurrency, or add"priceSpecification": {"@type":"PriceSpecification","minPrice":"","priceCurrency":"EUR"}using the lowest price in the feed for that price group. Never invent a price.- Promo and package price groups can have long IDs (for example
134217728). Be wary of a long ID on a standard room, but on a package the long ID is correct.- An offer with no end date needs no dates. Add
validFrom/validThroughonly if the promotion really runs for a fixed period.- Remove
bas=,cct=,_gl,_ga*from the booking URL.
T4 — FAQ page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Use this template only on a site with the T1 Hotel block. On a site that uses Site Schema, the FAQ 1.0 widget writes the FAQ schema itself and there is nothing to paste. FAQ 1.0 does that on every site, so this block on a page that uses it gives search engines the same questions twice. Accordion 1.0 writes no schema and is safe beside this block. Test the published page in the schema.org validator: it finds one FAQPage. If it finds two, remove this block or move the questions into Accordion 1.0.
Notes:
- Remove all HTML from the answer text. Write links as plain text (for example
call us on +353 91 569600).- Leave out questions that have no answer on the page.
- Text must match the page. The questions and answers in the JSON-LD must be exactly the ones the visitor can see on the page. Do not put answers in the code that are not shown on the page. Google will reject or ignore the schema.
- No promotional language in answers. Keep answers factual and direct. Google ignores FAQ schema that is used for sales copy (for example "We are the best hotel. Book now for 20% off!").
- Google no longer shows FAQ drop-downs. It removed them worldwide on 7 May 2026. The drop-down has gone from search results for all sites, and Google said FAQ reporting would leave Search Console and the Rich Results Test by August 2026. Keep
FAQPagemarkup so that machines can read your questions and answers. It tells search engines what the page is about, and AI answers (AI Overviews, ChatGPT, Claude) can use it. Do not use the Rich Results Test to preview drop-downs. Check the page in the schema.org validator, as for every other page type.
T5 — Restaurant / Bar page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Notes:
containedInPlacelinks the restaurant to the hotel's global@id.- For a bar that does not serve food, change
@typetoBarOrPuband leave outservesCuisine/menu.- Times use the 24-hour clock. A closing time after midnight (for example 02:00) is valid.
T6 — Blog / Guides page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Notes:
positionnumbers follow the order of the cards on the page.- Use the largest image from the
element'sdata-srcset(1200px wide if available).- Article URLs must be full addresses, starting with
https://.
T7 — Events page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Notes:
- Events that return every year (for example the Galway Races): create one
Eventper year with fixedstartDate/endDate. Do not use one undated event block.- Wedding and private-hire pages that do not advertise a specific event: leave out
Eventschema. ACollectionPage, or no schema, suits them better.
T8a — Apartment page (unit inside the hotel)
Use when: The apartments share the hotel's building, check-in desk and brand. Treat them as a type of room. The only difference from T2b is @type: "Apartment" in place of HotelRoom.
Disable Site Schema: ON, as on every sub-page.
Note:
ApartmentandHotelRoomare both kinds ofAccommodationin schema.org and accept the same properties. The different type tells search engines that the unit has several living spaces, not a single room. The Rich Results Test shows the same Vacation Rental errors as it does for HotelRoom. Ignore them.
Notes:
isPartOflinks this unit to the Hotel Hub, as in T2b.- Use
numberOfRoomsfor the number of bedrooms (for example2for a two-bedroom apartment). Do not usebedarrays, because an apartment has several rooms, each with its own beds.- Take the price and price group from the Bookassist feed, not from the page HTML.
- Leave out
validThroughif the feed's end date is3000-01-01.
T8b — ApartmentComplex hub (separate building)
Use when: The apartments are physically separate from the hotel, with a different address, entrance or operating brand. The apartments page becomes a Hub of its own, linked back to the Hotel with parentOrganization.
Disable Site Schema: ON, to remove the hotel's global block. This page is its own Hub, not a spoke of the hotel.
Notes:
@idis the apartments URL plus/#complex, which keeps it distinct from the Hotel Hub's/#hotel.parentOrganization→ Hotel Hub@idshows that the complex belongs to the hotel.- Do not include
makesOfferhere. Individual apartment pages use T8a and are spokes of this Hub. KeepingmakesOfferoff the Hub avoids Vacation Rental errors in the Rich Results Test.- If the complex has its own Bookassist
hotel_id/guide_id, use those inpotentialAction. If it shares the hotel's booking account, use the hotel's IDs.- Use the apartments' own address if it is different from the hotel's.
T9 — Contact page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
The main item is the contact page itself. Connect it to the Hub with about, and put the contact details on the referenced Hotel, so that they add to the hotel's existing description.
Notes:
- Do not use
LodgingBusinessor a secondHotelblock here. It creates a rival business entry that search engines cannot join to your Hub (see step 3 of How to Build Hotel Schema (Hub & Spoke)). The contact page is aContactPage. It refers to the hotel and does not describe it again.- Add a second
contactType(for examplereservations) only if that mailbox really exists.- Do not repeat the address or map coordinates. They are on the Hub.
T10 — Nearby third-party facilities (parking)
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Use this when a page describes facilities the hotel does not own, such as discounted parking at nearby car parks run by another company. List the actual facilities in an ItemList, on a WebPage connected to the Hub with about.
Notes:
- Do not present a facility as the hotel's own or as on-site, or say it is "beside the hotel", when it is another company's car park a few minutes away. Say that another company runs it and give the real walking distance.
- Do not attach an
Offerorpricefor a rate the hotel does not sell. Put the guest rate (for example "€12 per day with a reception validation pass") in thedescriptiontext only.- Parking that the hotel itself provides is already covered by
amenityFeatureon the Hub. A spoke is needed only to describe separate, outside options.
T11 — Meetings / Weddings venue page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Notes:
- There is no address here on purpose: the venue is inside the hotel, so the address comes from your homepage Hotel block. Keep
telephoneonly if your events team has its own number; otherwise delete that line.containedInPlacelinks the venue to the hotel's global@id. T5 uses the same connection for the restaurant.- This block describes the room or suite itself. Detail about one particular wedding or conference, such as its dates or its capacity, belongs on that event's own page, using T7.
- Leave out any private booking link for wedding guests or delegates, the kind you email to the organiser. Everything in this block is public, so a link placed here can be found by anyone.
T12 — Spa / Wellness page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Notes:
containedInPlacelinks the spa to the hotel's global@id.- Use the spa's own opening hours, not the hotel's. They are usually different. For a day the spa is closed, delete the whole block instead of leaving
00:00–00:00.- If an outside operator runs the spa under its own brand, keep
containedInPlacepointing at the hotel. This page describes the facility as a guest finds it on your site.
T13 — Golf page
Site Schema: set once for your whole site, not page by page. If you added the homepage Hotel block from T1 (the usual case), tick Disable Site Schema on this page too, as on every page. See How to Build Hotel Schema (Hub & Spoke).
Notes:
containedInPlacelinks the course to the hotel's global@id.- There is no schema.org property for hole count, par or course designer. Put those in
descriptionas readable text instead of inventing a field name.- Leave tee-time booking out of this block. A course that takes its own online bookings needs a separate
ReserveAction, and an invented one is worse than none.
Placeholder key
-
- Exact hotel name from the global schema, character for character
-
-
Hotel's base URL, no trailing slash (e.g.
https://www.example.ie) -
/#hotel -
The global
@id. Copy it exactly. The trailing slash and#hotelmust match -
-
Your site ID: the numeric folder name under
/files/ -
-
Phone in E.164 format:
+353XXXXXXXXX -
-
Your events team's own number, in E.164 format. T11 only. Delete the
telephoneline if there is none -
-
Two-letter country code:
IE,GB,ES, etc. -
-
ISO 4217:
EUR,GBP, etc. -
-
Numeric ID from the Bookassist price-group feed (
price_group=XXXX) -
- Lowest price in the feed (number only, no currency symbol)
-
-
validFrom: the feed's start date inYYYY-MM-DDformat -
-
$,$$,$$$, or$$$$ -
- Room size in square metres (number only)
-
-
Double,Single,Twin,King,Queen,Sofa -
- Maximum number of guests (integer)
-
-
24-hour time string, e.g.
14:00,23:30 -
0 - ISO date string
-
- Full apartment name as shown on the page
-
- Plain-text description (no HTML)
-
- Number of bedrooms in the apartment unit (integer)
-
- Name of the apartment complex
-
- Plain-text description of the complex
-
- Base URL of the apartment complex site or section, no trailing slash
-
-
Bookassist
hotel_idparameter -
-
Bookassist
guide_idparameter