A landing page file is an XML file that partners create to define various URL
destinations when a user clicks on a Hotel Ad price on Google and it gets
redirected to a partner's website. You can upload a landing page file using
Hotel Center. For details, refer to
[manage and update your landing pages](https://support.google.com/hotelprices/answer/9457428).

The root element of the landing page file is `<PointsOfSale>`. Each landing page
in the file is defined by a `<PointOfSale>` child element. You can have multiple
`<PointOfSale>` child elements in a landing page file. However, all landing
pages refer to the same partner.

> [!IMPORTANT]
> **Key Point:** You cannot use a single landing page file to define landing pages for more than one partner.

### Example

The following example shows a landing page file that defines two landing pages:

    <?xml version="1.0" encoding="UTF-8"?>
    <PointsOfSale>
      <PointOfSale id="TravelAgency">
        <DisplayNames display_text="TravelAgency.com" display_language="en"/>
        <DisplayNames display_text="TravelAgency.com.fr" display_language="fr"/>
        <Match status="yes" language="en"/>
        <Match status="yes" language="fr"/>
        <Match status="yes" country="US"/>
        <Match status="yes" country="FR"/>
        <Match status="yes" currency="USD"/>
        <Match status="yes" currency="EUR"/>
        <URL>http://partner.com/landing?hid=(PARTNER-HOTEL-ID)&amp;checkin=(CHECKINYEAR)-(CHECKINMONTH)-(CHECKINDAY)&amp;checkout=(CHECKOUTYEAR)-(CHECKOUTMONTH)-(CHECKOUTDAY)&amp;language=(USER-LANGUAGE)</URL>
      </PointOfSale>
      <PointOfSale id="Others">
        <DisplayNames display_text="TravelAgency en espanol" display_language="es"/>
        <Match status="yes" language="es"/>
        <Match status="yes" country="US"/>
        <Match status="yes" currency="USD"/>
        <URL>http://partner-espanol.com/landing?hotelID=(PARTNER-HOTEL-ID)</URL>
      </PointOfSale>
    </PointsOfSale>

In this example, English or French preferred users in the US or France
would match the first landing page. This landing page has two display names:
`TravelAgency.com` and `TravelAgency.com.fr`. These two sites support English
and French for languages, and US dollars and Euros for currencies. The generated
URL that is passed to the landing page includes details about the transaction,
such as the check-in and check-out dates, hotel ID, and user language.

A Spanish preferred user in the US would match the second landing page.
However, this landing page supports only one display name, one language, and
one currency. Also, the generated URL only sends the hotel ID to the landing
page and doesn't send the check-in date, length of stay or any other
information. The user must input that information again on your website.

For more information, see the
[landing pages file syntax](https://developers.google.com/hotels/hotel-prices/dev-guide/pos-syntax).

## Price accuracy and automated validation

To ensure that the rates displayed on Google match the prices on your landing
pages, Google uses an automated validator crawler to verify price accuracy. You
can tag your landing pages and booking funnels with microdata to enable seamless
price extraction.

For implementation instructions, refer to:

- [Crawler navigation and price tagging guide](https://developers.google.com/hotels/hotel-prices/structured-data/generic-crawler-guide)
- [Hotel price structured data reference](https://developers.google.com/hotels/hotel-prices/structured-data/hotel-price-structured-data)