# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Respond when a competitor publishes a comparison page about you.
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/respond-when-a-competitor-publishes-a-comparison-page-about-you
Page: https://www.roadwayai.com/workflows/respond-when-a-competitor-publishes-a-comparison-page-about-you
Library index: https://www.roadwayai.com/automation-library
---
name: respond-when-a-competitor-publishes-a-comparison-page-about-you
description: >-
When a competitor puts up a them-vs-you or alternative-to-you page, makes sure your own ads and comparison page win the searches it targets, with every change waiting for approval.
---
# Respond when a competitor publishes a comparison page about you
Source: https://www.roadwayai.com/workflows/respond-when-a-competitor-publishes-a-comparison-page-about-you
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 competitor puts up a them-vs-you or alternative-to-you page, makes sure your own ads and comparison page win the searches it targets, with every change waiting for approval.
Each run, it searches the web for new pages where a competitor compares itself with you. When it finds one, it bids on the matching comparison terms if you aren't already, drafts copy that answers their points from your approved claims, and sends the page to your team. Every change waits for approval. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your 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, competitors, cost_per_goal_baseline, cpa_guardrail, experiment_budget_pct, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, task_history, top_landing_pages
## Prompt
Respond when a competitor publishes a comparison page about you
Search the web for new pages from [set this to your own competitors] that compare themselves with us or pitch themselves as an alternative to us, not seen on the last run, and decide for each page:
1. Bid on the comparison terms
2. Answer in copy
3. Send for review only
4. Skip
Context and defaults (use these; don't ask):
- Named competitors and their domains: [set this to your own competitors]. If it isn't available, say so and skip the rules that depend on it.
- Web search: find and read competitor pages with the web search tool. If a page can't be read, say which one.
- 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 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 since the last run.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The cost guardrail: [set this to your own CPA guardrail], from the coworker's Guardrails. If not set, 1.3x the baseline cost per goal. A workflow qualification bar (for example "cost per lead under $100 to build a page") is not a ceiling.
- 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 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:
- Only act on pages published by the competitor itself that name us. Skip review sites and third-party listicles.
- Bid on the comparison terms: if we don't already, bid on "[competitor] vs [us]" and "[us] alternative" terms at [set this to your own experiment budget percent], sending traffic to our comparison page from [set this to your own top landing pages] or the closest page.
- Answer in copy: draft headlines and ChatGPT context hints that answer their main points from [set this to your own approved claims] only. Don't name the competitor where the platform's trademark rules forbid it.
- Send for review only: send the page and a summary of its claims to the team when it makes claims about us that need a human answer.
- Building our own comparison pages on a regular cycle belongs to the comparison landing page workflow. This one reacts to theirs.
- 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 already hurt performance. 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:
Competitor comparison page report
Summary:
The new comparison pages found, bids and copy drafted, and anything sent for review.
Bid on the comparison terms:
- [competitor page] - [reason]
Answer in copy:
- [competitor page] - [reason]
Send for review only:
- [competitor page] - [reason]
Skip:
- [competitor page] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/respond-when-a-competitor-publishes-a-comparison-page-about-you
Respond when a competitor publishes a comparison page about you
Respond when a competitor publishes a comparison page about you
When a competitor puts up a them-vs-you or alternative-to-you page, makes sure your own ads and comparison page win the searches it targets, with every change waiting for approval.
Each run, it searches the web for new pages where a competitor compares itself with you. When it finds one, it bids on the matching comparison terms if you aren't already, drafts copy that answers their points from your approved claims, and sends the page to your team. Every change waits for approval. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.