A responsive search ad (RSA) is the default — effectively the only — text ad format in Google Ads search campaigns: you provide components, Google performs assembly. Up to fifteen headlines and four descriptions go in; at each auction, the system selects and orders a combination, typically up to three headlines and two descriptions, predicted to perform for that query, that user, that context. The unit you write is not the unit anyone sees. Internalising that — an RSA is a bag of parts, not a paragraph — is the difference between fighting the format and using it.
How an RSA is assembled
The component rules, briefly: headlines run up to 30 characters, descriptions up to 90; assembled combinations vary by auction, and some placements show fewer headlines. Pinning locks an asset to a position — pin a compliance line to headline one and it always appears there, at the cost of excluding every alternative from that slot. Assembly itself is Google's models doing per-auction selection, the same family of machinery that runs matching and bidding: it learns which components earn engagement in which contexts, and skews future combinations accordingly.
The writing consequence is mechanical but easy to miss: any headline may appear beside any other, in any order. So every headline must stand alone — no sequences that depend on a predecessor. No two headlines should say the same thing in different words — near-duplicates spend a slot without adding an angle. And the set should cover distinct arguments — the keyword, the brand, price, proof, urgency, the objection — because coverage is what gives per-query selection something to choose between. You are not writing an ad. You are stocking a machine with arguments.
Asset-level reporting: what you can and cannot learn
Google reports impressions per asset and performance labels — Low, Good, Best — plus a combinations view of frequently served assemblies. What it does not give is per-asset conversion attribution: you cannot know that headline seven closed the deal, because headlines never appear alone. Read labels as engagement-weighted signals within this ad's context, not absolute verdicts — a Low label on a pinned disclaimer is the system reporting your constraint back to you, not news. Prune with labels; prove with structured copy tests. And note that Ad Strength measures whether you stocked the machine adequately — a completeness meter, not a performance score.
Drafting parts for the machine, by machine
RSA production is text generation under hard constraints — character limits, angle coverage, standalone-ness — which is exactly the work language models do well and humans find tedious at scale. A connected assistant drafts a full asset set against the keyword theme and landing page, counts characters before you ever see the draft, and pushes the approved set through the API — as a paused ad, so nothing serves until you enable it. The division of labour lands where it should: the machine proposes fifteen standalone headlines covering the angles; you strike the off-brand ones and approve; assembly does the rest. The full path from brief to live ad is in writing RSAs with AI.
At account scale, the same access powers the audits that never used to happen: ad groups running a lone RSA with seven headlines, near-duplicate headlines wasting slots, assets sitting at Low for a quarter. Stocking the machine is now cheap. Deciding what the parts should say — that stayed yours.