Localisation report
dropbox.com
Product: Dropbox provides secure cloud storage for storing, sharing, and accessing files across devices. Its products also support collaboration workflows such as video review, document signing, content organization, and secure document sharing.
Brand voice: clear, practical, collaborative
Localisation score
75/100
GoodThe website is generally well localised, with some issues to improve.
Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
Rank #9 of 24 public audits
Untranslated call to action
A de page still uses source-language CTA copy. Affects 10 sampled pages.
Found here
Pricing hero · <button>
https://www.dropbox.com/de/What we saw
Primary CTA: "Marketing" Seen on 10 pages, e.g. https://www.dropbox.com/de/, https://www.dropbox.com/es/, https://www.dropbox.com/fr/
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
No CJK-capable font detected
A ja page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
Found here
Page body · font-family
https://www.dropbox.com/ja/What we saw
font-family: var(--dig-type__family__action), var(--dig-type__family__action, var(--__dwgAtlasGroteskStack), var(--__dwgSharpGrotesk20BookStack) Seen on 2 pages, e.g. https://www.dropbox.com/ja/, https://www.dropbox.com/ko/
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Incorrect language code
html lang "es-419" is not a well-formed language or locale tag.
Found here
Document head · <html lang>
https://www.dropbox.com/es/What we saw
<html lang="es-419">
How to fix it
Use a well-formed BCP 47 language tag, such as en or fr-FR.
11 passed · 20 to fix · 4 not applicable
Locale detection
Fail88technicalPages should declare a correct html lang that matches the URL and content locale.
Incorrect language code
html lang "es-419" is not a well-formed language or locale tag.
Found here
Document head · <html lang>
https://www.dropbox.com/es/What we saw
<html lang="es-419">
How to fix it
Use a well-formed BCP 47 language tag, such as en or fr-FR.
Language switcher
Fail84technicalVisitors should move between locales without losing the current page.
Locale routes and labels are present
The evidence shows locale-specific routes for English, German, and Spanish, with localized language-selector labels. Preservation of the exact current page beyond the homepage is not demonstrated.
Found here
Header · <button>
https://www.dropbox.com/What we saw
"url":"https://www.dropbox.com/de/" ... "buttons":["Produkte","Lösungen","App herunterladen","Deutsch",...]; "url":"https://www.dropbox.com/es/" ... "buttons":["Productos","Soluciones","Obtener la aplicación","Español (Latinoamérica)",...]
How to fix it
Test switching languages from several interior pages and verify that the equivalent localized page is retained, not just the homepage.
Structured data
Fail0technicalJSON-LD inLanguage should match the page locale when structured data is present.
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Found here
JSON-LD · <script type="application/ld+json">
https://www.dropbox.com/What we saw
BreadcrumbList is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
International formatting
Fail55technicalDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
Formatting coverage is not demonstrated
The supplied page extracts contain no dates, numbers, currencies, calendars, or Arabic-digit examples, so locale-specific formatting cannot be verified.
Found here
Page content · <body>
What we saw
The provided page extracts list navigation, headings, and product copy but contain no date, number, or currency markup or values.
How to fix it
Audit representative localized pages containing dates, quantities, prices, and currencies, and verify each against the locale’s formatting conventions.
Accessibility localisation
Fail78technicallang, aria-label, and alt text should match the page locale.
Document language is localized in sampled pages
The sampled English, German, and Spanish pages expose localized HTML language values. No aria-label or alt-text values are included in the evidence, so those attributes remain unverified.
Found here
Document metadata · <html>
https://www.dropbox.com/de/What we saw
"url":"https://www.dropbox.com/de/" ... "htmlLang":"de"; "url":"https://www.dropbox.com/es/" ... "htmlLang":"es-419"; "url":"https://www.dropbox.com/" ... "htmlLang":"en"
How to fix it
Inspect localized pages for aria-label and alt attributes, then translate them consistently with the visible UI and document language.
Translation completeness
Fail0linguisticLocalized pages should not leave source-language copy in place, except brand names and URLs.
Untranslated call to action
A de page still uses source-language CTA copy. Affects 10 sampled pages.
Found here
Pricing hero · <button>
https://www.dropbox.com/de/What we saw
Primary CTA: "Marketing" Seen on 10 pages, e.g. https://www.dropbox.com/de/, https://www.dropbox.com/es/, https://www.dropbox.com/fr/
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Terminology consistency
Fail40linguisticImportant concepts should not be translated differently across pages.
Terminology inconsistency
"Teams" appears both untranslated and translated across de pages. Affects 16 sampled pages.
Found here
Header · <nav> or <button>
https://www.dropbox.com/de/What we saw
"Teams" appears untranslated on some de pages and translated on others Seen on 11 pages, e.g. https://www.dropbox.com/de/, https://www.dropbox.com/es/, https://www.dropbox.com/fr/
How to fix it
Use one translated label for "Teams" across de pages.
Brand voice
Fail88linguisticLocalized copy should preserve the intended tone of the source.
Core promotional tone is retained
The sampled localized titles and hero copy preserve the source’s concise, benefit-led promotional tone.
Found here
Page title and hero · <title>, <h1>
https://www.dropbox.com/es/What we saw
Source title: "Dropbox: Secure cloud storage, file sharing, and more"; German title: "Dropbox: Sicherer Cloud-Speicher, Dateifreigabe und vieles mehr"; Spanish title: "Dropbox: almacenamiento seguro en la nube, uso compartido de archivos y más"
Grammar and style
Fail88linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
Sampled locale-specific forms appear consistent
The evidence shows localized capitalization and phrasing in German and Spanish navigation, headings, and titles, with no explicit grammar error in the supplied samples.
Found here
Navigation and headings · <nav>, <h1>
https://www.dropbox.com/de/What we saw
German: "Produkte", "Lösungen", "Anwendungsfälle", "Branchen"; Spanish: "Productos", "Soluciones", "Casos de uso", "Industrias"
Cultural adaptation
Fail55contextualCurrency, dates, addresses, and local examples should fit the market.
Market-specific adaptation is not evidenced
The supplied extracts show locale labels and translated copy, but no localized currency, dates, addresses, or market-specific examples to assess cultural fit.
Found here
Page content · <body>
What we saw
The provided extracts contain navigation, headings, product descriptions, and language labels, but no currency, date, address, or local-example values.
How to fix it
Review pricing, date displays, contact details, and market examples for each target market and localize them where appropriate.
Product context
Fail89contextualLanguage should match product concepts such as plans, settings, and workflows.
Product terminology is retained in sampled locales
The localized content preserves recognizable Dropbox product names and workflow concepts, including Replay, Sign, Reclaim.ai, and Dash.
Found here
Product feature list · <body>
https://www.dropbox.com/de/What we saw
"Replay Review and approve videos faster Sign Request and add signatures to documents Reclaim.ai Schedule habits, tasks, and meetings with AI Dash Find, organize, and protect company content"; German: "Replay Videos schneller überprüfen und genehmigen ... Sign Anfordern und Hinzufügen von Unterschriften ..."
Contextual meaning
Fail89contextualStrings should be judged in surrounding page and component context, not in isolation.
Surrounding page context supports the sampled translations
Navigation, headings, titles, and feature descriptions align across the sampled source, German, and Spanish page extracts, supporting contextual rather than isolated translation.
Found here
Page structure · <title>, <nav>, <h1>, <body>
https://www.dropbox.com/es/What we saw
German structure: "Produkte" / "Anwendungsfälle" / "Branchen" / "An die Arbeit – mit deutlich weniger Aufwand"; Spanish structure: "Productos" / "Casos de uso" / "Industrias" / "Completa más trabajo trabajando menos"
Text expansion
Fail40visualLonger translations should not create obvious length pressure versus the source UI.
Localized text is much longer than the source
A de string is 182% the length of the source, which often causes overflow. Affects 26 sampled pages.
Found here
Control · <button>
https://www.dropbox.com/de/What we saw
EN "Watch testimonial" → DE "Jetzt Erfahrungsbericht ansehen" (182%) Seen on 8 pages, e.g. https://www.dropbox.com/de/, https://www.dropbox.com/es/, https://www.dropbox.com/fr/
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Fail62visualTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
No CJK-capable font detected
A ja page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
Found here
Page body · font-family
https://www.dropbox.com/ja/What we saw
font-family: var(--dig-type__family__action), var(--dig-type__family__action, var(--__dwgAtlasGroteskStack), var(--__dwgSharpGrotesk20BookStack) Seen on 2 pages, e.g. https://www.dropbox.com/ja/, https://www.dropbox.com/ko/
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Fail58visualLanguage-specific images and alt text should match the page locale.
Image still looks like the source locale
Alt text or filename on a ja page appears to be English. Affects 2 sampled pages.
Found here
Page body · <img alt>
https://www.dropbox.com/ja/What we saw
alt="ファイルの同期と共有の画面が表示されたデスクトップ版 Dropbox とモバイル版 Dropbox" src="https://fjord.dropboxstatic.com/warp/conversion/dropbox/warp/en-us/index/desktop-mobile-fss-1440x1440-ja.png?id=6f063d1a-9ac3-4c00-835e-ab1bf83038da&output_type=png" Seen on 2 pages, e.g. https://www.dropbox.com/ja/, https://www.dropbox.com/ko/
How to fix it
Localize the image asset and alt text for this page locale.
Visual hierarchy
Fail55visualLocalization should not make headings or CTAs lose scanability.
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 39 sampled pages.
Found here
Page body · heading
https://www.dropbox.com/What we saw
Dropbox teams up with McLaren Racing as an Official Technology Partner of McLaren Formula 1 Team Seen on 14 pages, e.g. https://www.dropbox.com/, https://www.dropbox.com/de/, https://www.dropbox.com/es/
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fail82visualRepeated components should stay visually consistent across locales.
Structural consistency is visible, visual consistency is unverified
The sampled locales expose corresponding button and heading groups, but the evidence contains no screenshots or computed styles to confirm visual consistency.
Found here
Header and page structure · <nav>, <button>, <h1>
https://www.dropbox.com/de/What we saw
English buttons: "Products", "Solutions", "Get app"; German buttons: "Produkte", "Lösungen", "App herunterladen"; Spanish buttons: "Productos", "Soluciones", "Obtener la aplicación"
How to fix it
Compare rendered screenshots or computed styles across locales and verify that equivalent components retain the same spacing, hierarchy, and treatment.
Text overflow
Fail78visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Overflow cannot be confirmed from text extracts
The German and Spanish labels differ in length from the English labels, but no rendered dimensions or screenshots show whether any button or navigation text clips or overflows.
Found here
Header · <button>
https://www.dropbox.com/es/What we saw
English: "Get app"; German: "App herunterladen"; Spanish: "Obtener la aplicación"
How to fix it
Test the longest localized labels at supported widths and allow buttons and navigation items to wrap, resize, or reflow without clipping.
Layout breakage
Fail78visualLocalized pages should not overlap, break grids, or overflow modals.
Layout integrity is not directly evidenced
The extracts show corresponding page structures across locales but provide no rendered layout, dimensions, or screenshots to verify grid, overlap, or modal behavior.
Found here
Page layout · <body>
What we saw
The evidence provides page status, language, buttons, headings, and text extracts, but no screenshot or layout measurement.
How to fix it
Run visual regression checks for each locale, focusing on navigation, hero sections, grids, and modal content at representative viewport sizes.
Responsive localisation
Fail78visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
Responsive behavior is unverified
The evidence confirms localized pages load successfully, but it contains no mobile, tablet, or desktop screenshots or viewport-specific results.
Found here
Page layout · <body>
https://www.dropbox.com/What we saw
Sampled pages have "status":200, but the provided evidence contains no viewport dimensions or responsive render results.
How to fix it
Test each sampled locale across mobile, tablet, and desktop widths and verify that localized navigation, headings, and CTAs reflow without clipping.
Incorrect language code
html lang "es-419" is not a well-formed language or locale tag.
Found here
Document head · <html lang>
https://www.dropbox.com/es/What we saw
<html lang="es-419">
How to fix it
Use a well-formed BCP 47 language tag, such as en or fr-FR.
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Found here
JSON-LD · <script type="application/ld+json">
https://www.dropbox.com/What we saw
BreadcrumbList is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Untranslated call to action
A de page still uses source-language CTA copy. Affects 10 sampled pages.
Found here
Pricing hero · <button>
https://www.dropbox.com/de/What we saw
Primary CTA: "Marketing" Seen on 10 pages, e.g. https://www.dropbox.com/de/, https://www.dropbox.com/es/, https://www.dropbox.com/fr/
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Terminology inconsistency
"Teams" appears both untranslated and translated across de pages. Affects 16 sampled pages.
Found here
Header · <nav> or <button>
https://www.dropbox.com/de/What we saw
"Teams" appears untranslated on some de pages and translated on others Seen on 11 pages, e.g. https://www.dropbox.com/de/, https://www.dropbox.com/es/, https://www.dropbox.com/fr/
How to fix it
Use one translated label for "Teams" across de pages.
Localized text is much longer than the source
A de string is 182% the length of the source, which often causes overflow. Affects 26 sampled pages.
Found here
Control · <button>
https://www.dropbox.com/de/What we saw
EN "Watch testimonial" → DE "Jetzt Erfahrungsbericht ansehen" (182%) Seen on 8 pages, e.g. https://www.dropbox.com/de/, https://www.dropbox.com/es/, https://www.dropbox.com/fr/
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
No CJK-capable font detected
A ja page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
Found here
Page body · font-family
https://www.dropbox.com/ja/What we saw
font-family: var(--dig-type__family__action), var(--dig-type__family__action, var(--__dwgAtlasGroteskStack), var(--__dwgSharpGrotesk20BookStack) Seen on 2 pages, e.g. https://www.dropbox.com/ja/, https://www.dropbox.com/ko/
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
No Korean word-break rule found in sampled CSS
Embedded CSS was found, but it does not declare word-break: keep-all for Hangul.
Found here
CSS · word-break
https://www.dropbox.com/ko/What we saw
Sampled <style>/inline CSS declares fonts but no word-break: keep-all
How to fix it
Add word-break: keep-all for Korean text containers.
Image still looks like the source locale
Alt text or filename on a ja page appears to be English. Affects 2 sampled pages.
Found here
Page body · <img alt>
https://www.dropbox.com/ja/What we saw
alt="ファイルの同期と共有の画面が表示されたデスクトップ版 Dropbox とモバイル版 Dropbox" src="https://fjord.dropboxstatic.com/warp/conversion/dropbox/warp/en-us/index/desktop-mobile-fss-1440x1440-ja.png?id=6f063d1a-9ac3-4c00-835e-ab1bf83038da&output_type=png" Seen on 2 pages, e.g. https://www.dropbox.com/ja/, https://www.dropbox.com/ko/
How to fix it
Localize the image asset and alt text for this page locale.
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 39 sampled pages.
Found here
Page body · heading
https://www.dropbox.com/What we saw
Dropbox teams up with McLaren Racing as an Official Technology Partner of McLaren Formula 1 Team Seen on 14 pages, e.g. https://www.dropbox.com/, https://www.dropbox.com/de/, https://www.dropbox.com/es/
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Locale routes and labels are present
The evidence shows locale-specific routes for English, German, and Spanish, with localized language-selector labels. Preservation of the exact current page beyond the homepage is not demonstrated.
Found here
Header · <button>
https://www.dropbox.com/What we saw
"url":"https://www.dropbox.com/de/" ... "buttons":["Produkte","Lösungen","App herunterladen","Deutsch",...]; "url":"https://www.dropbox.com/es/" ... "buttons":["Productos","Soluciones","Obtener la aplicación","Español (Latinoamérica)",...]
How to fix it
Test switching languages from several interior pages and verify that the equivalent localized page is retained, not just the homepage.
Formatting coverage is not demonstrated
The supplied page extracts contain no dates, numbers, currencies, calendars, or Arabic-digit examples, so locale-specific formatting cannot be verified.
Found here
Page content · <body>
What we saw
The provided page extracts list navigation, headings, and product copy but contain no date, number, or currency markup or values.
How to fix it
Audit representative localized pages containing dates, quantities, prices, and currencies, and verify each against the locale’s formatting conventions.
Document language is localized in sampled pages
The sampled English, German, and Spanish pages expose localized HTML language values. No aria-label or alt-text values are included in the evidence, so those attributes remain unverified.
Found here
Document metadata · <html>
https://www.dropbox.com/de/What we saw
"url":"https://www.dropbox.com/de/" ... "htmlLang":"de"; "url":"https://www.dropbox.com/es/" ... "htmlLang":"es-419"; "url":"https://www.dropbox.com/" ... "htmlLang":"en"
How to fix it
Inspect localized pages for aria-label and alt attributes, then translate them consistently with the visible UI and document language.
Sampled translations preserve core product meaning
The German and Spanish samples retain the source actions for storing, sharing, and accessing files, as well as the localized product and navigation concepts.
Found here
Hero and navigation · <body>
https://www.dropbox.com/es/What we saw
Source: "Store, share, and access files across devices"; German: "Dateien geräteunabhängig speichern, teilen und darauf zugreifen"; Spanish: "Almacena y comparte archivos en diferentes dispositivos"
Sampled localized copy reads naturally
The available German and Latin American Spanish samples use coherent, idiomatic phrasing without an obvious machine-translation artifact.
Found here
Hero and navigation · <body>
https://www.dropbox.com/de/What we saw
German: "Sicherer Cloud-Speicher, Dateifreigabe und vieles mehr"; Spanish: "almacenamiento seguro en la nube, uso compartido de archivos y más"
Core promotional tone is retained
The sampled localized titles and hero copy preserve the source’s concise, benefit-led promotional tone.
Found here
Page title and hero · <title>, <h1>
https://www.dropbox.com/es/What we saw
Source title: "Dropbox: Secure cloud storage, file sharing, and more"; German title: "Dropbox: Sicherer Cloud-Speicher, Dateifreigabe und vieles mehr"; Spanish title: "Dropbox: almacenamiento seguro en la nube, uso compartido de archivos y más"
Sampled locale-specific forms appear consistent
The evidence shows localized capitalization and phrasing in German and Spanish navigation, headings, and titles, with no explicit grammar error in the supplied samples.
Found here
Navigation and headings · <nav>, <h1>
https://www.dropbox.com/de/What we saw
German: "Produkte", "Lösungen", "Anwendungsfälle", "Branchen"; Spanish: "Productos", "Soluciones", "Casos de uso", "Industrias"
Sampled CTAs communicate the intended actions
The localized buttons preserve the source actions to get the app, watch a testimonial, and watch a webinar.
Found here
Header and hero · <button>
https://www.dropbox.com/de/What we saw
Source: "Get app", "Watch testimonial", "Watch webinar"; German: "App herunterladen", "Jetzt Erfahrungsbericht ansehen", "Jetzt das Webinar ansehen"; Spanish: "Obtener la aplicación", "Ver el testimonio", "Mira el seminario web"
Market-specific adaptation is not evidenced
The supplied extracts show locale labels and translated copy, but no localized currency, dates, addresses, or market-specific examples to assess cultural fit.
Found here
Page content · <body>
What we saw
The provided extracts contain navigation, headings, product descriptions, and language labels, but no currency, date, address, or local-example values.
How to fix it
Review pricing, date displays, contact details, and market examples for each target market and localize them where appropriate.
Buttons and navigation retain UI roles
The sampled localized strings remain short action or navigation labels and are presented in the evidence as buttons and headings in the same component roles as the source.
Found here
Header · <button>
https://www.dropbox.com/es/What we saw
Source buttons: "Products", "Solutions", "Get app"; German buttons: "Produkte", "Lösungen", "App herunterladen"; Spanish buttons: "Productos", "Soluciones", "Obtener la aplicación"
Product terminology is retained in sampled locales
The localized content preserves recognizable Dropbox product names and workflow concepts, including Replay, Sign, Reclaim.ai, and Dash.
Found here
Product feature list · <body>
https://www.dropbox.com/de/What we saw
"Replay Review and approve videos faster Sign Request and add signatures to documents Reclaim.ai Schedule habits, tasks, and meetings with AI Dash Find, organize, and protect company content"; German: "Replay Videos schneller überprüfen und genehmigen ... Sign Anfordern und Hinzufügen von Unterschriften ..."
Surrounding page context supports the sampled translations
Navigation, headings, titles, and feature descriptions align across the sampled source, German, and Spanish page extracts, supporting contextual rather than isolated translation.
Found here
Page structure · <title>, <nav>, <h1>, <body>
https://www.dropbox.com/es/What we saw
German structure: "Produkte" / "Anwendungsfälle" / "Branchen" / "An die Arbeit – mit deutlich weniger Aufwand"; Spanish structure: "Productos" / "Casos de uso" / "Industrias" / "Completa más trabajo trabajando menos"
Copy remains appropriate for a broad work-productivity audience
The sampled copy consistently addresses teams and work use cases while describing practical file, video, signature, and content workflows.
Found here
Headings and feature list · <h1>, <body>
https://www.dropbox.com/es/What we saw
"Teams"; "Use cases"; "Find, organize, and share your work, all in one place"; German: "Teams", "Anwendungsfälle"; Spanish: "Dropbox para equipos", "Casos de uso"
Structural consistency is visible, visual consistency is unverified
The sampled locales expose corresponding button and heading groups, but the evidence contains no screenshots or computed styles to confirm visual consistency.
Found here
Header and page structure · <nav>, <button>, <h1>
https://www.dropbox.com/de/What we saw
English buttons: "Products", "Solutions", "Get app"; German buttons: "Produkte", "Lösungen", "App herunterladen"; Spanish buttons: "Productos", "Soluciones", "Obtener la aplicación"
How to fix it
Compare rendered screenshots or computed styles across locales and verify that equivalent components retain the same spacing, hierarchy, and treatment.
Overflow cannot be confirmed from text extracts
The German and Spanish labels differ in length from the English labels, but no rendered dimensions or screenshots show whether any button or navigation text clips or overflows.
Found here
Header · <button>
https://www.dropbox.com/es/What we saw
English: "Get app"; German: "App herunterladen"; Spanish: "Obtener la aplicación"
How to fix it
Test the longest localized labels at supported widths and allow buttons and navigation items to wrap, resize, or reflow without clipping.
Layout integrity is not directly evidenced
The extracts show corresponding page structures across locales but provide no rendered layout, dimensions, or screenshots to verify grid, overlap, or modal behavior.
Found here
Page layout · <body>
What we saw
The evidence provides page status, language, buttons, headings, and text extracts, but no screenshot or layout measurement.
How to fix it
Run visual regression checks for each locale, focusing on navigation, hero sections, grids, and modal content at representative viewport sizes.
Responsive behavior is unverified
The evidence confirms localized pages load successfully, but it contains no mobile, tablet, or desktop screenshots or viewport-specific results.
Found here
Page layout · <body>
https://www.dropbox.com/What we saw
Sampled pages have "status":200, but the provided evidence contains no viewport dimensions or responsive render results.
How to fix it
Test each sampled locale across mobile, tablet, and desktop widths and verify that localized navigation, headings, and CTAs reflow without clipping.
Optional. Enter your work email and we will send a concise summary of this public report.
Strong localisation signals. Create a workspace to keep locales healthy as you ship, or book a deeper review.
