Hotel OTAs Content Capability Matrix: Booking vs Expedia vs Google

Sources: the three per-venue Labs in this cluster (Google, Booking.com, Expedia) plus the Booking Connectivity /tags API, Google Lodging Format Schema, Expedia Group Connectivity Hub, and cross-OTA practitioner guides. Last reviewed: 2026-04-24.

Key takeaways

The three biggest hotel OTAs hold different structured content models. Treating them as interchangeable destinations for the same content pack is the top source of listing-audit failure modes. Google is the loosest schema (owner description plus GBP amenities plus an optional Hotel Center feed for rooms and rates). Booking is the strictest (structured photo-tag taxonomy, auto-synthesized default description, 0 to 100 percent Property Page Score). Expedia is the most fan-out-heavy (one content change propagates to Expedia, Hotels.com, Orbitz, and ebookers).

Each platform scores the listing against a different input set. Booking discloses its score publicly in the Extranet. Expedia discloses the penalty curve (roughly 50 percent conversion loss on incomplete amenities) but not a single numeric score. Google gates whole features (room carousel, Prices tab) on whether the property has a Hotel Center feed at all. Same content, three different scoring functions, three different failure modes.

This article is the synthesis. Read the three per-venue deep-dives first if possible. The matrix below is the practitioner reference that maps each content dimension to each platform's structured handling. The fix path is per-platform, not universal. OTALift validators encode the per-platform rules so a single listing-audit report surfaces gaps scoped to the venue that penalizes them.

Why it moves bookings

Each OTA's ranking function takes a different input vector. Booking weighs 5 factors: availability, price competitiveness, conversion, reviews, and response time ¹. Expedia weights offer strength plus content completeness heavily, with VIP Access as the multiplier ². Google weighs Hotel Ads participation, feed health, GBP completeness, and reviews ³. The same underlying listing is scored by three incomparable functions. Optimizing for one can leave the others under-served.

Content gaps surface differently per platform. On Booking, gaps appear as a Property Page Score below 100 percent, with the missing fields named explicitly in the Extranet ⁴. On Expedia, they appear as the roughly 50 percent conversion rule-out for incomplete amenities ⁵. On Google, they appear as missing surfaces altogether: no room carousel without Hotel Center, no Prices tab without Hotel Ads bidding ⁶. The owner has to read each platform's diagnostic independently. There is no universal "health score" across the three.

Feed fan-out amplifies mistakes. A bad photo on Expedia is four bad surfaces (Expedia, Hotels.com, Orbitz, ebookers) ⁷. A bad owner description on Booking leaves the machine-composed default in place, often dull, never differentiated ⁸. A thin attribute set on Google produces a thin AI summary, regardless of description quality. The blast radius of a single bad edit is different per venue.

Commercial-visibility levers are venue-scoped. Booking Genius, Expedia VIP Access plus One Key, Google Hotel Ads: none of them transfer ⁴²³. A property that enrolls in Booking Genius gets Booking visibility. That does not translate to any Expedia or Google benefit. Practitioners who think in terms of "loyalty programs" as a single category miss that each OTA has its own.

Review ingestion models diverge. Booking and Expedia accept only verified-stay reviews. Google aggregates across sources (TripAdvisor imports, GBP reviews, other aggregators), which changes what review-response strategy makes sense per platform. A fast-response workflow tuned for Booking's 72-hour moderation window does not automatically address Google's TripAdvisor-imported reviews.

What "great" looks like

The matrix below is the practitioner reference. Each row is a content dimension. Each column is a platform's structured handling of that dimension.

Dimension	Google (GBP + Hotel Center)	Booking.com (Extranet)	Expedia Group (Partner Central)
Canonical schema	Lodging Format Schema (20+ domain blocks) 9	Property + Rooms + Facilities (+ /tags)	Property + Rooms + Amenities + Rate Plans
Property description	Owner-written on GBP; ML may override or blend 10	Auto-synthesized from facilities + location unless owner overrides 8	Owner-written surfaces verbatim more than either peer 11
Amenity taxonomy	GBP hotel amenities (casino, kids' club, housekeeping) + Lodging Schema domains 129	Structured facilities (property and room level) as direct Property Page Score input 4	Partner Central amenity set as direct conversion gate (roughly 50 percent rule-out on incomplete) 5
Room-level content	Room Bundles via Hotel Prices feed (Prices tab only); bed-placeholder fallback if no room photo 13	Structured room types with per-room galleries plus bathroom photo requirement 14	Structured room types with layouts, beds, and per-room photo coverage required 15
Photo minimums	Loose floor (250x250 min, 720x720 recommended) 16	10-photo minimum, 4 per room, 1 bathroom per room, 2048x1080 min, 4000x3000 recommended, landscape only 14	At least 20 property photos, 4 per room plus 1 bathroom, 1 per amenity, 1000 pixel reject floor, 2880 pixel recommended 15
Photo tag/slot system	No structured slot system; algorithmic best-photo selection 16	Structured tag taxonomy via /tags API (Shower, Toilet, Patio, Property building, etc.) 17	Photo category structure (room, bathroom, exterior, amenity); no per-tag granularity 15
Rate plan model	Rate plans via Hotel Prices feed (room type, rate plan, stay dates, taxes, cancellation) 18	Flexible, Non-Refundable, Genius, Mobile, Early Booker; differentiated cancellation per plan	OBP, derived, or standard plus Flexible, Non-Refundable, Package, Member Only Deal 19
Loyalty / visibility lever	Hotel Ads participation plus Free Booking Links gate 6	Genius program opt-in (percent discount for visibility plus badge)	VIP Access (invitation-only) plus One Key (up to 3 times OneKeyCash at VIP properties) 220
Ranking inputs	Hotel Ads bid plus feed health plus GBP completeness plus reviews (plus TrustYou topic breakdown) 3	Availability times price times conversion times reviews times response time 1	Offer strength plus content completeness plus reviews plus VIP Access score plus cancellation rate 2
Review ingestion	Mixed: GBP reviews plus TripAdvisor plus other aggregators; TrustYou provides topic breakdowns 3	Verified-stay only. 72-hour response moderation window. 2025 recalibration weights response time higher	Verified-stay only. Imports across Expedia, Hotels.com, Orbitz, and ebookers feed
Published scoreboard	No single score; per-surface signals 6	Property Page Score (0 to 100 percent; 100 percent is up to 18 percent more bookings) 4	No public score; VIP Access invitation is the binary gate 2
Feed fan-out	GBP to Google Hotels to Hotel Ads / Free Booking Links (one ecosystem, multiple surfaces)	Single surface (one Extranet, one property page)	One feed to Expedia, Hotels.com, Orbitz, and ebookers (4 surfaces) 7

Common failure modes

Treating the three OTAs as interchangeable content destinations. A content pack optimized for Booking's Property Page Score will not automatically hit Expedia's amenity bar or Google's feed completeness. The taxonomies diverge. What counts as "complete" on Booking is a subset of what counts as complete on Expedia, which is a different shape from what Google's Lodging Schema expects.

Optimizing for a universal photo set. 20 landscape JPEGs at 2880 pixels with descriptive filenames might hit all three minimums mechanically but miss Booking's per-tag requirements ¹⁷. An untagged photo on Booking does not land in its right-gallery slot. The same photo tagged as Property building on Booking is classified correctly; untagged, it sits in the generic pool.

Leaving auto-synthesized content in place. Booking auto-composes the default property description from facilities and location when the owner does not override ⁸. Google's ML may blend or override owner text ¹⁰. Only Expedia surfaces owner copy consistently verbatim ¹¹. A property that accepts the defaults is letting machines speak for the owner on two of three major platforms.

Missing platform-scoped commercial levers. Not enrolling in Booking Genius, not pursuing Expedia VIP Access readiness, not participating in Google Hotel Ads. Each is a per-platform visibility ceiling. Independent properties in particular often skip one or more, leaving meaningful visibility on the table.

Confusing content edits across PMSes and channel managers. Most channel managers push a shared content feed, but the OTAs render disparate subsets. A field that exists in the PMS but is not in Partner Central's structured amenity set is content no traveler will see on Expedia. The channel manager shows the field as populated; Expedia just ignores it.

Not tracking feed fan-out on Expedia specifically. One content change on Expedia is a change on 4 surfaces. Not spot-checking Hotels.com, Orbitz, or ebookers hides surface-specific rendering bugs ⁷. Hotels.com and Expedia use different brand templates; a photo that crops cleanly on one may clip a key element on the other.

Ignoring review-ingestion differences. A response strategy that works for verified-stay reviews on Booking and Expedia does not map one-to-one to Google, where TripAdvisor imports and unverified reviews coexist ³. The reply workflow, review moderation process, and escalation paths differ enough that most properties benefit from platform-specific runbooks.

Step-by-step fix

1. Read the three per-venue Labs first. Each platform's structured content model is documented in detail at google-hotels-as-a-venue, booking-com-as-a-venue, and expedia-as-a-venue. This matrix is the synthesis, not the primary reference. Running audits without the per-venue grounding misses nuance that affects prioritization.

2. Inventory what each OTA currently holds about the property. Partner Central (Expedia), the Extranet (Booking), and GBP plus Hotel Center (Google) each have an owner-facing UI showing exactly what is on the consumer side. Take screenshots. Export where possible. Make a baseline before fixing anything.

3. Run the capability matrix against the property data per platform. For each row and platform cell, mark it populated, partial, or missing. The matrix in the What "great" looks like section is the template. The exercise forces a per-platform perspective rather than a blended "our listing is 85 percent complete" narrative.

4. Prioritize by visibility impact per platform. Booking: Property Page Score gaps first because the score is published and moves impressions ⁴. Expedia: amenity completeness first because the 50 percent conversion penalty is the biggest single hit ⁵. Google: Hotel Ads or Hotel Center feed enrollment first because it gates the room carousel and Prices tab ⁶¹³.

5. Fix in descending-impact order. Do not batch-edit across platforms. The structured schemas diverge enough that per-platform passes are faster. Working through Booking to 100 percent Property Page Score, then Expedia to 90 percent amenity completeness, then Google to Hotel Center enrollment, produces measurable wins at each step.

6. Verify per-platform post-edit. Property Page Score for Booking (check weekly after major edits). Partner Central content-score indicators for Expedia. GBP plus Hotel Center feed health for Google (with a several-day review latency ¹⁰). Verification windows differ; plan accordingly.

7. Track per-platform regressions separately. The same content edit can pass Booking's tag check, fail Expedia's 1000 pixel floor, and vanish on Google's algorithmic best-photo selection. A unified dashboard obscures this. Per-platform regression trackers surface the actual failure modes.

8. Watch cross-OTA divergence for integrity signals. Photo-count mismatches, amenity-list mismatches, and room-type-count mismatches across platforms are often signals of feed-sync bugs upstream (channel manager, PMS connectivity). Divergence is diagnostic data, not just a cosmetic issue.

Soft recommendations

• Read the three venue-specific Labs before this matrix, not after. This article is a synthesis and assumes the per-venue detail has been absorbed. Practitioners who skip the deep-dives and come straight to the matrix tend to misapply the rules.

• Do not try to unify content editing across OTAs at the workflow level. The three canonical field sets are different enough that a master content doc approach loses fidelity against any single platform's scoring function. Per-platform source-of-truth UIs are the cost of doing business in multi-OTA distribution.

• If the property runs a channel manager, audit the subset of fields it actually pushes. Most push a narrower shape than any single OTA accepts. The OTA's extra fields (Booking's tags, Expedia's amenity micro-taxonomy) are often left empty by default because the channel manager does not surface them.

• Per-platform regression dashboards beat cross-platform ones. The failure modes do not rhyme. A weekly per-OTA check catches issues faster than a unified scorecard that blends signals.

• Feed fan-out on Expedia is the single highest-impact hidden-bug surface. A content change on Expedia is 4 downstream surfaces. Spot-check a randomly chosen Hotels.com or Orbitz page after each major edit. The cost of the check is five minutes; the cost of missing a cross-brand rendering bug is days of lost bookings.

Self-audit checklist

• I have a populated listing on each OTA I distribute through.
• I have read the three per-venue Labs (Google, Booking, Expedia) before running this matrix.
• I know each platform's canonical structured content set (not just the fields I edit in my PMS).
• I know which platform holds which commercial-visibility lever: Google Hotel Ads plus Free Booking Links, Booking Genius, Expedia VIP Access plus One Key.
• I have populated the matrix in the What "great" looks like section against my own data and can name the top 3 per-platform gaps.
• I have prioritized fixes by per-platform impact (not by shared-edit convenience).
• I track per-platform regressions separately, not via a unified score.
• I spot-check Expedia's 4-surface fan-out (Expedia, Hotels.com, Orbitz, ebookers) after major edits.

How OTALift surfaces this

OTALift's listing-audit report runs venue-scoped validators behind a unified UI. PhotoPresenceValidator enforces per-platform slot rules: Booking tag coverage via the /tags inventory, Expedia per-amenity coverage against the 2018 Photo Guidelines, Google feed-room-photo presence against the Room Bundles requirement. ContentFacilitiesValidator weights amenity completeness per platform's penalty curve, with Expedia heaviest at roughly 50 percent conversion rule-out. PlatformGapValidator flags cross-venue divergence (photo-count mismatches, amenity-list mismatches, room-type-count mismatches) as feed-sync integrity signals, not just cosmetic issues. HeroAlignmentValidator enforces each platform's hero-photo handling model: Booking's fixed hero, Expedia's primary, Google's algorithmic selection. The Ideal Listing maps these matrix rows to each platform's structured target so recommendations are per-platform actionable rather than blended into a single completeness percentage.

Related articles

• Google as a Hotel Listing Venue. The deep-dive on what Google holds.
• Booking.com as a Hotel Listing Venue. The deep-dive on Extranet plus Property Page Score.
• Expedia as a Hotel Listing Venue. The deep-dive on Partner Central plus VIP Access plus One Key.
• Photo Count Minimums by OTA and Room Type. Direct cross-platform photo spec comparison, complementary to the photo-minimums row of this matrix.
• Pillar: How OTA Ranking Algorithms Actually Work. Where the per-platform ranking inputs fit into the full model.

Sources and methodology

Footnotes

1. Booking.com for Partners, "Search results, ranking and visibility." https://partner.booking.com/en-gb/help/growing-your-business/analytics-reports/search-results-ranking-and-visibility ↩ ↩²

2. Expedia Group, "Join VIP Access Program for Top Hotel Properties." Invitation-only, scored program. https://partner.expediagroup.com/en-us/industries/hotels/vip-access-program ↩ ↩² ↩³ ↩⁴ ↩⁵

3. ROI300, "The Definitive Guide to Google Hotel Reviews and Local SEO 2026." TrustYou topic breakdown plus review-source mix. https://roi300.com/google-hotel-reviews/ ↩ ↩² ↩³ ↩⁴ ↩⁵

4. Booking.com for Partners, "Using the property page score to attract more guests." 0 to 100 percent score, up to 18 percent more bookings. https://partner.booking.com/en-gb/help/commercial-insights/keys-success/using-property-page-score-attract-more-guests ↩ ↩² ↩³ ↩⁴ ↩⁵

5. Expedia Group Blog, "Unlocking Success in Hotel Bookings." Roughly 50 percent of travelers rule out incomplete-amenity listings. https://partner.expediagroup.com/en-us/resources/blog/hotel-booking-success-guide-expedia-partner-central ↩ ↩² ↩³

6. Google Hotel Center Help, "About hotel free booking links." Free-booking-links gate. https://support.google.com/hotelprices/answer/10472393 ↩ ↩² ↩³ ↩⁴

7. Expedia Group, "Maximize Hotel Distribution and Revenue." Feed fans out to Expedia, Hotels.com, Orbitz, and ebookers. https://partner.expediagroup.com/en-us/industries/hotels ↩ ↩² ↩³

8. Booking.com for Partners, "Changing your property description or room details." Auto-synthesized default. https://partner.booking.com/en-us/help/property-page/general-info/changing-your-property-description-or-room-details ↩ ↩² ↩³

9. Google for Developers, "Google Lodging Format Schema." Canonical structured schema with 20+ domain blocks. https://developers.google.com/hotels/hotel-content/proto-reference/lodging-schema ↩ ↩²

10. Google Business Profile Help, "Manage your hotel's details." Hotel Details section plus several-day review latency. https://support.google.com/business/answer/9177958 ↩ ↩² ↩³

11. SiteMinder, "Expedia Partner Central: Complete guide for hotels." https://www.siteminder.com/r/expedia-partner-central/ ↩ ↩²

12. Google Business Profile Help, "Hotel amenities." https://support.google.com/business/answer/6215588 ↩

13. Google for Developers, "Room Bundles: Hotel Prices." Prices-tab-only room surface; bed-placeholder fallback. https://developers.google.com/hotels/hotel-prices/dev-guide/room-bundles ↩ ↩²

14. Booking.com for Partners, "Understanding photo requirements for your property." https://partner.booking.com/en-us/help/property-page/photos-extranet/understanding-photo-requirements-your-property ↩ ↩²

15. Expedia Group Photo Guidelines (2018 PDF). At least 20 photos, 4 per room, 1 bathroom, 1 per amenity, 1000 pixel reject floor, 2880 pixel recommended. https://mslps.expedia.com/images/en_EN_Flyer_EG%20Photo%20Guidelines%20_150818.pdf ↩ ↩² ↩³

16. Google Business Profile Help, "Manage your Business Profile photos and videos." https://support.google.com/business/answer/6103862 ↩ ↩²

17. Booking.com Connectivity, "Managing tags." Structured photo-tag taxonomy (/tags API). https://developers.booking.com/connectivity/docs/messaging-api/managing-tags ↩ ↩²

18. Google for Developers, "Integration Overview: Hotel Prices." Price feed schema. https://developers.google.com/hotels/hotel-prices/dev-guide/data-feeds ↩

19. Expedia Group Connectivity Hub, "Documentation: avail and rate APIs." OBP, derived, and standard rate-plan models. https://developers.expediagroup.com/supply/lodging/docs/avail_and_rate_apis/avail_rates/learn/ ↩

20. Expedia Group, "Unlock More with One Key Travel Rewards." Blue/Silver/Gold/Platinum tiers, up to 3 times OneKeyCash at VIP Access properties. https://partner.expediagroup.com/en-us/solutions/distribute-your-inventory/one-key-travel-rewards ↩