Before submitting your feeds to Google, you can validate them with published schemas.
The following table lists the available schemas that you can use to validate your feeds against:
| Schema (Download) | Applicable pricing delivery modes | Schema (Location) |
|---|---|---|
| Hotel List Feed | All | www.gstatic.com/localfeed/local_feed.xsd |
| Landing pages | All | www.gstatic.com/ads-travel/hotels/api/point_of_sale.xsd |
| Transaction (Property Data) | ARI | www.gstatic.com/ads-travel/hotels/api/transaction_property_data.xsd |
| OTA_HotelRateAmountNotifRQ | ARI | www.gstatic.com/ads-travel/hotels/api/ota_hotel_rate_amount_notif_rq.xsd |
| OTA_HotelAvailNotifRQ | ARI | www.gstatic.com/ads-travel/hotels/api/ota_hotel_avail_notif_rq.xsd |
| TaxFeeInfo | ARI | www.gstatic.com/ads-travel/hotels/api/tax_fee_info.xsd |
| Promotions | ARI | www.gstatic.com/ads-travel/hotels/api/promotions.xsd |
| Transaction | Pull, Changed Pricing | www.gstatic.com/ads-travel/hotels/api/transaction.xsd |
| Rate rules | Pull, Changed Pricing | www.gstatic.com/ads-travel/hotels/api/private_rates.xsd |
| Hint Response | Changed Pricing | www.gstatic.com/ads-travel/hotels/api/hint.xsd |
| Query (from Google to partners) | Pull, Changed Pricing, Live Pricing Query | www.gstatic.com/ads-travel/hotels/api/query.xsd |
To validate your files with these schemas, you can use a third-party XML tool
such as xmllint.
The syntax for using xmllint to validate a schema is as follows:
Use http: for the schema_location URL
since xmllint doesn't support https:.
$ xmllint --schema schema_location file_to_validate
The following example validates the mypriceupdates.xml file against the Transaction message schema:
$ xmllint --schema http://www.gstatic.com/ads-travel/hotels/api/transaction.xsd mypriceupdates.xml
The following example validates the myfeed.xml file against the Hotel List Feed schema and only showing the errors if they exist:
$ xmllint --noout --schema http://www.gstatic.com/localfeed/local_feed.xsd myfeed.xml