If you've been running Google Ads for more than five minutes in the last few years, you've noticed it: Responsive Search Ads consistently gobble up impressions while your carefully crafted Expanded Text Ads sit in the corner wondering what went wrong. A common question in the r/PPC community is whether RSAs are actually worth the trade-off — surrendering creative control for algorithmic favoritism. After managing over $350M in Google Ads spend across industries ranging from SaaS to ecommerce to local services, my answer is nuanced: RSAs are worth it when you know how to use them properly, and they're a liability when you don't.
Let's start with what practitioners in the r/PPC community have been observing for years: Google gives RSAs preferential auction treatment. This isn't a conspiracy theory — it's baked into how Ad Rank and Quality Score interact with ad format eligibility. Google's machine learning needs data to optimize RSA combinations, and it generates that data by serving RSAs more aggressively, especially in competitive auctions.
When Expanded Text Ads were deprecated in June 2022, this debate became moot for new campaigns. But the underlying question hasn't gone away: are you getting real performance out of RSAs, or just more impressions on a worse ad?
Here's what I've consistently seen across accounts: RSAs with poor asset diversity and low Ad Strength ratings can generate 30–40% more impressions than a comparable ETAs used to — but with CTRs running 15–25% lower. That's not a win. That's volume masking inefficiency.
Before you can optimize RSAs, you need a mental model of how Google assembles them. You provide up to 15 headlines and 4 descriptions. Google then tests combinations of up to 3 headlines and 2 descriptions, choosing what it believes will perform best for each query and user context.
With 15 headlines, there are potentially thousands of three-headline combinations. The vast majority of your traffic will concentrate on a small handful of "winning" combos — often just 3–5 headline combinations account for 60–80% of impressions in mature RSAs I've audited. This means:
Ad Strength is Google's proxy signal for asset diversity, not for conversion performance. I've seen "Excellent" rated RSAs with mediocre CVRs and "Poor" rated RSAs that quietly drove strong ROAS because the practitioner knew what they were doing. Don't optimize for the rating — optimize for results.
Since ETAs are no longer available for new ad creation, the practical comparison now lives between well-built RSAs and poorly-built RSAs. But for historical context — and for anyone still managing legacy accounts with ETAs still serving — here's what the data showed:
| Metric | Well-Optimized ETA | Default/Lazy RSA | Well-Optimized RSA |
|---|---|---|---|
| CTR (relative) | Baseline | –10% to –20% | +5% to +15% |
| CVR (relative) | Baseline | –5% to –15% | +0% to +10% |
| Impression Share | Baseline | +25% to +40% | +30% to +45% |
| Creative Control | Full | Low | Medium (with pinning) |
| Maintenance Overhead | High (manual testing) | Low | Medium |
The takeaway: a well-optimized RSA outperforms a lazy RSA by a wide margin, and in many verticals will match or beat historical ETAs while generating more volume. The delta between good and bad RSA execution is the entire ballgame.
This is where most practitioners leave money on the table. Here's the framework I use across every account I touch:
If you're migrating from ETAs, your top-performing ETA headlines are your starting point. Break your winning ETA into its component headlines and seed your RSA with them. Don't start from scratch and hope the algorithm figures it out.
Every RSA should have headlines covering these functional categories, with 2–3 headlines per category:
Pinning locks a specific headline to a specific position (H1, H2, or H3). This is your lever for maintaining message control in high-stakes ad groups — especially brand campaigns, competitor campaigns, or regulated industries where compliance matters.
My pinning rules of thumb:
Google recommends a minimum of one RSA per ad group, but for any ad group generating meaningful volume (>500 impressions/week), running 2–3 RSAs with different creative angles is far superior. This gives you:
In practice, I typically run 2 RSAs per core ad group: one focused on product/feature messaging and one focused on social proof/trust messaging. The winning angle then informs future creative iterations.
RSA reporting frustrates a lot of practitioners because you can't see individual headline combination performance the same way you could review ETA variants. Here's how I extract signal from what's available:
In the "View Asset Details" report, Google rates each headline and description as Low, Good, or Best. Here's how to use this:
While Google doesn't expose full combination-level data, you can segment campaign reports by ad and monitor CTR, CVR, and conversion rate trends at the RSA level. Set a monthly cadence to review:
For accounts with 50+ active RSAs, manually reviewing asset details is a time sink. I use Google Ads scripts to pull asset-level performance data across all active RSAs into a Google Sheet on a weekly schedule. This surfaces "Low"-rated headlines at scale without clicking into each ad individually. If you're managing multiple accounts or large portfolios, this is a non-negotiable efficiency gain.
RSAs don't exist in isolation — their performance is deeply tied to how your campaign and ad group structure supports them.
With broad match keywords increasingly funneling diverse search queries through a single ad group, RSAs earn their keep because they can dynamically adapt messaging to varied search intents. With exact match keywords in tightly themed ad groups, the flexibility advantage diminishes — and pinned RSAs (or very tightly written RSAs) become more appropriate.
RSAs are designed to work in concert with Smart Bidding. The algorithm uses RSA combination data as a signal alongside bid adjustments. Running manual CPC with RSAs leaves performance on the table — you're giving Google creative flexibility without the bidding intelligence to capitalize on it. If your campaign has <30 conversions/month, the algorithm doesn't have enough fuel regardless of ad format, and tight ETAs with manual bidding may historically have been more predictable. In that scenario, focus on building conversion volume before worrying about RSA optimization depth.
Whether you're auditing an existing account or building new campaigns, here's how to put everything above into practice immediately:
RSAs are worth it. But "worth it" has a prerequisite: you have to treat them as a dynamic, ongoing creative system rather than a set-and-forget checkbox. The practitioners who are frustrated with RSAs are almost always the ones who uploaded 15 generic headlines, got an "Excellent" badge, and walked away. The ones winning with RSAs are iterating constantly, reading the asset data, and building ads the way a copywriter thinks — not the way a checkbox thinks.
