Localisation report

Booking.com

Online travel

booking.com

Product: Booking.com is an online travel booking platform for accommodations, flights, car rentals, cruises, attractions, and airport taxis. It connects travelers with more than 2 million properties across over 85,000 destinations.

Brand voice: helpful, accessible, trustworthy

Localisation score

71/100

Needs improvement

Users may encounter noticeable localisation problems.

70Technical Audit
64Linguistic Audit
79Contextual Audit
71Visual Audit

Audited: 8/16/2026Scope: Public smart sample · technical, linguistic, contextual, and visual creditsConfidence: Indicative health check from sampled pages — not a full site crawl.

Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits

How you compare

Rank #10 of 22 public audits

Top 59% of audited domainsPublic average: 68/100

See the full leaderboard

Fix first

hightechnical · 100% confidence
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Found here
Sitemap · sitemap.xml
What we saw
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
How to fix it
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
hightechnical · 95% confidence
Currency does not match the locale
A de page still shows dollar amounts without a local currency. Affects 2 sampled pages.
Found here
Page body · sampled copy
https://www.booking.com/index.de.html
What we saw
$301 Seen on 2 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.fr.html
How to fix it
Use a de-appropriate currency instead of unlocalized dollar amounts.
highlinguistic · 92% confidence
Untranslated call to action
A de page still uses source-language CTA copy. Affects 3 sampled pages.
Found here
Primary action · <button>
https://www.booking.com/index.de.html
What we saw
Primary CTA: "Festivals & Events" Seen on 3 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.nl.html, https://www.booking.com/index.fr.html
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.

Audit criteria

5 passed · 24 to fix · 6 not applicable

Needs attention (24)

Language switcher
Fail55technical
Visitors should move between locales without losing the current page.
- infotechnical · 65% confidence
  Current-page preservation is not verifiable
  The evidence lists many locales and English homepage variants, but does not expose the locale-switcher links or demonstrate that switching locales preserves the current path.
  Found here
  Header · <nav>
  https://www.booking.com/
  What we saw
  "locales":["ar","bg","ca","cs","da","de","el","en-gb",...], with homepage URLs such as "https://www.booking.com/" and "https://www.booking.com/index.en-gb.html"
  How to fix it
  Inspect the rendered language-switcher links on a non-homepage URL. Verify that each locale link maps to the equivalent locale-prefixed path.
Localized SEO metadata
Fail88technical
Titles, descriptions, and og:locale should be localized per locale.
- mediumtechnical · 95% confidence
  og:locale does not match the page
  og:locale is nb_NO on a no page.
  Found here
  Document head · <meta property="og:locale">
  https://www.booking.com/index.no.html
  What we saw
  <meta property="og:locale" content="nb_NO"> on a no page
  How to fix it
  Set og:locale to match the no page locale.
Sitemap
Fail18technical
Like Lighthouse: a valid XML sitemap must be discoverable, robots.txt should reference it with an absolute Sitemap: URL, and localized URLs should appear for published locales.
- hightechnical · 100% confidence
  Valid sitemap not found
  No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
  Found here
  Sitemap · sitemap.xml
  What we saw
  robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
  How to fix it
  Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
Structured data
Fail0technical
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% confidence
  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.booking.com/
  What we saw
  WebSite is present but inLanguage is missing
  How to fix it
  Set JSON-LD inLanguage to match each page locale.
International formatting
Fail62technical
Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- hightechnical · 95% confidence
  Currency does not match the locale
  A de page still shows dollar amounts without a local currency. Affects 2 sampled pages.
  Found here
  Page body · sampled copy
  https://www.booking.com/index.de.html
  What we saw
  $301 Seen on 2 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.fr.html
  How to fix it
  Use a de-appropriate currency instead of unlocalized dollar amounts.
Accessibility localisation
Fail78technical
lang, aria-label, and alt text should match the page locale.
- infotechnical · 60% confidence
  Locale-specific accessibility text is only partially evidenced
  The English homepage explicitly exposes htmlLang and direction, but the evidence does not show lang, aria-label, or alt attributes for the non-English locales.
  Found here
  Document root · <html>
  https://www.booking.com/
  What we saw
  "htmlLang":"en-us","dir":"ltr"; buttons include "Select datesCheck-in date — Check-out date" and "Search"
  How to fix it
  Audit each localized document's <html lang>, accessible names, and image alt text against the active locale.
Translation completeness
Fail50linguistic
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% confidence
  Untranslated call to action
  A de page still uses source-language CTA copy. Affects 3 sampled pages.
  Found here
  Primary action · <button>
  https://www.booking.com/index.de.html
  What we saw
  Primary CTA: "Festivals & Events" Seen on 3 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.nl.html, https://www.booking.com/index.fr.html
  How to fix it
  Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 35% confidence
  Localized copy is not present in the supplied evidence
  The supplied page samples are English pages, so untranslated source-language strings on localized pages cannot be assessed.
  Found here
  Document body · <body>
  https://www.booking.com/
  What we saw
  The sampled text is English: "Find deals for any season ... Enter destination ... Search"; the evidence is marked "truncated":true.
  How to fix it
  Provide representative rendered content from each target locale and scan visible strings for retained English copy.
Terminology consistency
Fail40linguistic
Important concepts should not be translated differently across pages.
- mediumlinguistic · 95% confidence
  Terminology inconsistency
  "Hotels" appears both untranslated and translated across de pages. Affects 9 sampled pages.
  Found here
  Header · <nav> or <button>
  https://www.booking.com/index.de.html
  What we saw
  "Hotels" appears untranslated on some de pages and translated on others Seen on 5 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.nl.html, https://www.booking.com/index.fr.html
  How to fix it
  Use one translated label for "Hotels" across de pages.
Translation accuracy
Fail50linguistic
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 35% confidence
  Cross-locale accuracy cannot be verified
  No translated target-language strings or source-to-target pairs are included, so preservation of meaning, numbers, and actions cannot be evaluated.
  Found here
  Hero and search form · <h1>, <form>
  https://www.booking.com/
  What we saw
  The available strings are English, including "Find deals for any season" and "Search"; no target-language equivalent is shown.
  How to fix it
  Compare localized strings with the source for product meaning, quantities, and action semantics across the main booking flow.
Fluency
Fail82linguistic
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 55% confidence
  English sample is fluent
  The available English marketing and navigation copy reads naturally, but fluency of the listed target locales is not evidenced.
  Found here
  Hero · <h1>
  https://www.booking.com/
  What we saw
  "Find deals for any season" and "From cozy bed & breakfasts to luxury hotels"
  How to fix it
  Review native-language samples for each locale, especially headings, form labels, and date-related messages.
Brand voice
Fail82linguistic
Localized copy should preserve the intended tone of the source.
- infolinguistic · 55% confidence
  Consumer-oriented source tone is evident
  The English sample uses an inviting, benefit-led travel-booking tone; localized preservation of that tone cannot be confirmed from the truncated evidence.
  Found here
  Hero · <h1>
  https://www.booking.com/
  What we saw
  "Find deals for any season" and "Why Booking.com?"
  How to fix it
  Use native reviewers to compare localized headings and promotional copy with the source's welcoming, action-oriented tone.
Grammar and style
Fail78linguistic
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 55% confidence
  English style sample is broadly consistent
  The visible English headings and navigation use consistent sentence-style capitalization, but locale-specific grammar and punctuation are not shown.
  Found here
  Primary navigation · <nav>
  https://www.booking.com/
  What we saw
  "Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Find deals for any season"
  How to fix it
  Check capitalization, punctuation, agreement, and formality against each locale's editorial conventions.
CTA intent
Fail85contextual
Localized calls to action should communicate the intended product action.
- infocontextual · 60% confidence
  Primary search action is clear in the English sample
  The search form exposes a direct "Search" action and supporting destination/date controls. Target-locale CTA intent is not evidenced.
  Found here
  Search form · <form>, <button>
  https://www.booking.com/
  What we saw
  Buttons include "Search", "Select datesCheck-in date — Check-out date", and "2 adults · 0 children · 1 room"
  How to fix it
  Verify that localized CTA labels retain the same search, date-selection, and guest-selection actions.
Cultural adaptation
Fail50contextual
Currency, dates, addresses, and local examples should fit the market.
- mediumcontextual · 78% confidence
  Possible cultural adaptation gap
  A de page still uses US-style currency or contact details. Affects 12 sampled pages.
  Found here
  Page body · sampled copy
  https://www.booking.com/index.de.html
  What we saw
  $301 Seen on 12 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.nl.html, https://www.booking.com/index.fr.html
  How to fix it
  Use locale-appropriate currency and contact formats instead of US-style defaults.
UI context
Fail82contextual
Translations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 60% confidence
  English controls have identifiable form context
  The evidence identifies search, date, guest, and category controls, but does not show how translated strings fit their rendered components.
  Found here
  Search form · <button>
  https://www.booking.com/
  What we saw
  "Select datesCheck-in date — Check-out date", "2 adults · 0 children · 1 room", and "Search"
  How to fix it
  Review localized strings in their actual buttons, fields, navigation items, and dialogs to confirm each remains concise and contextually clear.
Product context
Fail85contextual
Language should match product concepts such as plans, settings, and workflows.
- infocontextual · 60% confidence
  Core booking concepts are clear in the source sample
  The page clearly presents stays, flights, car rental, cruises, attractions, dates, guests, and search. Equivalent terminology in target locales is not shown.
  Found here
  Primary navigation and search form · <nav>, <form>
  https://www.booking.com/
  What we saw
  "Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Select dates ... 2 adults · 0 children · 1 room"
  How to fix it
  Validate localized terminology against the product glossary for each booking workflow and category.
Contextual meaning
Fail85contextual
Strings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 60% confidence
  Source strings are supported by surrounding context
  The English page places navigation, promotional headings, and booking controls in a coherent travel-search flow; target-language context is unavailable.
  Found here
  Hero and search form · <h1>, <form>
  https://www.booking.com/
  What we saw
  "Find deals for any season" followed by "Enter destination", "Select dates", and "Search"
  How to fix it
  Evaluate translated strings in the same surrounding component and workflow rather than in isolation.
Audience context
Fail88contextual
Language should fit the intended audience, such as consumer, enterprise, or developer.
- infocontextual · 65% confidence
  Consumer travel audience is clear
  The page is explicitly framed for travelers booking accommodation and related services, with consumer-oriented navigation and actions.
  Found here
  Primary navigation and hero · <nav>, <h1>
  https://www.booking.com/
  What we saw
  "Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "From cozy bed & breakfasts to luxury hotels"
  How to fix it
  Ensure localized wording remains accessible and consumer-friendly rather than becoming overly formal or technical.
Localized images and assets
Fail50visual
Language-specific images and alt text should match the page locale.
- infovisual · 30% confidence
  Image localization cannot be assessed
  The supplied evidence contains no image markup, asset identifiers, or alt-text samples for any locale.
  Found here
  Page media · <img>
  https://www.booking.com/
  How to fix it
  Inspect localized pages for image asset selection and verify that every meaningful image has locale-appropriate alt text.
Visual hierarchy
Fail76visual
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80% confidence
  Heading is excessively long
  A localized heading may crowd the visual hierarchy.
  Found here
  Page body · heading
  https://www.booking.com/index.pt-pt.html
  What we saw
  Apoio ao cliente de confiança com o qual pode contar, 24 horas por dia e 7 dias por semana
  How to fix it
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fail70visual
Repeated components should stay visually consistent across locales.
- lowvisual · 95% confidence
  Repeated components differ across locales
  Button counts differ between the source locale and it.
  Found here
  Page body · <button>
  https://www.booking.com/index.it.html
  What we saw
  Source locale has 19 buttons; it has 17.
  How to fix it
  Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Fail72visual
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 45% confidence
  Visual text fit is unverified
  No screenshots or rendered dimensions are supplied. The combined date control label is a possible text-fit area, but overflow cannot be confirmed from text extraction alone.
  Found here
  Search form · <button>
  https://www.booking.com/
  What we saw
  "Select datesCheck-in date — Check-out date"
  How to fix it
  Test translated labels at mobile and desktop widths, allowing wrapping or flexible control sizing where needed.
Layout breakage
Fail75visual
Localized pages should not overlap, break grids, or overflow modals.
- infovisual · 45% confidence
  Localized layout integrity is unverified
  The evidence provides page text and metadata but no screenshots or layout measurements, so overlap, grid, and modal behavior cannot be confirmed.
  Found here
  https://www.booking.com/
  What we saw
  The supplied evidence is a truncated structured preview containing URLs, headings, buttons, and text, with no rendered layout data.
  How to fix it
  Run visual checks for long translations, right-to-left locales, navigation, forms, and dialogs at representative viewport sizes.
Responsive localisation
Fail65visual
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 45% confidence
  Responsive localization is unverified
  No mobile, tablet, or desktop screenshots or viewport results are included, so responsive behavior must be treated as an estimate.
  Found here
  https://www.booking.com/
  What we saw
  The evidence lists page content but does not include viewport dimensions, screenshots, or responsive test outcomes.
  How to fix it
  Test representative locales across mobile, tablet, and desktop widths, including long labels and right-to-left layouts.

Passed audits (5)

Not applicable (6)

Detected locales

ar (hreflang)bg (hreflang)ca (hreflang)cs (hreflang)da (hreflang)de (hreflang)el (hreflang)en-gb (hreflang)en-us (html_lang)es-ar (hreflang)es-mx (hreflang)et (hreflang)fi (hreflang)fr (hreflang)he (hreflang)hi (hreflang)hr (hreflang)hu (hreflang)id (hreflang)is (hreflang)it (hreflang)ja (hreflang)ko (hreflang)lt (hreflang)lv (hreflang)ms (hreflang)nl (hreflang)no (hreflang)pl (hreflang)pt-br (hreflang)pt-pt (hreflang)ro (hreflang)ru (hreflang)sk (hreflang)sl (hreflang)sr (hreflang)sv (hreflang)th (hreflang)tl (hreflang)tr (hreflang)uk (hreflang)vi (hreflang)zh-hans (hreflang)zh-hant (hreflang)

Full findings

mediumtechnical · 95% confidence
og:locale does not match the page
og:locale is nb_NO on a no page.
Found here
Document head · <meta property="og:locale">
https://www.booking.com/index.no.html
What we saw
<meta property="og:locale" content="nb_NO"> on a no page
How to fix it
Set og:locale to match the no page locale.
hightechnical · 100% confidence
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Found here
Sitemap · sitemap.xml
What we saw
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
How to fix it
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
lowtechnical · 95% confidence
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.booking.com/
What we saw
WebSite is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
hightechnical · 95% confidence
Currency does not match the locale
A de page still shows dollar amounts without a local currency. Affects 2 sampled pages.
Found here
Page body · sampled copy
https://www.booking.com/index.de.html
What we saw
$301 Seen on 2 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.fr.html
How to fix it
Use a de-appropriate currency instead of unlocalized dollar amounts.
highlinguistic · 92% confidence
Untranslated call to action
A de page still uses source-language CTA copy. Affects 3 sampled pages.
Found here
Primary action · <button>
https://www.booking.com/index.de.html
What we saw
Primary CTA: "Festivals & Events" Seen on 3 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.nl.html, https://www.booking.com/index.fr.html
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
mediumlinguistic · 95% confidence
Terminology inconsistency
"Hotels" appears both untranslated and translated across de pages. Affects 9 sampled pages.
Found here
Header · <nav> or <button>
https://www.booking.com/index.de.html
What we saw
"Hotels" appears untranslated on some de pages and translated on others Seen on 5 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.nl.html, https://www.booking.com/index.fr.html
How to fix it
Use one translated label for "Hotels" across de pages.
mediumcontextual · 78% confidence
Possible cultural adaptation gap
A de page still uses US-style currency or contact details. Affects 12 sampled pages.
Found here
Page body · sampled copy
https://www.booking.com/index.de.html
What we saw
$301 Seen on 12 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.nl.html, https://www.booking.com/index.fr.html
How to fix it
Use locale-appropriate currency and contact formats instead of US-style defaults.
lowvisual · 80% confidence
Heading is excessively long
A localized heading may crowd the visual hierarchy.
Found here
Page body · heading
https://www.booking.com/index.pt-pt.html
What we saw
Apoio ao cliente de confiança com o qual pode contar, 24 horas por dia e 7 dias por semana
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
lowvisual · 95% confidence
Repeated components differ across locales
Button counts differ between the source locale and it.
Found here
Page body · <button>
https://www.booking.com/index.it.html
What we saw
Source locale has 19 buttons; it has 17.
How to fix it
Keep the same repeated controls across locales, or drop unused ones on purpose.
infotechnical · 65% confidence
Current-page preservation is not verifiable
The evidence lists many locales and English homepage variants, but does not expose the locale-switcher links or demonstrate that switching locales preserves the current path.
Found here
Header · <nav>
https://www.booking.com/
What we saw
"locales":["ar","bg","ca","cs","da","de","el","en-gb",...], with homepage URLs such as "https://www.booking.com/" and "https://www.booking.com/index.en-gb.html"
How to fix it
Inspect the rendered language-switcher links on a non-homepage URL. Verify that each locale link maps to the equivalent locale-prefixed path.
infotechnical · 60% confidence
Locale-specific accessibility text is only partially evidenced
The English homepage explicitly exposes htmlLang and direction, but the evidence does not show lang, aria-label, or alt attributes for the non-English locales.
Found here
Document root · <html>
https://www.booking.com/
What we saw
"htmlLang":"en-us","dir":"ltr"; buttons include "Select datesCheck-in date — Check-out date" and "Search"
How to fix it
Audit each localized document's <html lang>, accessible names, and image alt text against the active locale.
infolinguistic · 35% confidence
Localized copy is not present in the supplied evidence
The supplied page samples are English pages, so untranslated source-language strings on localized pages cannot be assessed.
Found here
Document body · <body>
https://www.booking.com/
What we saw
The sampled text is English: "Find deals for any season ... Enter destination ... Search"; the evidence is marked "truncated":true.
How to fix it
Provide representative rendered content from each target locale and scan visible strings for retained English copy.
infolinguistic · 35% confidence
Cross-locale accuracy cannot be verified
No translated target-language strings or source-to-target pairs are included, so preservation of meaning, numbers, and actions cannot be evaluated.
Found here
Hero and search form · <h1>, <form>
https://www.booking.com/
What we saw
The available strings are English, including "Find deals for any season" and "Search"; no target-language equivalent is shown.
How to fix it
Compare localized strings with the source for product meaning, quantities, and action semantics across the main booking flow.
infolinguistic · 55% confidence
English sample is fluent
The available English marketing and navigation copy reads naturally, but fluency of the listed target locales is not evidenced.
Found here
Hero · <h1>
https://www.booking.com/
What we saw
"Find deals for any season" and "From cozy bed & breakfasts to luxury hotels"
How to fix it
Review native-language samples for each locale, especially headings, form labels, and date-related messages.
infolinguistic · 55% confidence
Consumer-oriented source tone is evident
The English sample uses an inviting, benefit-led travel-booking tone; localized preservation of that tone cannot be confirmed from the truncated evidence.
Found here
Hero · <h1>
https://www.booking.com/
What we saw
"Find deals for any season" and "Why Booking.com?"
How to fix it
Use native reviewers to compare localized headings and promotional copy with the source's welcoming, action-oriented tone.
infolinguistic · 55% confidence
English style sample is broadly consistent
The visible English headings and navigation use consistent sentence-style capitalization, but locale-specific grammar and punctuation are not shown.
Found here
Primary navigation · <nav>
https://www.booking.com/
What we saw
"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Find deals for any season"
How to fix it
Check capitalization, punctuation, agreement, and formality against each locale's editorial conventions.
infocontextual · 60% confidence
Primary search action is clear in the English sample
The search form exposes a direct "Search" action and supporting destination/date controls. Target-locale CTA intent is not evidenced.
Found here
Search form · <form>, <button>
https://www.booking.com/
What we saw
Buttons include "Search", "Select datesCheck-in date — Check-out date", and "2 adults · 0 children · 1 room"
How to fix it
Verify that localized CTA labels retain the same search, date-selection, and guest-selection actions.
infocontextual · 60% confidence
English controls have identifiable form context
The evidence identifies search, date, guest, and category controls, but does not show how translated strings fit their rendered components.
Found here
Search form · <button>
https://www.booking.com/
What we saw
"Select datesCheck-in date — Check-out date", "2 adults · 0 children · 1 room", and "Search"
How to fix it
Review localized strings in their actual buttons, fields, navigation items, and dialogs to confirm each remains concise and contextually clear.
infocontextual · 60% confidence
Core booking concepts are clear in the source sample
The page clearly presents stays, flights, car rental, cruises, attractions, dates, guests, and search. Equivalent terminology in target locales is not shown.
Found here
Primary navigation and search form · <nav>, <form>
https://www.booking.com/
What we saw
"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Select dates ... 2 adults · 0 children · 1 room"
How to fix it
Validate localized terminology against the product glossary for each booking workflow and category.
infocontextual · 60% confidence
Source strings are supported by surrounding context
The English page places navigation, promotional headings, and booking controls in a coherent travel-search flow; target-language context is unavailable.
Found here
Hero and search form · <h1>, <form>
https://www.booking.com/
What we saw
"Find deals for any season" followed by "Enter destination", "Select dates", and "Search"
How to fix it
Evaluate translated strings in the same surrounding component and workflow rather than in isolation.
infocontextual · 65% confidence
Consumer travel audience is clear
The page is explicitly framed for travelers booking accommodation and related services, with consumer-oriented navigation and actions.
Found here
Primary navigation and hero · <nav>, <h1>
https://www.booking.com/
What we saw
"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "From cozy bed & breakfasts to luxury hotels"
How to fix it
Ensure localized wording remains accessible and consumer-friendly rather than becoming overly formal or technical.
infovisual · 30% confidence
Image localization cannot be assessed
The supplied evidence contains no image markup, asset identifiers, or alt-text samples for any locale.
Found here
Page media · <img>
https://www.booking.com/
How to fix it
Inspect localized pages for image asset selection and verify that every meaningful image has locale-appropriate alt text.
infovisual · 45% confidence
Visual text fit is unverified
No screenshots or rendered dimensions are supplied. The combined date control label is a possible text-fit area, but overflow cannot be confirmed from text extraction alone.
Found here
Search form · <button>
https://www.booking.com/
What we saw
"Select datesCheck-in date — Check-out date"
How to fix it
Test translated labels at mobile and desktop widths, allowing wrapping or flexible control sizing where needed.
infovisual · 45% confidence
Localized layout integrity is unverified
The evidence provides page text and metadata but no screenshots or layout measurements, so overlap, grid, and modal behavior cannot be confirmed.
Found here
https://www.booking.com/
What we saw
The supplied evidence is a truncated structured preview containing URLs, headings, buttons, and text, with no rendered layout data.
How to fix it
Run visual checks for long translations, right-to-left locales, navigation, forms, and dialogs at representative viewport sizes.
infovisual · 45% confidence
Responsive localization is unverified
No mobile, tablet, or desktop screenshots or viewport results are included, so responsive behavior must be treated as an estimate.
Found here
https://www.booking.com/
What we saw
The evidence lists page content but does not include viewport dimensions, screenshots, or responsive test outcomes.
How to fix it
Test representative locales across mobile, tablet, and desktop widths, including long labels and right-to-left layouts.

Pages sampled

202 · https://www.booking.com/ · lang=en-us
202 · https://www.booking.com/ · lang=en-us
200 · https://www.booking.com/index.en-gb.html · lang=en-gb
200 · https://www.booking.com/index.de.html · lang=de
200 · https://www.booking.com/index.nl.html · lang=nl
200 · https://www.booking.com/index.fr.html · lang=fr
200 · https://www.booking.com/index.es.html · lang=es
200 · https://www.booking.com/index.es-ar.html · lang=es-ar
200 · https://www.booking.com/index.es-mx.html · lang=es-mx
200 · https://www.booking.com/index.ca.html · lang=ca
200 · https://www.booking.com/index.it.html · lang=it
200 · https://www.booking.com/index.pt-pt.html · lang=pt-pt
200 · https://www.booking.com/index.pt-br.html · lang=pt-br
200 · https://www.booking.com/index.no.html · lang=no
200 · https://www.booking.com/index.fi.html · lang=fi

Email me a summary

Optional. Enter your work email and we will send a concise summary of this public report.

Next step

Solid baseline with room to improve. Create a workspace for continuous locale monitoring, or book an audit review.

Book an audit review