A translated page can be linguistically accurate and still fail in production. This multilingual website QA checklist helps you test language switching, URLs, metadata, hreflang connections, links, forms, structured page elements, accessibility labels, and search visibility before and after publishing.
Overview
Multilingual content quality assurance has two connected parts: reviewing the translated content itself and checking whether the website delivers it correctly. The first part covers meaning, terminology, tone, and readability. The second covers the technical and user experience details that determine whether visitors can find, understand, and use the page.
Run this checklist for a single translated article, a product collection, a new language launch, or a large website migration. Keep a record of the page tested, language, reviewer, date, issue, severity, and resolution. A simple issue log prevents the same localization bug from being rediscovered during every release.
Use the following priority levels to decide what to fix first:
| Priority | Examples | Recommended action |
|---|---|---|
| Critical | Wrong-language page, broken checkout, inaccessible form, incorrect legal or safety information | Hold publication or fix immediately |
| High | Broken language switcher, incorrect canonical or hreflang connection, missing title, broken primary link | Fix before promotion and preferably before indexing |
| Medium | Untranslated labels, awkward line breaks, inconsistent terminology, missing localized image text | Resolve in the current content cycle |
| Low | Minor spacing, punctuation, or nonessential copy issues | Log and include in the next maintenance pass |
For the language and terminology portion of the review, pair this process with a translation quality assurance checklist and an approved glossary or style guide. Technical checks cannot compensate for a page that communicates the wrong meaning.
Checklist by scenario
Before publishing a translated page
- Confirm that the page is assigned to the intended language and regional variant.
- Check the language switcher from the original page and the translated page. It should lead to the equivalent version, not simply to a language home page.
- Open the page in a private browser window or a browser profile with no saved preferences. Confirm that language detection, redirects, and manual language selection behave as intended.
- Review the translated URL slug. Check spelling, readability, allowed characters, redirect behavior, and consistency with the site’s URL convention.
- Verify the page title, meta description, heading hierarchy, and visible introduction. Each should be written for the target audience rather than copied mechanically from the source language.
- Check the canonical URL and language annotations, including hreflang relationships where the site uses them. Confirm that language versions reference the correct equivalents and that the set is consistent in both directions.
- Test internal links. They should point to translated destinations when those destinations exist, rather than sending users back to an unrelated source-language page.
- Inspect buttons, navigation labels, search prompts, cookie controls, error messages, account areas, and other interface strings for untranslated or truncated text.
- Review images, captions, charts, downloadable files, video subtitles, tooltips, and embedded content. Text inside an image may need a localized asset or an accessible text alternative.
- Check dates, times, number formats, measurement units, currencies, addresses, and contact details against the market and content brief.
Before a campaign, seasonal update, or high-traffic release
- Recheck promotional claims, availability dates, discount terms, and calls to action in every active language.
- Submit each important form using realistic localized data. Test required fields, validation messages, confirmation emails, and success pages.
- Test the complete purchase, registration, download, or inquiry journey on desktop and mobile layouts.
- Confirm that campaign links retain their tracking parameters without creating malformed or language-inconsistent URLs.
- Check whether translated headings, buttons, and banners expand or wrap in a way that hides information or changes the visual hierarchy.
- Verify that scheduled content, cached pages, feeds, and social previews show the intended language and metadata.
After publishing or migrating a language set
- Fetch or open a sample of published URLs from each language and template type.
- Run a broken-link scan, then manually inspect high-value links such as navigation, category pages, forms, downloads, and conversion paths.
- Use the site’s analytics, logs, or search tools to look for unexpected redirects, soft error pages, spikes in exits, and visits landing on the wrong language.
- Inspect the rendered HTML rather than relying only on the CMS editing screen. This helps reveal missing metadata, duplicated elements, or strings that remain hidden in the editor.
- Review indexing signals using the site’s chosen search and webmaster tools. Treat reports as diagnostic evidence and investigate representative URLs instead of assuming that one report describes every page.
- Compare the final page against the approved source and translation files. A migration can remove content that was present during translation review.
What to double-check
Language relationships and SEO elements
Language versions need clear relationships. Check that the switcher, alternate links, canonical URLs, XML sitemaps where applicable, and internal links agree about which pages are equivalents. Look for self-referencing errors, missing return connections, links to redirected URLs, and references to pages that do not exist. Use the documentation for the current CMS and search tooling when validating implementation details, since field names and workflows vary.
Review keyword targeting independently for each market. A direct translation of a source keyword may not match how local users search. The multilingual keyword research workflow can help editors separate translation from search-term selection. Confirm that the chosen terms appear naturally in the title, headings, copy, and metadata without forcing repetition.
Accessibility and layout
Check the page language attribute, accessible names for controls, alt text, captions, form instructions, and error messages. Test keyboard navigation and zoom, then inspect narrow screens. Languages can change line length, word order, punctuation, and text direction. If a right-to-left language is supported, verify directionality in the page, components, icons, forms, and mixed-language strings rather than checking only the body copy.
Forms, data, and transactional content
Localization gaps often appear after the visitor clicks a translated call to action. Test every handoff: the form, validation, confirmation, email, account screen, payment or booking step, and support message. Check that currency and date displays are understandable, while stored values remain consistent for internal systems. Review legal, consent, shipping, and contact information with the appropriate content owner before release.
Common mistakes
- Testing only the page body: Metadata, navigation, forms, image labels, and system messages are part of the localized experience.
- Assuming a successful CMS publish means a successful launch: Preview and production environments can differ. Always test the rendered public URL.
- Using machine translation output without a review path: Automated workflows can speed up drafts, but terminology, context, and sensitive claims still need appropriate human review. See how to review AI translations.
- Linking every language switcher to a homepage: This makes users repeat their search and can hide missing page equivalents.
- Checking only one device or browser: Test representative browsers, screen sizes, and input methods, especially for menus and forms.
- Treating untranslated text as a minor cosmetic issue: A missing button label, alt attribute, or error message can block a task or create an accessibility problem.
- Changing URLs without a redirect and mapping plan: Record old and new URLs, test redirects, and update internal links and language relationships together.
- Publishing all languages at once without sampling: A smaller staged release makes it easier to identify whether a problem belongs to the translation, template, integration, or deployment process.
When to revisit
Use this checklist whenever a translated page is created, revised, migrated, or connected to a new template. Schedule a broader multilingual SEO and localization audit before seasonal planning cycles, major campaigns, redesigns, CMS releases, domain changes, and new language launches. Revisit it after installing translation integrations, changing URL rules, modifying forms, or updating navigation and structured page components.
For an efficient recurring process, divide the work into three passes:
- Content pass: terminology, meaning, tone, readability, dates, currency, and market relevance.
- Experience pass: language switching, navigation, layouts, forms, accessibility, media, and mobile behavior.
- Technical pass: URLs, redirects, metadata, canonicals, hreflang, internal links, rendered HTML, and indexing signals.
End each audit by saving the tested URL set, recording unresolved issues, assigning owners, and noting the next review trigger. That small record turns website translation testing from a one-time launch task into a repeatable part of multilingual publishing.