> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/blogs/blog-posts/product-links-in-blog-posts.md).

# Product links in blog posts

Promote featured items from a blog post as product links

Broadcast can help you promote featured products right from a blog post. Add product links to any article, and Broadcast will add them to the sidebar with an image, product title, and direct link:

<figure><img src="https://2636770384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsD7BEEDU3B7WiEJlN0F7%2Fuploads%2FsrMeCGuXSgztNTPsnUnY%2Fproducts-links.jpg?alt=media&amp;token=a7ad235e-5acc-49d0-b792-e45df3653f07" alt=""><figcaption></figcaption></figure>

### How to

* In the Theme Editor, add or display the 'Related product&#x73;**'** block to the Default blog post template.&#x20;
* Add one or more product links directly into the article on any of your blog posts (Shopify Blog posts). Broadcast will then generate the "Related products" sidebar promotions from these links.&#x20;

Watch this quick video on how to correctly add the product link and title to any blog post page:

{% embed url="<https://www.loom.com/share/531cf9891e2447bd8c013912c0ca8a88?sid=566e7de0-16f3-494a-9d64-7bea30f7e453>" %}


---

# 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://broadcast.presidiocreative.com/blogs/blog-posts/product-links-in-blog-posts.md?ask=<question>&goal=<user_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.
