# Responsive Search Ads: 15 Headlines, One Machine

What a responsive search ad is, how Google assembles it per auction, and how to write headlines as parts for a machine to recombine.

Glossary · Published 2026-08-10, updated 2026-10-26.

> A responsive search ad (RSA) is the standard Google Ads search format: you supply up to fifteen headlines and four descriptions, and Google assembles a combination — typically up to three headlines and two descriptions — for each auction, chosen to fit the query and the searcher. An RSA is not an ad so much as a bag of parts; writing the parts for recombination is the entire craft.

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](https://adcopilot.cloud/blog/ad-copy-testing-with-ai). And note that [Ad Strength](https://adcopilot.cloud/glossary/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](https://adcopilot.cloud/google-ads-mcp-server) drafts a full asset set against the keyword theme and landing page, counts characters before you ever see the draft, and creates the ad from the set you approve in the chat; AdCopilot proposes that write first, and your AI client asks before it runs if it is set to ask before AdCopilot's write tools. The ad starts enabled, so in a live campaign it serves once Google approves it — ask for it paused if you want a last look in the interface first. 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](https://adcopilot.cloud/blog/write-responsive-search-ads-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.

## Questions

### How many headlines should I actually provide?

Enough distinct ones — and no filler to hit fifteen. The machine benefits from genuine variety: different angles (price, proof, speed, objection-handling), different lengths, keyword-bearing and brand-bearing options. Eight to ten strong, genuinely different headlines beat fifteen where five are paraphrases, because near-duplicates add combinations without adding information. Provide variety until you run out of true angles, then stop.

### Do pinned headlines hurt performance?

Pinning constrains assembly — a pinned position excludes every alternative from that slot, which shrinks what auction-time selection can try, and Google's guidance leans against it. But compliance lines, required disclaimers and brand rules are real constraints too: when a message must always show, pin it and accept the trade knowingly. Pin for necessity, never for tidiness.

---

This is the markdown copy of https://adcopilot.cloud/glossary/responsive-search-ad. The index of the site's pages is https://adcopilot.cloud/llms.txt.
