Book a call

Review AI Translated Website Content Before Publishing

A translated service page can quietly change a promise your business has approved. Give one page and its enquiry journey a review you can inspect before it goes live.

A translated page can change the promise a buyer reads

Imagine an approved service page says, “We aim to reply within two working days after receiving a complete brief.” In this hypothetical example, a language reviewer finds that the translation drops the expression of intent, the working-day qualification and the requirement for a complete brief. A visitor could now read an unconditional promise to reply within two days.

If you can't read the target language, you need evidence that the translation preserves the approved promise and its conditions.

The European Commission's explanation of revision and post-editing describes post-editing as correcting machine-generated translations. It distinguishes a light edit for basic accuracy and understanding from a full edit for clearer, polished output. Agree how thorough the review should be before someone begins checking a public page.

Off Piste recommends starting with one service page and its enquiry journey. The review needs business approval, qualified language review, checks of the implemented page and a named owner for the release decision.

Define one service page and its enquiry journey

Choose a page whose source copy the business has already approved. Record its URL, saved version and approval date, then name the target language and intended market. “French for customers in France” is a more useful brief than “French” when service availability or local conventions affect the offer.

Assign a service owner to confirm the promise, a linguistic reviewer to compare source and target, a developer to repair implementation defects and a release owner to decide when publication can proceed. One person may hold several roles if they have the competence and authority for each.

Include the page title and description, navigation, buttons, form labels, help text, validation errors, confirmation screen and automated acknowledgement. If the translated page leads to a form in the source language without explanation, the customer path is unfinished.

Confirm which language the team can support after submission. If replies will be in another language, agree how to explain that before the visitor sends an enquiry. Use the wider AI assisted content workflow to coordinate this pilot with your other editorial checks.

Give the reviewer approved source copy and terminology

Save the exact source version used for translation. Identify claims, exclusions, prices, units, currencies, dates and qualifications that must retain their meaning. In the response-time example, the service owner should explicitly confirm that the wording describes an aim, counts working days and starts only after a complete brief arrives.

If the source doesn't explain what a complete brief means, ask its owner to resolve that ambiguity. A reviewer shouldn't have to invent a business rule to make the translation read naturally. Update the approved source first if clarification changes the promise.

Use an approved content brief and source pack to keep the baseline and supporting evidence together. Add a short locale glossary that records each important term, its intended meaning, approved target wording where available and names or product terms that should remain unchanged. Have the language reviewer confirm proposed target terms before treating them as approved.

Supply a few approved terminology and voice examples so the reviewer can judge audience suitability. Agree which expressions may be adapted and which commitments require close preservation. Record the translation tool or workflow, generation date and output version so you can trace later corrections to the draft the reviewer checked.

Commission qualified source and target language review

For this pilot, Off Piste recommends a language professional competent in both languages, the intended locale and the subject matter. Ask about relevant website review experience and how they'll document findings. Choose someone who can assess service exclusions and technical promises as well as everyday language.

Agree the review scope in writing. It should cover accuracy against the source, omissions, approved terminology, suitability for the intended audience and whether critical commitments retain their meaning. Specify that the work includes the rendered page and enquiry messages after implementation. The Commission's distinction between light and full post-editing helps explain why a request to “check the translation” needs a clearer brief.

Ask the reviewer to flag uncertainty and return ambiguous source wording to its owner. Contractual, regulated or sector-sensitive material also needs the appropriate specialist's review. The service owner remains responsible for confirming what the business can deliver.

Back-translation and a second AI model can surface questions, but they can't independently establish correctness. Linguistic approval needs qualified source-to-target review.

Record defects and verify the repaired version

A useful finding identifies the passage, explains the change in meaning and states what must happen next. The localisation quality issue types in W3C ITS 2.0 distinguish terminology, mistranslation and omission, among other categories. You can adapt a small set for a practical review record without claiming certification or introducing a scoring system.

  • Mistranslation means the target conveys a different meaning from the source.
  • Omission means necessary linguistic content is missing.
  • Terminology covers incorrect domain terms or inconsistent use of agreed terms.
  • Locale convention issues can cover unsuitable date, currency or number formats. This is a plain-language grouping for the pilot record, rather than a single ITS category.

Keep the record short enough that you can use it for every material finding. Include source version and passage, target version and location, defect category, business consequence, required repair, repair owner, reviewer recheck and final outcome. Store the actual source and target passages in your working record. Include an explanation in a language the marketing lead can read if needed.

For the hypothetical response-time finding, the review follows three steps.

  1. The reviewer compares approved source version S1 with target draft T1 and identifies the response-time paragraph. They record that the target has lost the intent, working-day and complete-brief qualifications, creating a broader commitment.
  2. The service owner confirms that all three qualifications must remain. The repair instruction asks the language professional to restore that meaning in natural target-language wording. The reviewer chooses the wording.
  3. The repair owner saves target version T2. The reviewer compares T2 against S1 again, confirms the conditions are preserved and records the outcome with their name and date. Any unresolved ambiguity returns to the service owner.

In a real review, retain the verified bilingual evidence alongside the explanation. Close the finding after the reviewer checks the repair.

Test the translation on the published customer path

Once the developer has implemented the approved wording, give the linguistic reviewer access to the rendered preview. Ask them to inspect the page in context, including the response-time sentence and the messages surrounding the form. Copy can be correct in a document and still be missing or clipped in the template.

Work through the journey in the order a customer would, recording the URL, device or viewport, result and repair owner for each failure.

  1. Use the language switch from the source page. Confirm that it reaches the equivalent translated service page and that the visitor can switch back deliberately.
  2. Read the page on mobile and desktop. Check for missing translations, clipped buttons, text expansion, reading order and text direction where applicable. Follow service and enquiry links to their intended destinations.
  3. Open the form and inspect labels, instructions and help text. Submit incomplete or invalid entries to expose validation messages, then confirm that the corrected form can be submitted.
  4. Make an authorised test enquiry. Check the confirmation screen, receipt by the business and any automated acknowledgement. Have the reviewer verify those messages and confirm that the promised support language matches the team's actual capability.

W3C's guidance on reaching translated pages recommends language links that let people change their preference. It also cautions against using country flags to identify languages. Language names let visitors choose their preferred reading language directly.

In the worked example, the acknowledgement must preserve the approved response expectation too. If it still promises an unconditional two-day reply, the journey needs another repair even though the service paragraph passed review.

Separate linguistic findings from implementation defects so each reaches the right owner. A missing qualification goes back for language repair and recheck. A clipped button or form that loses the selected language needs a developer. If your team can't resolve those defects, get help with website publishing and enquiry path implementation before approving the journey.

Give the developer a bounded language and search handoff

Alongside the customer-path test, ask the developer to verify language handling and discovery on the implemented version.

  • Declare the page's default language on the HTML element and mark passages in another language where appropriate, following W3C's language declaration guidance.
  • Confirm distinct URLs for language versions, consistent visible language in content and navigation, and working links between equivalent pages. Google's multilingual site guidance recommends separate language URLs and explains that Google determines language from visible content.
  • Where hreflang is implemented, check fully qualified alternate URLs and reciprocal references. Each language version's set should include itself and the other versions, as specified in Google's alternate-language requirements.

HTML language declarations help software interpret the content. Search annotations identify alternate versions. Google says it doesn't use hreflang or the HTML lang attribute to detect the page's language, so these checks serve different purposes.

Record unresolved URL or annotation issues for the person responsible for technical SEO. If you need external support, discuss the site's SEO foundations and establish the specific implementation scope. These checks don't guarantee indexing or rankings.

Approve a version and reopen it when the source changes

The release owner needs a record that identifies exactly what passed. Save the source and target versions, reviewed URL, language and market, linguistic reviewer approval, service-owner approval, resolved findings, journey-test result and approval date. Use the wider finished content audit for publication checks beyond the translation-specific work.

Hold publication when a material meaning error remains, critical wording hasn't been reviewed, the enquiry path is broken or nobody owns the release decision. In the hypothetical pilot, approval follows the reviewer's recheck of T2 and a successful test of the implemented response-time wording through the acknowledgement. If implementation changes that wording, reopen the affected finding before release. Check the live URL after publication against the approved version.

A later change to a price, claim, exclusion, service area or availability can invalidate the translated copy. Changes to forms, templates and acknowledgements can also reopen the journey test. Tie each translation to its source version and add affected locales to your post-publication evidence maintenance record. Name the person who checks whether a source edit requires a translation update.

Start by listing one service page and every message between its language switch and enquiry acknowledgement. Identify the missing approval or broken step, then give it an owner. If the gap is linguistic competence, commission a qualified language professional. If it's implementation, assign the developer and agree the recheck.