# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Spin up landing pages once keyword volume and profitability clear your bar.
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/spin-up-landing-pages-once-keyword-volume-and-unit-economics-clear-your-bar
Page: https://www.roadwayai.com/workflows/spin-up-landing-pages-once-keyword-volume-and-unit-economics-clear-your-bar
Library index: https://www.roadwayai.com/automation-library
---
name: spin-up-landing-pages-once-keyword-volume-and-unit-economics-clear-your-bar
description: >-
Drafts a dedicated landing page when a keyword or ad theme's volume and profitability clear your thresholds, then sets up a test against the current page. Needs a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway.
---
# Spin up landing pages once keyword volume and profitability clear your bar
Source: https://www.roadwayai.com/workflows/spin-up-landing-pages-once-keyword-volume-and-unit-economics-clear-your-bar
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
Drafts a dedicated landing page when a keyword or ad theme's volume and profitability clear your thresholds, then sets up a test against the current page. Needs a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway.
Each run, the agent looks for keywords and ad themes that send enough traffic to a generic page and are profitable enough to deserve their own. For the ones that clear your bar it uses a page builder MCP such as Webflow, Framer, Lovable or Ploy to draft a dedicated page, with the keyword in the headline and only the proof and claims you have approved. It never publishes. After you approve and publish the page, it sets up an even test against the old page and keeps whichever converts better.
## 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_terms, cms_tool, cost_per_goal_baseline, funnel_metrics, goal_metric, lookback_window, max_change_pct, min_sample_size, monthly_budget_cap, page_volume_threshold, pay_back_target, proof_points, task_history, top_landing_pages, utm_template, win_bar
## Prompt
Spin up landing pages once keyword volume and profitability clear your bar
Find keywords, ad themes and audiences sending enough traffic to a generic page, and decide for each whether a dedicated landing page earns its place:
1. Build page and launch test
2. Build page, hold traffic
3. Not yet
4. Skip
Context and defaults (use these; don't ask):
- The monthly volume bar for building a dedicated page or campaign: [set this to your own page volume threshold]. If not set, 500 visits or searches a month.
- The top landing pages: [set this to your own top landing pages]. If not set, rank pages by Roadway lead rate ([set this to your own goal metric] ÷ new visitors) for the same intent over the lookback window.
- The analysis window for optimization decisions: [set this to your own lookback window]. If not set, 30 days.
- 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.
- Target months for a customer to pay back their acquisition cost: [set this to your own pay back target]. If not set, 12 months.
- The page builder for drafting pages (a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway): [set this to your own CMS tool]. If it isn't available, say so and skip the rules that depend on it.
- The proof points: [set this to your own proof points]. If not set, use only approved claims.
- 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 UTM parameter template: [set this to your own UTM template]. If it isn't available, say so and skip the rules that depend on it.
- Minimum conversions per variant before declaring a test: [set this to your own min sample size]. If not set, 30 conversions per variant.
- The win bar for calling a winner: [set this to your own win bar]. If not set, 95%.
- The brand and product names and their misspellings: [set this to your own brand terms]. If it isn't available, say so and skip the rules that depend on it.
- 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:
- Candidates: keywords or ad themes with at least [set this to your own page volume threshold] that all land on a homepage or a general page from [set this to your own top landing pages], and audiences with enough clicks in [set this to your own lookback window] to trust the pattern.
- Build only when profitability clears the bar: cost per goal at or under [set this to your own cost per goal baseline] or a payback inside [set this to your own pay back target], using Roadway-attributed [set this to your own goal metric], and the existing page's conversion rate below the best page for similar intent in [set this to your own top landing pages].
- Draft the page through [set this to your own CMS tool] as an unpublished draft and never publish it: the keyword or theme in the headline, the proof from [set this to your own proof points], claims only from [set this to your own approved claims], one CTA, and the same tracking and UTMs as the current page ([set this to your own UTM template]).
- Build page and launch test: after approval, and once a person has published the page, run it against the current page for 14 days or until each page has [set this to your own min sample size] conversions. The page builder MCP cannot split traffic, so use a second ad in the same ad group that points to the new page, or the testing tool on the site, and say which. Build page, hold traffic: when the page needs a legal, design or product review first.
- Keep the page only if it beats the old page on Roadway lead or conversion rate with enough data to call a clear winner ([set this to your own win bar]). Otherwise point the ads back at the old page and recommend archiving the page.
- Cap new pages at 3 per run, and never create a page for brand terms ([set this to your own brand terms]).
- 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:
Landing page spin-up report
Summary:
The keywords, ads and audiences that qualified, the pages drafted, and the results of pages already live.
Build page and launch test:
- [keyword or theme] - [reason]
Build page, hold traffic:
- [keyword or theme] - [reason]
Not yet:
- [keyword or theme] - [reason]
Skip:
- [keyword or theme] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/spin-up-landing-pages-once-keyword-volume-and-unit-economics-clear-your-bar
Spin up landing pages once keyword volume and profitability clear your bar
Spin up landing pages once keyword volume and profitability clear your bar
Drafts a dedicated landing page when a keyword or ad theme's volume and profitability clear your thresholds, then sets up a test against the current page. Needs a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway.
Each run, the agent looks for keywords and ad themes that send enough traffic to a generic page and are profitable enough to deserve their own. For the ones that clear your bar it uses a page builder MCP such as Webflow, Framer, Lovable or Ploy to draft a dedicated page, with the keyword in the headline and only the proof and claims you have approved. It never publishes. After you approve and publish the page, it sets up an even test against the old page and keeps whichever converts better.
