Audit a multilingual website

GUIDE / PROTOCOL

Audit a multilingual website

A language version should answer its reader in that language and lead to the right page throughout the journey.

Direct answer

What should a multilingual audit check?

Inventory pages and variants, then compare technical declarations with the content actually served. A valid URL is insufficient when text, links, forms or images send readers to another language.

01 / Review method

Review method

01

Map the variants

For each canonical page, record available languages, URLs, missing variants and pages with genuinely equivalent topics.

02

Inspect signals

Check status, self-referencing canonical per language, reciprocal hreflang, x-default, sitemap and the document lang attribute.

03

Read as a visitor

Review headings, menus, cards, FAQs, forms, validation messages, internal links and image alternatives in every language.

04

Test the entire journey

Switch language mid-journey, follow links, submit dummy data and check mobile rendering, including right-to-left layouts.

02 / Evidence to keep

Evidence to keep

URL matrix

One row per page intent, with variants, status, canonical and reciprocity.

Content capture

Title, main answer, navigation, form and check date for each language.

Issue log

Untranslated string, wrong-language link, missing variant or changed meaning, with priority.

Native review

Have decisive text checked by a proficient reader and record corrections.

AFTER THE REVIEW

Decide from the evidence

01

A translation has no equivalent page

Do not declare hreflang to a page answering a different intent. Build a useful counterpart or leave the relation absent and guide readers another way.

02

The language switcher loses context

Connect variants of the current page, then test the full journey, forms and internal links in every language.

03 / FAQ

Frequently asked questions

Should every canonical point to French?

No. An equivalent translated page may declare its own URL as canonical.

Can an incomplete language be published?

Yes, if available pages have value and omissions are explicit; do not declare a nonexistent variant.

Why test forms?

Labels, errors, acknowledgements and redirects can remain in another language after the page appears translated.

What if two markets use the same language?

Add regional variants only when the content or offer genuinely differs, and document the target codes and URLs.

Describe a context