> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/keystone/guides/products/product-linked-products.md).
# Linked products block
### Overview
If you have multiple versions of one product split into different product listing it may be hard for customers to find the option they want. Using the "Linked products" block you can display additional products as options on your product page.
How it works:
* The block shows all products from the collection assigned to the metafield
* All linked products must be in the same collection
* If the block is empty, the metafield isn’t set or the collection is empty
> Note: You can’t link individual products directly; you must use a collection as the intermediary.
***
### Enable the product block
1. Go to Online Store > Themes > Customize
2. Navigate to the product template then click "Add block" within the "Product" section
3. Move the block and add a label
* It's usually best to display the "Linked products" block above the "Buy buttons"
* Try adding a label that describes the additional linked products. If the additional products are variants of different color you could update the label to "Color".
4. Hit **Save**
***
### Create metafield definition
1. Navigate to **Settings** > **Custom data** > **Products**
2. Click **Add definition**
3. In the name field type "Linked collection"
4. Ensure the namespace and key field is `custom.linked_collection`
5. Set the data type as "Collection"
6. Hit **Save**
***
### Update metafield
1. Navigate to the product you'd like to update
2. Scroll to the bottom and select a collection for the metafield
3. Click **Save**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.brickspacelab.com/keystone/guides/products/product-linked-products.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.