# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Write SEO briefs for paid keywords that prove they convert.
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/write-seo-briefs-for-paid-keywords-that-prove-they-convert
Page: https://www.roadwayai.com/workflows/write-seo-briefs-for-paid-keywords-that-prove-they-convert
Library index: https://www.roadwayai.com/automation-library
---
name: write-seo-briefs-for-paid-keywords-that-prove-they-convert
description: >-
When a non-brand paid search keyword keeps converting at or under your baseline and no page of yours ranks for it, writes an SEO brief so organic can take over some of that spend. Needs the Semrush or Ahrefs MCP connected in Roadway.
---
# Write SEO briefs for paid keywords that prove they convert
Source: https://www.roadwayai.com/workflows/write-seo-briefs-for-paid-keywords-that-prove-they-convert
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
When a non-brand paid search keyword keeps converting at or under your baseline and no page of yours ranks for it, writes an SEO brief so organic can take over some of that spend. Needs the Semrush or Ahrefs MCP connected in Roadway.
Each run, it looks for non-brand paid keywords that keep converting at or under your baseline cost and checks Semrush or Ahrefs for a page of yours that ranks. When none does, it writes an SEO brief from the ads and search terms that already work, so organic can take over some of that spend. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. You get a short report with the numbers behind every line, so you can check it yourself.
## 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
cost_per_goal_baseline, creative_library, funnel_metrics, goal_metric, min_sample_size, page_volume_threshold, slack_delivery, task_history
## Prompt
Write SEO briefs for paid keywords that prove they convert
Find non-brand Google and Microsoft search keywords that keep converting at or under the baseline cost per goal, check with the Semrush or Ahrefs MCP whether any page of ours ranks for them, and decide for each keyword:
1. Write SEO brief
2. Already covered
3. Not ready yet
Context and defaults (use these; don't ask):
- Rankings: use the Semrush or Ahrefs MCP connected in Roadway. If neither is connected, say so and stop. Roadway has no native ranking data.
- 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 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 minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- The creative library: [set this to your own creative library]. If not set, use the ad platform's asset performance and Task History.
- Where briefs go: a Notion MCP connected in Roadway. If none is connected, send each brief to [set this to your own slack delivery].
- The delivery channel: [set this to your own slack delivery]. If Slack isn't connected, deliver in the run's thread.
Rules:
- A keyword qualifies when it's non-brand, clears [set this to your own page volume threshold], has converted at or under [set this to your own cost per goal baseline] for 3 runs in a row with at least [set this to your own min sample size] goal events, and the MCP shows no page of ours in the top 10.
- Write SEO brief: target query, search intent, the winning ad headlines and angles for that keyword, the questions people ask in the search terms report, and the landing page that converts best for it today.
- Already covered: a page of ours ranks in the top 10. Say which page and its position.
- Not ready yet: the keyword is close but hasn't held for 3 runs in a row.
- No spend changes. This workflow only writes briefs.
- Briefs that start from ChatGPT Ads contexts belong to the ChatGPT Ads to SEO workflow. This one starts from search keywords.
- Judge everything on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions, and check [set this to your own task history] so you don't repeat a finding the team already acted on. This workflow doesn't change budgets, bids or ads.
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:
Paid-to-SEO brief report
Summary:
Keywords that qualified, briefs written and where they were saved.
Write SEO brief:
- [keyword] - [reason]
Already covered:
- [keyword] - [reason]
Not ready yet:
- [keyword] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/write-seo-briefs-for-paid-keywords-that-prove-they-convert
Write SEO briefs for paid keywords that prove they convert
Write SEO briefs for paid keywords that prove they convert
When a non-brand paid search keyword keeps converting at or under your baseline and no page of yours ranks for it, writes an SEO brief so organic can take over some of that spend. Needs the Semrush or Ahrefs MCP connected in Roadway.
Each run, it looks for non-brand paid keywords that keep converting at or under your baseline cost and checks Semrush or Ahrefs for a page of yours that ranks. When none does, it writes an SEO brief from the ads and search terms that already work, so organic can take over some of that spend. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. You get a short report with the numbers behind every line, so you can check it yourself.