Use this specification to format your product information to successfully show your local products on Google. Submit your product data in the right format. This allows you to create successful local inventory ads and free local product listings.
The product information that you submit using the attributes below forms the foundation for your ads and free local listings. Make sure that everything you submit is of the quality you would show to a customer.
This article lists all of the attributes that you can provide in your products feed to implement local inventory ads and free local listings.
Primary feeds
To use an existing primary feed that has not been enabled for local inventory ads or free local listings, you will need to enable the local extension and select your destinations. To enable local destinations:
- Sign in to your Merchant Center account.
- Click Products.
- Click Feeds.
- Select the primary feed that you wish to modify.
- Add local inventory ads or free local product listings as a destination for all countries and languages of this feed.
Google recommends submitting all of your products in a single feed for both local inventory ads and free local listings. For newly created feeds, all applicable feed destinations can be selected during feed creation. Learn how to create a primary feed. For existing feeds, use primary feed settings to opt in to local inventory ads and/or free local listings as additional destinations. If you need to exclude products from either Shopping ads or local inventory ads and free local product listings, you may use the excluded destination [excluded_destination] attribute. Learn more about excluded destination
If you have a legacy product feed created before 3 October 2019, this doesn't apply to you and you can continue to submit offers in separate feeds.
Submit a primary feed
File type: You can use either a delimited text file (recommended), XML or API.
Registering a new feed: Follow the standard steps to register a new feed.
Please note that products may take up to two days to appear after submission.
Important: Some attributes in this product data specification contain spaces and underscores. To make sure that you submit attributes with correct characters and spacing, follow the guidelines below for your file type:
- Tab-delimited feeds: Spaces are required. If the attribute has underscores, use a space instead of the '_'.
- XML feeds or XML API: Underscores are required and are converted into white space when received
- JSON API: Underscores are required and are converted into white space when received
Summary of attribute requirements
| Attribute | Submission requirements |
|---|---|
| Required for all products that you sell in shops. | |
|
Required for all new products with a GTIN assigned by the manufacturer. Optional (strongly recommended) for all other products. |
|
|
Required for all new products (except movies, books and musical recording brands). Optional for all other products. |
|
|
Required if your product is used or refurbished. Optional for new products. |
|
|
Certifications, such as energy efficiency ratings, associated with your product Available for EU and EFTA countries and the UK Required for products that require certain certification information to be shown in your Shopping ads or free listings, for example due to local energy efficiency labelling regulations Optional for all other products Note: If you aren't able to locate your product in the EU EPREL database, you can use the energy efficiency class attributes instead for a limited transition period.
|
Consult the EU energy efficiency regulations or any applicable local law to determine if you need to provide this attribute. |
|
Energy efficiency class Minimum energy efficiency class Maximum energy efficiency class |
Required if your products target any of the EU member states, the United Kingdom or Switzerland. Optional if your products don't target any of the EU member states, the United Kingdom or Switzerland. Note: These attributes are being deprecated. Please use the certification
[certification] attribute instead to show the EU energy efficiency class. |
|
Recommended if you're using a single primary feed to submit product data for both online and local offers. Use this attribute to exclude products that are not sold in shops from appearing in your local inventory ads and free local listings. |
|
|
Optional If you're using a legacy local products feed to submit product data for local offers, you may use these attributes to match the products that you sell both online and in store across your products feed and your local products feed. To do this, you have two options:
[condition] attribute in this feed. |
|
|
Sale price effective date |
Recommended Price
Required Price [unit_pricing_measure] and unit pricing base measure [unit_pricing_base_measure] are required when regulated by local laws or regulations. |
|
Collection method Collection SLA |
If you want to allow people to purchase products online and pick them up in store, you will need to provide these two attributes:
Important: From 1 September 2024, collection method Learn more about collect today, collect later for local inventory ads and collect later for Shopping ads. |
|
Link for merchant-hosted local shop front Mobile link for merchant-hosted local shop front |
Optional if you want to participate in a merchant-hosted local shop front. Link Link for merchant-hosted local shop front Mobile link for merchant hosted local shop front |
Important note (XML only): If you're 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 be processed correctly.
Required identification attributes
These attributes tell us basic information about your products and are required for all items.
[id] – An identifier of the item
The identifier for each item is unique across all shops, and cannot be reused between feeds of the same type for the same country in the same language.
When to include: Required for all of the items in your feed.
| Type | String |
| Text/tab-delimited example | 421486 |
| XML example | <g:id>421486</g:id> |
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, excluding 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)
- When an item is submitted, the ID can't change when you update your data feed or be used for a different product at a later time
- If you're using ID for Shopping campaigns, we recommend that you only use lowercase or case-insensitive characters
[title] – Title of the item
The name of your item. Google recommends that you include characteristics (such as colour or brand) in the title that differentiate the item from other products. If there's a match, Google may serve your online item or Google Catalogue data instead.
When to include: Required for all of the items in your feed.
| Type | Text (string), fewer 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 delivery' and do not use BLOCK CAPITALS.
- For variant products, you're required to include the common title of the variant items. For example, if 'Men's Pique Polo Shirt' is available in red and blue colours, you can have one of the following titles:
- Men's Pique Polo Shirt (can be used for both variants)
- Men's Pique Polo Shirt – Red (for the red shirt)
- Men's Pique Polo Shirt – Blue (for the blue shirt)
[description] – Description of the item
Include only information relevant to the product. Describe its most relevant attributes, such as size, material, intended age range, special features or other technical specifications. You should also include details about the product's visual attributes (e.g. shape, pattern, texture and design), since we may use this text to find your item.
We recommend that you enter around 500–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 of the items in your feed.
| Type | Text |
| Character limit | 5,000 |
| Text (TSV) | 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> |
Important:
- Make sure that you follow Google's editorial guidelines closely. For example, do not include any promotional text such as 'Free delivery', 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 shop or other websites
- Billing, payment or sales information
- References to internal categorisation systems, for example: 'Toys & Games > Toys > Baby Dolls'
- Comparisons to other products beyond the item that you're selling, for example: 'even better/faster/larger than X'
- Details about other products, accessories or similar items available
[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 that customers see on product detail pages.
If you have multiple different images of the product, submit the main image using this attribute and include all other images in the additional image link [additional_image_link] attribute.
Image size:
- Submit the largest, highest-resolution, full-size image that you have for the product, up to 16 MB file size.
- Recommended image size is at least 800 x 800 pixels.
- For clothing 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 between 75–90% of the full image.
When to include: Required for all of the items in your feed.
| Type | URL (Must start with 'http://' or 'https://') |
| Character limit | 2,000 |
| Text (TSV) | http://www.example.com/image1.jpg |
| XML (feeds) | <g:image_link>http://www.example.com/image1.jpg |
By meeting the requirements and recommendations below, you can improve the shopping experience for customers.
Requirements:
- You must have an image of an item in order to submit it
- 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 colour images that are only a square of colour, except for products in the 'Vehicle Paint' (3812), 'Craft Paint, Ink & Glaze' (505378) and 'Painting Consumables' (503740) categories
- Images containing promotional elements (for example: calls to action such as 'buy', service-related information such as extended warranty, free delivery, 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 of whether 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 (for example: 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 multipacks 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 colour
[color], pattern[pattern]and material[material]attributes, or your item might be disapproved.
Recommendations:
- If you can't 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 colour, each individual variant item that you submit must have an image that displays the product in a single colour.
- The main image should be taken on a solid white, grey or light-coloured 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
[additional_image_link]attribute.
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).
- Google recommends 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 makes sure that Google can correctly crawl your images.
Cropping:
We may automatically crop your image to focus more on the product.
[condition] – Condition or state of the item
Google allows the promotion of quality second-hand products. Google also allows the promotion of refurbished products as long as they comply with local laws and regulations and with our policies.
There are only three accepted values:
- New
[new]: The product is brand new and has never been used. It is unopened in its original packaging. - 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 if your product is used or refurbished. Optional for new products.
| Type | Only three values are accepted:
|
| Text (TSV) |
|
| XML | <g:condition>used</g:condition> |
Important: If you're submitting the attribute names in English, you'll need to 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. 8-digit UPC-E codes should be converted to 12-digit codes.
- EAN (in Europe/GTIN-13): 13-digit number.
- JAN (in Japan/GTIN-13): 8 or 13-digit number.
- ISBN (for books): 10 or 13-digit number. 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.
| Where to include | Required for all new products with a GTIN assigned by the manufacturer |
| 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 of the item
When to include: Required for all new products (except movies, books and musical recording brands). Optional for all other products.
| Type | Text |
| Character limit | 70 |
| Text (TSV) | Acme |
| XML (feeds) | <g:brand>Acme</g:brand> |
Important: Do not provide your shop name as the brand unless you manufacture the product.
Certification [certification] – Certification of the item
[certification] attribute to describe certifications associated with a product, such as energy efficiency ratings.[certification] attribute in your product data for applicable products. Google will look up your product in the EU EPREL database and render the appropriate energy efficiency class in graphical or textual form on your Shopping ads and free listings. For example:[energy_efficiency_class] attributes until the end of the transition period on 1 September 2024.Sub-attributes:
- Authority
[certification_authority](required): The authority or certification body responsible for issuing the certification. At this time, we only support the values 'EC' or 'European_Commission'. - Name
[certification_name](required): The name of the certification. At this time, we only support the value 'EPREL', which represents energy efficiency certifications in the EU European Product Registry for Energy Labelling (EPREL) database. - Code
[certification_code](required): The code of the certification. For example, for the EPREL certificate with the link https://eprel.ec.europa.eu/screen/product/dishwashers2019/123456, the code is 123456.
| Type | Text |
| Text (TSV) | EC:EPREL:123456 |
| XML | <g:certification> |
Required energy efficiency class attributes (EU only)
[certification] attribute instead to show the EU energy efficiency class with your ads and free listings.[energy_efficiency_class] attributes during the transition period ending on 1 September 2024.[energy_efficiency_class], minimum energy efficiency class [min_energy_efficiency_class], maximum energy efficiency class [max_energy_efficiency_class]
When to include: It's strongly recommended that you submit the energy efficiency class, minimum energy efficiency class and maximum energy efficiency class attributes for applicable products. You might need to provide this class for these types of products:
| Refrigerators | Ovens |
| Freezers | Water heaters |
| Washing machines | Hot water storage appliances |
| Tumble dryers | Air conditioners |
| Combined washer-dryers | Electrical lamps |
| Wine-storage appliances | Luminaires |
| Dishwashers | Televisions |
| Type |
Accepted values:
|
| Text (TSV) |
A+ |
| XML example | <g:energy_efficiency_class>A+</g:energy_efficiency_class> |
Important:
- The minimum energy efficiency class
[min_energy_efficiency_class]value must be smaller than the maximum energy efficiency class[max_energy_efficiency_class]value. For example, your scale must run from A to D rather than D to A. - The energy efficiency class
[energy_efficiency_class]value that you provide must be within the range of the minimum energy efficiency class value and the maximum energy efficiency class value. For example, if your range runs from A to D, your energy efficiency class value may not be G.
Recommended exclusion attributes
You can use the excluded destination [excluded_destination] attribute to exclude products that are ineligible for a particular destination. Use it to control the different locations where your content can appear. For example, you could use this attribute if you want a product to appear in a Shopping ads campaign, but not in local offers.
When to include: Recommended if you want to prevent your product from participating in certain types of ads and listings.
Supported values:
- Shopping ads
[Shopping_ads]. Prevent your product offers from being shown in Shopping ads. Learn about Shopping ads - Display ads
[Display_ads]. Prevent your product offers from being shown in Dynamic Remarketing Ads. Learn about dynamic remarketing for retail - Local inventory ads
[Local_inventory_ads]. Prevent your product offers from being shown in local inventory ads. Learn more about local inventory ads - Free listings
[Free_listings]. Prevent your product offers from being shown in free listings. Learn more about showing your products for free on Google - Free local listings
[Free_local_listings]. Prevent your local product offers from being shown for free on Google. Learn more about listing your local products for free on Google
Shopping Actions, Surfaces across Google, Local surfaces across Google. These values will still be accepted, but we recommend that you update your products to include the new values for these destinations: Buy_on_Google_listings, Free_listings, Free_local_listings.Format
Follow these formatting guidelines to make sure that we understand the data that you're submitting.
| Supported values | Shopping_ads, Display_ads, Local_inventory_ads, Free_listings, Free_local_listings |
| Repeated field | Yes |
| File format | Example value |
| Text feeds | Display_ads |
| XML feeds | <g:excluded_destination>Display_ads</g:excluded_destination> |
Repeated fields
Text
To submit multiple destinations that you would like to exclude, submit the attribute multiple times, once for each destination (recommended). For example:
| Product data for an orthopaedic dog bed | |
| Attribute | Value |
Title [title] |
XXL orthopaedic dog bed |
Excluded destination [excluded_destination] |
Display_ads |
Excluded destination [excluded_destination] |
Shopping_ads |
You can also separate each destination with a comma (,):
Display_ads, Shopping_ads
XML
To submit multiple destinations to exclude for an XML feed, include a separate attribute for each excluded destination:
<g:excluded_destination>Display_ads</g:excluded_destination>
<g:excluded_destination>Shopping_ads</g:excluded_destination>
For more format API information, see the Content API for Shopping
Matching attributes if you are using a legacy local products feed (optional)
[webitemid] – Match online and local IDs
If you can't match the ID [id] attribute in your local products feed to the ID in your products feed, you can use the matching ID for matching. You'd submit different values for your ID, but the same value for matching ID and ID. This should always match the ID of the corresponding variant in your products feed, if one exists.
Since matching ID is only used for matching, multiple items may share the same matching ID 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 product.
| Type | Text (string) |
| Text (TSV) | 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, with the exception of 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 matching ID
[webitemid]can't change when you update your data feed or be used for a different product at a later point in time
[gtin] – Global Trade Item Number (GTIN) of the item
In this attribute, you'll 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 ID [id] attribute to match, you'll need to use either matching ID [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 (TSV) | 0606449056822 |
| XML example | <g:gtin>0606449056822</g:gtin> |
[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 ID [id] attribute to match, you'll need to use either matching ID [webitemid] or unique product identifiers as the matching attributes.
If you're using any unique product identifiers to match, you need to include condition in this feed.
| Type | Text (string) |
| Text (TSV) | RND2150 |
| XML example | <g:mpn>RND2150</g:mpn> |
[brand] – Brand of the item
When to include: If you sell your products both in-store and online and cannot use the ID [id] attribute to match, you'll need to use either matching ID [webitemid] or unique product identifiers as the matching attributes.
If you're using any unique product identifiers to match, you need to include condition in this feed.
| Type | Text (string) |
| Text (TSV) | Netgear |
| XML example | <g:brand>Netgear</g:brand> |
Clothing
Clothing requires several additional attributes in the primary feed:
[item_group_id] – Shared identifier for all variants of the same product
All items that are variants of the same product need the same item group ID value. If you have a 'Parent SKU' that's shared by all variants of a product, you can provide that as the item group ID value.
When to include: Required for Brazil, France, Germany, Japan, the UK and the US for all items with variants that use these detailed product attributes: colour [color], size [size], pattern [pattern], material [material], age group [age group], gender [gender], size type [size type] and size system [size_system]. Recommended for all other countries.
| Type | Alphanumeric code |
| Character limit | 50 |
| Text (TSV) | AB12345 |
| XML (feeds) | <g:item_group_id>AB12345</g:item_group_id> |
Important:
- The item group ID
[item_group_id]attribute is different from the ID[id]attribute. An item group ID attribute has 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 the item group ID should 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'll automatically look for variant attributes. If an item uses an item group ID, make sure that the item has at least one detailed product attribute.
[color] – Colour of the item
This defines the dominant colour(s) of an item. When a single item has multiple colours, you can submit up to two additional values as accent colours:
- Combine the colours with '/' in order of prominence (dominant colour first, then up to two accent colours). For example, a black shoe with green accents should have a colour value of 'Black/Green'. In the case of non-deformable goods in Clothing like jewellery or wooden accessories where finishes or materials are equivalent to colour, the finish or material name can be submitted in the colour
[color]attribute (e.g. 'Mahogany' vs 'Stainless Steel' vs 'Rose Gold'). - If you're using XML, represent the '/' with '#47;'
When to include: Required for all products in an item group that vary by colour and all clothing items in feeds that target Brazil, France, Germany, Japan, the UK and the US. Recommended for all products for which colour is an important, distinguishing attribute.
| Type | Text |
| Character limit | 100 |
| Text (TSV) | Black |
| XML (feeds) | <g:colour>Black</g:colour> |
What not to include:
- Colour values that contain numbers (e.g. '0 2 4 6 8').
- Colour values that contain non-alphanumeric characters (e.g.
#fff000). - Single letter colour values (e.g. 'G') in Latin-based languages. Single-letter colour values in Chinese/Japanese/Korean languages (e.g. '红') are acceptable.
- Colour values that reference the product or product image (e.g. 'see image').
- Descriptive values that are not actually valid colour names (e.g. multicolour, various, variety, see image, N/A).
- Long colour values exceeding 40 characters.
- Long colour values that are aggregates of several other colours (e.g.
RedPinkBlue). Instead:- If you are trying to indicate multiple colours for a single item (not product variants), specify a primary colour, optionally followed by at most 2 secondary colours, separated by a '/'. For example, replace
RedPinkBluewithRed/Pink/Blue. - If you are trying to indicate multiple colours for multiple similar items (product variants), submit these as separate products each with the same item group ID and a different colour value.
- If you are trying to indicate multiple colours for a single item (not product variants), specify a primary colour, optionally followed by at most 2 secondary colours, separated by a '/'. For example, replace
A note on invalid submissions:
- If you submit a colour value that violates the syntactic rules above, Google may reject the entire item at the time of feed submission.
- Google regularly verifies the correctness of the attributes that you submit, including colour. If the values provided are found to be incorrect, Google may remove all of your items from the Shopping tab.
Important:
- For variants, each different colour or colour combination must be submitted as its own item, in conjunction with the item group ID.
- Use consistent names of colours across variants of the same product, as well as across multiple products of the same category.
- The values that you provide may be displayed to customers, so provide values that they will be able to understand.
[size] – Size of the item
This indicates the size of a product. For 'Clothing & Accessories' items, you can also submit the size type [size_type] and size system [size_system] attributes to provide more details about your sizing.
- Submit only one attribute per item. If you provide multiple size attributes for the same item, only the first will be applied. Additional size attributes will be discarded, and you will receive a warning.
When to include: Required for all of the products in an item group that vary by size. Required for all of the clothing items in the 'Clothing & Accessories > Clothing' and 'Clothing & Accessories > Shoes' product categories in product data that targets Brazil, France, Germany, Japan, the UK and the US. Recommended for all of the products for which the size is an important, distinguishing attribute.
| Type | TextIf you're targeting the US, refer to the list of recognised values (US only) For all other countries, see example sizes. |
| Character limit | 100 |
| Text (TSV) | 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. Learn more about submitting clothing products
- 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 in the same category. For example, within a group of T-shirts, use 'S', 'M' and 'L' as sizes, not 'S', 'Medium' and 'Lrg'.
- You can use the same image for size variants if specific images aren't available, but we recommend that the link
[link]attribute leads to a page that specifies all of the details about the variant item. - The values that you provide may be displayed to customers, so provide values that they'll be able to understand.
- You can provide additional details about your sizing in the text string. For example, you can provide '3.5 Child' 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.
Sample sizing values
Sizing values can be difficult to represent across different types of clothing products. You are not required to provide these exact values but it may be helpful for you to standardise the size values of your clothing products. You can also use the size type [size_type] and size system [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 trousers: 24x30, 24x32, 24x34
Plus, Petite, Big, Tall, Inside Leg, etc.
- When an item applies to a special size group, like Plus, Petite, Maternity or Big and Tall, use the size type
[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.
- For Europe: 37, 38, 39, 40, 41, 42, 43, 44, 45.
[gender] – Gender of the item
When to include: Required for all of the products in an item group that vary by gender and for all clothing 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 three values are accepted:
|
| Text (TSV) | male |
| XML (feeds) | <g:gender>male</g:gender> |
Important
- If you're submitting the attribute names in English, then you'll need to 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' and 'watch bands' subcategories of 'Clothing & Accessories'.
[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 of the products in an item group that vary by age group and all clothing items in feeds that target Brazil, France, Germany, Japan, the UK and the US. Recommended for all products for which the age group is an important, distinguishing attribute.
| Format | There are only five accepted values:
|
| Text (TSV) | 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 age range 0–3 months and/or the single value 'newborn' [newborn]. - Infant
[infant]: Between 3–12 months old. Infant sizes are often identified by the age range 3–12 months. - Toddler
[toddler]: Between 1–5 years old. Toddler sizes are often identified by the age range 12–24 months or 1–5 years. - Children
[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 teenagers or older. All sizes within this age group have been manufactured to fit an adult or teenager in that age range.
- Newborn
- 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' and 'watch bands' subcategories of 'Clothing & Accessories'.
- If an item clearly isn't just for children, it should be declared as adult
[adult]because only one value may be submitted per item.
Pricing attributes (optional)
There are also some optional attributes that you can submit if they apply to you:
[price] – National default price of the item
If the product price is consistent across shops, use this attribute to submit this default price. Submit this price if product price is consistent across shops or if you are implementing the merchant-hosted local shop front basic feature.
Otherwise, any shop-specific prices that you include in the local products inventory feed will override this attribute value.
If you're implementing the merchant-hosted local shop front (basic) feature, the pricing attributes are required and must match the price on your landing page.
When to include: Recommended for all items.
| Type | Price (float) |
| Text (TSV) | 299.99 GBP |
| XML example | <g:price>299.99</g:price> |
[sale_price] – Advertised sale price of the item
Use this attribute to submit the advertised sale price of the item.
Google recommends submitting the sale price effective date [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's submitted in your feed.
When to include: Recommended for items on sale.
| Type | Number |
| Text (TSV) | 249.99 |
| XML example | <g:sale_price>249.99</g:sale_price> |
[sale_price_effective_date] – Date range during which an item is on sale
Used in conjunction with the sale price [sale_price] attribute. This attribute indicates the dates during which the sale price is effective. Learn more about sale price definitions
| 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. If the time zone is not specified, UTC is assumed. |
|
Text (TSV) |
UTC example: 2021-07-19T17:00:00/2021-07-27T05:00:00 PST example: 2021-07-19T09:00:00-08:00/2021-07-26T21:00:00-08:00 |
| XML | <g:sale_price_effective_date>2021-07-19T17:00:00/2021-07-27T05:00:00</g:sale_price_effective_date> |
Unit pricing measure [unit_pricing_measure] – Define the measure and dimension of your product
Use the unit pricing measure [unit_pricing_measure] attribute to define the measure and dimension of your product. This value allows customers to understand the exact cost per unit for your product.
When to include: Optional for each product, except when regulated by local laws or regulations.
| Type | Positive number + unit |
| Text (TSV) | 1.5 kg |
| XML example | <g:unit_pricing_measure>1.5kg</g:unit_pricing_measure> |
Unit pricing base measure [unit_pricing_base_measure] – Include the denominator for your unit price
[unit_pricing_measure], then use the unit pricing base measure to include the denominator for your unit price. To make the unit prices more comparable for all ads and free local listings on a page, yours might show a different base measure than what you provide here.| Type | Integer + unit |
| Text (TSV) | 100 g |
| XML example | <g:unit_pricing_base_measure>100 g</g:unit_pricing_base_measure> |
Click and collect attributes (optional)
You can highlight the click and collect option by adding the following two attributes to your feed. Add these attributes to your primary feed for any items where the values are true in all shops (for example, a customer can collect the XYZ television in any of your shops nationally).
Collection method[pickup_method] – Click and collect option for the item
Important: From 1 September 2024, collection method [pickup_method] will no longer be required to enable click and collect for your offers.
Specify whether click and collect is available for this offer and whether the collection option should be shown as buy, reserve, deliver to shop or not supported.
- Buy
[buy]: The entire transaction occurs online - Reserve
[reserve]: The item is reserved online and the transaction occurs in-store - Deliver to shop
[ship_to_store]: The item is purchased online and dispatched to a local shop for the customer to collect - Not supported
[not_supported]: The item is not available for click and collect
| Type | Text (string). Must be one of the specified values listed above. |
| Text (TSV) | buy |
| XML example | <g:pickup_method>buy</g:pickup_method> |
[pickup_SLA] – Item click and collect timeline
Specify the expected date that an order will be ready for collection, relative to when the order is placed.
- Same day
[same_day]: Indicates that the item is available for collection the same day that the order is placed, subject to cut-off times. - Next day
[next_day]: Indicates that the item is available for collection the day following the day that the order is placed. - 2-day
[2-day]: Indicates that the item will be dispatched to a shop for a customer to collect in two days. - 3-day
[3-day]: Indicates that the item will be dispatched to a shop for a customer to collect in three days. - 4-day
[4-day]: Indicates that the item will be dispatched to a shop for a customer to collect in four days - 5-day
[5-day]: Indicates that the item will be dispatched to a shop for a customer to collect in five days. - 6-day
[6-day]: Indicates that the item will be dispatched to a shop for a customer to collect in six days. - 7-day
[7-day]: Indicates that the item will be dispatched to a shop for a customer to collect in seven days. - Multi-week
[multi-week]: Indicates that the item will be dispatched to a shop for a customer to collect in more than one week.
| Type | Text (string). Must be one of the specified values listed above. |
| Text (TSV) | Same day [same_day] |
| XML example | <g:pickup_sla>same_day</g:pickup_sla> |
Merchant-hosted local shop front attributes (optional)
To use the merchant-hosted local shop front, add the attributes ads redirect [ads_redirect] and link for merchant-hosted local shop front [link_template] to your primary feed. You can also add the optional attribute mobile link for merchant-hosted local shop front [mobile_link_template] to deliver a merchant-hosted local shop front optimised for mobile devices and track mobile clicks.
[link]
When customers click your ad or designated free listing, if your account is enabled for the merchant-hosted local shop front (basic) feature, they're sent to a landing page on your website for the product. Set the URL for this landing page with the link [link] attribute.
Important:
- Use your verified domain name.
- Start with
httporhttps. - Use an encoded URL that complies with RFC 2396 or RFC 1738. For example, a comma would be represented as '%2C'.
- Don't link to an interstitial page unless legally required.
| Type | URL. (Must start with 'http://' or 'https://'.) |
| Text (TSV) | http://mikemart.com/123 |
| XML | <g:link>http://mikemart.com/123</g:link> |
[link_template]
When customers click your ad or free listing, if your account is enabled for the merchant-hosted local shop front (full) feature, they're sent to a landing page on your website for the product. Set the URL for this landing page with the link for merchant-hosted local shop front [link_template] attribute.
Important:
- Include the shop code {
store_code} ValueTrack parameter. URL structures vary across websites. Shop codes can be URL parameters or part of the URL path. - Verify and claim your website URL, and make sure that 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 the ads redirect
[ads_redirect]attribute only.
| Type | URL. (Must start with 'http://' or 'https://'.) |
| Text (TSV) | http://mikemart.com/123?store={store_code} |
| XML |
|
[mobile_link_template]
When customers click your ad or free listing, if your account is enabled for the merchant-hosted local shop front (full) feature, they're sent to a landing page on your website for the product.
The mobile link for merchant-hosted local shop front [mobile_link_template] attribute lets you include a URL to a mobile-optimised version of your landing page. This mobile version will be shown to customers on mobile devices, like phones or tablets.
Important:
- Include the shop code {
store_code} ValueTrack parameter. URL structures vary across websites. Shop codes can be URL parameters or part of the URL path. - Verify and claim your website URL, and make sure that the website URL registered in Merchant Center matches the domain in the link for merchant-hosted local shop front
[link_template]attribute. If the website URL doesn't match the registered domain, learn how to resolve this issue. - Include URL tracking parameters in ads redirect
[ads_redirect]only.
| Type | URL. (Must start with 'http://' or 'https://'.) |
| Text (TSV) | http://mikemart.com/123?store={store_code} |
| XML |
|
[ads_redirect]
When customers click your ad, if your account is enabled for the merchant-hosted local shop front feature, they're sent to a landing page on your website for the product.
Use ads redirect to set a URL that includes tracking parameters, which can help you better understand traffic to your landing page.
Important:
- Include the shop code {
store_code} ValueTrack parameter. URL structures vary across websites. Shop codes can be URL parameters or part of the URL path. - Verify and claim your website URL, and make sure that 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.
- When you set up this attribute, a customer who clicks on your ad will be taken to the location in the ads redirect
[ads_redirect]attribute instead of the ones that you set in the link for merchant-hosted local shop front[link_template]or mobile link for merchant-hosted local shop front[mobile_link_template]attributes.
| Type | URL. (Must start with 'http://' or 'https://'.) |
| Text (TSV) | http://mikemart.com/123?store={store_code} |
| XML |
|
Additional attributes (optional)
Submit additional information about your products in your primary feed for more detailed ads or listings. See the product data specification for all of the possible attributes.