BlogLocalization

Translated ad QAa checklist before every market goes live

6 min read

A translation can be right and the ad can still be wrong. The German headline is correct and runs into the Reels caption. The Japanese line breaks in the middle of a word. The French price shows $4.99. None of this shows up in a string sheet, because it only exists once the text is inside the video. Alconost puts it plainly: the proofreader sees the correct word, the reviewer looking at the screen sees it cut off, and a typical review of that kind for a mobile app turns up 40 to 200 findings per language (Alconost).

The six checks below come in the order the problems tend to show up. They apply whatever tool made the versions. Run them on one version of the next batch you send to a new market before you approve the rest.

1. Length and line breaks

The shortest text in an ad grows the most. Spanish, French and German run about 25–30% longer than English on average, but by IBM's guidelines very short English strings of up to ten characters can become two to three times as long (W3C). "Play now" is eight characters. Headlines, buttons and price tags are that kind of text, and they're what a viewer reads in the first second.

Look at where each line breaks. A headline that was one punchy line in English may now be three, and the break may split a number from its unit or an adjective from its noun. German compounds can't wrap, so a word like "Spielfortschritt" sets the line length on its own. If the button text had to shrink, it may be too small to read on a phone at arm's length, and a shorter word from the translator beats smaller type.

Watch the timing as well as the space. A line that takes three seconds to read in English may need four in German, so that market's version may need the text on screen longer.

2. Scripts, fonts and direction

Brand fonts are often drawn for Latin letters only, and a missing character gets a fallback font, so a Russian, Arabic or Japanese headline can come out in a typeface that has nothing to do with the brand. Game localization checklists ask for a dedicated fallback for Chinese, Japanese, Korean, Arabic, Thai and Devanagari, and a check that every character in every translation has a glyph (Loxily).

Arabic and Hebrew read right to left, and so should the composition: the text aligns right, and anything that points the way the eye moves, an arrow, a swipe or a progress bar, points the other way, while media controls such as play and fast-forward keep their usual direction. Arabic letters join, so a line that renders as separate letters means the font isn't shaping the script, and any Arabic reader will see it at once. Numbers stay left to right inside right-to-left text, so a price or a level number can land in the wrong place in the sentence.

Chinese and Japanese don't use spaces, so line breaks follow other rules. In Japanese, closing brackets, small kana and most punctuation must not start a line, and opening brackets must not end one (Wikipedia). A headline that breaks against those rules looks careless to a native reader even when every character is right. Thai has no spaces either and stacks marks above and below the letters, so check that nothing is clipped at the top or bottom of the line.

3. Prices, numbers and dates

The price in the ad has to be the price the viewer sees in their store, and that is rarely the US price converted at today's rate. When Apple last published the figures, in 2023, the App Store set prices across 175 storefronts and 43 currencies, either equalized by Apple against your base country or set by you storefront by storefront (Apple). Take each market's price from that market's storefront. A German viewer who sees €5.39 in the ad and €4.99 in the store doesn't think the ad is wrong. They think the offer has changed.

Then check how the price is written. The US writes $4.99, Germany 4,99 € and Brazil R$ 4,99. Dates follow local rules too: a German "bis 1.12." is a deadline on 1 December, a US "12/1" is the same day, and Japanese dates need 月 after the month. Make sure each market got its own figure, written its own way, and that the layout around a longer figure like "R$ 24,90" holds.

4. Safe zones in every placement

Longer text takes more of the frame. In Reels, Meta's guidance is to keep anything important out of the top 14%, the bottom 20–35% and 6% in from each side, because the platform's buttons and captions sit there (Billo). An English headline clear of the caption can push into it in German, and a price above the like button can slide under it.

Check every placement on its own, with the placement's interface on top rather than on the clean export. The likeliest failures are the tall versions in the longest languages, and the square versions in Arabic, where a right-aligned block lands in a different corner.

Legal lines are the one place where a good translation isn't enough. The disclaimer, the subscription terms and the risk warnings have to match the version legal approved for that market word for word, so they come from legal's approved text, not from a translation of the English line. Check each against the approved wording, and check that it stays on screen long enough and large enough to read.

Some markets decide what has to be translated. In France the Toubon law requires a French translation of any foreign-language words, hooks or legal mentions in an ad, as readable as the original, and slogans fall under it even when they are registered trademarks (ARPP). An English tagline kept in the French version needs a French line next to it.

6. Sign-off by someone who reads the language

The last check is the one no tool replaces: a person who reads the language watches the finished ad, not the string sheet. Alconost's example is "Finished", which needs a different ending depending on what it describes. In an ad the guesses that go wrong are a joke that doesn't land, a pun that turns into nonsense, a tone too formal for a game or too casual for a bank, and a call to action that reads as an order. Someone who reads the language sees all of it in fifteen seconds.

It can be a colleague in that market or an outside reviewer, as long as they'll say when a line is merely correct. Give them every placement of their market, since a line can read well in 16:9 and break in 9:16. When they find something, the correction should touch that line and nothing else, so they only need to look at that line again.

If your ads are built in layers

Most of the failures above happen because the text was fitted into the space the English left. Meta's AI dubbing replaces only the audio and leaves the on-screen text in the source language; HeyGen's In-Video Text Translate translates text found in a finished video and fits it into the original's space (Maginative).

With Motn the text is never part of the picture, so the translation goes into the text itself and the layout is set again around a longer or shorter line, in every placement. Each market's price is its own live value, and a reviewer's correction is a direct edit to that market's text. The checklist still applies; it just starts from versions laid out for their language. The same routine covers store preview videos in every language, and the reasoning behind it is in localizing video ads is more than translation.

Make yours on Motn.