Why Your RSA Can't Be Edited (and What We Did Instead)

Responsive Search Ads come with a counter-intuitive limitation: once an RSA is created, its headlines and descriptions cannot be edited directly. Want to change the copy? You create a new ad. When we first hit this, we assumed we were missing an option somewhere — after checking, it was not an interface problem. It is a product rule, and arguing with it is a waste of time. Understanding the logic helps: an RSA's performance depends on Google testing many combinations of its assets, and the optimization system needs a fixed asset set to learn from — allowing arbitrary edits would interrupt that learning, so Google simply doesn't allow them.

Work around it: push new, auto-pause old

If the assets cannot be edited, change the push strategy: create a fully-loaded RSA — 15 headlines and 4 descriptions — and as soon as it passes review, automatically pause the old ad while keeping the structure synchronized. In our records, AI completion filled in +12 headlines and +2 descriptions in one pass, and on the example account we pushed 2 fully-loaded RSAs that both passed review, with the old ads paused automatically at the same time. For the operator, the end result is almost indistinguishable from an edit — it is just implemented as a swap instead of a change.

Three details that matter

First, the new ad has to be complete — with fewer than 10 headlines, Google has too little material to build combinations and ad strength stays low. Second, use health scoring to locate the weak assets: which headlines are duplicated, uncompetitive, or dragging the combinations down — fixing those is where the real gain sits, and there is no need to rewrite the strong assets too. Third, let AI complete only the weak assets and keep the strong ones — you are editing the copy, not replacing the blood; keeping the proven assets means the new ad can hold its own from day one.

Swap on push: never let two ads fight

Once the new fully-loaded ad passes review, the old ad must be paused immediately. Otherwise two ads in the same group compete for the same auctions and pollute your data — and the conclusions you draw from that data lose their meaning. Our flow pauses the old ad at the exact moment the new one goes live, which removes the “two ads fighting” scenario structurally. After approval we keep tracking impression share and ad strength to confirm the swap delivered what it promised before deciding on the next round.

The 5-step RSA optimization checklist

• Diagnose asset health — locate weak or duplicated headlines and descriptions.
• Have AI generate the full 15/4 — complete the weak assets, keep the strong ones.
• Preview old vs. new — look before you push.
• Push new and auto-pause old together — the swap happens in one step.
• Track impression share after approval — verify the optimization actually paid off.

This is exactly how our ads automation module handles RSA copy optimization for the accounts we run.