# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Test competitor comparison landing 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/test-competitor-comparison-landing-pages
Page: https://www.roadwayai.com/workflows/test-competitor-comparison-landing-pages
Library index: https://www.roadwayai.com/automation-library
---
name: test-competitor-comparison-landing-pages
description: >-
Drafts "us vs competitor" and "alternative to" landing pages for competitor-targeted campaigns, then tests them against the generic page. Needs a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway.
---
# Test competitor comparison landing pages
Source: https://www.roadwayai.com/workflows/test-competitor-comparison-landing-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
Drafts "us vs competitor" and "alternative to" landing pages for competitor-targeted campaigns, then tests them against the generic page. Needs a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway.
Each run, the agent reviews each competitor-targeted campaign and the page it lands on. It uses a page builder MCP such as Webflow, Framer, Lovable or Ploy to draft an honest comparison page, with a feature table, where each product fits best and migration help. It never publishes. Once you publish the page, the test runs it against the current page with an even split, and the agent calls a winner when each page has enough conversions.
## 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, funnel_metrics, goal_metric, max_change_pct, min_sample_size, monthly_budget_cap, task_history
## Prompt
Test competitor comparison landing pages
For each competitor-targeted campaign or audience, review its landing page and decide:
1. Launch comparison page test
2. Declare winner
3. Keep current
Context and defaults (use these; don't ask):
- 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 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:
- Page builder: use a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway to create each page as a draft. If none is connected, say so, write the page brief instead of the page, and stop. Never publish a page. Publishing is a person's call.
- Comparison pages should be honest: a feature table, where each product fits best, migration help and proof. Keep claims current and in line with the approved claims.
- Once a person has published the page, run it against the current page with an even split. The page builder MCP cannot split traffic, so use a second ad that points to the comparison page or the testing tool on the site, and say which. Judge on cost per [set this to your own goal metric] and lead quality after the minimum number of conversions per variant.
- 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:
Comparison page experiment report
Summary:
The tests and results by competitor.
Launch comparison page test:
- [campaign] - [reason]
Declare winner:
- [campaign] - [reason]
Keep current:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/test-competitor-comparison-landing-pages
Drafts "us vs competitor" and "alternative to" landing pages for competitor-targeted campaigns, then tests them against the generic page. Needs a page builder MCP such as Webflow, Framer, Lovable or Ploy connected in Roadway.
Each run, the agent reviews each competitor-targeted campaign and the page it lands on. It uses a page builder MCP such as Webflow, Framer, Lovable or Ploy to draft an honest comparison page, with a feature table, where each product fits best and migration help. It never publishes. Once you publish the page, the test runs it against the current page with an even split, and the agent calls a winner when each page has enough conversions.
