Important update: new articles for the Product data specification
Today we launched changes to the format of the Product data specification.
What this means
The requirements for your product data are still the same. So if your product data currently meets our requirements, that won’t change with this update. The changes should make it easier for you to understand what to submit and how to optimize your product data for success on Google.
How it works
Now instead of one article with all the requirements, the information is broken up into different articles depending on what you’re doing:
- The new product data specification lets you know exactly what you need to do to get started. This article lists every attribute, when it’s required, and the minimum requirements for submitting it. Use this table when you’re first starting out and just getting a feed set up. Check it out.
- Each attribute has its own article with detailed information if you need to review some examples, troubleshoot issues, or optimize your data. This also means that you'll be able to search for an attribute article in the search bar or bookmark a link directly to an attribute that you reference often. Check it out.
- For some of the more complicated areas, new best practices guides explain how to format several attributes. For example, if you’re advertising a custom product or software subscription, you can review a guide specifically about how to submit these types of products. Check it out.
New attribute names for certain languages
Based on your feedback, we updated our attribute translations for certain languages so their meaning should be clearer to you. We’ll still accept the old translations for now. While you don’t have to update your product data yet, we recommend doing it soon for your own troubleshooting purposes.
Attribute translations were updated in these languages:
- Chinese (simplified)
- Portuguese (Brazil)
To see the updated translations for each language, select that language from the menu at the bottom of this page.
Other small changes
In addition to these big changes, we also made some minor changes that you might notice:
- Attributes now look like
codeand use underscores (
_). Instead of the ‘sale price’ attribute, you’ll now see the
sale_priceattribute. This doesn’t mean that you have to start using underscores instead of spaces, either spaces (
sale price) or underscores (
sale_price) are still accepted depending on the format of your product data. However, we think this new style will help you better understand when we’re talking about an attribute.
- TRUE and FALSE is now yes and no. To make our language clearer, we’re now accepting yes and no along with TRUE and FALSE. There’s no need to change your product data to use the new values yet however. Moving forward, we’ll also stop talking about TRUE and FALSE and talk only about yes and no.
Merchant Center Announcements | October 2016