What is probably happening
The account still relies on expanded text ads
Expanded text ads are a legacy format. If old ad groups were never migrated properly, the account may contain historical ads that cannot be created or edited like modern responsive search ads.
Ad groups have weak responsive search ad coverage
A campaign can lose flexibility if each ad group has too few headlines, weak descriptions, over-pinned assets or copy that does not match the active keywords.
The migration changed more than the ad format
Performance can drop if the RSA migration also changed match types, landing pages, conversion actions, bids or campaign structure. Separate the ad-format issue from other edits.
Policy, landing page or final URL changes block the replacement ads
New responsive search ads still need approval. Claims, trademarks, destination issues and tracking templates can delay or limit serving.
How to check it without breaking anything
List every ad group that still depends on legacy text ads.
Check whether each ad group has at least one eligible responsive search ad.
Compare historical top-performing headlines and descriptions before replacing them.
Review pinned assets and avoid locking the RSA so tightly that Google cannot test useful combinations.
Confirm final URLs, tracking templates, consent, conversion actions and landing page status.
Do not change bids, keywords and ads in the same pass unless you can measure the impact separately.
After launch, segment performance by ad group, search term, asset combination, device and conversion action.
How I would solve it step by step
Create a migration inventory
Export the affected campaigns and mark which ad groups lack eligible responsive search ads. Keep the historical ad text for reference before making changes.
Build responsive search ads from proven intent
Use historical winning messages, core offers, search intent and landing page language. Do not write generic RSA assets just to make the warning disappear.
Protect measurement continuity
Before publishing replacements, check conversion actions, enhanced conversions, consent mode, final URLs and auto-tagging. A migration is useless if the new ads cannot be measured properly.
Roll out in controlled batches
Start with the most important ad groups, monitor eligibility and conversion quality, then move through the rest of the account with a clear before-and-after log.
If it gets technical
You can follow this path yourself. If the diagnosis reveals a strange data mismatch, a delicate tracking setup, a risky bidding decision or a blocker that needs account access, Lia keeps this context and brings it to CreatikLab so you do not start from zero.
Take this context to LiaWhat I would not do
Replacing old text ads with generic responsive search ads that ignore historical search intent.
Pinning every headline and removing the flexibility that responsive search ads need.
Changing keywords, bidding and landing pages at the same time as the ad migration.
Ignoring conversion tracking and then blaming the new ad format for reporting loss.
Leaving low-volume ad groups without a clean RSA because the account has too many legacy structures.
Frequently asked questions
Are old expanded text ads the same as responsive search ads?
No. Responsive search ads combine multiple headlines and descriptions dynamically. A migration should preserve proven messaging while adapting to the RSA format.
Should I copy the old text ad into one RSA?
Use the old ad as evidence, not as the whole strategy. Add enough high-quality headlines and descriptions to cover the search intent without over-pinning everything.
Can this affect conversion tracking?
The ad format itself is not the tracking system, but migrations often include URL, landing page, consent or tag changes. Check measurement before judging performance.
