Translating Google Ads Headlines: Shorten the Copy Without Losing the Offer

The 30-character limit is only the first constraint

Google's responsive search ad documentation sets these field limits:

The same documentation says one RSA can contain up to 15 headlines and four descriptions, while the creation flow requires at least three headlines and two descriptions. Google may assemble assets in different combinations and orders. It also says Korean, Japanese, and Chinese are double-width languages for this limit, so every character counts as two. The Google Ads API system-limits page independently lists 30 characters for headlines, 90 for descriptions, and 15 for each path.

A valid count does not promise a complete visual rendering. Google's preview shows only potential combinations, and its help page warns that shortening can occur in some formats. Headline 2, Headline 3, and Description 2 are not guaranteed to appear; even text within the limit may be shortened with an ellipsis when space is tight. Wider glyphs can also occupy more rendered width than narrow ones.

This changes how you split a localized message. Do not put “Free Shipping” in one unpinned headline and “Orders Over €50” in another, then assume both will always travel together. The first asset is materially false by itself. A safer headline is “Free Shipping on €50+ Orders”—28 characters—because the benefit and threshold remain attached.

There is also a current operational change to watch. Google's language-targeting help page says that, starting in September 2026, campaign-level language targeting for Search campaigns will be removed and Search ads will automatically match based on the language of the ads. That platform change does not validate a translation; it makes consistent ad-language production, native phrasing, and market review more consequential.

Shorten the sentence, not the deal

Before editing characters, turn the source offer into a small contract. The contract is not legal drafting. It is a list of the facts a reasonable reader would use to decide what the ad promises.

For “Save up to 40% this weekend on selected annual plans for new customers,” the offer atoms are:

• Benefit: save money.
• Value: 40%.
• Ceiling: up to, not a guaranteed 40% on every eligible item.
• Time: this weekend.
• Scope: selected annual plans.
• Eligibility: new customers.

Not every atom must appear in every headline. But every headline that states the promotion must remain true without an unseen companion. A category headline such as “Plans for Growing Teams” does not need the discount terms because it does not claim a discount. The moment a headline says “40% Off,” the ceiling and any condition that changes who or what receives 40% become material.

Use three labels during production:

This atom audit is more reliable than asking whether the shortened line “sounds close.” A line can sound fluent while broadening the offer. Google's Misrepresentation policy bars misleading statements and the omission of material information, and it separately addresses pricing that creates a false impression of cost. Character pressure is not a reason to turn a ceiling into a guarantee or a conditional benefit into an unconditional one.

Compression also has a quality floor. Google's Editorial policy rejects incomprehensible assets, nonstandard grammar, incorrect symbol use, and gimmicky spacing. “FrShp50€” may be short, but it is not a localization strategy. If a compact expression is not ordinary market language, regain space somewhere else.

A seven-step headline localization workflow

1. Freeze the source offer before translating

Create an offer record with the exact amount, currency, product, audience, threshold, dates, redemption mechanism, and exclusions. Resolve contradictions between the brief, landing page, feed, and terms before language work begins. Translators should not have to infer whether “30% off plans” means monthly and annual plans or annual plans only.

A minimal production row can look like this:

The landing page is part of the check, not an optional reference. Google's RSA best-practices page recommends including promotions and prices in assets and matching the advertised promotion to the landing page.

2. Write a natural full translation

Do not begin by squeezing the source into 30 characters. First produce the sentence a competent local copywriter would choose without the field limit. That version exposes the real expansion problem and becomes the semantic reference for later cuts.

Short strings can expand sharply across languages. The W3C's background note on text size in translation explains that source and target lengths differ systematically and that very short strings can have especially large expansion ratios. It also warns that abbreviations do not necessarily transfer. That is exactly why an English micro-headline cannot be treated as a universal mold.

3. Confirm the market term, not just the dictionary term

The most literal translation of a product category may not be what local customers search. Check the landing page, product taxonomy, query data, and a qualified market reviewer. Google's Keyword Planner documentation says the tool can generate related keyword ideas and monthly-search estimates; use those signals to compare plausible local terms, not to declare a machine-selected phrase linguistically correct.

Record the decision. For example, a German market may accept the compact compound Gratisversand, while another brand's style guide may prefer Kostenloser Versand. Both may be understandable, but only one may match the page, query language, and brand register.

4. Count the exact target string

Count after punctuation, spaces, symbols, capitalization, and accents are finalized. The tables in this article count Unicode characters in the exact Latin-script string after standard normalization. Google Ads' own editor or API remains the final validator, especially for double-width languages and dynamically generated assets.

Do not remove spaces merely to pass the counter. Google explicitly treats unacceptable spacing as an editorial issue. Also remember that a 30-character Latin headline can still render wider or narrower depending on its glyphs and placement.

5. Apply the shortening ladder in a safe order

Use the least destructive move first:

1. Remove polite framing and filler verbs. “Get,” “enjoy,” “take advantage of,” and their local equivalents often contribute no offer fact.
2. Replace a phrase with an ordinary compact local form. Spanish a partir de 50 € may become desde 50 €; German kostenloser Versand may become Gratisversand when that wording suits the market.
3. Use familiar numerals and symbols. “Thirty percent” can become “30%,” but spacing and symbol conventions still need local review.
4. Delete duplicated context. A brand name already carried by the business-name field may not need to consume every headline—unless the asset would become unclear without it.
5. Move secondary explanation to a description. Preserve the headline's truthful core, then use 90 characters for context.
6. Create a different headline, not a mutilated one. An accurate category, benefit, or action headline can join the RSA without restating the full promotion.
7. Pin only when visibility is genuinely mandatory. Google's RSA documentation says a required disclaimer can be pinned to Description 1, and assets pinned to Headline 1, Headline 2, or Description 1 will continue to show in those positions. The same documentation warns that pinning reduces available combinations and can affect ad strength.

The order matters. “Save 40% This Weekend” is not a clever compression of “Save up to 40% This Weekend.” It is a different claim. No later description can reliably repair an unpinned headline that may appear alone.

6. Back-translate the shortened candidate

Have a reviewer who can see both languages paraphrase the compact headline back into the source language without looking at the original. Compare offer atoms, not word order.

Ask five questions:

1. Is the amount still a ceiling, floor, or guaranteed value as intended?
2. Does the same product or plan qualify?
3. Is the threshold still attached to the benefit?
4. Are the duration and eligibility unchanged?
5. Has the tone become unnatural, vague, or more aggressive?

A back-translation of “30 % Rabatt auf Pläne” is “30% discount on plans.” That immediately reveals the lost annual-only scope.

7. Run the standalone and combination tests

Read every promotion headline alone. Then read it beside every plausible category, brand, and call-to-action headline. Google advises writing assets that can appear in different orders, so test for accidental repetition, contradiction, dangling grammar, and claims that depend on another slot.

Also preview the ad on available placements, but treat preview as a layout sample—not proof that every combination or every character will always appear. Keep a source-of-truth sheet with the approved target copy, count, preserved atoms, reviewer, review date, landing-page match, and pinning decision.

Four worked examples in three languages

The following examples teach different failure modes. “Full translation” is the unconstrained semantic reference, “safe headline” is the compressed teaching candidate, and “unsafe cut” shows the meaning lost. Counts are for the exact strings shown.

Example 1: annual-plan scope

The safe versions remove framing or use a shorter verb while keeping the amount and product scope. The unsafe versions fit comfortably because they advertise a broader discount than the source offer.

Example 2: free-shipping threshold

The threshold belongs with the shipping claim. A description may explain whether the threshold is before tax or which shipping method is included, but it should not be asked to rescue an unconditional “Free Shipping” headline.

Example 3: trial duration and card requirement

Here “no card” is a friction-reduction promise rather than a restriction. It may be strategically important even when the headline remains technically true without it. Marking atoms as material is not only about avoiding deception; it also prevents a translator from deleting the differentiator that made the offer worth advertising.

Example 4: “up to” is not expendable

Words such as up to, bis zu, and hasta are short in form but decisive in meaning. They are also the exact words most likely to be cut by someone optimizing only the counter. Treat them as locked whenever they define the claim.

Open the editable three-language lab to filter all 36 variants, edit the strings, and see the character counts update. The offer notes describe the original examples; edited wording needs a fresh meaning check. A flat CSV version is included for production handoff.

Use descriptions without hiding the truth

Descriptions create room, but they do not make every headline safe. Use a description for explanation when the headline already tells the truth on its own.

For the fictional OrbitDesk trial, this small RSA set remains combination-safe:

If the business requires both “14 days” and “no card” to appear in every served ad, do not merely distribute them across unpinned assets. Use a complete Headline 1 candidate, or place a complete statement in Description 1 and pin it there after accepting the combination tradeoff. If continuous visibility is not mandatory, preserve meaning across the asset library while allowing distinct accurate headlines to rotate.

This distinction also improves the set. A translated RSA should not contain 15 near-identical discount headlines. Google's best-practices page encourages unique headlines and descriptions of varying lengths. Build assets around different truthful jobs—offer, category, use case, proof available on the landing page, brand, and action—rather than producing 15 synonym swaps.

A pre-upload localization QA sheet

Before a localized RSA reaches Google Ads, the reviewer should be able to answer every row below with evidence.

The language sign-off cannot be replaced by a counter, translation-memory match, back-translation, or general-purpose AI output. Those tools can expose inconsistencies and accelerate variants. A qualified reviewer still decides whether the compressed line is ordinary, persuasive, and accurate in the market where it will run.

The decision rule

When a correct translation is too long, do not ask, “Which word can we delete?” Ask, “Which offer facts must this particular asset carry, and what is the shortest natural way to carry them?” Remove framing first, choose compact local language second, move nonessential explanation third, and change the headline concept before you change the promise.

A headline that is 31 characters is a production problem. A headline that is 24 characters because it deleted the minimum spend, annual-plan restriction, or “up to” is an offer-integrity problem. Solve the first without creating the second.

Sources

• About responsive search ads — Google Ads Help. Character limits, asset counts, ordering, shortening, visibility, and pinning. Checked September 9, 2026.
• System Limits — Google Ads API, Google for Developers. Ad field limits; page last updated August 19, 2026. Checked September 9, 2026.
• About language targeting — Google Ads Help. September 2026 Search-language targeting change. Checked September 9, 2026.
• Best practices for creating effective responsive search ads — Google Ads Help. Natural copy, unique assets, promotions, and landing-page consistency. Checked September 9, 2026.
• Editorial — Google Advertising Policies. Grammar, comprehensibility, symbols, spacing, and double-width limits. Checked September 9, 2026.
• Misrepresentation — Google Advertising Policies. Misleading representation and pricing practices. Checked September 9, 2026.
• Use Keyword Planner — Google Ads Help. Keyword ideas and search estimates. Checked September 9, 2026.
• Text size in translation — W3C Internationalization. Published July 3, 2007; translation expansion and abbreviation cautions. Checked September 9, 2026.