If you've been running Google Ads for more than a couple of years, you've probably restructured your RSA setup at least once — and if you haven't, 2026 is the year you probably should. The old playbook of ultra-tight SKAGs (Single Keyword Ad Groups) made sense in an Expanded Text Ad world, but Responsive Search Ads operate on entirely different principles. The question isn't just "how many headlines should I write?" — it's about how much signal you're giving Google's machine learning, how your ad groups are sized, and whether your creative strategy is actually helping the algorithm or fighting it.
A common question in the r/PPC community right now is whether the tight keyword groupings we all relied on for ETAs still make sense for RSAs in 2026. The short answer: not entirely. The longer answer requires understanding what RSAs actually optimize for versus what ETAs did.
With ETAs, tight ad groups meant you could write hyper-specific copy matched to a narrow set of keywords. The ad was static, so relevance was entirely on you. With RSAs, Google is dynamically assembling combinations from your asset pool — up to 43,680 possible headline & description combinations from a full 15-headline, 4-description asset pool. The system needs enough search query diversity within the ad group to learn which combinations perform best. Feed it three keywords and 300 impressions a month, and it can't learn anything meaningful.
From managing campaigns across a wide range of verticals and budgets, the practical floor for an RSA ad group to generate meaningful optimization is roughly 100–150 impressions per week at a minimum, and ideally you want to be targeting groups that can hit 50+ clicks per month. Below that, Google's serving decisions become effectively random from an asset combination standpoint.
That doesn't mean you throw every keyword in one ad group. It means you stop obsessing over one-keyword ad groups and instead think about thematic clusters that share genuine user intent. A group covering [project management software], [project management tool], [best project management app], and [project tracking software] is thematically coherent. The user intent is nearly identical across all four, and grouping them gives your RSA enough volume to actually learn.
In practice, I've seen strong results with 5–15 keywords per ad group when those keywords share a tight thematic intent. The specific number matters less than the intent coherence. What you're avoiding is mixing high-funnel informational queries with bottom-funnel transactional ones in the same group — that creates creative tension that no RSA can resolve cleanly.
| Approach | Keywords/Ad Group | RSA Learning Speed | Creative Flexibility | Best For |
|---|---|---|---|---|
| SKAG (Legacy) | 1–2 | Very Slow / None | Low | ETAs (deprecated) |
| Tight Thematic | 3–7 | Moderate | Medium | Low-volume niches |
| Broader Thematic | 8–15 | Fast | High | Most accounts in 2026 |
| Consolidated (STAG-style) | 15+ | Fastest | Highest | Smart Bidding, high volume |
Most practitioners either write 15 headlines that all say roughly the same thing (wasted opportunity) or write 15 headlines that are so varied they create incoherent ad combinations (performance killer). The goal is structured variety — different angles covering the same core value proposition.
Here's the asset breakdown I use across high-spend accounts:
With only 4 description slots and 90 characters each, descriptions are where many practitioners leave performance on the table. Google will typically show 2 descriptions at a time, so each one needs to stand alone as a compelling statement while also complementing any other description it might appear alongside.
Write descriptions that expand on different pillars: one for features, one for benefits, one for trust/social proof, and one for a clear call to action with any relevant offer details. Avoid writing four descriptions that all say "Try our software today. It's the best on the market."
Pinning headlines to specific positions (1, 2, or 3) reduces the combinations Google can test and typically hurts Ad Strength scores. That said, there are legitimate use cases:
If you must pin, pin only 1–2 headlines maximum and leave the remaining slots fully flexible. Pinning position 1 and position 2 while leaving position 3 flexible is a reasonable compromise for brand-sensitive accounts. Never pin all three positions — at that point you've built a glorified ETA.
As practitioners often discuss, Ad Strength is Google's self-reported quality metric — and it's imperfect. "Excellent" Ad Strength does correlate with better impression share and lower CPCs in aggregate, but it's a means to an end, not the end itself.
What Ad Strength is actually measuring:
The practical benchmark: aim for "Good" or "Excellent" on every RSA, but don't sacrifice messaging quality to chase the score. I've seen "Poor" RSAs outperform "Excellent" ones when the "Poor" RSA had tighter, more compelling copy for a specific audience. Conversion data always beats Ad Strength score.
Google now labels individual assets as "Best," "Good," "Low," or "Unrated" (usually assets with insufficient data). Here's how to act on those labels:
A structured testing cadence prevents both stagnation (never refreshing assets) and over-iteration (changing things before you have data). The framework I recommend:
Google's Smart Bidding algorithms — tCPA, tROAS, Maximize Conversions — perform better with more data in a single campaign than spread thin across many micro-campaigns. In 2026, the broader structural trend is consolidation: fewer campaigns with more ad groups, rather than dozens of hyper-segmented campaigns.
This doesn't mean you consolidate everything into one campaign. It means you stop creating separate campaigns for every device, match type variation, or minor keyword category difference. Bid strategy and audience targeting handle a lot of the segmentation that used to require structural separation.
Broad Match + Smart Bidding is no longer the boogeyman it used to be — in high-conversion-volume accounts (>50 conversions per month at the campaign level), it frequently outperforms Phrase and Exact-only structures. The reason: Broad Match feeds the RSA algorithm more query variety, which accelerates creative learning.
The practical recommendation for most accounts:
If you're sitting with a legacy account structure built around ETAs and SKAGs, here's a practical roadmap to modernize it without blowing up performance:
The bottom line is that RSA structure in 2026 is less about rigid keyword clustering and more about giving machine learning the right inputs: enough data volume, enough creative variety, and enough campaign-level signal to make Smart Bidding work efficiently. The practitioners who are winning aren't micromanaging every headline combination — they're building intelligent frameworks and letting Google optimize within those guardrails.
