# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Mirror rising search language in ad copy.
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/mirror-rising-search-language-in-ad-copy
Page: https://www.roadwayai.com/workflows/mirror-rising-search-language-in-ad-copy
Library index: https://www.roadwayai.com/automation-library
---
name: mirror-rising-search-language-in-ad-copy
description: >-
Spots new phrases rising in your search terms and on-site searches, and works them into headlines and ad groups before competitors catch on.
---
# Mirror rising search language in ad copy
Source: https://www.roadwayai.com/workflows/mirror-rising-search-language-in-ad-copy
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
Spots new phrases rising in your search terms and on-site searches, and works them into headlines and ad groups before competitors catch on.
Spots new phrases rising in your search terms and on-site searches, and works them into headlines and ad groups before competitors catch on. When a phrase is showing up often enough in weekly search terms to trust the trend, and it grew clearly versus the prior period, it will add it to ad copy and a matching ad group, and keep it if it converts. It checks for this trigger every time it runs, so you can react within hours instead of at the 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, brand_voice, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, site_search_terms, task_history, top_search_terms
## Prompt
Mirror rising search language in ad copy
Compare the last 14 days of [set this to your own top search terms] and [set this to your own site search terms] with the prior 60 days, and decide for each rising phrase:
1. Add to headlines
2. Create ad group
3. Add negative
4. Ignore
Context and defaults (use these; don't ask):
- The highest-converting search terms across Google and Microsoft: [set this to your own top search terms]. If it isn't available, say so and skip the rules that depend on it.
- On-site and search query trends for new language: [set this to your own site search terms]. If it isn't available, say so and skip the rules that depend on it. Source: a PostHog MCP connected in Roadway (site-search events).
- 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 brand voice: [set this to your own brand voice]. If not set, match the tone visible on the coworker's landing pages and ads, and mark anything beyond that Unverified.
- 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 rising phrase is showing up often enough in weekly search terms to trust the trend, grew clearly versus the prior period, and is not in the current ad copy or ad groups.
- Add to headlines when the phrase fits the ad group's intent: write it in natural language, keep the current best headlines, and use only claims from [set this to your own approved claims].
- Create ad group when the phrase has its own intent or landing page. Add negative when it signals a mismatch (jobs, free, a competitor product you do not compete with).
- Review the ad copy rating and performance after 14 days and keep new language when conversion matches or beats the control.
- Check [set this to your own brand voice] and policy limits, and never add trademarked competitor terms to headline text.
- 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 hurt performance in the last 30 days. 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 search language report
Summary:
The new phrases found, the copy and ad groups changed, and results.
Add to headlines:
- [phrase] - [reason]
Create ad group:
- [phrase] - [reason]
Add negative:
- [phrase] - [reason]
Ignore:
- [phrase] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/mirror-rising-search-language-in-ad-copy
Spots new phrases rising in your search terms and on-site searches, and works them into headlines and ad groups before competitors catch on. When a phrase is showing up often enough in weekly search terms to trust the trend, and it grew clearly versus the prior period, it will add it to ad copy and a matching ad group, and keep it if it converts. It checks for this trigger every time it runs, so you can react within hours instead of at the next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
