Stay organized with collectionsSave and categorize content based on your preferences.
Overview
Google shows your hotel attribute data across Search and Maps. You can send
this data to Google with theGoogle Lodging Format.
To send Google your lodging data, you can either embed the data in your hotel
list feed (preferred method) or set up a dedicated file transfer. The
following sections cover each option.
Embed data in your hotel list feed
If you have an existinghotel list feed,
you can include the lodging data in the<attributes>section under the<client_attr name="lodging">. The value for this attribute is the
Base64-encoded string of the encodedLodgingproto for the listing. Using
this method, theLodging.place_idfield should be the Hotel ID of the
specific listing entry in your feed.
If you aren't able to include the lodging data directly in the listing entry,
you can set up a separate hosted file transfer. TheLodgingproto data can be
formatted as a textproto or JSON. The setup is very similar to that of thehotel listing feed. Contact
your technical account manager (TAM) for help setting this up.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-09-18 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[[["\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."]]
