Skip to content
DIRECT STAYSOLUTIONS
← The Direct Stay Journal

Vacation Rental Schema Markup: What to Add and How to Test It

By Direct Stay Solutions ·

The Direct Stay Journal · Booking technology

I’d start by opening one cabin page and checking whether the rental name, photos, and guest limit agree with the booking calendar. Schema markup is a way to give search engines labeled information about those same facts. It can help them read what’s on the page. Getting into Google’s dedicated vacation rental feature takes a separate integration.

Choose the markup for the page you’re looking at

Schema is structured information about a page. JSON-LD is one way to write it so tools can read fields like the cabin name, photos, and guest capacity. Start by opening the exact public URL and asking what the page is about.

PageWhat I’d describeWhat I’d check first
Single cabin pageThe specific rental and its accommodation detailsThe named cabin, guest limit, photos, and date button all refer to the same stay.
Owner advice articleArticle or BlogPostingThe headline, author, and publisher match the page.
Brand or collection pageThe actual business or collectionEach cabin has a distinct page guests can reach.

In the Norfork Lakefront Cabins case study, look for the difference between the three-cabin collection and Overlook Cabin’s own page. Overlook has its own booking path into Guesty. That’s the distinction I’d check before deciding which page describes an individual rental.

Check Google’s vacation rental eligibility before buying an add-on

Schema.org’s VacationRental type describes a rental. Google’s dedicated vacation rental feature has its own eligibility and integration requirements. Google’s implementation guide is written for sites working with a Google Technical Account Manager and with access to Hotel Center. If you’re interested in joining, start with the interest form linked in Google’s vacation rental documentation. Submitting it does not guarantee an invitation.

For an eligible implementation, check Google’s current requirements for the name, stable property ID, location coordinates, accommodation and occupancy, and listing photos. Google currently calls for at least eight photos, including a bedroom, bathroom, and common area. If you don’t have the integration, I’d spend my next hour on the cabin page and booking path before paying for a plugin that promises a travel listing.

Work through one cabin with the wrong details

Worked example: Heron Porch Cabin

Fictional example. Heron Porch sleeps four and has access to a shared pool. Its website page is right, but a copied listing record says six guests, shows a different cabin’s bedroom, and lists a private pool. The booking engine correctly stops at four guests. I’d first find which theme or plugin produces the wrong record, then fix the source.

  1. Open the cabin page beside the rendered markup. Compare the name, property ID, guest limit, photo URLs, and amenity details. Keep Heron Porch’s own stable ID when correcting the record.
  2. Set the occupancy to four, replace the other cabin’s photo, and remove the private-pool claim. Keep the shared-pool description visible on the page. If the theme and plugin both emit conflicting records for Heron Porch, choose one source to maintain those facts.
  3. Rerun the tests below on the public URL. On a phone, check that the date button opens the right cabin and that the booking engine still enforces the four-person limit.

If the records now agree and the site lacks Google’s travel integration, I’d close the data fix and leave the integration request as a separate decision.

Compare the wrong markup with the corrected version

These fictional examples show the fields we changed. The image URLs are placeholders. For a Google vacation rental integration, use the full list of required fields and qualifying photos in Google’s documentation.

Before

{
  "@context": "https://schema.org",
  "@type": "VacationRental",
  "name": "Heron Porch Cabin",
  "identifier": "heron-porch-01",
  "image": [
    "https://example.com/other-cabin/bedroom.jpg"
  ],
  "containsPlace": {
    "@type": "Accommodation",
    "occupancy": {
      "@type": "QuantitativeValue",
      "value": 6
    },
    "amenityFeature": {
      "@type": "LocationFeatureSpecification",
      "name": "Private pool",
      "value": true
    }
  }
}

After

{
  "@context": "https://schema.org",
  "@type": "VacationRental",
  "name": "Heron Porch Cabin",
  "identifier": "heron-porch-01",
  "image": [
    "https://example.com/heron-porch/bedroom.jpg"
  ],
  "containsPlace": {
    "@type": "Accommodation",
    "occupancy": {
      "@type": "QuantitativeValue",
      "value": 4
    },
    "amenityFeature": {
      "@type": "LocationFeatureSpecification",
      "name": "Shared pool access",
      "value": true
    }
  }
}
What the Schema Markup Validator returned for these samples
What to inspectBeforeAfterWhat I’d verify on the property
Errors and warnings0 errors, 0 warnings0 errors, 0 warningsBoth samples passed the vocabulary check. Compare the reported values with the actual stay.
Occupancy value64The booking engine should allow no more than four guests.
Bedroom imageOther cabinHeron PorchOpen the actual image URL and confirm it shows the right room.
Amenity namePrivate poolShared pool accessCheck who can use the pool and what guests read on the page.

To reproduce the vocabulary check, wrap either JSON sample in a <script type="application/ld+json"> tag with its closing tag, then paste it under Code snippet in the Schema Markup Validator. For your own rental, test the public URL afterward. Use Google’s Rich Results Test for supported feature checks and confirm travel eligibility separately.

Run the right test for the question you have

  1. Which records does the page contain? In the Schema Markup Validator, choose Fetch URL and paste the public cabin URL. Open each detected item and compare its type and values with the page. Look for two records that describe the same cabin differently.
  2. What does Google’s rich-result test detect? In the Rich Results Test, use the URL tab, enter the cabin URL, and select Test URL. If the relevant feature is detected, open the item and fix critical issues. A passing test is separate from enrollment and does not guarantee a special search appearance.
  3. Can Google reach the page you want indexed? In Search Console, open URL Inspection and paste the exact cabin URL. Check indexing and Google’s chosen canonical URL. Use Test live URL after a fix. If the wrong URL is favored, check your internal links and sitemap before requesting indexing. See the full Search Console walkthrough.

Keep the claims guests can verify

Use the cabin’s own photos and real operating facts. Leave out invented ratings, an amenity shared by another property, and claims your guests cannot verify on the page. Keep helpful questions on the page for guests and check Google’s search documentation updates before paying for a tool that advertises a particular search feature.

If people search for cabin for four with pool access, the property page should say who shares the pool and when it’s open. A search for things to do near Norfork Lake with kids belongs on a local guide. Link that guide to a suitable cabin when it helps readers pick where to stay.

Use article markup on an article

This fictional example uses JSON-LD to describe an advice article. Replace the sample headline, URL, author, and publisher with the real ones for that article. Use your business as the author if that’s who produced the piece.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Explain Shared Cabin Amenities",
  "url": "https://example.com/shared-amenities-guide/",
  "author": {"@type": "Organization", "name": "Example Rental Editorial Team"},
  "publisher": {"@type": "Organization", "name": "Example Rental"}
}

Retest when the property or website changes

Record the public URL, cabin ID, markup source, the facts you verified, and the date you last tested. Repeat the check after changing capacity, photos, the booking connection, or the theme or SEO plugin. Confirm your sitemap still lists the preferred public URL.

Search Console shows Google impressions and clicks. GA4 can show date-button taps if you’ve configured tracking. Your booking system confirms reservations. If the cabin page gets clicks for pool searches but few people check dates, I’d review the pool photos, the sharing details, and the mobile booking link. That gives you something you can test and improve.

Make the property page, markup, and booking link agree

Direct Stay can set up property pages and technical SEO, check what the theme and SEO plugin publish, and test that Check dates opens the correct cabin. If you already have a site, our Search Console walkthrough shows how to check the page Google sees.

Meet Dane, founder of Direct Stay Solutions

Dane Richardson, founder of Direct Stay Solutions

From my work in property management and on the Norfork cabin website, I’d check the cabin guests actually chose before changing anything. Send me the public property page, your booking link, and the markup result that has you puzzled. I’ll compare the name, occupancy, and photos across all three.