Schema markup for small properties: what it does, and what it won't

Your website is written for guests. Schema markup is a second copy of the key facts, written for software. It sits in the page code, invisible to guests, and says things like “this is a vacation rental, at this address, with five units, check-in at 3pm, no pets.”

Search engines and AI tools can work these facts out from your regular text. Schema just removes the guesswork.

A lot of what gets promised about schema doesn't apply to small properties. Two things in particular:

• No review stars from your own reviews. Google won't show star ratings for reviews a business controls about itself. Adding your rating to schema doesn't change that.
• No vacation rental rich results on your own. Google's vacation rental listings in search come from sites connected through its Hotel Center program, usually large booking platforms and channel partners.

If someone sells you schema as a shortcut to stars or special search boxes, ask them to show you where Google says so.

• Tells Google exactly what kind of business you are, so you show up for the right searches.
• Gives AI tools clean facts to work with when a guest asks for a place like yours.
• Connects your website to your listings and profiles, so search engines know they're all the same property.
• Spells out each room separately, so a question like "a quiet room with a patio" can match the right one.

It works alongside an llms.txt file and clear, consistent page text. None of the three does much alone.

Here's a trimmed-down version of what's on comalinn.com. The whole property is described once, with each of the five units listed inside it.

{
  "@context": "https://schema.org",
  "@type": "VacationRental",
  "name": "Comal Inn",
  "numberOfRooms": 5,
  "address": { "streetAddress": "424 Comal Ave", "addressLocality": "New Braunfels", ... },
  "checkinTime": "15:00",
  "checkoutTime": "11:00",
  "petsAllowed": false,
  "amenityFeature": [
    { "name": "Private Entrance", "value": true },
    { "name": "Self Check-In", "value": true },
    ...
  ],
  "sameAs": [ "Booking.com listing", "Expedia listing", "Tripadvisor", "Google Maps", ... ],
  "containsPlace": [
    { "@type": "Accommodation", "name": "The Juniper", "occupancy": ..., "bed": ... },
    ...
  ]
}

• One VacationRental block for the property, with address, check-in times, policies and amenities.
• Each unit listed inside it as an Accommodation, with its own occupancy and bed details.
• Links to our OTA listings, Tripadvisor and Google Maps, so all of them point back to one property.
• A breadcrumb trail on each room and cottage page, so the site structure is clear.

1. 01Duplicate blocks.Our own site had the same property described twice, once in the site layout and again on the homepage. Google has to guess which one is right. Pick one.
2. 02Facts that don't match the page.We listed "no cleaning fee" for the whole property, but it applies to four units, not the Cottage. Schema should say exactly what the page and your listings say.
3. 03Set it and forget it.Rates, policies and amenities change. Your schema needs to change with them.