Content API for Shopping

Data Quality Feed

After product uploads, not all items may be displayed on Google Shopping, the product rank may suddenly drop or your account may face the risk of suspension. The most likely reason for these potential problems

The Data Quality feed lets you retrieve a data quality report that lists the various data quality issues captured across your product data. This report is available on both the account or sub-account level and is returned as an XML response to a GET call.


  1. Issue Types
  2. Suspension Policies
  3. Retrieving Data Quality Issues
  4. Response XML Elements

Issue Types

The following table describes the issue types that may appear on your account.

Issue ID Description
price_mismatch The submitted price does not match the price specified on the web page.
strong_id_missing, strong_id_bad The item has a wrong or missing unique product identifier.
availability_mismatch The availability value does not match with what is specified on the web page.
landing_page_error, landing_page_roboted The Google web crawler is unable to access the landing web page or access is blocked.
title_all_caps The item title is in all CAPS, which is disallowed.
image_link_broken, image_link_missing, image_link_roboted Googlebot is unable to crawl the item’s image, either because it is broken, does not exist, or is blocked in the robots.txt file.
description_short The item's description is too short per Google's Products Feed Specification. We recommend that you submit descriptions with at least 15 characters.
condition_mismatch The condition value does not match with what is specified on the web page.
language_mismatch The language of the title or description differs from the language specified for the item. See the Requirements for Google Shopping listings help center article for information on which languages products should be listed in depending on locale.

Back to top

Suspension Policies

The following table explains the various suspension policies:

Policy Description
title_all_caps Some of your items have titles that contain an excessive amount of capitalized text.
image_link_problem The submitted images links are not working properly, possibly because your robots.txt file is blocking our crawler. See the Unique product identifiers Help Center article.
condition_mismatch Some of your items are submitted with a condition that differs from that on your website.
crawl_error Some of the pages linked from your items cannot be crawled.
language_mismatch Some titles and descriptions of your items are in a language that differs from that of the feed.
strong_id Some of your items are missing valid unique product identifiers.
price_and_availability_mismatch Some of your items have a price/availabilty that differs from that on your website.

Back to top

Retrieving Data Quality Issues

To get a data quality report on your account or sub-account, you need to send a GET request. You will get a response XML with details on issues, number of affected items and so on.

Note 1: We recommend retrieving the data quality information once a day. A higher frequency is not necessary, as the information is updated only once a day.

Note 2: The response XML data is based on the scan of all the valid feeds for the specified account.

Following is an example GET request and its XML response having the data quality report comprising two data quality issues.

GET Request Example:

While the first URL is a GET request for merchant account ID 12345, the second URL is for a sub-account ID 98765, belonging to MCA ID 54321. To get a data quality report across sub-accounts, the MCA would need to only remove the sub-account number from the URL.

Note: To retrieve a list of data quality issues for a single user account, you need to mention the account ID twice, as shown in the first URL example above.

Response XML Examples:

Following is the response XML for the data quality issue price_mismatch:

<sc:issue_group country="US" id="US_price_mismatch">
  <sc:issue id="price_mismatch" last_checked="2012-03-07T07:12:18Z" num_items="57">
      <sc:title>1 ft Computer Power Cord IEC 320 C14 to NEMA 5-15R PAC100</sc:title>

Following is the response XML for the data quality issue strong_id:

  <sc:issue_group country="US" id="US_strong_id">
    <sc:issue id="strong_id_missing" last_checked="2012-03-07T22:11:14Z" num_items="253">
        <sc:title>Canon Powershot SX230IS 12.1 Megapixels - Red Digital Camera Bonus Kit</sc:title>
    <sc:issue id="strong_id_bad" last_checked="2012-03-07T22:11:14Z" num_items="22">
        <sc:title>BROAN 500 CFM Internal Blower</sc:title>

Following is a snippet of the response XML for the data quality issue of policies:

    <sc:policy country="US" destinations="ShoppingApi,Shopping" id="strong_id" severity="critical">

Note 1: For an MCA requesting DQ reports across all sub-accounts, the response is limited to 25 sub-accounts, by default. If needed, understand how to browse through more than 25 sub-accounts, and to specify a different number of sub-accounts (maximum 100) per response.

Note 2: The above code snippets (as well as the response XML elements table below) include only elements that are relevant to the data quality information. The atom-feed specific elements are excluded for the sake of clarity.

Back to top

Response XML Elements

The following table explains the relevant data quality elements in the response XML:

Element Type Attribute Description Included in XML?
issue_group: A group of issues that corresponds to one or multiple policy actions. id Unique ID per account report. Always
country Country for which the issue_group is relevant. Always
issue: Values that relate to the said data quality issue. id Issue identifier. Always
num_items Number of items in the account found to have the said issue. Optional
last_checked Last time the account was checked for this issue. Always
offending_term Gives the word or phrase that is causing the issue. For certain issues
example_item Elements: These represent the item attributes. sc:item_id Unique item ID. Always
sc:title Title of the item. Always
sc:link Landing page of the item. Always
sc:submitted_value The item value. Optional
sc:value_on_landing_page The actual value on the landing page is different than what is submitted, or conflicts with a policy. Optional
policies Element: The only sub-element is the policy element. A policy is an actionable rule, optionally based on one or more issue groups such as item demotion or account suspension. policy_id The policy's unique ID. Always

Country in which the policy applies.

destinations The destinations for which the policy applies. Always
earliest_reinstatement The date of the end of any penalty period that applies. Optional
severity The severity of the policy, possible values are: suggestion, error and critical. Optional
sc:issue_group_reference References one issue_group ID in the same report. Optional

Back to top

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.