Search
Clear search
Close search
Google apps
Main menu
true

Matching Report

The Matching report shows errors with matching your feed data with Google's canonical list of hotels. You should resolve all issues in your feed.

To use the Matching report:

  1. Open Hotel Ads Center in a browser.
  2. Select the Tools tab.
  3. Select Matching Report in the left-hand navigation.

The Matching report shows the hotel ID and name as it appears in your feed. In addition, the report shows the hotel name in Google's canonical list (MATCHED GOOGLE HOTEL NAME), as well as any hotels that the hotel is overclustered with.

The DATA ISSUES column in the Matching Report tool displays errors for each hotel.

DEVELOPER'S NOTE: The table below includes the both the value of the error in the Matching Report's DATA ISSUES column and the value of the <dataIssues> element returned by the Hotels API, using the following format: "Matching_Report_message" (API_error_code).

The following table describes the data issue error messages and provides guidance on how to resolve the issue. Correct the issues and resubmit your Hotel List Feed.

Error Message (API Error Code) Description/Remedial Action
"No Data Issue"
(NO_DATA_ISSUE)
There are no issues with this hotel's details in the Hotel List Feed.
"Duplicate Address"
(DUPLICATE_ADDRESS)

The address is the same as another address in the Hotel List Feed.

Be sure that:

  • You do not use the same address for more than one property.
  • The address refers to the local business. Do not use the address of the company’s headquarters.
"Missing Physical Street Address"
(MISSING_PHYSICAL_STREET_ADDRESS)

The provided address is not a physical street address.

Be sure that:

  • This listing has a valid business address.
  • Do not use a post office box.
  • Do not use the company’s headquarters. Use the property’s local address.
"Missing Street Name"
(MISSING_STREET_NAME)

The address does not contain a street name. A street name is required according to the postal conventions of the country.

Be sure that:

  • The address includes a street name.
  • The address is not a post office box.
"Missing Street Number"
(MISSING_STREET_NUMBER)

The address does not contain a street number. A street number is required according to the postal conventions of the country.

Be sure that:

  • The address includes a street number.
  • The address is not a post office box.
"Missing Address"
(MISSING_ADDRESS)

The address is missing. Be sure that this listing has a valid business address.

Be sure that:

  • Do not use post office boxes.
  • Use the local address of the property, not the company’s headquarters.
  • Include a street address as well as region, postal code, and country.
"Missing Country"
(MISSING_COUNTRY)

The address does not specify a country or the country code is invalid.

Be sure that:

  • You entered a two-letter country code. For example, enter “US” for the United States and “CA” for Canada.
  • The value is an ISO 3166-1 alpha-2 country code.
"Invalid Postal Code"
(INVALID_POSTAL_CODE)

The postal code is invalid.

Be sure that:

  • The postal code is correct for the country in which the property is located. In the US, the postal code (or ZIP code) is five digits; for example, “90210”.
  • If you use the Detailed Address Format for US postal codes, provide the postal code (such as “90210”) and the ZIP+4 (such as “1351”) in separate fields.
"Invalid Postal Code Suffix"
(INVALID_POSTAL_CODE_SUFFIX)

The postal code suffix is invalid.

Be sure that:

  • Provide a valid postal code suffix. In the US, the postal code suffix (or ZIP+4) is a four-digit value. For example, “1234”.
"Unexpected Postal Code Suffix"
(UNEXPECTED_POSTAL_CODE_SUFFIX)

The postal code suffix does not follow the format defined by the country’s postal system.

Be sure to:

  • Verify the provided postal code suffix. In the US, this four-digit value is known as the ZIP+4. For example, “1234”.
"Unexpected Postal Code"
(UNEXPECTED_POSTAL_CODE)

The provided postal code does not follow the format defined by the country’s postal system.

Be sure to:

  • Verify the provided postal code.
"Invalid Amenities"
(INVALID_AMENITIES)

The specified amenities are invalid.

Be sure to:

  • Verify the list of amenities.
"Invalid email Address"
(INVALID_EMAIL_ADDRESS)

The email address for the property is invalid.

Be sure that:

  • You provided a valid email address, which includes the domain name. For example, “user@example.com”.
  • The format for valid email addresses is defined by RFC 2822. For more information, see https://www.ietf.org/rfc/rfc2822.txt.
"Duplicate Lat-long"
(DUPLICATE_LATLONG)

The property’s lat-long is the same as that of another property in the Hotel List Feed. More than one listing in the feed cannot have the same lat-long.

Be sure that:

  • Do not use the same lat-long for more than one property.
  • If you generated the lat-long based on a postal address, ensure that the address is complete and includes all components, such as the street number and a valid postal code.
  • Try using a postal code extension for more accuracy.
  • To verify your lat-long, use a service such as http://maps.google.com.
"Lat-long Inconsistent With Address"
(LATLONG_INCONSISTENT_WITH_ADDRESS)

The lat-long that you entered for the property is significantly different from the lat-long that Google generated from the address.

Be sure that you:

  • Provide an accurate lat-long value for the property. To get a valid lat-long, use a service such as http://maps.google.com.
"Missing Lat-long"
(MISSING_LATLONG)

The lat-long is missing for this property.

Be sure to:

"Could Not GeoCode Lat-long"
(COULD_NOT_GEOCODE)

Google could not generate a valid lat-long for the property from the address specified.

Be sure to:

  • Provide a complete and valid address.
  • Verify the street number, postal code, and other aspects of the property’s address.
"Missing Hotel Name"
(MISSING_HOTEL_NAME)

The hotel name is missing.

Be sure to:

  • Provide a valid hotel name.
  • The maximum number of characters in a valid hotel name is 200.
  • Do not include special characters such as “&” and “$” in the property name.
  • Do not capitalize all letters; only capitalize the first letter in each word, if necessary.
"Invalid Hotel Name"
(INVALID_HOTEL_NAME)

The hotel name is not valid.

Be sure that:

  • The listing has a valid business name.
  • Avoid abbreviations and truncated hotel names.
  • The maximum number of characters in a valid hotel name is 200.
  • Do not include special characters such as “&” and “$” in the property name.
  • Do not capitalize all letters; only capitalize the first letter in each word, if necessary.
"Hotel Name Too Long"
(HOTEL_NAME_TOO_LONG)

The name of the hotel has too many characters.

Be sure that:

  • The name does not exceed 200 characters.
  • You use abbreviations if necessary.
  • No special characters such as “&” and “$” are used in the property name.
"Parse Error In XML"
(PARSE_ERROR_IN_XML)

Google encountered an error while importing your Hotel List Feed.

Be sure to:

"Unexpected Attribute In XML"
(UNEXPECTED_ATTRIBUTE_IN_XML)

Google encountered an error while importing your Hotel List Feed.

Be sure to:

"Duplicate Phone Number"
(DUPLICATE_PHONE_NUMBER)

The phone number you provided for this property is the same as the phone number for another property. More than one listing in the Hotel List Feed cannot have the same phone number.

Be sure to:

  • Use a unique phone number for each property.
  • Use a unique number for each ”type” of phone number (such as “main”, “mobile”, or “fax”).
  • When a business has multiple properties, do not use a central main number for all properties. Use the individual property’s numbers instead.
"Missing Phone Number"
(MISSING_PHONE_NUMBER)

The phone number for this property is missing.

Be sure to:

  • Provide a unique voice phone number for each property location.
  • Use the following rules for phone numbers:
    • You can use add dashes, spaces, or parentheses in the phone number to make it easier to read. For example, use “610-222-3333” or “(610) 222-3333”, rather than “6102223333”.
    • Each phone number field can contain only one phone number. Do not specify multiple numbers, such as 650-123-2222/33.
    • You can enter an extension of up to 7 digits, preceded by one of the following abbreviations: "ext", "extn", and "x"; for example: "408-555-1111x12345".
    • You can separate an extension with spaces; for example: "650-222-3333 ext 123".
    • Do not use alphabetical characters in the phone number. A phone number must be all digits.
    • Each property should specify one of each type of phone number: "main", "mobile", "tollfree", "fax", or "tdd".
    • Use an online validator or related library to verify the validity of the phone number.
    • If you include the country code, you must precede it with a "+". For example, “+65 6722-2323” for a number in Singapore (country code is 65) or “+001 (408) 555-1111” for a number in the United States (country code is 001).
"Missing Voice Phone Number"
(MISSING_VOICE_PHONE_NUMBER)

The phone number that you provided for this property is not a voice number.

Be sure to:

  • Provide a unique voice phone number for each property. Fax or other non-voice phone numbers are not sufficient.
  • Use the following rules for phone numbers:
    • You can use add dashes, spaces, or parentheses in the phone number to make it easier to read. For example, use “610-222-3333” or “(610) 222-3333”, rather than “6102223333”.
    • Each phone number field can contain only one phone number. Do not specify multiple numbers, such as 650-123-2222/33.
    • You can enter an extension of up to 7 digits, preceded by one of the following abbreviations: "ext", "extn", and "x"; for example: "408-555-1111x12345". You can separate an extension with spaces; for example: "650-222-3333 ext 123".
    • Do not use alphabetical characters in the phone number. A phone number must be all digits.
    • Each property should specify one of each type of phone number: "main", "mobile", "tollfree", "fax", or "tdd".
    • Use an online validator or related library to verify the validity of the phone number.
    • If you include the country code, you must precede it with a "+". For example, “+65 6722-2323” for a number in Singapore (country code is 65) or “+001 (408) 555-1111” for a number in the United States (country code is 001).
"Invalid Phone Number Format"
(INVALID_PHONE_NUMBER_FORMAT)

The phone number you provided is not valid.

Use the following rules for phone numbers:

  • You can use add dashes, spaces, or parentheses in the phone number to make it easier to read. For example, use “610-222-3333” or “(610) 222-3333”, rather than “6102223333”.
  • Each phone number field can contain only one phone number. Do not specify multiple numbers, such as 650-123-2222/33.
  • You can enter an extension of up to 7 digits, preceded by one of the following abbreviations: "ext", "extn", and "x"; for example: "408-555-1111x12345". You can separate an extension with spaces; for example: "650-222-3333 ext 123".
  • Do not use alphabetical characters in the phone number. A phone number must be all digits.
  • Each property should specify one of each type of phone number: "main", "mobile", "tollfree", "fax", or "tdd".
  • Use an online validator or related library to verify the validity of the phone number.
  • If you include the country code, you must precede it with a "+". For example, “+65 6722-2323” for a number in Singapore (country code is 65) or “+001 (408) 555-1111” for a number in the United States (country code is 001).
"Invalid Phone Number"
(INVALID_PHONE_NUMBER)

The phone number you provided is not valid.

Be sure to:

  • Provide a valid voice phone number.
  • Use the following rules for phone numbers:
    • You can use add dashes, spaces, or parentheses in the phone number to make it easier to read. For example, use “610-222-3333” or “(610) 222-3333”, rather than “6102223333”.
    • Each phone number field can contain only one phone number. Do not specify multiple numbers, such as 650-123-2222/33.
    • You can enter an extension of up to 7 digits, preceded by one of the following abbreviations: "ext", "extn", and "x"; for example: "408-555-1111x12345". You can separate an extension with spaces; for example: "650-222-3333 ext 123".
    • Do not use alphabetical characters in the phone number. A phone number must be all digits.
    • Each property should specify one of each type of phone number: "main", "mobile", "tollfree", "fax", or "tdd".
    • Use an online validator or related library to verify the validity of the phone number.
    • If you include the country code, you must precede it with a "+". For example, “+65 6722-2323” for a number in Singapore (country code is 65) or “+001 (408) 555-1111” for a number in the United States (country code is 001).
"Invalid Phone Number Country Code"
(INVALID_PHONE_NUMBER_COUNTRY_CODE)

The phone number’s country code is not valid.

Be sure to:

  • Precede the country code with a "+". For example, “+65 6722-2323” for a number in Singapore (country code is 65) or “+001 (408) 555-1111” for a number in the United States (country code is 001).
  • Consult the list of valid country codes for allowed values.
"Phone Number Too Long"
(PHONE_NUMBER_TOO_LONG)

The phone number for the property contains too many digits.

Be sure to:

  • Follow the country’s phone number format.
  • Do not exceed 7 digits for the extension.
  • Use only digits in the phone number; alphabetical characters are not supported.
"Phone Number Too Short"
(PHONE_NUMBER_TOO_SHORT)

The phone number is invalid because it has too few digits.

Be sure that:

  • The phone number follows the country’s phone number format.
  • The phone number uses only digits; alphabetical characters are not supported.
  • Use an online validator or related library to verify the validity of the phone number.
"Invalid Website URL"
(INVALID_WEBSITE_URL)

The specified address is not a valid URL.

Be sure to:

  • Include the protocol prefix “http://” or “https://”. Note that some websites only support HTTP and not HTTPS, and vice versa.
  • Open the website in your browser to ensure that the URL is correct.
  • Use a URL validator to verify that the syntax is correct.
  • Where possible, use links to pages that are specific to the property and not to an entire hotel chain.
  • Do not use link-shorteners such as http://bit.ly.
  • URL-encode the address if it contains spaces or other special characters.
  • Do not refer to URLs that redirect to other URLs.
"Unknown Issue"
(UNKNOWN)

An unknown error caused the hotel to not be indexed. Check the Hotel List Feed for illegal characters or other issues.

 

Was this article helpful?
How can we improve it?