Search
Clear search
Close search
Google apps
Main menu

Local products feed specification

This page lists all the attributes you can provide in your local products feed for local inventory ads.

Submit local products feeds 

File type: You can use either delimited text file (recommended), XML or API.

Registering a new feed: Follow the standard steps to register a new feed, and select "local products" as the feed type.

Please note that products may take up to 2 days to appear after submission.

Important: Some attributes in this local products feed spec contain spaces and underscores. To make sure you submit attributes with correct characters and spacing, follow the guidelines below for your file type:

Summary of attribute requirements

  Attribute Submission requirements
Required identification attributes

itemid

title

Required for all products you sell in stores.

Required if data is not available in online products feed

description

image_link

condition

gtin

brand

google_product_category

Use the product attributes to provide rich product information in your local products feed. 

Optional matching attributes

webitemid

gtin

mpn

brand

 

If you’re using Shopping ads, you should match product you sell both online and in-store across your products feed and your local products feed. To do this, you have 3 options:

  • Match id to itemid value

  • Match id to webitemid value

  • Match gtin + brand or mpn + brand values

If you’re using any unique product identifiers to match, you need to include condition in this feed.
Optional pricing attributes

price

sale price

sale price effective date

Optional. May also be submitted at the store level in your local product inventory feed.
Optional store pickup attributes

pickup method

pickup SLA

pickup_link_template

mobile_pickup_link_template

Optional. May also be submitted at the store level in your local products inventory feed.
Optional merchant hosted local storefront attributes

link_template

mobile_link_template

adwords_redirect

Optional.
 

Important note (XML only): If you are updating your Merchant Center feed in XML for any of the attributes listed below, you must add the Google Merchant Center namespace declaration. Otherwise, your feed may not process correctly. 

Required identification attributes

These attributes tell us basic information about your products and are required for all items.

itemid [itemid] - An identifier of the item

The identifier for each item, unique across all stores, and cannot be re-used between feeds of the same type for the same country in the same language. If the item exists in your products feed, please attempt to match this attribute to the id attribute in the online feed. If this isn’t possible, see webitemid below.

When to include: Required for all items.

Type String
Text/Tab delimited example 421486
XML example <g:itemid>421486</g:itemid>

Important:

  • Use the same itemid values in both your local products and local product inventory feeds.
  • Starting and trailing whitespaces and carriage returns (0x0D) are removed.
  • Each sequence of carriage return (0x0D) and whitespace characters (Unicode characters with the whitespace property) is replaced by a single whitespace (0x20).
  • Only valid unicode characters are accepted; this excludes the following characters:
    • control characters (except carriage return 0x0D)
    • function characters
    • private area characters
    • surrogate pairs
    • non assigned code points (in particular any code point larger than 0x10FFFF)
  • Once an item is submitted, the id must not change when you update your data feed.
  • Once an item is submitted, the id must not be used for a different product at a later point in time.
  • If you are using itemid for Shopping campaigns we recommend that you only use lowercase or case-insensitive characters.
title [title] - Title of the item

This is the name of your item. We recommend you include characteristics such as color or brand in the title that differentiate the item from other products. Note that sometimes we might serve the title from your online item or from Google Catalog data instead if there is a match.

When to include: Required for all items.

Type Text (string), not longer than 70 characters
Text/Tab delimited example Netgear ReadyNAS Duo
XML example <g:title>Netgear ReadyNAS Duo</g:title>

Important:

  • Follow our Editorial guidelines closely. For example, do not include any promotional text such as "Free shipping," and do not use BLOCK CAPITALS.
  • For variant products, you are required to include the common title of the variant items. For example if “Mens Pique Polo Shirt” is available in red and blue colors, you can have one of the following titles:
    • Mens Pique Polo Shirt (Can be used for both variants)
    • Mens Pique Polo Shirt - Red (For the red shirt)
    • Mens Pique Polo Shirt - Blue (For the blue shirt)

Recommended product feed attributes

We strongly recommend providing the following information for all the products you sell in stores. However, it is only required for products that are not mapped to a products feed. For example:

  • If  you do not have a products feed, these attributes are required for all products in your local products feed

  • If you do have a products feed, these attributes are required for products sold only in stores

description [description] - Description of the item

Include only information relevant to the item. Describe its most relevant attributes, such as size, material, intended age range, special features, or other technical specs. Also include details about the item’s most visual attributes, such as shape, pattern, texture, and design, since we may use this text for finding your item.

We recommend that you submit around 500 to 1,000 characters, but you can submit up to 5,000 characters. Descriptions should follow standard grammar rules and end with a punctuation mark.

When to include: Required for all items.

Type Text
Character limit 5,000
Text/Tab delimited Solid red, queen-sized bed sheets made from 100% woven polyester 300 thread count fabric. Set includes one fitted sheet, one flat sheet, and two standard pillowcases. Machine washable; extra deep fitted pockets.
XML (Feeds) <description>Solid red, queen-sized bed sheets made from 100% woven polyester 300 thread count fabric. Set includes one fitted sheet, one flat sheet, and two standard pillowcases. Machine washable; extra deep fitted pockets.</description>
Content API v2 (JSON) "description": "Solid red, queen-sized bed sheets made from 100% woven polyester 300 thread count fabric. Set includes one fitted sheet, one flat sheet, and two standard pillowcases. Machine washable; extra deep fitted pockets."
Content API v2 (XML) <description>Solid red, queen-sized bed sheets made from 100% woven polyester 300 thread count fabric. Set includes one fitted sheet, one flat sheet, and two standard pillowcases. Machine washable; extra deep fitted pockets.</description>

Important:

  • Make sure to follow our Editorial guidelines closely. For example, do not include any promotional text such as "Free shipping", do not use BLOCK CAPITALS, and do not include a description of your brand or company.
  • Additionally, the following information should not be included in descriptions:
    • Links to your store or other websites
    • Billing, payment, or sales information
    • References to internal categorization systems, e.g. "Toys & Games > Toys > Baby Dolls"
    • Comparisons to other products beyond the item you’re selling, e.g. “even better/faster/larger than X”
    • Details about other products, accessories, or similar items available
image link [image_link] - URL of an image of the item

This is the URL of the main image for a product and is the first image users see on product detail pages.

If you have multiple different images of the item, submit the main image using this attribute, and include all other images in the 'additional image link' attribute.

Image size:

  • Submit the largest, highest resolution, full-size image you have for the product, up to 16MB file size.
  • Recommended image size is at least 800 x 800 pixels in height and width.
  • For apparel products, images must be at least 250 x 250 pixels and can't be larger than 64 megapixels. For all other products, images must be at least 100 x 100 pixels and can't be larger than 64 megapixels.
  • Do not scale up images or submit thumbnails. We recommend the product to take no less than 75%, but not more than 90%, of the full image

When to include: Required for all items.

Content API v2 (JSON) "imageLink": "http://www.example.com/image1.jpg" Content API v2 (XML) <image_link>http://www.example.com/image1.jpg</image_link>
Type URL. (Must start with 'http://' or 'https://'.)
Character limit 2,000
Text/Tab delimited http://www.example.com/image1.jpg
XML (Feeds) <g:image_link>http://www.example.com/image1.jpg
</g:image_link>

By meeting the requirements and recommendations below, you can improve the shopping experience for Google Express users.

Requirements:

  • If you have no image of the item, you cannot submit the item.
  • The following types of images are also not allowed
    • Placeholder or incorrect product images
    • Generic images, graphics, or illustrations that are not the actual product images, except for products in the 'Hardware' (632) or 'Vehicles and parts' (888) categories, which allow graphics and/or illustrations of the actual product
    • Single color images that are only a square of color, except for products in the 'Vehicle Paint' (3812), 'Craft Paint, Ink & Glaze' (505378), and 'Painting Consumables' (503740) categories
    • Images containing promotional elements (e.g. calls to action such as “buy”; service-related information such as extended warranty; free shipping; price information; promotional adjectives such as “best, cheap”; condition or compatibility such as new, 2-piece, adaptable) or names and/or logos of merchants regardless if the above mentioned elements overlay the product. This also applies to watermarks with promotional elements or names and/or logos of merchants.
    • Images containing obstructing content (e.g. watermarks, brand names and/or logos) that overlay the product being sold
    • Images that include borders
    • Images of a bundle that do not show the entire bundle
    • Images of multipack that do not display a single unit of the product

    Landing pages with no image or placeholder images that do not show the actual product are also not allowed.

    • Make sure that the image you provide for each item matches the values provided in the colorpattern, and material attributes, or your item might be disapproved.

Recommendations:

  • For all other countries and categories: If you cannot provide the appropriate images to submit your items as variants, you may list your variant products as a single item with multiple values for the variant attributes and provide the available image.
  • The image must accurately display the product and include minimal or no product staging.
  • For variants based on color, each individual variant item you submit must have an image that displays the product in a single color.
  • The main image should be taken on a solid white, gray or light colored background.
  • The main image of a product should include a main and/or clear view of the product being sold. Additional views of the product (other than the main view) should be submitted in the ‘additional image link’ attributes.

Formatting:

  • The accepted image formats are non-animated GIF (.gif), JPEG (.jpg/.jpeg), PNG (.png), BMP (.bmp), and TIFF (.tif/.tiff) and the file extensions for these images should correspond to their format.
  • The accepted URL protocols are ‘http’ and ‘https’. Any symbols used within the image URL must be replaced by URL encoded entities (e.g. comma = %2C).
  • We recommend that you submit stable URLs for your images and only update the URL if the actual image of the product has changed. This is especially important if you use a content delivery network to host images, and it will ensure that we can correctly crawl your images.

Cropping:

We may automatically crop your image to focus more on the product. To opt out of this feature, contact us.

condition [condition] - Condition or state of the item

Google Shopping allows the promotion of quality second-hand items. Google Shopping also allows the promotion of refurbished items as long as they comply with local laws and regulations and with our policies.

There are only 3 accepted values:

  • 'new' [new]: The product is brand-new and has never been used. It's in its original packaging, which has not been opened.
  • 'refurbished' [refurbished]: The product has been professionally restored to working order, is "as new", and comes with warranty. The packaging may or may not be the original packaging. This is sometimes referred to as "remanufactured".
  • 'used' [used]: Use this value if 'new' and 'refurbished' don't apply. For example, if the product has been used before, is a refilled printer cartridge, the original packaging has been opened, or the original packaging is missing.

When to include: Required for all items.

Content API v2 (JSON) "condition": "used" Content API v2 (XML) <condition>used</condition>
Type Only 3 values are accepted:
  • 'new' [new]
  • 'refurbished' [refurbished]
  • 'used' [used]
Text/Tab delimited

used

XML <g:condition>used</g:condition>

 

Important: If you are submitting the attribute names in English, you must provide the attribute values in English as well.

[gtin] - Global Trade Item Number (GTIN) of the item

Use the 'gtin' attribute to submit Global Trade Item Numbers (GTINs) in one of the following formats:

  • UPC (in North America / GTIN-12): 12-digit number like 323456789012; 8-digit UPC-E codes should be converted to 12-digit codes
  • EAN (in Europe / GTIN-13): 13-digit number like 3001234567892
  • JAN (in Japan / GTIN-13): 8 or 13-digit number like 49123456 or 4901234567894
  • ISBN (for books): 10 or 13-digit number like 1455582344 or 978-1455582341. If you have both, only include the 13-digit number. ISBN-10 are deprecated and should be converted to ISBN-13.
  • ITF-14 (for multipacks / GTIN-14): 14-digit number like 10856435001702.
Where to include Required for all items
Type 8-, 12-, 13-, or 14-digit number (UPC, EAN, JAN, or ISBN)
Character limit 50
Text/Tab delimited 3234567890126
XML (Feeds) <g:gtin>3234567890126</g:gtin>

Important:

  • We accept only valid GTINs as defined in the official GS1 validation guide, which includes these requirements:
    • The checksum digit is present and correct.
    • The GTIN is not restricted (GS1 prefix ranges 02, 04, 2).
    • The GTIN is not a coupon (GS1 prefix ranges 98 - 99).
brand [brand] - Brand of the item

When to include: Refer to the Unique Product Identifier Rules for your target country.

Content API v2 (JSON) "brand": "Acme" Content API v2 (XML) <brand>Acme</brand>
Type Text
Character limit 70
Text/Tab delimited Acme
XML (Feeds) <g:brand>Acme</g:brand>

Important: You must not provide your store name as the brand unless you manufacture the product.

google product category [google_product_category] - Google category of the item

Use the google_product_category attribute to indicate the category of your item based on the Google product taxonomy.

When to include: Required for all products in the following categories:

Apparel & Accessories > Clothing (1604)
Apparel & Accessories > Shoes (187)
Apparel & Accessories > Clothing Accessories > Sunglasses (178)
Apparel & Accessories > Handbags, Wallets & Cases > Handbags (3032)
Apparel & Accessories > Jewelry > Watches (201)
Media > Books (784)
Media > DVDs & Videos (839)
Media > Music & Sound Recordings (855)
Software > Video Game Software (1279) (includes computer games)

Note: Make sure that you provide the full category specification. Do not only provide the highest-level category (e.g. “Apparel & Accessories (166)” or “Media (783)”).

File format Example entry
Text feeds

2271

or

Apparel & Accessories > Clothing > Dresses

XML feeds

<g:google_product_category>2271</g:google_product_category>

or

<g:google_product_category>Apparel &amp; Accessories &gt; Clothing &gt; Dresses</g:google_product_category>

Content API v2 (JSON)

"googleProductCategory": "2271"

or

"googleProductCategory": "Apparel & Accessories > Clothing > Dresses"

Content API v2 (XML)

<google_product_category>2271</google_product_category>

or

<google_product_category>Apparel &amp; Accessories &gt; Clothing &gt; Dresses</google_product_category>

Important:

  • Follow these formatting guidelines to make sure we understand the data you're submitting:
    • Supported values: Predefined Google product category: the ID or the full path of the product category
      • Download a list of all Google product categories:
      • Download this list in another language, as needed: 
        • Select that language from the menu at the bottom of this article. These links will update to that language.
      • Prevent garbled text in the .txt version by using one of these methods:
        • Change your browser encoding to Unicode UTF-8. Learn how to change your browser encoding.
        • Download the .txt version: right-click on the link, and then click Save Link As
    • Limit: Use one category per product

For complete details, refer to google product category definition.

Optional matching attributes

The easiest way to match products across feed is using the same value for ID in your products feed and itemid in your local products feed. If this is not possible, you must use the following attributes to match products across your products and local products feeds.

webitemid [webitemid] - Match online and local IDs

If you cannot match the itemid in your local products feed to the id in your products feed, you can use webitemid for matching. You’d submit different values for your itemid, but the same value for webitemid and id. This should always match the id of the corresponding variant in your products feed, if one exists.

Since webitemid is only used for matching, multiple items may share the same webitemid if they map to the same item in your products feed.

When to include: Recommended for all items with different ids/SKUs for online versus local products.

Type Text (string)
Text/Tab delimited example WB1011
XML example <g:webitemid>WB1011</g:webitemid>

Important:

  • Starting and trailing whitespaces and carriage returns (0x0D) are removed.
  • Each sequence of carriage return (0x0D) and whitespace characters (Unicode characters with the whitespace property) is replaced by a single whitespace (0x20).
  • Only valid unicode characters are accepted; this excludes the following characters:
    • control characters (except carriage return 0x0D)
    • function characters
    • private area characters
    • surrogate pairs
    • non assigned code points (in particular any code point larger than 0x10FFFF)
  • Once an item is submitted, the webitemid must not change when you update your data feed.
  • Once an item is submitted, the webitemid must not be used for a different product at a later point in time.
gtin [gtin] - Global Trade Item Number (GTIN) of the item

In this attribute, you will include Global Trade Item Numbers (GTINs) for your products.

When to include: If you sell your items both in-store and online and cannot use the itemid attribute to match, you’ll need to use either webitemid or unique product identifiers as matching attributes.

If you’re using any unique product identifiers to match, you need to include condition in this feed.

Type Text (string)
Text/Tab delimited example 0606449056822
XML example <g:gtin>0606449056822</g:gtin>
mpn [mpn] - Manufacturer Part Number (MPN) of the item

This code uniquely identifies the product to its manufacturer. In particular, the combination of brand and MPN clearly specifies one product.

When to include: If you sell your items both in-store and online and cannot use the itemid attribute to match, you’ll need to use either 'webitemid' or unique product identifiers as matching attributes.

If you’re using any unique product identifiers to match, you need to include condition in this feed.

Type Text (string)
Text/Tab delimited example RND2150
XML example <g:mpn>RND2150</g:mpn>
brand [brand] - Brand of the item

When to include: If you sell your items both instore and online and cannot use the 'itemid' attribute to match, you’ll need to use either 'webitemid' or unique product identifiers as matching attributes.

If you’re using any unique product identifiers to match, you need to include condition in this feed.

Type Text (string)
Text/Tab delimited example Netgear
XML example <g:brand>Netgear</g:brand>

Apparel items

Apparel items require several additional attributes in the local products feed:

item group id [item_group_id] - Shared identifier for all variants of the same product

All items that are variants of the same product must have the same item group id. If you have a “Parent SKU” that is shared by all variants of a product, you can provide that as the value for 'item group id'.

When to include: For Brazil, France, Germany, Japan, the UK, and the US, required for all items with variants that use these detailed product attributes: ‘color’, ‘size’, ‘pattern’, ‘material’, ‘age group’, ‘gender’, ‘size type’ and ‘size system’. Recommended for all other countries.

Type Alphanumeric code
Character limit 50
Text/Tab delimited AB12345
XML (Feeds) <g:item_group_id>AB12345</g:item_group_id>
Content API v2 (JSON) "itemGroupId": "AB12345"
Content API v2 (XML) <item_group_id>AB12345</item_group_id>

Important:

  • The ‘Item group id’ attribute is different from the ‘ID’ attribute. An ‘Item group ID’ attribute will have common values for a group of variants whereas the ‘ID’ attribute should have unique values across a group of variants and for all other items, as well.
  • The values provided for item group id must be unique between products, and only shared by items that are variants of the same product.
  • If you send us an ‘item group id’ attribute, we will automatically look for variant attributes. If an item uses ‘Item group id’, make sure the item has at least one detailed product attribute.
color [color] - Color of the item

This defines the dominant color(s) for an item. When a single item has multiple colors, you can submit up to two additional values as accent colors:

  • Combine the colors with ‘/’ in order of prominence (dominant color first, then at most two accent colors). For example, a black shoe with green accents should have a color value of 'Black/Green'. In the case of non-deformable goods in Apparel like jewelry or wooden accessories where finishes or materials are equivalent to color, the finish or material name can be submitted in the color attribute (e.g., 'Mahogany' vs. 'Stainless Steel' vs. 'Rose Gold').
  • Limit the number of colors submitted to three values per item.
  • If you're using XML, you must represent the '/' with &#47;

When to include: Required for all products in an item group that vary by color. Required for all apparel items in feeds that target Brazil, France, Germany, Japan, the UK, and the US. Recommended for all products for which color is an important, distinguishing attribute.

Content API v2 (JSON) "color": "Black" Content API v2 (XML) <color>Black</color>
Type Text
Character limit 100
Text/Tab delimited Black
XML (Feeds) <g:color>Black</g:color>

What not to include:

  • Color values that contain numbers (e.g., '0 2 4 6 8')
  • Color values that contain non-alphanumeric characters (e.g., '#fff000')
  • Single letter color values (e.g., 'G') in Latin-based languages. Single letter color values in Chinese-Japanese-Korean languages (e.g., '红') are acceptable.
  • Color values that reference the product or product image (e.g., 'see image')
  • Descriptive values that are not actually valid color names (e.g. multicolor, various, variety, see image, N/A)
  • Long color values exceeding 40 characters
  • Long color values that are aggregates of several other colors (e.g., RedPinkBlue). Instead:
    • If you are trying to indicate multiple colors for a single item (not product variants), specify a primary color, optionally followed by at most two secondary colors, separated by a '/'. Here replace RedPinkBlue with Red/Pink/Blue
    • If you are trying to indicate multiple colors for multiple similar items (product variants), submit these as separate products each with the same item group ID and a different color value.

A note on invalid submissions:

  • If you submit a color value that violates the syntactic rules above, we may reject the entire item at the time of feed submission.
  • We regularly verify the correctness of the attributes you submit, including color. If the values provided are found to be incorrect, we may remove all of your items from Google Shopping.

Important:

  • For variants, each different color or color combination must be submitted as its own item, in conjunction with the 'item group id'.
  • Use consistent names of colors across variants of the same product, as well as across multiple products of the same category.
  • The values you provide may be displayed to users, so provide values that they will be able to understand.
size [size] - Size of the item

This indicates the size of a product. For ‘Apparel & Accessories’ items, you can also submit the ‘size type’ and ‘size system’ attributes to provide more details about your sizing.

When to include: Required for all products in an item group that vary by size. Required for all apparel items in the 'Apparel & Accessories > Clothing' and 'Apparel & Accessories > Shoes' product categories in product data that targets Brazil, France, Germany, Japan, the UK, and the US. Recommended for all products for which size is an important, distinguishing attribute.

Content API v2 (JSON) "sizes": ["XL"] Content API v2 (XML) <size>XL</size>
Type Text

If you are targeting the US, refer to the list of recognized values (US only)

For all other countries, see example sizes
Character limit 100
Text/Tab delimited XL
XML (Feeds) <g:size>XL</g:size>

Important:

  • For variants, each different size or size combination must be submitted as a separate item, in conjunction with the 'item group id'. Visit submitting apparel products for more details.
  • If sizes contain multiple dimensions, condense them into one value (e.g., “16/34 Tall” for neck size 16 inches, sleeve length 34 inches, and “Tall” fit).
  • Use consistent size values across variants of the same product, as well as across multiple products of the same category. For example, within a group of t-shirts, use “S”, “M” , and “L” as sizes, not “S”, “Medium” , and “Lrg”.
  • You may use the same image for size variants if specific images are not available but we recommend that the ‘link’ attribute leads to a page which specifies all the details about the variant item.
  • The values you provide may be displayed to users, so provide values that they will be able to understand.
  • You can provide additional details about your sizing in the text string. For US sizes, for example, you can provide “3.5 Kid” or “3.5 Toddler”.
  • If your item is one size fits all or one size fits most, you can use the phrase 'one size', 'OS', 'one size fits all', ‘OSFA’, ‘one size fits most’, or ‘OSFM’ in this attribute.

Example Sizing Values

Sizing values can be difficult to represent across different types of apparel products. It is not required to provide these exact values, but it may be helpful for you to standardize the size values of your apparel products. You can also use the ‘size type’ and ‘size system’ attributes to provide more information about the sizing of your products.

Tops, Outerwear, and Dresses

XXS, XS, S, M, L, XL, 1XL, 2XL, 3XL, 4XL, 5XL, 6XL
00, 0, 02, 04, 06, 08, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34

Bottoms

XXS, XS, S, M, L, XL, 1XL, 2XL, 3XL, 4XL, 5XL, 6XL
00, 0, 02, 04, 06, 08, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34
23, 24, 26, 27, 28, 29, 30, 32, 34, 36, 38, 40, 42, 44
For Pants: 24x30, 24x32, 24x34

Plus, Petite, Big, Tall, Inseams, etc.

When an item applies to a special size group, like Plus, Petite, Maternity, or Big and Tall, use the ‘size type’ attribute.
When an item includes an inseam, consider using this format for the size: 30 Short, 30 Regular, 30 Long

Shoes

For US: 5, 5.5, 6, 6.5, 7, 7.5, 8, 8.5, 9, 9.5, 10, 10.5, 11, 11.5, 12, 12.5, 13, 13.5, 14, 14.5, 15, 15.5, 16. Note: When a shoe is available in different width sizes, an indication is recommended: 9.5 M, 8 W, 12 N.
For Europe: 37, 38, 39, 40, 41, 42, 43, 44, 45
gender [gender] - Gender of the item

When to include: Required for all products in an item group that vary by gender. Required for all apparel items in feeds that target Brazil, France, Germany, Japan, the UK, and the US. Recommended for all products for which gender is an important, distinguishing attribute.

Format Only 3 values are accepted:
  • 'male' [male]
  • 'female' [female]
  • 'unisex' [unisex]
Text/Tab delimited male
XML (Feeds) <g:gender>male</g:gender>
Content API v2 (JSON) "gender": "male"
Content API v2 (XML) <gender>male</gender>

Important

  • If you are submitting the attribute names in English, you must provide the attribute values in English as well.
  • This attribute is recommended rather than required for the ‘pinback buttons’, ‘tie clips’, ‘wristbands’, ‘shoe covers’, ‘shoe laces’, ‘spurs’, ‘watch bands’ subcategories of ‘Apparel & Accessories’.
age group [age_group] - Target age group of the item

Use the age group attribute to indicate the demographic of your item.

When to include: Required for all products in an item group that vary by age group. Required for all apparel items in feeds that target Brazil, France, Germany, Japan, the UK, and the US. Recommended for all products for which age group is an important, distinguishing attribute.

Content API v2 (JSON) "ageGroup": "adult" Content API v2 (XML) <age_group>adult</age_group>
Format There are only 5 accepted values:
  • 'newborn' [newborn]
  • 'infant' [infant]
  • 'toddler' [toddler]
  • 'kids' [kids]
  • 'adult' [adult]
Text/Tab delimited adult
XML (Feeds) <g:age_group>adult</g:age_group>

Important:

  • The target market for each value is defined as follows:
    • 'newborn' [newborn]: Up to 3 months old. Newborn sizes are often identified by the month (0-3) age range and/or the single value 'newborn' [newborn].
    • 'infant' [infant]: Between 3-12 months old. Infant sizes are often identified by the month (3-12) age range.
    • 'toddler' [toddler]: Between 1-5 years old. Toddler sizes are often identified by the month (12-24) or year (1-5) age range.
    • 'kids' [kids]: Between 5-13 years old. All sizes within this age group have been manufactured to fit a child in that age range.
    • 'adult' [adult]: Typically teens or older. All sizes within this age group have been manufactured to fit an adult or teen in this age range.
  • If you are submitting the attribute names in English, you must provide the attribute values in English as well.
  • This attribute is recommended rather than required for the ‘pinback buttons’, ‘tie clips’, ‘wristbands’, ‘shoe covers’, ‘shoe laces’, ‘spurs’, ‘watch bands’ subcategories of ‘Apparel & Accessories’.
  • If an item is not clearly just for children, it should be declared as 'adult' [adult] because only 1 value may be submitted per item.
google product category [google_product_category] - Google category of the item

Use the google_product_category attribute to indicate the category of your item based on the Google product taxonomy.

When to include: Required for all products in the following categories:

Apparel & Accessories > Clothing (1604)
Apparel & Accessories > Shoes (187)
Apparel & Accessories > Clothing Accessories > Sunglasses (178)
Apparel & Accessories > Handbags, Wallets & Cases > Handbags (3032)
Apparel & Accessories > Jewelry > Watches (201)
Media > Books (784)
Media > DVDs & Videos (839)
Media > Music & Sound Recordings (855)
Software > Video Game Software (1279) (includes computer games)

Note: Make sure that you provide the full category specification. Do not only provide the highest-level category (e.g. “Apparel & Accessories (166)” or “Media (783)”).

File format Example entry
Text feeds

2271

or

Apparel & Accessories > Clothing > Dresses

XML feeds

<g:google_product_category>2271</g:google_product_category>

or

<g:google_product_category>Apparel &amp; Accessories &gt; Clothing &gt; Dresses</g:google_product_category>

Content API v2 (JSON)

"googleProductCategory": "2271"

or

"googleProductCategory": "Apparel & Accessories > Clothing > Dresses"

Content API v2 (XML)

<google_product_category>2271</google_product_category>

or

<google_product_category>Apparel &amp; Accessories &gt; Clothing &gt; Dresses</google_product_category>

Important:

  • Follow these formatting guidelines to make sure we understand the data you're submitting:
    • Supported values: Predefined Google product category: the ID or the full path of the product category
      • Download a list of all Google product categories:
      • Download this list in another language, as needed: 
        • Select that language from the menu at the bottom of this article. These links will update to that language.
      • Prevent garbled text in the .txt version by using one of these methods:
        • Change your browser encoding to Unicode UTF-8. Learn how to change your browser encoding.
        • Download the .txt version: right-click on the link, and then click Save Link As
    • Limit: Use one category per product

For complete details, refer to google product category definition.

Optional pricing attributes

There are also some optional attributes that you can submit if they apply to you.

price [price] - National default price of the item

If product price is consistent across stores, use this attribute to submit this default price. Any store-specific prices that you include in the local product inventory data feed will override this attribute value.

Note: Google assumes the currency based on the country of the store location. If the currency is set at item level, make sure it complies to ISO 4217 Standard.

When to include: Recommended for all items.

Type price (float)
Text/Tab delimited example 299.99 USD
XML example <g:price>299.99</g:price>
sale price [sale_price] - Advertised sale price of the item

Use this attribute to submit the advertised sale price of the item.  

We recommend submitting the 'sale price effective date' attribute for any items with sale prices, as this will determine when your sale price should be live. If the 'sale price effective date' isn't submitted, the sale price will be in effect for that item for as long as it is submitted in your feed.

When to include: Recommended for items on sale.

Type number
Text/Tab delimited example 249.99
XML example <g:sale_price>249.99</g:sale_price>
sale price effective date [sale_price_effective_date] - Date range during which an item is on sale

Used in conjunction with sale price. This attribute indicates the date range during which the sale price applies. Learn more about the format for the sale price effective date. 

Note: Timezone is optional [YYYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]. If timezone is absent, Google assumes the local timezone for each store. Additionally, note that we use 24-hour time for the hour values.

Type Start and end dates separated by a forward slash (/). The start is specified by the format (YYYY-MM-DD), followed by the letter ‘T’, the time of the day when the sale starts, followed by an expression of the time zone for the sale, as defined by the ISO 8601 standard. The end date should be in the same format.

Text/Tab delimited example

UTC example: 2015-07-19T17:00:00Z/2015-07-27T05:00:00Z
PST example: 2015-07-19T09:00:00-08:00/2015-07-26T21:00:00-08:00
XML example <g:sale_price_effective_date>2015-07-19T17:00:00/2015-07-27T05:00:00</g:sale_price_effective_date>

Optional store pickup attributes

You can highlight the store pickup option by adding the following 4 attributes to your feed. Add these attributes to your local products feed for any items where the values are true in all stores (e.g. a customer can pick up the XYZ television in any of your stores nationally). For store-specific pickup information, add these attributes to your local product inventory feed.

pickup method - Store pickup option for the item

Specify whether store pickup is available for this offer and whether the pickup option should be shown as buy, reserve, or not supported

  • 'buy': the entire transaction occurs online
  • 'reserve': the item is reserved online and the transaction occurs in-store
  • 'not supported': the item is not available for store pickup
Type Text (string). Must be one of the 3 accepted values: 'buy', 'reserve', or 'not supported'
Example buy 
pickup SLA - Item store pickup timeline

Specify the expected date that an order will be ready for pickup, relative to when the order is placed.

  • 'same day': indicates that the item is available for pickup the same day that the order is placed, subject to cutoff times
  • 'next day': indicates that the item is available for pickup the following day that the order is placed. 
Type Text (string). Must be one of the 2 accepted values: 'same day' or 'next day'
Example same day  
pickup_link_template

When users click your store pickup button and your account is enabled for the store pickup feature, they’re sent to a store specific landing page on your website for the advertised product. Set the URL for this landing page with the pickup_link_template attribute.

Important: 

  • Include the store_code ValueTrack parameter. URL structures vary across websites. Store codes can be URL parameters, or part of the URL path. 
  • Verify and claim your website URL, and make sure the website URL registered in Merchant Center matches the domain in the pickup_link_template. If the website URL doesn’t match the registered domain, learn how to resolve this issue.
Type URL. (Must start with 'http://' or 'https://'.)
Example http://mikemart.com/123?store={store_code}
mobile_pickup_link_template

When users click your store pickup button and your account is enabled for the store pickup feature, they’re sent to a landing page on your website for the advertised product. 

The mobile_pickup_link_template attribute lets you include a URL to a mobile-optimized version of your landing page. This mobile version will be shown to users on mobile devices, like phones or tablets.

Important: 

  • Include the store_code ValueTrack parameter. URL structures vary across websites. Store codes can be URL parameters, or part of the URL path. 
  • Verify and claim your website URL, and make sure the website URL registered in Merchant Center matches the domain in the mobile_pickup_link_template. If the website URL doesn’t match the registered domain, learn how to resolve this issue.
Type URL. (Must start with 'http://' or 'https://'.)
Example http://mikemart.com/123?store={store_code}

Optional merchant hosted local storefront attributes

To use the merchant hosted local storefront, add the attributes adwords_redirect and link_template to your local products feed. You can also add the optional attribute mobile_link_template to deliver a merchant hosted local storefront optimized for mobile devices and track mobile clicks.

link_template

When users click your ad if your account is enabled for the merchant hosted local storefront feature, they’re sent to a landing page on your website for the advertised product. Set the URL for this landing page with the link_template attribute.

Important: 

  • Include the store_code ValueTrack parameter. URL structures vary across websites. Store codes can be URL parameters, or part of the URL path. 
  • Verify and claim your website URL, and make sure the website URL registered in Merchant Center matches the domain in the link_template. If the website URL doesn’t match the registered domain, learn how to resolve this issue.
  • Include URL tracking parameters in adwords_redirect only. 
Type URL. (Must start with 'http://' or 'https://'.)
Example http://mikemart.com/123?store={store_code}
mobile_link_template

When users click your ad if your account is enabled for the merchant hosted local storefront feature, they’re sent to a landing page on your website for the advertised product.

The mobile_link_template attribute lets you include a URL to a mobile-optimized version of your landing page. This mobile version will be shown to users on mobile devices, like phones or tablets.

Important: 

  • Include the store_code ValueTrack parameter. URL structures vary across websites. Store codes can be URL parameters, or part of the URL path. 
  • Verify and claim your website URL, and make sure the website URL registered in Merchant Center matches the domain in the link_template. If the website URL doesn’t match the registered domain, learn how to resolve this issue.
  • Include URL tracking parameters in adwords_redirect only. 
Type URL. (Must start with 'http://' or 'https://'.)
Example http://mikemart.com/123?store={store_code}  
adwords_redirect

When users click your ad if your account is enabled for the merchant hosted local storefront feature, they’re sent to a landing page on your website for the advertised product. 

Use adwords_redirect to set a URL that includes tracking parameters, which can help you better understand traffic to your landing page.

Important: 

  • Include the store_code ValueTrack parameter. URL structures vary across websites. Store codes can be URL parameters, or part of the URL path. 
  • Verify and claim your website URL, and make sure the website URL registered in Merchant Center matches the domain in the link_template. If the website URL doesn’t match the registered domain, learn how to resolve this issue.
  • Once you've set up this attribute, a user who clicks on your ad will be taken to the location in the adwords_redirect attribute instead of the ones you set in the link_template or mobile_link_template attributes.
Type URL. (Must start with 'http://' or 'https://'.)
Example http://mikemart.com/123?store={store_code}

Optional additional attributes

Submit additional information about your products in your local products feed for more detailed local inventory ads. See the products feed specification for all possible attributes.

Was this article helpful?
How can we improve it?