DEV Community

hack game
hack game

Posted on Edited on

A practical way to validate Google Ads RSA headlines before publishing

Google Ads responsive search ads ask for multiple headlines and descriptions that may display in different orders. A small-looking change in copy can push a field over its limit.

The relevant search-ad reference limits are separate:

Headline: 30 characters each; 3–15 assets.
Description: 90 characters each; 2–4 assets.
Display path: 15 characters for each optional path field.
The tricky part: double-width Chinese, Japanese and Korean characters count as two. A plain visible-character count may therefore be too optimistic for bilingual copy.

My workflow is to write at least three independent headlines, two distinct descriptions, validate every field, then review one illustrative combination. The final Google Ads editor remains the source of truth; a preview cannot guarantee which assets Google will show.

I put together a free in-browser workspace that checks multiple headlines and descriptions and lets you copy the draft into Google Ads: https://postchars.com/twitter-character-counter/?utm_source=devto&utm_medium=referral&utm_campaign=postchars_launch&utm_content=twitter_x_character_counter

The specifications are documented here: https://support.google.com/google-ads/answer/7684791

Would a paste-from-CSV feature or a shareable text-only checklist be more useful?

Top comments (0)