According to Google’s vacation rental documentation, the required properties for VacationRental include the accommodation, maximum occupancy and its numeric value, a unique identifier, images, latitude and longitude, and a name. Recommended properties include the address, rental type, ratings, brand, accommodation type, and amenities. Required properties establish eligibility for display, while recommended properties provide additional information. However, optional fields can have requirements of their own: “recommended” does not mean that any format or content is acceptable.
Required properties: start with accommodation and identification details
Use VacationRental as the main markup type and include the following information:
- containsPlace: Use Accommodation to describe a single accommodation, including details such as beds, occupancy, rooms, and amenities.
- containsPlace.occupancy: Use QuantitativeValue to describe the maximum number of guests allowed. Its value must give the guest count as an integer.
- identifier: The property’s unique identifier.
- image, latitude, longitude, name: Provide images, latitude, longitude, and the vacation rental’s name, respectively. Coordinates can also be specified using geo.latitude and geo.longitude.
For a property that accommodates up to five guests, for example, occupancy.value should be 5, not the number of guests on a particular booking. In addition to providing the required fields, you must follow the vacation rental policies, Search Essentials, and general structured data guidelines.
Images, coordinates, and identifiers have specific requirements
One image is not enough: the documentation requires at least eight photos, including at least one each of the bedroom, bathroom, and common area. Images must also meet the listing image requirements. Both longitude and latitude must be precise to at least five decimal places.
The identifier must be independent of the listing’s content and should not change when details such as the name or number of rooms are updated. Different language versions of the same listing must also use the same identifier.
Recommended properties: add the address, accommodation type, and other details
Use address to provide the full physical address, including the street, city, state, province or region, postal code, and unit number where applicable. A post office box cannot replace a physical address, and the country code must use ISO 3166-1 alpha-2.
additionalType can specify the rental type, such as Apartment or Villa, while containsPlace.additionalType distinguishes between EntirePlace, PrivateRoom, and SharedRoom. Other details you can add include the brand, aggregate rating, beds, floor area, number of bedrooms, and amenities.
According to the general guidelines, fewer recommended properties with complete, accurate information are better than more properties containing errors.
Optional information must still meet formatting and regional requirements
- Floor area: containsPlace.floorSize must include unitCode. Use MTK or SQM for square meters, and FTK or SQFT for square feet.
- Amenities: Names of Boolean amenities must be in English. Both the names and values of non-Boolean amenities must also be in English, even if the vacation rental information is in another language.
- Reviews: When you include review, you must provide review.datePublished. Vacation rental listings in France must also provide review.contentReferenceTime, indicating the date the reviewer’s stay began.
Reviews and aggregate ratings must also comply with the review snippet guidelines and their respective Review and AggregateRating property requirements. A date or score alone is not enough.
Vacation rental structured data: perspectives from across the web
Is it always better to include more recommended properties?
Not necessarily. Complete, accurate information matters more than the number of properties. Google's general structured data guidelines state that adding recommended properties can generally improve the chances of appearing with enhanced display features. However, fewer properties with complete, accurate information are better than extensive data containing errors. Do not add incomplete or inaccurate information just to increase the count; adding recommended properties does not guarantee display.
How can internet, parking, and pool types be marked up?
You can use non-Boolean values in amenityFeature, describing the types with internetType, parkingType, or poolType, respectively. For example, suggested values for internet and parking include Free, Paid, and None; pool types include Indoor, Outdoor, and None. The names and values of these amenities must be in English, even if the vacation rental information is in another language.
Are there alternative ways to mark up pet, smoking, and bathroom information?
To indicate whether pets and indoor smoking are allowed, you can use containsPlace.petsAllowed and containsPlace.smokingAllowed, respectively, instead of the corresponding amenity fields. If you provide the total number of bathrooms, use a simple sum, counting a half bathroom as 0.5. For example, two full bathrooms plus one half bathroom total 2.5.
How should license numbers and languages spoken by the host be added?
Some regions require the property's license number to be displayed; this can be provided using licenseNum. If there are multiple licenses, you can add this property multiple times, and including the issuing authority is recommended for context. If you provide the languages the host speaks, knowsLanguage should use IETF BCP 47 language codes, such as en-US or fr-FR.
References
- 度假民宿結構定義標記 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How can internet, parking, and pool types be marked up?; Are there alternative ways to mark up pet, smoking, and bathroom information?
- 結構化資料標記的運作方式簡介 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Is it always better to include more recommended properties?

