> 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-space-it/2026/september/attributi-conversazionali-per-i-canali-google-shopping.md).

# Attributi conversazionali per i canali Google Shopping

11 settembre 2026

### Cosa c'è di nuovo?

Google ha introdotto recentemente [attributi conversazionali](https://support.google.com/merchants/answer/17085370?hl=en\&sjid=5625477415808595011-EU) come parte de le loro nuove iniziative Merchant Api y Google AI. 

Abbiamo aggiunto questi attributi Para il feed di Google Shopping y ai Canali Api en Channable, permettendoti Para arricchire le schede dei prodotti y fornire più contesto Para i potenziali acquirenti. 

**Nuovi attributi**

* `question_y_answer` 
* `document_link` 
* `related_product` 
* `ítem_group_title` 
* `variant_option` 
* `popularity_rank` 

Per maggiori dettagli su come Google utilizza ogni attributo specifico y i formati accettati, consulta [la documentazione ufficiale di Google](https://support.google.com/merchants/answer/17085370?hl=en\&sjid=5625477415808595011-EU).

### Cosa devi fare

Nessuna azione è richiesta. Le Api di Google Shopping y i feed esistenti continuano a funzionare come prima. 

Puoi mappare questi attributi ai tuoi campi interni en la **Mappatura** o **Crea** fase de i tuoi Canali Google Shopping si desideri che i tuoi prodotti appaiano en la ricerca Google AI.


---

# 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-space-it/2026/september/attributi-conversazionali-per-i-canali-google-shopping.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.