Multilingual SEO: plan around the buyer, not the translation

One product, different questions

A literal translation may preserve the sentence and still miss the question a buyer would ask. Start by collecting the terms customers use for the product, its application and the problem it addresses. Do not assume a translated keyword has the same search intent.

Build a content brief for each language

Record the intended reader, the decision the page supports, the approved product facts and the next step. A shared product reference helps prevent conflicting specifications, while language-specific examples can make the material easier to understand.

Give each page one clear primary question. Use related questions as sections or separate supporting articles when they require substantial explanation.

Give language versions stable URLs

Google recommends distinct URLs for different language versions and appropriate annotations. Make language navigation available to readers and ensure each version can be accessed directly.

A language selector should take the reader to the equivalent content where it exists. When a translation is not ready, do not advertise an alternate URL that leads to an empty or unrelated page.

Review facts as well as fluency

Check units, product names, technical specifications and commercial statements as part of the language review. Assign someone to resolve factual conflicts. Fluent writing cannot compensate for a specification that changes between versions.

When a product or offer changes, review the related translations together. Use meaningful update dates that reflect actual changes rather than refreshing dates to create an appearance of freshness.

Write a page brief before requesting translation

Record the target language and buyer role, primary question, confirmed product facts, local units, decision-supporting material and enquiry route. Corporate introductions and buyer-facing explanations can share a factual foundation without mirroring every sentence.

Check terminology against customer language or relevant industry material. Language editors should not fill gaps in specifications, certifications or delivery terms with assumptions.

Test the complete language journey before publishing

Reach the article or product through the language-specific navigation, switch to the equivalent topic and continue to an enquiry form with matching feedback. Review titles, image descriptions, link labels and error messages as well as body copy.

When a language version is removed or consolidated, update internal links, alternate-language annotations and the sitemap together. Keep a correction record so outstanding translations remain visible.

References

• Google Search: managing multilingual sites ↗