# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Update Google Search ad copy and sitelinks when partners launch.
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/update-google-search-ad-copy-and-sitelinks-when-partners-launch
Page: https://www.roadwayai.com/workflows/update-google-search-ad-copy-and-sitelinks-when-partners-launch
Library index: https://www.roadwayai.com/automation-library
---
name: update-google-search-ad-copy-and-sitelinks-when-partners-launch
description: >-
Watches partner launches and adds partner headlines, sitelinks and callouts to your search ads, plus a dedicated partner integration ad group, on the next run.
---
# Update Google Search ad copy and sitelinks when partners launch
Source: https://www.roadwayai.com/workflows/update-google-search-ad-copy-and-sitelinks-when-partners-launch
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
Watches partner launches and adds partner headlines, sitelinks and callouts to your search ads, plus a dedicated partner integration ad group, on the next run.
Watches partner launches and adds partner headlines, sitelinks and callouts to your search ads, plus a dedicated partner integration ad group, on the next run. When a partner announces or ships an integration with you, it will rewrite RSA assets, add sitelinks and open an ad group on searches that pair the partner name with your category. It keeps watching for this trigger, so it can pick this up on the next run instead of waiting for a later 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, cost_guardrail, cost_per_goal_baseline, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, partner_launches, partners, task_history, top_landing_pages, top_search_terms
## Prompt
Update Google Search ad copy and sitelinks when partners launch
Check [set this to your own partner launches] for new partner and integration announcements, and for each one decide the Google Search Ads response:
1. Add partner assets to live ads
2. Launch partner ad group
3. Queue for the next copy cycle
4. Skip
Context and defaults (use these; don't ask):
- Partner launches: [set this to your own partner launches]. If it isn't available, say so and skip the rules that depend on it.
- Partners: [set this to your own partners]. If it isn't available, say so and skip the rules that depend on it.
- The highest-converting search terms across Google and Microsoft: [set this to your own top search terms]. If it isn't available, say so and skip the rules that depend on it.
- 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 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 cost guardrail: [set this to your own cost guardrail], from the coworker's Guardrails. If not set, 1.3x [set this to your own cost per goal baseline]. A workflow qualification bar (for example "cost per lead under $100 to build a page") is not a ceiling.
- 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 launches that are live or announced with a date within 14 days, confirmed on the partner's or your own changelog or blog. Skip rumors and "coming soon" without a date.
- Add partner assets to live ads: pin one new RSA headline ("Works with [partner]", "[partner] integration live") in position 2 or 3 of the highest-volume non-brand ad groups, and add a sitelink and a callout that point to the integration page. Keep at least 10 unpinned headlines.
- Launch partner ad group: open a campaign or ad group on "[partner] [your category]", "[partner] integration" and "[partner] alternative" style searches from [set this to your own partners] and [set this to your own top search terms], with exact and phrase match only, and send it to the integration page from [set this to your own top landing pages] or the closest page.
- Check the partner's brand rules before using their name or logo in ads. Use only claims in [set this to your own approved claims], and mark anything else Unverified.
- Remove or pause partner assets when the integration is deprecated or the ad group's cost per goal passes [set this to your own cost guardrail] once it has enough spend and goal events to judge, confirmed against [set this to your own funnel metrics].
- 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:
Partner launch copy report
Summary:
The partner launches found, the assets and ad groups changed, and early results.
Add partner assets to live ads:
- [partner launch] - [reason]
Launch partner ad group:
- [partner launch] - [reason]
Queue for the next copy cycle:
- [partner launch] - [reason]
Skip:
- [partner launch] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/update-google-search-ad-copy-and-sitelinks-when-partners-launch
Update Google Search ad copy and sitelinks when partners launch
Update Google Search ad copy and sitelinks when partners launch
Watches partner launches and adds partner headlines, sitelinks and callouts to your search ads, plus a dedicated partner integration ad group, on the next run.
Watches partner launches and adds partner headlines, sitelinks and callouts to your search ads, plus a dedicated partner integration ad group, on the next run. When a partner announces or ships an integration with you, it will rewrite RSA assets, add sitelinks and open an ad group on searches that pair the partner name with your category. It keeps watching for this trigger, so it can pick this up on the next run instead of waiting for a later review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
