RSA ad-group personalization

Personalize the Responsive Search Ads across my Google Ads ad groups for higher Quality Score and lower CPC. This is best run in Claude Code (long-running chat) because it works ad group by ad group in batches.

Step 1 — Business context
First, ask me to confirm three things before you write any copy: my ideal customer profile (ICP), my main product or service in one sentence, and my brand voice (e.g. formal expert, friendly challenger, etc.). Use the MCP to list my accessible Google Ads accounts; if I have more than one, ask which to work on.

Step 2 — Plan the batches
List my active ad groups sorted by 30-day spend (highest first). Batch them in groups of 5. Confirm the batch order with me, then process one batch at a time. Stop at the end of each batch and ask whether to continue.

Step 3 — For each ad group in the current batch
- Fetch the ad group's keywords (text, match type, search volume, conversions, Quality Score components).
- Fetch the current RSA(s): headlines, descriptions, pinned positions, current ad strength.
- Fetch the destination URL and read the landing page: title, H1, value propositions, social proof, CTA copy.

Step 4 — Generate the new RSA
Hard requirements (Google's limits):
- Exactly 15 headlines. Each headline must be 30 characters or fewer.
- Exactly 4 descriptions. Each description must be 90 characters or fewer.

Content requirements:
- At least 4 headlines must include the highest-volume keyword from the ad group (or a tight variant). Match how a user would actually search.
- At least 3 headlines must mirror phrases pulled directly from the landing page (value props, CTAs, social proof, numbers).
- If the campaign is generic / non-branded, include exactly one headline using Google's keyword-insertion syntax: {KeyWord:fallback text}. Use a fallback that still reads well if insertion fails.
- Pin the brand name to HEADLINE_1, and the primary CTA to HEADLINE_2 or HEADLINE_3. Leave the other headlines unpinned so Google can rotate.
- Cover at least three angles across the 15 headlines: outcome, social proof, urgency or scarcity, feature or benefit, price or offer.
- Descriptions should each end with a clear CTA and avoid duplicating headline copy.

Step 5 — Preview and confirm
For each ad group, call google_ads_preview_mutation with operation="update_rsa" and surface the exact payload. Wait for my explicit "execute" before applying. Only run this on accounts I own — confirm ownership before previewing.

Output requirements
Group results by ad group. For each ad group show the new RSA as a table (column for character count) and a 2-3 bullet rationale explaining the keyword/landing-page choices. After each batch, summarize: ad groups processed, RSAs updated, anything that needs my attention.