> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/tools/audit/prebuilt-alert-list/keywords/keyword-conflicts.md).
# Keyword conflicts
Adalysis will alert you to negative keywords (ad group, campaign, or list-level) that are blocking a regular keyword. You'll see the alert on your **Audit alerts** screen.
* Click the icons in the **Matched search terms** column to see the matched search terms for each keyword.
* Use the toggle **Show last 30 days performance** to see performance metrics and quality scores.
{% hint style="warning" %}
**Important:** due to how Google matches synonyms, it's still possible for keywords with conflicts to receive impressions. However, your keywords won't run as expected until the conflicts are resolved.
{% endhint %}
### **Resolving keyword conflicts**
To fix a keyword conflict, start by **selecting** the keywords.
#### **Option 1 — Delete negative keywords**
This is the best option if the negative keyword was added by mistake or at the wrong level (e.g., at the campaign level instead of the ad group level).
#### **Option 2 — Pause keywords**
Pause keywords if you're moving them to another ad group, or if you don't want to bid on them anymore.
{% hint style="success" %}
In **Audit > Audit settings** > **Prebuilt** > **Keywords**, you can also create an [auto resolve ](/tools/audit/how-to-auto-resolve-alerts.md)to remove or pause conflicting keywords.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.adalysis.com/tools/audit/prebuilt-alert-list/keywords/keyword-conflicts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.