Use the related product [related_product] attribute to indicate other products in your inventory that are related to this product, such as accessories, spare parts, or substitutes.
On this page
When to use
Optional for each product.
This attribute will be used in conversational AI experiences, for example to suggest other products that a user can purchase together with, or instead of, this product.
The related product[related_product] attribute can be used in all countries.
Format
Follow these formatting guidelines to make sure Google understands the data you're submitting. Learn more about how to submit attributes and attribute values.
| Type | Group attribute with 3 sub-attributes |
| Sub-attributes |
|
| Repeated field | Yes (up to 30) |
|
Schema.org property (What's this?) |
No |
| File format | Example value (for product that has 2 required parts and 1 accessory) |
| Text (TSV or CSV) data sources |
|
| XML data sources |
|
|
API data sources |
To format your data in the Merchant API, check the Merchant API resource. |
Minimum requirements
These are the requirements you'll need to meet to provide valid related products for your product:
- Submit all 3 of the relationship_type
[relationship_type], identifier type[identifier_type], and identifier[identifier]sub-attributes. - If a relationship type
[relationship_type]has multiple applicable related products, provide a separate related product[related_product]attribute for each of these related products. Don't comma-separate the identifiers as part of the identifier[identifier]sub-attribute. - Don't use special characters in the identifier
[identifier]sub-attribute. Only use alphanumeric, underscores, and dashes. Don't use commas, colons, double quotes, or backslashes.
Best practices
- A product can have multiple relationship types with other products, for example, it can have one or more substitutes, one or more accessories, and one or more required parts. Provide all of these relationship types and their related products with that relationship type.
Examples
A camera with 2 required parts (for example, a battery and a lens) and one accessory (for example, a carrying case) sold separately
In a Google Sheet, you’d submit this in one cell as follows:
| N |
O |
P | |
| 1 | ... | related_product | ... |
| 2 | ... | required_part:id:AZ7A,required_part:id:AZ7B,accessory:gtin:811571013579 |
... |
| 3 | ... | ... | ... |
Alternatively, you can also create multiple separate columns, each containing a single FAQ. For example, to have one column for each value, you can submit this in 3 cells as follows:
| N | O | P | Q | R | |
| 1 | ... | related_product | related_product | related_product | ... |
| 2 | ... | required_part:id:AZ7A |
required_part:id:AZ7B |
accessory:gtin:811571013579 |
... |
| 3 | ... | ... | ... | ... | ... |
In a tab-separated text file you can submit the FAQs in one cell as follows. Tab characters are represented by the <tab> symbol. Each sub-attribute value has been quoted for consistency:
|
Header: …<tab>related_product<tab>… product row: …<tab>required_part:id:AZ7A,required_part:id:AZ7B,accessory:gtin:811571013579<tab>… |
Alternatively, you can also create multiple separate columns, each containing one FAQ. For example, to have one column for each section, you can submit this in 3 tab-separated values as follows:
|
Header: …<tab>related_product<tab>related_product<tab>related_product<tab>… Product row: …<tab>required_part:id:AZ7A<tab>required_part:id:AZ7B<tab>accessory:gtin:811571013579<tab>… |