# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Launch paid campaigns for low-ranking but high-converting SEO / AEO pages.
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/launch-paid-campaigns-for-low-ranking-but-high-converting-seo-aeo-pages
Page: https://www.roadwayai.com/workflows/launch-paid-campaigns-for-low-ranking-but-high-converting-seo-aeo-pages
Library index: https://www.roadwayai.com/automation-library
---
name: launch-paid-campaigns-for-low-ranking-but-high-converting-seo-aeo-pages
description: >-
Finds organic pages that convert visitors well but rank low, using rankings from the Semrush or Ahrefs MCP, and launches paid search campaigns to buy the traffic SEO cannot win yet. Add the Peec AI MCP to include pages that AI answers do not cite. Needs the Semrush or Ahrefs MCP connected in Roadway.
---
# Launch paid campaigns for low-ranking but high-converting SEO / AEO pages
Source: https://www.roadwayai.com/workflows/launch-paid-campaigns-for-low-ranking-but-high-converting-seo-aeo-pages
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
Finds organic pages that convert visitors well but rank low, using rankings from the Semrush or Ahrefs MCP, and launches paid search campaigns to buy the traffic SEO cannot win yet. Add the Peec AI MCP to include pages that AI answers do not cite. Needs the Semrush or Ahrefs MCP connected in Roadway.
Finds organic pages that convert visitors well but rank low, using rankings from the Semrush or Ahrefs MCP, and launches paid search campaigns to buy the traffic SEO cannot win yet. Add the Peec AI MCP to include pages that AI answers do not cite. Needs the Semrush or Ahrefs MCP connected in Roadway. It runs the test with a fair split and waits for enough data before it calls a winner. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
## 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
aeo_citations, auto_approve, cost_per_goal_baseline, funnel_metrics, goal_metric, lookback_window, max_change_pct, min_sample_size, monthly_budget_cap, seo_page_performance, task_history
## Prompt
Launch paid campaigns for low-ranking but high-converting SEO / AEO pages
Use the Semrush or Ahrefs MCP to review organic rankings, and AI answer citations if available, for pages with a high organic conversion rate but weak visibility, and decide for each page:
1. Launch paid experiment
2. Add to an existing campaign
3. Hold
4. Skip
Context and defaults (use these; don't ask):
- Organic rankings, clicks and conversions per page and query: use the Semrush or Ahrefs MCP connected in Roadway, or [set this to your own SEO page performance] if you already have it. If neither is available, say so and stop.
- AI answer citations: [set this to your own AEO citations], or the Peec AI MCP if it is connected in Roadway. If neither is available, say so and skip the citation rules.
- 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 over the lookback window, and state the number.
- The minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- 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:
- Candidate pages convert organic visitors to [set this to your own goal metric] clearly better than the site average but rank low for their main queries, or (when citation data is available) are not cited in AI answers for those topics. Ignore pages with too little organic traffic to read in [set this to your own lookback window].
- Launch paid experiment: build a Google Search (and Microsoft, via import) ad group with exact and phrase match on the page's main queries from the MCP's keyword report and RSA copy that mirrors the page's H1 and value prop. For ChatGPT, build an ad group whose context hints describe the questions the page answers.
- Add to an existing campaign when an ad group already covers the intent but sends traffic to a weaker page. Swap the final URL and test.
- Hold when the page is already climbing in the rankings. Skip pages whose queries are informational with no commercial intent.
- Judge experiments on cost per [set this to your own goal metric] vs the baseline cost per goal after the minimum number of conversions, and share winning paid queries back to the SEO team as content and link-building priorities.
- 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:
SEO / AEO paid experiment report
Summary:
The pages found, the experiments launched by channel, and early results.
Launch paid experiment:
- [page] - [reason]
Add to an existing campaign:
- [page] - [reason]
Hold:
- [page] - [reason]
Skip:
- [page] - [reason]
Experiment sheet:
- [page] - [channel] - [queries / context hints] - [ad copy]
## Run it in Roadway
https://www.roadwayai.com/workflows/launch-paid-campaigns-for-low-ranking-but-high-converting-seo-aeo-pages
Launch paid campaigns for low-ranking but high-converting SEO / AEO pages
Launch paid campaigns for low-ranking but high-converting SEO / AEO pages
Finds organic pages that convert visitors well but rank low, using rankings from the Semrush or Ahrefs MCP, and launches paid search campaigns to buy the traffic SEO cannot win yet. Add the Peec AI MCP to include pages that AI answers do not cite. Needs the Semrush or Ahrefs MCP connected in Roadway.
Finds organic pages that convert visitors well but rank low, using rankings from the Semrush or Ahrefs MCP, and launches paid search campaigns to buy the traffic SEO cannot win yet. Add the Peec AI MCP to include pages that AI answers do not cite. Needs the Semrush or Ahrefs MCP connected in Roadway. It runs the test with a fair split and waits for enough data before it calls a winner. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
