Give proven search queries deliberate keyword, ad-group, and landing-page coverage without creating duplicates or mixing intent. Use after a search-term review finds real demand worth owning.
Installs into .claude/skills of the current project.
Are you the author of Query To Keyword Promoter?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/kelpi-ai-query-to-keyword-promoter)
---
name: query-to-keyword-promoter
description: 'Give proven search queries deliberate keyword, ad-group, and landing-page coverage without creating duplicates or mixing intent. Use after a search-term review finds real demand worth owning.'
---
# Query to Keyword Promoter
## Doctrine
A converting search term deserves a clear home only when the account can answer its intent. Promotion is not copying every winner into Exact. Check existing coverage, choose a match type for the job, route it to an ad group with the right promise, and hold the proposal if the landing page or ad message is missing.
## When to use
- After search-term review finds converting or high-value queries that are only arriving through broader coverage.
- Use a connected Google Ads MCP for read-only context, or paste search terms, current keywords, negatives, ad groups, ads, final URLs, and business targets.
- Include conversion lag and downstream lead quality when those affect the verdict.
## Run it
```
Build a READ-ONLY query-to-keyword promotion plan. Use live account data for context if connected; otherwise use what I paste. Add nothing.
1. Confirm the date range, primary conversion, target CPA or ROAS, and conversion delay.
2. For each candidate query show: spend, conversions, value, CPA or ROAS, current triggering keyword, current match type, current ad group, and current final URL.
3. Check whether the same intent already has deliberate coverage. Do not create a duplicate just because the search term looks good.
4. For each real opportunity propose: keyword text, Exact or Phrase match, destination ad group, message promise, final URL, negative conflicts, and why this structure fits the query.
5. If the query needs a different promise or page, propose a new focused ad group or hold it. Do not route consultants into an agency ad group just because both are professional services.
6. Explain the match-type choice without promising that Exact or Phrase will match only one literal query.
7. Add a measurement plan with the success metric, comparison window, conversion-delay allowance, and review date.
Return opportunities, already covered queries, and held queries. Mark every proposed keyword or new ad group "approval required". End with "No changes were made."
```
## Guardrails
- Use performance and business fit, not search volume alone.
- Check current keywords, close intent, negatives, ad copy, and the final page before proposing a new keyword.
- One ad group should answer one clear search job. Shared industry labels are not enough to mix different buyer intents.
- If there is no credible page or message for the query, hold it rather than sending it to the homepage by default.
- Adding a keyword or ad group changes delivery. This skill drafts the change and never executes it.
## Good output looks like
A small coverage plan where every proposed keyword has evidence, a match-type reason, one clear ad-group home, a credible page, and an approval gate.