Product data specification

ID [id]

Your product’s unique identifier

Required

Example
A2B4

Syntax
Max 50 characters

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Use a unique value for each product.
• Use the product's SKU where possible.
• Keep the ID the same when updating your data.
• Use only valid unicode characters.
• Use the same ID for the same product across countries or languages.

Title [title]

or

Structured title [structured_title]

Your product’s name

Required

Example (Title [title]):
Mens Pique Polo Shirt

Example (Structured title [structured_title]): trained_algorithmic_media:"Stride & Conquer: Original Google Men's Blue & Orange Power Shoes (Size 8)"

Syntax
Title [title]: Plain text.Max 150 characters

Structured title [structured_title]: 2 sub-attributes:

• Digital source type [digital_source_type] (Optional): This sub-attribute supports 2 values:
  • Default [default]: Specifies that the title provided using the content [content] sub-attribute was not created using generative AI.
  • Trained algorithmic media [trained_algorithmic_media]. Specifies that the title provided using the content [content] sub-attribute was created using Generative AI.

If no value is specified, the Default [default] value is used.

• Content [content] (Required): The title text. Max 150 characters.

Schema.org property:

Title [title]: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

Structured title [structured_title]: No

• Use one of the title [title] and structured title [structured_title] attributes to clearly identify the product you are selling.
• For titles created using generative AI, use the structured title [structured_title] attribute, otherwise use the title [title] attribute.
• Accurately describe your product and match the title from your landing page.
• Don’t include promotional text like "free shipping," all capital letters, or gimmicky foreign characters.

For variants:

• Include distinguishing features such as color or size.

For mobile devices:

• Include “with contract” if sold with a contract.
• For the United States, include “with payment plan” if sold in installments.

For Russia:

• For books and other information products, include the age rating at the beginning of the title.

Description [description]

or

Structured description [structured_description]

Your product’s description

Required

Example (description [description]):
Made from 100% organic cotton, this classic red men’s polo has a slim fit and signature logo embroidered on the left chest. Machine wash cold; imported.

Example (structured description [structured_description]):

trained_algorithmic_media:"Transform your TV with the effortless power of Google Chromecast. This sleek device discreetly connects to your television, unlocking a world of wireless streaming and mirroring possibilities. From movies and TV shows to photos and presentations, cast your favorite content directly to the big screen with its integrated HDMI connector."

Syntax
Description [description]: Plain Text. Max 5000 characters

Structured description [structured_description]: 2 sub-attributes:

• Digital source type [digital_source_type] (Optional): This sub-attribute supports 2 values:
  • Default [default]: Specifies that the title provided using the content [content] sub-attribute was not created using generative AI.
  • Trained algorithmic media [trained_algorithmic_media]. Specifies that the title provided using the content [content] sub-attribute was created using Generative AI.

If no value is specified, the Default [default] value is used.

Content [content] (Required): The description text. Max 5000 characters

Schema.org property:

Description [description]: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

Structured description [structured_description]: No

• Use one of the description [description] and structured description [structured_description] attributes to accurately describe your product and match the description from your landing page.
• For descriptions created using generative AI, use the structured description [structured_description] attribute, otherwise use the description [description] attribute.
• Don’t include promotional text like "free shipping," all capital letters, or gimmicky foreign characters.
• Include only information about the product. Don’t include links to your store, sales information, details about competitors, other products, or accessories.
• Use formatting (for example, line breaks, lists, or italics) to format your description.

Link [link]

Your product’s landing page

Required

Example
http://www.example.com/asp/sp.asp?cat=12&id=1030

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Use your verified domain name.
• Start with http or https.
• Use an encoded URL that complies with RFC 2396 or RFC 1738.
• Don't link to an interstitial page unless legally required.

Image link [image_link]

The URL of your product’s main image

Required

Example
http:// www.example.com/image1.jpg

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

For the image URL:

• Link to the main image of your product.
• Start with http or https.
• Use an encoded URL that complies with RFC 2396 or RFC 1738.
• Make sure the URL can be crawled by Google (robots.txt configuration allowing Googlebot and Googlebot-image).

For the image:

• Accurately display the product.
• Use an accepted format: JPEG (.jpg/.jpeg), WebP (.webp), PNG (.png), non-animated GIF (.gif), BMP (.bmp), and TIFF (.tif/.tiff).
• Don't scale up an image or submit a thumbnail.
• Don't include promotional text, watermarks, or borders.
• Don't submit a placeholder or a generic image.

• All images created using generative AI must contain meta data indicating that the image was AI-generated (for example, the IPTC DigitalSourceTypeTrainedAlgorithmicMedia metadata tag). Don't remove embedded metadata tags such as the IPTC DigitalSourceType property from images created using generative AI tools, for example Product Studio. The following IPTC NewsCodes specify the type of digital source that was used to create the image, and should be preserved:

  • TrainedAlgorithmicMedia: The image was created using a model derived from sampled content.
  • CompositeSynthetic: The image is a composite that includes synthetic elements.
  • AlgorithmicMedia: The image was created purely by an algorithm not based on any sampled training data (for example, an image created by software using a mathematical formula).

Additional image link [additional_image_link]

The URL of an additional image for your product

Optional

Example
http://www.example.com/image1.jpg

Syntax
Max 2000 characters

Schema.org property: No

• Meet the requirements for the image link [image_link] attribute with these exceptions:
  • The image can include product staging and show the product in use.
  • Graphics or illustrations can be included.
• Submit up to 10 additional product images by including this attribute multiple times.

• All images created using generative AI must contain meta data indicating that the image was AI-generated (for example, the IPTC DigitalSourceTypeTrainedAlgorithmicMedia metadata tag). Don't remove embedded metadata tags such as the IPTC DigitalSourceType property from images created using generative AI tools, for example Product Studio. The following IPTC NewsCodes specify the type of digital source that was used to create the image, and should be preserved:

  • TrainedAlgorithmicMedia: The image was created using a model derived from sampled content.
  • CompositeSynthetic: The image is a composite that includes synthetic elements.
  • AlgorithmicMedia: The image was created purely by an algorithm not based on any sampled training data (for example, an image created by software using a mathematical formula).

3D model link [virtual_model_link]

Additional link to show a 3D model of your product.

Optional (available only in the US)

Example
https://www.google.com/products/xyz.glb

Syntax/type

URL (Must start with "https://" or "https://")

Up to 2000 characters

• Use a 3D model. Your file shouldn’t exceed 15MB. Textures in the file can be up to 2K (4K isn’t supported).
• Provide a valid URL in your product data. The link should point to a .gltf, or .glb file.
• Review your 3D model. You can use a validation tool to verify if your 3D model works properly.

Mobile link [mobile_link]

Your product’s mobile-optimized landing page when you have a different URL for mobile and desktop traffic

Optional

Example
http://www.m.example.com/asp/ sp.asp?cat=12 id=1030

Syntax
Max 2000 alphanumeric characters

Schema.org property: No

• Meet the requirements for the link [link] attribute.

Availability [availability]

Your product's availability

Required

Example
in_stock

Supported values

• In stock [in_stock]
• Out of stock [out_of_stock]
• Preorder [preorder]
• Backorder [backorder]

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Accurately submit the product's availability and match the availability from your landing page and checkout pages.
• Provide the availability date [availability_date] attribute if you submit preorder [preorder] or backorder [backorder] as the availability value.

Availability date [availability_date]

Required if product availability is set to preorder

The date a preordered product becomes available for delivery

Example
(For UTC+1)
2016-02-24T11:07+0100

Syntax

• Max 25 alphanumeric characters
• ISO 8601
  • YYYY-MM-DDThh:mm [+hhmm]
  • YYYY-MM-DDThh:mmZ

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Use this attribute if your product's availability is set to preorder. Provide a value up to one year in the future.
• The availability date should also be added to the product’s landing page and be clear to your customers (for example, “May 6, 2023”).
  • If an exact date can’t be provided, you can use an estimated date (for example, “May 2023”).

Cost of goods sold [cost_of_goods_sold]

Your product’s description

Optional

The costs associated with the sale of a particular product as defined by the accounting convention you set up. These costs may include material, labor, freight, or other overhead expenses. By submitting the COGS for your products, you gain insights about other metrics, such as your gross margin and the amount of revenue generated by your ads and free listings.

Example
23.00 USD

Syntax

• ISO 4217 codes
• Use '.' rather than ',' to indicate a decimal point
• Numeric

Schema.org property: No

• The currency must be in the ISO 4217 format. For example, USD for US dollars.
• The decimal point must be a period (.). For example, 10.00 USD.

Expiration date [expiration_date]

The date that your product should stop showing

Optional

Example
(For UTC+1)
2016-07-11T11:07+0100

Syntax

• Max 25 alphanumeric characters
• ISO 8601
  • YYYY-MM-DDThh:mm [+hhmm]
  • YYYY-MM-DDThh:mmZ

Schema.org property: No

• Use a date less than 30 days in the future.
• Note that a latency of several hours may occur.

Price [price]

Your products price

Required

Example
15.00 USD

Syntax

• Numeric
• ISO 4217

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Accurately submit the product's price and currency, and match with the price from your landing page and at checkout.
• Make sure that your landing page and the checkout pages include the price in the currency of the target country in a place that's straightforward to find.
• Ensure that the product can be purchased online for the submitted price.
• Make sure that any customer in the target country can buy the product for the submitted price, and without paying for a membership.
• Don't submit a price of 0 (a price of 0 is allowed for mobile devices sold with a contract).
• For products sold in bulk quantities, bundles, or multipacks.
  • Submit the total price of the minimum purchasable quantity, bundle, or multipack.
• For the US and Canada:
  • Don't include tax in the price.
• For all other countries:
  • Include value added tax (VAT) or Goods and Services Tax (GST) in the price.
• For additional options to submit price-related information, see the following attributes:
  • Unit pricing measure [unit_pricing_measure]
  • Unit pricing base measure [unit_pricing_base_measure]
  • Sale price [sale_price]
  • Subscription cost [subscription_cost]
  • Installment [installment]

Sale price [sale_price]

Your product's sale price

Optional

Example
15.00 USD

Syntax

• Numeric
• ISO 4217

Schema.org property: No

• Meet the requirements for the price [price] attribute.
• Submit this attribute (sale price) in addition to the price [price] attribute set to the non-sale price.
• Accurately submit the product's sale price, and match the sale price with your landing page and the checkout pages.

Sale price effective date
[sale_price_effective_date]

The date range during which the sale price applies

Optional

Example
(For UTC+1)
2016-02-24T11:07+0100 /
2016-02-29T23:07+0100

Syntax

• Max 51 alphanumeric characters
• ISO 8601
  • YYYY-MM-DDThh:mm [+hhmm]
  • YYYY-MM-DDThh:mmZ
• Separate start date and end date with /

Schema.org property: No

• Use together with the sale price [sale_price] attribute.
• If you don't submit this attribute (sale price effective date), the sale price always applies.
• Use a start date before the end date.

Unit pricing measure
[unit_pricing_measure]

The measure and dimension of your product as it is sold

Optional (except when required by local laws or regulations)

Example
1.5kg

Syntax
Numerical value + unit

Supported units

• Weight: oz, lb, mg, g, kg
• Volume US imperial: floz, pt, qt, gal
• Volume metric: ml, cl, l, cbm
• Length: in, ft, yd, cm, m
• Area: sqft, sqm
• Per unit: ct

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Use the measure or dimension of the product without packaging.
• Use a positive number.
• For variants:
  • Include the same value for item group ID [item_group_id] and different values for unit pricing measure.

Unit pricing base measure
[unit_pricing_base_measure]

The product’s base measure for pricing (for example, 100ml means the price is calculated based on a 100ml units)

Optional (except when required by local laws or regulations)

Example
100g

Syntax
Integer + unit

Supported integers
1, 10, 100, 2, 4, 8

Supported units

• Weight: oz, lb, mg, g, kg
• Volume US imperial: floz, pt, qt, gal
• Volume metric: ml, cl, l, cbm
• Length: in, ft, yd, cm, m
• Area: sqft, sqm
• Per unit: ct

Additional supported metric integer + unit combinations
75cl, 750ml, 50kg, 1000kg

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Optional when you submit the unit pricing measure [unit_pricing_measure] attribute.
• Use the same unit of measure for this attribute (unit pricing measure) and unit pricing base measure.
• Keep in mind that the price (or sale price, if active) is used to calculate the unit price of the product. For example, if the price [price] attribute is set to 3 USD, unit pricing measure is 150ml, and unit pricing base measure is set to 100ml, then the unit price is 2 USD / 100ml.

Installment [installment]

Details of an installment payment plan

Optional

Example (implies a 0 down payment and "finance" credit type)
6:30 EUR

Syntax
This attribute uses 4 sub-attributes:

• Months [months] (Required)
  Integer, the number of installments the buyer has to pay.
• Amount [amount] (Required)
  ISO 4217, the amount the buyer has to pay per month
• Downpayment [downpayment] (Optional)
  ISO 4217, the amount the buyer has to pay upfront as a one time payment. Note: if you don't submit the sub-attribute, the default value is 0 or “no down payment”.
• Credit type [credit_type] (Optional). This sub-attributes uses the following supported values:
  • Finance [finance]
  • Lease [lease]

Note: if you don't submit the sub-attribute, the default value is finance [finance]. This sub-attribute is only applicable for Vehicle Ads.

Schema.org property: No

• Match the installment option that’s visible on your landing page.
• Don't require a loyalty card.
• Make sure the price [price] attribute is the total price when paid in full up-front and use the installment [installment] attribute to indicate an alternative payment option using installments with an optional initial down payment.

Subscription cost [subscription_cost]

Details a monthly or annual payment plan that bundles a communications service contract with a wireless product

Optional (available in certain countries for showing wireless products and services only)

Example
month:12:35.00USD

Syntax

• Period [period] (Required)
  The duration of a single subscription period. This sub-attribute uses the following supported values:
  • Month [month]
  • Year [year]
• Period length [period_length] (Required)
  Integer, the number of subscription periods (months or years) that the buyer must pay.
• Amount [amount] (Required)
• ISO 4217, the amount the buyer must pay per month. When displaying this amount, Google may round up to the nearest whole unit of local currency to save space. The provided value must still exactly match the amount as shown on your site.

Schema.org property: No

• Include the total amount due at checkout in the price [price] attribute.
• When used in combination with the installment [installment] attribute, also include the total amount due at checkout in the downpayment [downpayment] sub-attribute of the installment [installment] attribute.
• Match the communications payment plan that you display on your landing page. The plan must be easy to find on the landing page.

Loyalty program [loyalty_program]

The loyalty program [loyalty_program] attribute allows setting up of member prices and loyalty points.

Optional (available for Japan and the United States only)

Example
my_loyalty_program:silver:10 USD::10:

Syntax
This attribute uses 6 sub-attributes:

• Program label [program_label] (Required)
  The loyalty program label set in your loyalty program settings in Merchant Center
• Tier label [tier_label] (Required)
  The tier label set in your program settings in Merchant Center, used to differentiate benefits between each tier.
• Price [price] (Optional) The member specific price for the program and tier. This will display alongside the non-member price to give shoppers an idea of the benefits of joining your program. Only available in the United States.
• Cashback [cashback_for_future_use] (Optional) Currently not available.
• Loyalty points [loyalty_points] (Optional) The points that the members gain on purchasing the product on your website. This needs to be a whole number.
• Member price effective date [member_price_effective_date] (optional): This sub-attribute allows merchants to specify when their member pricing benefit begins and ends.

Schema.org property: No

• Submit the loyalty program [loyalty_program] attribute to match the loyalty program label and tiers configured under your Merchant Center account.

Minimum price [auto_pricing_min_price]

The lowest price to which a product's price can be reduced. Google uses this information for features such as sale price suggestions, automated discounts or dynamic promotions.

Optional

Example
15.00 USD

Syntax

• Numeric
• ISO 4217

Schema.org property: No

• Submit a minimum price [auto_pricing_min_price] attribute.
  • If you are using the automated discounts or dynamic promotions feature, to specify the minimum price to which your product can be reduced.
  • If you want to limit sale price suggestions to a minimum price e.g. to comply with local pricing laws or to indicate a MAP (minimum advertised price).

Condition [condition]

The condition of your product at time of sale

Required if your product is used or refurbished

Optional for new products

Example
new

Supported values

• New [new]
  Brand new, original, unopened packaging
• Refurbished [refurbished]
  Professionally restored to working order, comes with a warranty, may or may not have the original packaging
• Used [used]
  Previously used, original packaging opened or missing

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

Adult [adult]

Indicate a product includes sexually suggestive content

Required (If a product contains adult content)

Example
yes

Supported values

• Yes [yes]
• No [no]

Schema.org property: No

• Set the value of this attribute to yes if this individual product contains nudity or sexually suggestive content. If you don't submit the attribute, the default value is no. Learn about the adult-oriented content policy
• If your website is generally focused on an adult audience and contains adult-oriented content with or without nudity, indicate that in your Merchant Center settings.

Multipack [multipack]

The number of identical products sold within a merchant-defined multipack

Required (For multipack products in Australia, Brazil, Czechia, France, Germany, Italy, Japan, Netherlands, Spain, Switzerland, the UK and the US)

Required for free listings on Google if you’ve created a multipack

Optional for all other products and target countries

Example
6

Syntax
Integer

Schema.org property: No

• Submit this attribute if you defined a custom group of identical products and are selling them as a single unit of sale (for example, you're selling 6 bars of soap together).
• Submit the number of products in your multipack. If you don't submit the attribute, the default value is 0.
• If the product's manufacturer assembled the multipack instead of you, don't submit this attribute.

Bundle [is_bundle]

Indicates a product is a merchant-defined custom group of different products featuring one main product

 Required (For bundles in Australia, Brazil, Czechia, France, Germany, Italy, Japan, Netherlands, Spain, Switzerland, the UK and the US)

 Required for free listings on Google if you’ve created a bundle containing a main product

Optional for all other products and target countries

Example
yes

Supported values

• Yes [yes]
• No [no]

Schema.org property: No

• Submit yes if you're selling a custom bundle of different products that you created, and the bundle includes a main product (for example, a camera combined with a lens and bag). If you don't submit the attribute, the default value is no.
• Don't use this attribute for bundles without a clear main product (for example, a gift basket containing cheese and crackers).

Certification [certification]

Certifications, such as energy efficiency ratings, associated with your product

Available for the 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 labeling regulations

Optional for all other products

Example

EC:EPREL:123456

Syntax

This attribute uses the following sub-attributes:

• Authority [certification_authority] Certification authority. Only "EC" or "European_Commission" supported.
• Name [certification_name] Name of the certification. Only "EPREL" supported.
• Code [certification_code] 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

Schema.org property: No

Consult EU energy efficiency regulations or any applicable local law to determine if you need to provide this attribute. This includes products covered by EU energy labels, for example:

• Fridges and freezers
• Dishwashers
• Televisions and other external monitors
• Household washing machines and washer-dryers
• Refrigerating appliances with a direct-sales function
• Light sources

Energy efficiency class [energy_efficiency_class]

Your product’s energy label

Available for the EU and EFTA countries and the UK

Optional (except when required by local law or regulations)

Example
A+

Supported values

• A+++
• A++
• A+
• A
• B
• C
• D
• E
• F
• G

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Include the legally required energy label.

• To be used in combination with minimum energy efficiency class [min_energy_efficiency_class] and maximum energy efficiency class [max_energy_efficiency_class] to create an energy efficiency label, for example, A+ (A+++ to G).

Minimum energy efficiency class [min_energy_efficiency_class]

Your product’s energy label

Available for the EU and EFTA countries and the UK

Optional (except when required by local laws or regulations)

Available for EU & CH only

Example
A+++

Supported values

• A+++
• A++
• A
• B
• C
• D
• E
• F
• G

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Include the legally required energy label.

• To be used in combination with energy efficiency class [energy_efficiency_class] and maximum energy efficiency class [max_energy_efficiency_class] to create an energy efficiency label, for example, A+ (A+++ to D).

Maximum energy efficiency class [max_energy_efficiency]

Your product’s energy label

Available for the EU and EFTA countries and the UK

Optional (except when required by local laws or regulations)

Available for EU & CH only

Example
D

Supported values

• A+++
• A++
• A
• B
• C
• D
• E
• F
• G

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Include the legally required energy label

• To be used in combination with energy efficiency class [energy_efficiency_class] and minimum energy efficiency class [min_energy_efficiency_class] to create a textual or graphical energy efficiency label, for example, A+ (G to A+++)

Age group [age_group]

The demographic for which your product is intended

Required (For all apparel products that are targeted to people in Brazil, France, Germany, Japan, the UK, and the US as well as all products with assigned age groups)

Required for free listings for all Apparel & Accessories (ID: 166) products

Optional for all other products and target countries

Example
infant

Supported values

• Newborn [newborn]
  0-3 months old
• Infant [infant]
  3-12 months old
• Toddler [toddler]
  1-5 years old
• Kids [kids]
  5-13 years old
• Adult [adult]
  Teens or older

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Include one value per product.
• For variants:
  • Include the same value for item group ID [item_group_id] and different values for age group.

Color [color]

Your product’s color(s)

Required (For all apparel products that are targeted to Brazil, France, Germany, Japan, the UK, and the US as well as all products available in different colors)

Required for free listings for all Apparel & Accessories (ID: 166) products

Optional for all other products and target countries

Example
Black

Syntax
Max 100 alphanumeric characters (max 40 characters per color)

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Don’t use a number such as "0", "2", or "4".
• Don’t use characters that aren’t alphanumeric such as "#fff000".
• Don’t use only one letter such as R. (For Chinese, Japanese, or Korean languages, you can include a single character such as 红.)
• Don’t reference the product or image such as “see image”.
• Don't combine several color names into one word, such as "RedPinkBlue". Instead, separate them with a /, such as "Red/Pink/Blue". Don’t use a value that isn’t a color, such as "multicolor", "various", "variety", "men's", "women's", or "N/A".
• If your product features multiple colors, list the primary color first.
• For variants:
  • Include the same value for item group ID [item_group_id] and different values for color [color]

Gender [gender]

The gender for which your product is intended

Required (Required for all apparel items that are targeted to people in Brazil, France, Germany, Japan, the UK, and the US as well as all gender-specific products)

Required for free listings for all Google Apparel & Accessories (ID: 166) products

Optional for all other products and target countries

Example
Unisex

Supported values

• Male [male]
• Female [female]
• Unisex [unisex]

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• For some Apparel & Accessories (ID:166) categories like Shoelaces (ID:1856), this attribute is recommended instead of required since these categories aren't dependent on gender.
• For variants:
  • Include the same value for item group ID [item_group_id] and different values for gender

Material [material]

Your product’s fabric or material

Required (if relevant for distinguishing different products in a set of variants)

Optional for all other products

Example
leather

Syntax
Max 200 characters

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• To indicate multiple materials for a single product (not variants), add a primary material, followed by up to 2 secondary materials, separated by a /.
  • For example, instead of "CottonPolyesterElastane", use "cotton/polyester/elastane".
• For variants:
  • Include the same value for the item group ID [item_group_id] attribute and different values for the material attribute

Pattern [pattern]

Your product’s pattern or graphic print

Required (if relevant for distinguishing different products in a set of variants)

Optional for all other products

Example
striped
polka dot
paisley

Syntax
Max 100 characters

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• For variants:
  • Include the same value for the item group ID [item_group_id] attribute and different values for the pattern attribute

Size [size]

Your product’s size

Required (Required for all apparel products in Apparel & Accessories > Clothing (ID:1604) and Apparel & Accessories > Shoes (ID:187) categories targeted to people in Brazil, France, Germany, Japan, the UK, and the US as well as all products available in different sizes)

Required for free listings for all Apparel & Accessories > Clothing (ID:1604) and Apparel & Accessories > Shoes (ID:187) products

Optional for all other products and target countries

Example
XL

Syntax
Max 100 characters

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• For variants:
  • Include this with the same value for item group ID [item_group_id] and different values for size [size]
• If sizes contain multiple dimensions, condense them into one value. For example, "16/34 Tall" is for neck size of 16 inches, sleeve length of 34 inches, and “Tall” fit
• If your item is one size fits all or one size fits most, you can use one_size, OS, one_size fits_all, OSFA, one_size_fits_most, or OSFM.
• For merchant-defined multipack products, submit the multipack quantity using the multipack [multipack] attribute. Do not submit the multipack quantity under the size attribute.

Size type [size_type]

Your apparel product’s cut

Optional (Available for apparel products only)

Example
maternity

Supported values

• Regular [regular]
• Petite [petite]
• Maternity [maternity]
• Big [big]
• Tall [tall]
• Plus [plus]

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Submit up to 2 values.
• If you don't submit the attribute, the default value is regular.

Size system [size_system]

The country of the size system used by your product

Optional (Available for apparel products only)

Example
US

Supported values

• US
• UK
• EU
• DE
• FR
• JP
• CN
• IT
• BR
• MEX
• AU

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• If you don't submit the attribute, the default value is your target country.

Item group ID [item_group_id]

ID for a group of products that come in different versions (variants)

Required (Brazil, France, Germany, Japan, the United Kingdom, and the US if the product is a variant)

Required for free listings for all product variants

Optional for all other products and target countries

Example
AB12345

Syntax
Max 50 alphanumeric characters

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Use a unique value for each group of variants. Use the parent SKU where possible.
• Keep the value the same when updating your product data.
• Use only valid unicode characters.
• Use an item group ID for a set of products that differ by one or more of these attributes:
  • Color [color]
  • Size [size]
  • Pattern [pattern]
  • Material [material]
  • Age group [age_group]
  • Gender [gender]
• Include the same attributes for each product in the item group. For example, if a product varies by size and color, submit size [size] and color [color] for every product that share the same value for item group ID [item_group_id].
• If your products differ by design elements that aren't represented by the attributes above, don't use item group ID.

Product length [product_length]

Your product's length

Optional

Example
20 in

Syntax
Number + unit

Supported values
1-3000

• Decimal values are supported

Supported units

• cm
• in

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Include as many of the product measurement attributes as possible.
• Use the same unit of measurement for each product dimension attribute (including product length, width, and height). Otherwise, the information won't be displayed.

Product width [product_width]

Your product's width

Optional

Example
20 in

Syntax
Number + unit

Supported values
1-3000

• Decimal values are supported

Supported units

• cm
• in

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Include as many of the product measurement attributes as possible.
• Use the same unit of measurement for each product dimension attribute (including product lengths, width, and height). Otherwise, the information won't be displayed.

Product height [product_height]

Your product's height

Optional

Example
20 in

Syntax
Number + unit

Supported values
1-3000

• Decimal values are supported

Supported units

• cm
• in

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Include as many of the product measurement attributes as possible.
• Use the same unit of measurement for each product dimension attribute (including product lengths, width, and height). Otherwise, the information won't be displayed.

Product weight [product_weight]

Your product's weight

Optional

Example
3.5 lb

Syntax
Number + unit

Supported values
0-2000

• Decimal values are supported

Supported units

• lb
• oz
• g
• kg

Schema.org property: Yes (Learn more about Merchant listing (Product, Offer) structured data on Google Search Central)

• Use the actual assembled product weight for this attribute.
• If your product comes in multiple pieces, for example, as part of a bundle, use the complete weight of all the pieces in the listing.

Product detail [product_detail]

Technical specifications or additional details of your product

Optional

Example
General:Product Type:Digital player

Syntax
This attribute uses 3 sub-attributes:

• Section name [section_name]: Max 140 characters
• Attribute name [attribute_name]: Max 140 characters
• Attribute value [attribute_value]: Max 1000 characters

Schema.org property: No

• Don't add information covered in other attributes, all capital letters, gimmicky foreign characters, promotion text, or list keywords or search terms.
• Don’t add information such as price, sale price, sale dates, shipping, delivery date, other time-related information, or your company’s name.
• Only provide an attribute name and value when the value is confirmed. For example, provide “Vegetarian=False” if a food product is not vegetarian.

Product highlight [product_highlight]

The most relevant highlights of your products

Optional

Example
Supports thousands of apps, including Netflix, YouTube, and HBO Max

Syntax
Max 150 characters

Schema.org property: No

• Use between 2 and 100 product highlights.
• Describe only the product itself.
• Don't list keywords or search terms.
• Don’t include promotional text, all capital letters, or gimmicky foreign characters.