> 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-subtitles.md).

# Product subtitles

Enhance product displays with short descriptions using Metafields. Taglines provide additional context and appeal to customers.

#### How to Add Taglines or Subtitles

1. **Enable the Feature**
   * Go to **Theme Settings > Product Cards**
   * Check **"Enable product tagline"**
   * Click **Save**
2. **Create Metafield Definition**
   * Navigate to **Settings > Custom Data > Products**
   * Click **Add Definition**
   * Search for **"Product subtitle"** in the Name field
   * Select it and click **Save**
   * *Note:* Uses standard metafield `descriptors.subtitle`
3. **Add Taglines to Products**
   * Open the product you want to update
   * Scroll to **Product Metafields** at the bottom
   * Enter your tagline in the **"Product subtitle"** field
   * Click **Save**
   * *Tip:* Use bulk editor for multiple products

#### Best Practices

* **Keep it short:** 5-8 word impactful phrases
* **Highlight value:** Focus on key benefits
* **Be consistent:** Match your brand voice
* **Test & optimize:** Try different versions

#### Additional Notes

* Works with all product types
* Updates appear immediately
* Supports special characters
* Can be translated if using multilingual stores


---

# 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-subtitles.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.