# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Open ad groups for category terms whose search volume is climbing.
The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude.
To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts.
In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/open-ad-groups-for-category-terms-whose-search-volume-is-climbing
Page: https://www.roadwayai.com/workflows/open-ad-groups-for-category-terms-whose-search-volume-is-climbing
Library index: https://www.roadwayai.com/automation-library
---
name: open-ad-groups-for-category-terms-whose-search-volume-is-climbing
description: >-
Uses keyword research to catch new category terms gaining search volume that you don't bid on yet, so you show up before the auction gets crowded. It skips terms when the volume data is too coarse to tell.
---
# Open ad groups for category terms whose search volume is climbing
Source: https://www.roadwayai.com/workflows/open-ad-groups-for-category-terms-whose-search-volume-is-climbing
From the Workflow Automation Library by Roadway.
## Before you use this outside Roadway
This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway.
You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected.
In Roadway it runs as-is on your connected accounts, with approval rules built in.
## What it does
Uses keyword research to catch new category terms gaining search volume that you don't bid on yet, so you show up before the auction gets crowded. It skips terms when the volume data is too coarse to tell.
Each run, it uses keyword research to find category terms whose search volume is clearly rising and that you don't bid on yet. When one clears your volume bar, it opens a small test ad group with copy from your value props, and skips terms where the data is too coarse to tell. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## Steps
1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names.
2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs.
3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes.
## Variables
approved_claims, auto_approve, cost_per_goal_baseline, cpa_guardrail, experiment_budget_pct, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, page_volume_threshold, task_history, value_props
## Prompt
Open ad groups for category terms whose search volume is climbing
Use keyword research to find terms related to our category whose search volume has clearly risen since the last run and that no keyword of ours covers, and decide for each term:
1. Open a test ad group
2. Watch
3. Skip
Context and defaults (use these; don't ask):
- Keyword data: Google Keyword Planner and Microsoft keyword research, plus the Semrush or Ahrefs MCP if one is connected in Roadway, since it gives finer volume data.
- The volume bar for building a dedicated page or campaign: [set this to your own page volume threshold]. If not set, 500 visits or searches since the last run.
- The value props: [set this to your own value props]. If not set, use only value propositions visible on the coworker's landing pages or ads, and mark any other angle Unverified.
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The baseline cost per goal: [set this to your own cost per goal baseline]. If not set, compute it: Roadway spend ÷ Roadway-attributed [set this to your own goal metric] for the same campaigns, and state the number.
- The cost guardrail: [set this to your own CPA guardrail], from the coworker's Guardrails. If not set, 1.3x the baseline cost per goal. A workflow qualification bar (for example "cost per lead under $100 to build a page") is not a ceiling.
- The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar.
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- A term qualifies when its volume has clearly risen for 3 runs in a row, clears [set this to your own page volume threshold], and no keyword of ours covers it.
- Skip terms where the volume data doesn't change between runs or is too coarse to show a rise, and say so.
- Open a test ad group on the term with exact and phrase match and copy from [set this to your own value props] at [set this to your own experiment budget percent].
- Cut the test when its cost per goal passes [set this to your own CPA guardrail] once it has enough spend and goal events to judge. If it converts, add it to the landing page workflow's list.
- Terms already showing up in our own search terms belong to the rising search language workflow. This one finds terms we don't see yet.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that already hurt performance. Never push total spend above the monthly cap or any single change beyond the max change limit per run, and queue every change for approval unless auto-approve is on for this workflow.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision.
- Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates.
- When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask.
- For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading.
- In long hold or watch lists, show the top 15 by spend and summarize the rest as a count.
Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers.
Report structure:
Rising category term report
Summary:
Rising terms found, ad groups opened, and early results.
Open a test ad group:
- [term] - [reason]
Watch:
- [term] - [reason]
Skip:
- [term] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/open-ad-groups-for-category-terms-whose-search-volume-is-climbing
Open ad groups for category terms whose search volume is climbing
Open ad groups for category terms whose search volume is climbing
Uses keyword research to catch new category terms gaining search volume that you don't bid on yet, so you show up before the auction gets crowded. It skips terms when the volume data is too coarse to tell.
Each run, it uses keyword research to find category terms whose search volume is clearly rising and that you don't bid on yet. When one clears your volume bar, it opens a small test ad group with copy from your value props, and skips terms where the data is too coarse to tell. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.