> 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/changelog-nl/2026/september/conversationele-attributen-voor-google-shopping-kanalen.md).

# Conversationele attributen voor Google Shopping-Kanalen

11 september 2026

### Wat is er nieuw?

Google heeft onlangs geïntroduceerd [conversatie-attributen](https://support.google.com/merchants/answer/17085370?hl=en\&sjid=5625477415808595011-EU) als onderdeel van hun nieuwe Merchant Api en Google AI-initiatieven. 

We hebben deze attributen toegevoegd aan Google Shopping-feed en Api-kanalen in Channable, waardoor je je productvermeldingen kunt verrijken en meer context kunt bieden Naar potentiële kopers. 

**Nieuwe attributen**

* `vraag_en_antwoord` 
* `documentkoppeling` 
* `gerelateerd product` 
* `titel van Itemgroep` 
* `variant_optie` 
* `populariteitsrang` 

Voor meer details over hoe Google elk specifiek attribuut gebruikt en welke formaten worden geaccepteerd, kijk je in [Google’s officiële documentatie](https://support.google.com/merchants/answer/17085370?hl=en\&sjid=5625477415808595011-EU).

### Wat je moet doen

Geen actie is vereist. Bestaande Google Shopping-API's en feeds blijven gewoon werken zoals voorheen. 

Je kunt deze attributen koppelen aan je interne velden in de **Mapping** of **Build** stap van je Google Shopping-kanalen als je wilt dat je producten verschijnen 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/changelog-nl/2026/september/conversationele-attributen-voor-google-shopping-kanalen.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.