Reference
Hotel feed requirements comparison
See which fields are required or recommended across Google Hotel Center, Wego, trivago, Meta and Criteo, and distinguish published contracts from readiness checks.
Contract level
readiness
Meta Catalog Readiness
JSON / XML / CSV / TSV
Field matrix
● required · ○ recommended · — not defined in this rule pack
| Field | Google Hotel Center Hotel List | Wego Hotel Feed | trivago FastConnect Hotel Data | Meta Catalog Readiness | Criteo Catalog Feed |
|---|---|---|---|---|---|
id | ● | ● | ● | ● | ● |
name | ● | ● | ● | ○ | ○ |
address | ● | ● | ● | — | — |
postalCode | — | — | ● | — | — |
city | — | ● | ● | — | — |
province | — | — | ● | — | — |
country | ● | ● | ● | — | — |
phone_or_geo | ● | — | — | — | — |
latitude | — | ● | ● | — | — |
longitude | — | ● | ● | — | — |
category | — | — | ● | — | — |
starRating | — | — | ● | — | — |
link | — | — | — | ○ | ○ |
image | — | — | — | ○ | ○ |
description | — | — | — | ○ | ○ |
How to use this table
Canonical source feed
Build a reusable canonical hotel master-data model first, then apply platform-specific mappings.
Validation mode
A published-contract rule and a readiness heuristic do not carry the same evidence level. This page keeps them deliberately separate.
Agent / CLI usage
# MCP prompt
Compare the platform requirements for Google Hotel Center, Wego and trivago.
# CLI
npx @metasearch/feed-validator compare hotels.csv --targets google-hotel-center,wego,trivagoImportant
This reference does not replace platform onboarding or certification. Meta and Criteo rule packs are readiness/mapping checks. A new mandatory field is promoted to published-contract status only when public evidence exists.