Google 住宿数据传输
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
概览
Google 会在 Google 搜索和 Google 地图上显示酒店属性数据。您可以使用 Google 住宿格式将这些数据发送给 Google。
如需向 Google 发送住宿数据，您可以在酒店列表 Feed 中嵌入数据（首选方法），也可以设置专用文件传输。以下部分介绍了各个选项。
在酒店列表 Feed 中嵌入数据
如果您已有酒店列表 Feed，则可以将住宿数据添加到 <client_attr name="lodging"> 下的 <attributes> 部分中。此属性的值是商家信息中经过编码的 Lodging proto 的 Base64 编码字符串。使用此方法时，Lodging.place_id 字段应是 Feed 中特定商家信息条目的酒店 ID。
其他参考资料
详情请参阅以下内容：
设置专用文件传输
如果您无法直接在商家信息条目中包含住宿数据，则可以设置单独的托管文件传输。Lodging proto 数据可以设置为 textproto 或 JSON。此设置与酒店商家信息 Feed 的设置非常相似。如需有关此设置的帮助，请与您的技术支持客户经理 (TAM) 联系。
保留所有权利。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eGoogle uses the Google Lodging Format to display hotel attribute data in Search and Maps.\u003c/p\u003e\n"],["\u003cp\u003eHotels can send their data to Google by embedding it within their hotel list feed or by using a dedicated file transfer.\u003c/p\u003e\n"],["\u003cp\u003eEmbedding data involves placing Base64-encoded Lodging proto within the \u003ccode\u003e<attributes>\u003c/code\u003e section of the hotel list feed, using Hotel ID for \u003ccode\u003eLodging.place_id\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDedicated file transfer is an alternative for hotels unable to embed data directly, requiring separate hosting similar to the hotel listing feed process and TAM assistance.\u003c/p\u003e\n"]]],[],null,["# Google Lodging Data Transfer\n\nOverview\n--------\n\nGoogle shows your hotel attribute data across Search and Maps. You can send\nthis data to Google with the [Google Lodging Format](/hotels/hotel-content/proto-reference/lodging-schema).\n\nTo send Google your lodging data, you can either embed the data in your hotel\nlist feed (preferred method) or set up a dedicated file transfer. The\nfollowing sections cover each option.\n\nEmbed data in your hotel list feed\n----------------------------------\n\nIf you have an existing [hotel list feed](/hotels/hotel-prices/xml-reference/hotel-list-feed),\nyou can include the lodging data in the `\u003cattributes\u003e` section under the\n`\u003cclient_attr name=\"lodging\"\u003e`. The value for this attribute is the\nBase64-encoded string of the encoded `Lodging` proto for the listing. Using\nthis method, the `Lodging.place_id` field should be the Hotel ID of the\nspecific listing entry in your feed.\n\n### Additional references\n\nFor more information, see the following:\n\n- [Hotel list feed attributes](/hotels/hotel-prices/xml-reference/hotel-list-feed#attribute-names)\n\n- [Encoding a proto](/protocol-buffers/docs/encoding)\n\nSet up a dedicated file transfer\n--------------------------------\n\nIf you aren't able to include the lodging data directly in the listing entry,\nyou can set up a separate hosted file transfer. The `Lodging` proto data can be\nformatted as a textproto or JSON. The setup is very similar to that of the\n[hotel listing feed](/hotels/hotel-prices/dev-guide/hlf#hosting-hlf). Contact\nyour technical account manager (TAM) for help setting this up."]]
