Google RSA Headlines: The 30-Character Limit Explained

Google Responsive Search Ads enforce a hard 30-character limit per headline — measured in characters, not bytes, with CJK scripts counted at 2 each. This page is the reference for what counts, what gets rejected, and how to fit copy without padding.

The spec, exactly.

Google Ads RSAs accept up to 15 headlines, each capped at 30 characters. The character count includes spaces, punctuation, and most symbols. You must supply at least 3 headlines for the ad to save. Descriptions, for reference, are 90 characters each (up to 4) — different limit, same counting rules.

Why 30 characters.

The limit predates RSAs — it traces back to the original AdWords text ad format, designed around a single SERP line at desktop widths around 512px. Google's renderer pipes three of your headlines into a slot separated by pipe characters (Headline 1 | Headline 2 | Headline 3), and the combined string has to fit before the URL truncates. Thirty characters per slot keeps the rendered ad legible across viewports, including the narrower mobile SERP where Google may show only two headlines.

What happens when you exceed it.

The Google Ads UI blocks save with a hard error — the headline field turns red and the ad won't publish. Same behavior via the Editor and the API (HeadlineAsset returns STRING_TOO_LONG). There is no silent truncation at upload. At serve time, however, Google may truncate a *combined* headline string if the device width is too narrow, usually appending an ellipsis. You can't control which headline gets cut — another reason to make each one stand alone.

Counting gotchas.

• Emoji: most emoji count as 1 character in Google's validator, but Google rejects ads with excessive or decorative emoji on policy grounds regardless of length. Don't rely on them to save space.
• CJK characters: Chinese, Japanese, and Korean ideographs count as 2 characters each. A 15-character Japanese headline hits the cap.
• Curly quotes and em dashes: count as 1 each, but watch paste-from-Word artifacts — a smart apostrophe (') and a straight one (') both count the same, but rendering varies across fonts.
• RTL languages (Arabic, Hebrew): count by character, but bidirectional text combined with Latin keywords can render unpredictably. Preview before publishing.
• Dynamic Keyword Insertion: {KeyWord:Default} — only the *default* text counts toward the limit at validation, but the inserted keyword must also fit at serve time or Google falls back to default. Always size your default to the worst-case keyword in the ad group.
• Ad customizers ({=FeedName.Attribute}): same rule. Validator checks the fallback string.

Fitting copy in 30 characters.

• Front-load the keyword or the value prop. The first ~20 characters carry most of the scan weight.
• Cut articles ruthlessly: "Get the Best CRM Software" (25) → "Best CRM Software" (17).
• Numerals beat words: "Save Twenty Percent" (19) → "Save 20%" (8).
• Title Case scans faster than Sentence case in the SERP, but Google rejects ALL CAPS except for acronyms.
• Avoid trailing punctuation — exclamation points are policy-restricted to one per ad and never in headline 1.

The 25–28 character zone.

Headlines that land at exactly 30 often look engineered. Copy in the 25-28 range reads more naturally and leaves visual breathing room next to the pipe separators. This is a craft observation, not a Google rule — but A/B tests on RSA assets consistently show the cleaner-reading headline wins on CTR.

Pinning and the limit interact.

Pinning doesn't change the character cap, but it changes which headlines render where. If you pin a 30-character headline to position 1 and Google selects a 30-character headline for position 2, the combined string almost certainly truncates on mobile. Pinned + long = mobile risk.

Example

Original draft: "Get the Industry's Most Powerful Project Management Tool Today" (63 chars). Trim path: drop the article and superlative chain → "Powerful Project Management" (27). Or split into two assets: "Project Management, Simplified" (30) and "Built for Teams of 5–500" (24). Two distinct angles, both in spec, both scannable.

Questions