Our direct booking engine v2.19 completes a years-in-the-making vacation rental structured data roadmap and prepares for Google Hotel Center integration, covering where we are, what’s new, and what’s next.
When a guest searches Google for a three-bedroom beachfront house on Maui that sleeps six, something happens before any result appears: Google runs every candidate page through its understanding of what that page actually is, in machine terms.
Airbnb’s listing for that property looks like this to Google: a vacation rental, three bedrooms, beachfront access, maximum occupancy six, nightly rate from $420, eight photos labeled by room and view, coordinates confirmed. Bookable directly.
Your listing for the same property, the one at a better rate with a local team and a direct booking link, has been building toward the same level of machine-readable clarity since we introduced SEO metadata templating in version 1.5. Version 2.19 is where that build completes.
How We Got Here
Structured data in the TechSpokes booking engine has been part of the roadmap for years, built in stages.
Version 1.5 introduced SEO metadata templating: the framework that automatically generates titles, descriptions, and page-level signals from your property management software, without operators having to write or maintain them manually. That was the first layer of making booking engine pages legible to search engines at scale.
Version 2.11 added full VacationRental schema for individual property pages and brought SEO templating to PMS unit custom properties. Each listing started emitting a complete structured data profile: property type, coordinates, address, occupancy, bed configuration, amenities, live pricing, and images described as named objects rather than raw URLs. That is the layer that makes individual listings eligible for Google’s rich result formats.
What version 2.11 did not yet cover was everything above the individual property: resort pages, destination collections, search results, and platforms that aggregate inventory from multiple vacation rental companies. Version 2.19 closes that.
What Our Booking Engine v2.19 Adds
Version 2.19 expands structured data beyond individual listings so Google can understand your entire inventory (including resort pages, destination collections, and search results) as a set of real, bookable vacation rentals with normalized attributes and live pricing. The impact is clearer eligibility for rich results at both property and destination levels, more consistent visibility across multi-company inventory, and a cleaner path toward Google Hotel Center readiness.
Resorts and Collection Pages Schemas
Any page that groups multiple properties now emits structured data as an inventory. Resort pages, destination pages, area collections, search results: to Google, none of these are content pages with links anymore. They are declared collections of known vacation rental entities, and that changes how they surface for destination-level searches.
A page for “Kaanapali oceanfront condos” listing twelve properties now tells Google it is an inventory of twelve specific, confirmed vacation rental entities. A page without that declaration is an article that happens to mention some properties. Google treats them accordingly.
The Multi-Company Data Mapping Problem
Some TechSpokes clients run mini-OTA platforms: sites that bring together inventory from multiple independent vacation rental companies under one booking engine. Each company sends data in its own format, with its own category names, amenity labels, and property classifications. One calls it a “beach cottage.” Another calls it an “oceanside bungalow.” A third files it as “type 4B.” None of those map to the vocabulary Google uses, and none of them map to each other.
For a single-company site, this is a one-time configuration. For a multi-company platform, it is an ongoing normalization problem that grows with every new data source. Without a systematic solution, the schema outputs unrecognized terms that Google ignores, or becomes inconsistent across the site in ways you would not catch without auditing every page individually.
Version 2.19 ships the complete data mapping layer for this. Amenity terms, property types, bed labels, and category names from any source are resolved to Google’s accepted vocabulary before the schema is generated. Custom overrides are configurable per term. It is one of the harder problems in this space to solve at scale, and it is now solved.
What Full Vacation Rental Schema Describes
A complete VacationRental profile describes the property type (condominium, house, cabin, villa, and others mapped to Google’s recognized vocabulary), exact coordinates, full address, occupancy limit, bedroom and bathroom count, floor size in the correct unit for the country, and the bed configuration room by room. It includes the amenities Google recognizes, beach access, private pool, hot tub, washer and dryer, air conditioning, ocean view, pet-friendly, each declared as a confirmed feature rather than mentioned in passing in a description.
Pricing comes from live availability in your property management software: the actual minimum and maximum nightly rates across the full range of dates loaded in your calendar. If your calendar carries two years of availability, two years of data feed the schema. When a quote is active, the confirmed price is used. When the property is fully booked, it shows as sold out.
Images are included as fully described objects. Each photo carries a name and a caption: “Kaanapali condo, ocean view from lanai,” “Master bedroom with king bed and blackout shades,” “Heated private pool with direct beach access.” Google uses those to match the right image to a specific search. A family looking for a pool sees the pool photo in the snippet. Someone searching for ocean views sees the lanai shot. Without that context, Google guesses from pixel content alone.
What Changes in Search Results
In search results, properties with complete structured data are eligible for the richer formats: the card with the property photo, price range, property type, and star rating. Properties without it are plain links. Both appear on the same results page, and the difference in how guests engage with them is real.
For AI-powered search tools (Google AI Overviews, Bing Copilot, Perplexity, and others), a property page with confirmed, structured attributes retrieves more reliably for specific queries than one where the same details exist only as prose. Structured data does not train AI models on your properties and does not guarantee placement in any AI summary. What it does is make your pages more accurately represented in the search index those tools draw from. That matters as AI-powered search takes a larger share of how guests start the discovery process.
Keeping the Portfolio in Order
Knowing the schema is implemented is one thing. Knowing it is correct across a hundred properties is another, especially when PMS configurations change and new inventory arrives from sources with different naming conventions.
Every property in your list now shows a schema health status icon: blue for complete without any issues, orange for gaps worth addressing, red for issues that affect rich result eligibility, muted for properties not yet validated since their last update. Hovering the icon shows you what is missing directly in the list (we do value your time). Clicking it takes you straight to Google’s Rich Results Test for that property, where you can see the full schema, which elements Google recognizes, any recommendations, and any errors.
Validation runs automatically after each PMS sync. If a change affects the schema output, the status updates and flags it for review.
Google Hotel Center Is Next
Google Hotel Center is the integration that allows vacation rental properties to appear directly in Google’s travel surfaces: the accommodation panels that show live availability and pricing inline in search, the same surfaces where major OTAs and hotel chains currently appear. Getting there requires every property to already have a complete, validated, consistently normalized structured data profile. That is what v2.19 establishes.
We are in active preparation for that integration. Operators whose properties are properly mapped and validated today will be ready when it ships.
It Is Already on Your Site
No update to deploy. Version 2.19 is part of your direct booking website service and went live automatically.
To check your properties, hover any health status icon in your property list for a quick summary, or click it to open Google’s Rich Results Test directly for that property.