How to Check Translation Quality When You Don't Speak the Language

If you've paid for a translation into a language you don't read — Arabic, French, English, Gulf-market copy — the honest way to check translation quality is not to trust your gut, because you can't. You verify it through a second independent pair of eyes, structured questions, and a few practical tests anyone can run. This guide gives a business owner or client a clear, non-technical way to QA a translator and review work you can't read yourself, so you don't publish something embarrassing, wrong, or off-brand in front of the exact audience you're trying to win.

Start before the work: brief and sample

The best quality check happens before a single full page is translated. Half of all bad translations trace back to a weak brief, not a weak translator.

Give the translator, up front:

• A short glossary of the terms that must stay consistent — your brand name, product names, technical words, and anything you do not want translated (leave a brand name in Latin letters, for example).
• The audience and tone. "Formal Gulf business Arabic" is a completely different job from "casual Lebanese social-media Arabic." Say which one.
• The purpose. A legal contract, a marketing caption, and an app menu each need a different hand. A translator who knows the goal makes better choices.

Then ask for a paid sample — one paragraph or a single screen — before you commit to the whole job. It costs little, and it's the cheapest quality gate you have. If the sample comes back late, sloppy, or with the wrong tone, you've learned that for a few dollars instead of the full fee.

If you're still choosing who to hire, our guides on how to hire an Arabic–English translator and how to hire a French–Arabic translator in Lebanon walk through what a strong candidate looks like.

The back-translation test (and its limits)

The classic trick for a text you can't read is back-translation: have a second, independent person translate the finished work back into your original language, then compare it to what you started with.

How to do it properly:

• Use a different translator than the one who did the work — never the same person, and never a machine tool checking a human, or you learn nothing.
• Give the back-translator only the translated text, not your original. They shouldn't know what it "should" say.
• Compare meaning, not wording. Small phrasing differences are normal and fine. What you're hunting for are changes in meaning: a "must" that became a "may," a number that shifted, a negative that flipped to a positive, a whole sentence that vanished.

The limit to understand: back-translation catches meaning errors and omissions, but it does not reliably catch tone, style, or natural flow. A translation can back-translate perfectly and still read stiff, robotic, or foreign to a native speaker. That's why you also need a native reviewer.

Hire a second native speaker to review

For anything that matters — a website, a contract, a campaign — pay a second native speaker to review the final text. This is the single most reliable quality check that exists, and it's cheap relative to the damage a bad public translation does.

Give the reviewer specific questions instead of a vague "is this good?":

• Does it read like it was written by a native, or does it read translated?
• Is the tone right for the audience (formal, casual, Gulf, Lebanese)?
• Are there grammar or spelling mistakes?
• Did anything get left out or added compared to the source?
• Would you be comfortable publishing this under your own name?

A vague brief gets you a vague "looks fine." Specific questions get you a real review. On a marketplace this is easy to arrange: you hire the translator and a separate reviewer as two small jobs, and the reviewer has no reason to protect the first person's work.

Simple checks you can run yourself

Even without reading the language, you're not helpless. A few mechanical checks catch a surprising share of problems.

• Numbers, dates, names, prices. These look the same-ish across languages. Sit with the source and the translation side by side and confirm every phone number, price, date, and proper name matches exactly. A wrong price or number is one of the most common and most damaging errors.
• Length and structure. If your English has five paragraphs and the Arabic has three, ask why. Missing chunks show up as missing length. (Some length change between languages is normal — French usually runs longer than English, for instance — but a big gap is a red flag.)
• Untranslated leftovers. Scan for stray words in the original language sitting inside the translation, or the reverse. Copy a suspicious line into a search engine or a free tool just to sanity-check it — not as your real QA, only as a smell test.
• The visual test for Arabic. If the text is Arabic, put it into the actual design — the website, the post, the menu — and look at it. Arabic runs right-to-left (RTL). If it comes out scrambled, punctuation lands on the wrong side, or English/numbers break the flow, you'll see it even if you can't read a word.

Watch for the machine-translation red flags

A real risk is paying for "human translation" and quietly receiving raw machine output with light edits. You can't read the language, but there are tells a native reviewer will spot fast — so ask them to look specifically for:

• Over-literal phrasing that no native would actually say.
• The wrong word for the context — a term that's technically a synonym but wrong here (common with idioms, names, and industry jargon).
• Inconsistent terms — the same word translated three different ways across the document.
• Formal/informal mismatch — flipping between registers in a way a human wouldn't.

Machine translation has its place for rough understanding, but for anything a customer or a court will read, you want a human who owns the result. The clean way to guarantee that is a clear scope and a reviewer, not blind trust.

Put money behind the checkpoints

The final piece is structuring payment so quality is checked before you've paid in full. Never pay the whole fee on delivery of a text you can't verify.

Split the job into milestones: a sample first, then the full draft, then a final payment released only after your second native reviewer has signed off. In Lebanon, be explicit that you're paying in fresh dollars, not old bank dollars (lollars), since the value gap is huge and the translator needs to know exactly what they'll receive.

This is where Furrsati helps. When you hire the translator on the platform, the money sits in escrow until you confirm the milestone is done — so you can run your back-translation and your native review before the final payment is released. Neither side loses: the translator is guaranteed payment for good work, and you don't pay for a text you haven't verified. Payouts come out the way that suits the freelancer — OMT, Whish, bank transfer, or USDT, all inside Lebanon, no Payoneer or PayPal needed. See what's involved on our translation services page.

Frequently Asked Questions

How do I check a translation if I can't read the language?

Use a second, independent person to review it — that's the core method. Back-translate the finished text with a different translator to catch meaning errors, and hire a separate native speaker to confirm the tone and flow are natural. Combine that with your own checks on numbers, names, dates, and length.

What is back-translation and does it really work?

Back-translation means having a second translator convert the finished work back into your original language so you can compare meaning. It reliably catches omissions and changes in meaning — a flipped number, a dropped sentence, a "must" that became a "may." It does not catch tone or natural flow well, so pair it with a native reviewer.

Can I just use a free online tool to check the translation?

A free tool is fine as a quick smell test — to spot untranslated leftovers or get a rough sense — but never as your real quality check. Machine output misses tone, context, and nuance, and for anything a customer or court will read, you need a human native reviewer who owns the result.

How can I tell if a "human" translation is actually machine output?

You usually can't yourself, but a native reviewer will spot the tells fast: over-literal phrasing no native would say, the wrong word for the context, the same term translated inconsistently, and register that jumps between formal and informal. Ask your reviewer to look for exactly these.

How much of my budget should go to reviewing the translation?

Treat the review as a normal, expected line item, not an extra. A paid sample and a second native reviewer cost a fraction of the full job and save you from publishing something wrong in front of your target audience. Building it into milestones means you pay for the review as part of doing the job right.

Get a translation you can actually trust

Checking work in a language you don't read comes down to a simple system: brief well and take a paid sample, back-translate to catch meaning errors, hire a second native speaker for tone, run your own checks on numbers and length, and hold payment against milestones until it all passes. When you're ready, post your translation project on Furrsati and hire trusted Lebanese and Gulf translators — plus a separate reviewer — with your money protected in escrow until you're confident it's right.