How to Fix Localisation Quality on Multilingual Pages

If your site uses hreflang to serve pages in more than one language, each version must read as if it were written for that market, not run through a translator and published. This guide shows you how to list every localised page, have native speakers review them, fix untranslated and mistranslated content, and adapt prices, dates and legal text to each locale.

By Updated ⏱ 2-4 hours per language for a priority review, then ongoing🎯 Intermediate● Medium impactContent
Illustration: Localisation quality fix guide
CONTENT · FIX GUIDE Localisation quality IMPACTEFFORT TIME2-4 hours per language for a priority review, then ongoing LEVELIntermediate

Why it matters

Google's spam policies list text translated by an automated tool without human review or curation before publishing as an example of auto-generated spam, and low-quality localised pages can rank poorly in their target market. AI answer engines also tend to quote clear, fluent passages, so awkward phrasing reduces your chances of being cited. For users, mixed-language menus, wrong currencies or literal idioms lower trust and conversion, and a mistranslated returns policy or checkout instruction can lead to complaints or legal exposure.

✕Beforeexample.com/de/versand/ reads "Wirschiffen Ihre Bestellung in 3-5Geschäftstagen" with a USD price and✓Afterexample.com/de/versand/ reads "Wirversenden Ihre Bestellung innerhalbvon 3–5 Werktagen" with EUR prices, a

What you need

A list of your localised URLs, from your sitemap, CMS or a crawler such as Screaming Frog
A native-speaking reviewer for each target language, either staff or a professional translator
Access to your CMS or translation plugin to edit localised content
Google Search Console access to see traffic by country and page

Step-by-step fix

1

List every page that has hreflang alternates

Start with the pages that declare language versions, because these are the pages that need review. Crawl the site with Screaming Frog and open the Hreflang tab, or pull the alternates from a page's HTML. Export the URLs grouped by language code such as de, fr-FR or es-MX.

text
curl -s https://www.example.com/ | grep -o '<link[^>]*hreflang="[^"]*"[^>]*>'
Pro tip: If hreflang is set in your XML sitemap instead of the HTML head, open sitemap.xml and look for xhtml:link entries.
2

Prioritise pages by traffic and revenue

In Google Search Console go to Performance > Search results, add a Country filter for each target market, and sort pages by clicks. Review these first:

  • Home page and main category or service pages
  • Product, pricing and checkout pages
  • Shipping, returns, privacy and terms pages
  • Top-performing blog posts in each market
Pro tip: Legal and checkout pages carry the most risk from mistranslation, so put them near the top even if their traffic is low.
3

Have a native speaker review each priority page

Give the reviewer the source page and the localised page side by side. Ask them to mark issues by type so fixes can be batched:

  • Untranslated: English left in menus, buttons, alt text, form errors or emails
  • Mistranslated: wrong meaning, literal idioms, wrong product terms
  • Unnatural: grammatically correct but obviously machine-translated
  • Not localised: wrong currency, date format, units, phone format or address format
text
URL | Element | Issue type | Current text | Suggested text
/de/versand/ | H1 | Mistranslated | Wir schiffen... | Wir versenden...
/de/produkt/x | Button | Untranslated | Add to cart | In den Warenkorb
Pro tip: Pick reviewers from the target market. Spanish for Mexico and Spanish for Spain use different vocabulary, so match the reviewer to the hreflang region.
4

Create a glossary and style guide per language

List your brand name, product names, key terms and terms that should stay in English, plus the approved translation for each. Add tone rules, such as formal 'Sie' or informal 'du' in German, or 'vous' or 'tu' in French. Load the glossary into your translation tool, for example DeepL glossaries, WPML Translation Management or Phrase, so future translations stay consistent.

text
source_term,de,fr,notes
Example Co,Example Co,Example Co,never translate
free shipping,kostenloser Versand,livraison gratuite,
checkout,Kasse,paiement,
account,Konto,compte,
5

Fix content, strings and locale formatting

Apply the reviewer's corrections in your CMS. Then check the template strings that page editors often miss: navigation, footer, cookie banner, form labels and validation messages, 404 page, and transactional emails. Set the correct lang attribute on each version, and show prices, dates and numbers in local formats.

Translate the title tag, meta description, image alt text and URL slug as well as the body text.

html
<html lang="de-DE">
<head>
  <title>Versand & Lieferzeiten | Example Co</title>
  <meta name="description" content="Kostenloser Versand ab 50 €. Lieferung innerhalb von 3–5 Werktagen in Deutschland und Österreich.">
  <link rel="alternate" hreflang="de-DE" href="https://www.example.com/de/versand/">
  <link rel="alternate" hreflang="en-GB" href="https://www.example.com/en/shipping/">
  <link rel="alternate" hreflang="x-default" href="https://www.example.com/en/shipping/">
</head>
Pro tip: For price and date formatting in JavaScript, use Intl.NumberFormat('de-DE', {style:'currency', currency:'EUR'}) rather than building strings by hand.
6

Remove or noindex versions you can't maintain

If a language version is mostly raw machine output and you have no reviewer for it, it is usually better to remove it than leave it live. Either redirect it to the closest reviewed version with a 301, or add noindex and remove its hreflang entries from all other versions so the hreflang sets stay reciprocal. Re-publish it once a native speaker has reviewed it.

html
<meta name="robots" content="noindex, follow">
7

Set up a review step for future translations

Add native-speaker review to your publishing workflow so new pages don't go live as raw machine output. In most CMSs this means a 'Needs review' status, or a translation job that is only marked complete after a reviewer approves it. Schedule a quarterly spot-check of 10–20 pages per language.

Pro tip: Machine translation followed by human post-editing (MTPE) is acceptable and cheaper than full human translation, provided a native speaker edits every page before it is published.
8

Check the results

Ask a second native speaker who hasn't seen the earlier review to read the top five pages in each language. Re-crawl the site to confirm the hreflang tags are reciprocal and the lang attributes are correct. After 4–8 weeks, compare clicks, CTR and conversions by country in Search Console and analytics.

Platform-specific notes

WordPress (WPML / Polylang)

In WPML, go to WPML > Translation Management to assign pages to translators and require review. Use WPML > String Translation for theme and plugin strings. In Polylang, theme strings are under Languages > Translations. WooCommerce emails and checkout strings often need a separate WPML or Polylang add-on.

Shopify

Use Shopify's Translate & Adapt app (Settings > Languages > Translate) to edit auto-translations. Check the theme content, checkout, notifications and the metafields sections separately. Set local currencies in Settings > Markets so prices aren't simply converted USD amounts.

Wix

Go to Settings > Multilingual and open the Translation Manager. Auto-translated text is shown there, and each item must be edited and saved. Check menus, forms and SEO settings (Page > SEO Basics) in each language.

Webflow

With Webflow Localization, switch the locale in the Designer and edit text directly. Machine-translated locales should be reviewed page by page. Translate CMS items, SEO title, meta description and slugs per locale in the page or collection settings.

Next.js

Translations usually live in JSON message files used by next-intl or similar libraries. Have reviewers edit those files or a connected TMS (for example Crowdin or Lokalise), and set the lang attribute per locale in the root layout.

Check that it worked

✅ How to verify

  • A native speaker who didn't do the original review reads the top pages in each language and finds no untranslated strings or unnatural phrasing.
  • A crawl in Screaming Frog shows no hreflang errors in the Hreflang tab, and the html lang attribute matches the hreflang code on every localised page.
  • Visiting each localised checkout and contact form shows local currency, date formats and translated error messages.
  • Search Console Performance, filtered by country, shows stable or rising CTR for localised pages over the following 4–8 weeks.

⚠️ Common mistakes

  • Translating only the body text and leaving title tags, meta descriptions, alt text, buttons and form errors in English.
  • Using one reviewer for all variants of a language, such as Spanish for Spain and for Mexico, or Portuguese for Portugal and for Brazil.
  • Converting the currency symbol without localising shipping terms, VAT wording or legal pages for that market.
  • Noindexing or deleting a language version but leaving hreflang links to it on the other versions.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

Does Google penalise machine-translated content?

Google's spam policies list text translated by an automated tool without human review or curation as an example of spammy auto-generated content. Machine translation is fine as a starting point. The risk comes from publishing it without a human editing it for accuracy and usefulness.

Is DeepL or ChatGPT good enough for website translation?

They produce strong first drafts, but they still miss product terminology, tone, legal nuance and local conventions. Use them with a glossary, and have a native speaker post-edit every page before it goes live.

Should I translate URL slugs?

Yes, where your platform supports it. Localised slugs such as /de/versand/ instead of /de/shipping/ look more trustworthy in search results. If you change existing slugs, add 301 redirects and update your hreflang tags.

How do I know if my localised pages are low quality?

Look for high bounce rates or low conversion rates by country compared with your main market, English text left in templates, and customer support questions caused by confusing wording. A native-speaker review of your top pages is the most reliable test.