> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/changelog/2026/september/conversational-attributes-for-google-shopping-channels.md).

# Conversational Attributes for Google Shopping channels

September 11, 2026

### What's new?

Google recently introduced [conversational attributes](https://support.google.com/merchants/answer/17085370?hl=en\&sjid=5625477415808595011-EU) as part of their new Merchant API and Google AI initiatives. 

We’ve added these attributes to Google Shopping feed and API channels in Channable, allowing you to enrich your product listings and provide more context to potential buyers. 

**New attributes**

* `question_and_answer` 
* `document_link` 
* `related_product` 
* `item_group_title` 
* `variant_option` 
* `popularity_rank` 

For more details on how Google uses each specific attribute and the accepted formats, check out [Google’s official documentation](https://support.google.com/merchants/answer/17085370?hl=en\&sjid=5625477415808595011-EU).

### What you need to do

No action is required. Existing Google Shopping APIs and feeds continue to run as before. 

You can map these attributes to your internal fields in the **Mapping** or **Build** step of your Google Shopping channels if you'd like your products to surface in Google AI search.


---

# 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://helpcenter.channable.com/changelog/2026/september/conversational-attributes-for-google-shopping-channels.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.