> 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/list-advertise/list-and-advertise-it/google/gestisci-and-ottimizzare-google-ads/google-testo-ads/gruppi-di-annunci/sospendere-manualmente-le-parole-chiave-su-google-testo-ads.md).
# Sospendere manualmente le parole chiave su Google Testo Ads
Questo articolo spiega l'impostazione “Consenti keyword messe in pausa manualmente” nella pagina Keyword di Channable e come influisce sulle keyword in Google Ads.
Se non hai ancora un account, puoi [creare un account di prova gratuito](https://www.channable.com/signup) o scoprire come Channable può aiutarti a [creare facilmente campagne dinamiche di annunci di testo per Google](https://www.channable.com/integrations/google-adwords-tool).
## Consenti keyword messe in pausa manualmente
Nella pagina Keyword troverai un'impostazione chiamata “Consenti keyword messe in pausa manualmente”:
Questa impostazione ti permette di mettere in pausa manualmente le keyword direttamente nel tuo account Google Ads senza che Channable annulli quella pausa.
* Per gestire nuovamente una keyword messa in pausa manualmente:
* Riattiva la keyword nel tuo account Google Ads, OPPURE
* Disattiva l'impostazione “Consenti keyword messe in pausa manualmente” in Channable.
Se hai selezionato le tue keyword per essere messe in pausa manualmente, potrai vedere quello stato nel [fase Anteprima](/list-advertise/list-and-advertise-it/google/gestisci-and-ottimizzare-google-ads/google-testo-ads/controllo-dei-tuoi-annunci-en-il-passaggio-vista-previa.md) del generatore di annunci:
{% hint style="info" %}
Qualsiasi keyword con lo status "Messa in pausa manualmente" non sarà più modificata da Channable.
{% endhint %}
---
# 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/list-advertise/list-and-advertise-it/google/gestisci-and-ottimizzare-google-ads/google-testo-ads/gruppi-di-annunci/sospendere-manualmente-le-parole-chiave-su-google-testo-ads.md?ask=&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.
