Rapport de localisation

Booking.com

Online travel

booking.com

Produit: 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.

Voix de marque: helpful, accessible, trustworthy

Score de localisation

71/100

À améliorer

Les utilisateurs peuvent rencontrer des problèmes de localisation perceptibles.

70Audit technique
64Audit linguistique
79Audit contextuel
71Audit visuel

Audité: 8/16/2026Portée: Échantillon intelligent public · crédits techniques, linguistiques, contextuels et visuelsConfiance: Contrôle indicatif de l’état de santé à partir de pages échantillonnées — il ne s’agit pas d’une exploration complète du site.

15 pages échantillonnées parmi les crédits de localisation techniques, linguistiques, contextuels et visuels. Comment nous évaluons les audits de localisation

Comment vous vous comparez

Rang #10 sur 22 audits publics

Top 59 % des domaines auditésMoyenne publique : 68/100

Voir le classement complet

À corriger en priorité

hightechnical · 100 % de confiance
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Trouvé ici
Sitemap · sitemap.xml
Ce que nous avons constaté
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
Comment le corriger
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
hightechnical · 95 % de confiance
Currency does not match the locale
A de page still shows dollar amounts without a local currency. Affects 2 sampled pages.
Trouvé ici
Page body · sampled copy
https://www.booking.com/index.de.html
Ce que nous avons constaté
$301 Seen on 2 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.fr.html
Comment le corriger
Use a de-appropriate currency instead of unlocalized dollar amounts.
highlinguistic · 92 % de confiance
Untranslated call to action
A de page still uses source-language CTA copy. Affects 3 sampled pages.
Trouvé ici
Primary action · <button>
https://www.booking.com/index.de.html
Ce que nous avons constaté
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
Comment le corriger
Translate leftover source-language CTAs to match the surrounding locale copy.

Critères d’audit

5 réussis · 24 à corriger · 6 non applicable

À examiner (24)

Language switcher
Échec55technique
Visitors should move between locales without losing the current page.
- infotechnical · 65 % de confiance
  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.
  Trouvé ici
  Header · <nav>
  https://www.booking.com/
  Ce que nous avons constaté
  "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"
  Comment le corriger
  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
Échec88technique
Titles, descriptions, and og:locale should be localized per locale.
- mediumtechnical · 95 % de confiance
  og:locale does not match the page
  og:locale is nb_NO on a no page.
  Trouvé ici
  Document head · <meta property="og:locale">
  https://www.booking.com/index.no.html
  Ce que nous avons constaté
  <meta property="og:locale" content="nb_NO"> on a no page
  Comment le corriger
  Set og:locale to match the no page locale.
Sitemap
Échec18technique
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 % de confiance
  Valid sitemap not found
  No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
  Trouvé ici
  Sitemap · sitemap.xml
  Ce que nous avons constaté
  robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
  Comment le corriger
  Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
Structured data
Échec0technique
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95 % de confiance
  Structured data omits inLanguage
  JSON-LD is present but does not declare inLanguage on sampled pages.
  Trouvé ici
  JSON-LD · <script type="application/ld+json">
  https://www.booking.com/
  Ce que nous avons constaté
  WebSite is present but inLanguage is missing
  Comment le corriger
  Set JSON-LD inLanguage to match each page locale.
International formatting
Échec62technique
Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- hightechnical · 95 % de confiance
  Currency does not match the locale
  A de page still shows dollar amounts without a local currency. Affects 2 sampled pages.
  Trouvé ici
  Page body · sampled copy
  https://www.booking.com/index.de.html
  Ce que nous avons constaté
  $301 Seen on 2 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.fr.html
  Comment le corriger
  Use a de-appropriate currency instead of unlocalized dollar amounts.
Accessibility localisation
Échec78technique
lang, aria-label, and alt text should match the page locale.
- infotechnical · 60 % de confiance
  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.
  Trouvé ici
  Document root · <html>
  https://www.booking.com/
  Ce que nous avons constaté
  "htmlLang":"en-us","dir":"ltr"; buttons include "Select datesCheck-in date — Check-out date" and "Search"
  Comment le corriger
  Audit each localized document's <html lang>, accessible names, and image alt text against the active locale.
Translation completeness
Échec50linguistique
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92 % de confiance
  Untranslated call to action
  A de page still uses source-language CTA copy. Affects 3 sampled pages.
  Trouvé ici
  Primary action · <button>
  https://www.booking.com/index.de.html
  Ce que nous avons constaté
  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
  Comment le corriger
  Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 35 % de confiance
  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.
  Trouvé ici
  Document body · <body>
  https://www.booking.com/
  Ce que nous avons constaté
  The sampled text is English: "Find deals for any season ... Enter destination ... Search"; the evidence is marked "truncated":true.
  Comment le corriger
  Provide representative rendered content from each target locale and scan visible strings for retained English copy.
Terminology consistency
Échec40linguistique
Important concepts should not be translated differently across pages.
- mediumlinguistic · 95 % de confiance
  Terminology inconsistency
  "Hotels" appears both untranslated and translated across de pages. Affects 9 sampled pages.
  Trouvé ici
  Header · <nav> or <button>
  https://www.booking.com/index.de.html
  Ce que nous avons constaté
  "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
  Comment le corriger
  Use one translated label for "Hotels" across de pages.
Translation accuracy
Échec50linguistique
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 35 % de confiance
  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.
  Trouvé ici
  Hero and search form · <h1>, <form>
  https://www.booking.com/
  Ce que nous avons constaté
  The available strings are English, including "Find deals for any season" and "Search"; no target-language equivalent is shown.
  Comment le corriger
  Compare localized strings with the source for product meaning, quantities, and action semantics across the main booking flow.
Fluency
Échec82linguistique
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 55 % de confiance
  English sample is fluent
  The available English marketing and navigation copy reads naturally, but fluency of the listed target locales is not evidenced.
  Trouvé ici
  Hero · <h1>
  https://www.booking.com/
  Ce que nous avons constaté
  "Find deals for any season" and "From cozy bed & breakfasts to luxury hotels"
  Comment le corriger
  Review native-language samples for each locale, especially headings, form labels, and date-related messages.
Brand voice
Échec82linguistique
Localized copy should preserve the intended tone of the source.
- infolinguistic · 55 % de confiance
  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.
  Trouvé ici
  Hero · <h1>
  https://www.booking.com/
  Ce que nous avons constaté
  "Find deals for any season" and "Why Booking.com?"
  Comment le corriger
  Use native reviewers to compare localized headings and promotional copy with the source's welcoming, action-oriented tone.
Grammar and style
Échec78linguistique
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 55 % de confiance
  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.
  Trouvé ici
  Primary navigation · <nav>
  https://www.booking.com/
  Ce que nous avons constaté
  "Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Find deals for any season"
  Comment le corriger
  Check capitalization, punctuation, agreement, and formality against each locale's editorial conventions.
CTA intent
Échec85contextuel
Localized calls to action should communicate the intended product action.
- infocontextual · 60 % de confiance
  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.
  Trouvé ici
  Search form · <form>, <button>
  https://www.booking.com/
  Ce que nous avons constaté
  Buttons include "Search", "Select datesCheck-in date — Check-out date", and "2 adults · 0 children · 1 room"
  Comment le corriger
  Verify that localized CTA labels retain the same search, date-selection, and guest-selection actions.
Cultural adaptation
Échec50contextuel
Currency, dates, addresses, and local examples should fit the market.
- mediumcontextual · 78 % de confiance
  Possible cultural adaptation gap
  A de page still uses US-style currency or contact details. Affects 12 sampled pages.
  Trouvé ici
  Page body · sampled copy
  https://www.booking.com/index.de.html
  Ce que nous avons constaté
  $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
  Comment le corriger
  Use locale-appropriate currency and contact formats instead of US-style defaults.
UI context
Échec82contextuel
Translations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 60 % de confiance
  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.
  Trouvé ici
  Search form · <button>
  https://www.booking.com/
  Ce que nous avons constaté
  "Select datesCheck-in date — Check-out date", "2 adults · 0 children · 1 room", and "Search"
  Comment le corriger
  Review localized strings in their actual buttons, fields, navigation items, and dialogs to confirm each remains concise and contextually clear.
Product context
Échec85contextuel
Language should match product concepts such as plans, settings, and workflows.
- infocontextual · 60 % de confiance
  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.
  Trouvé ici
  Primary navigation and search form · <nav>, <form>
  https://www.booking.com/
  Ce que nous avons constaté
  "Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Select dates ... 2 adults · 0 children · 1 room"
  Comment le corriger
  Validate localized terminology against the product glossary for each booking workflow and category.
Contextual meaning
Échec85contextuel
Strings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 60 % de confiance
  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.
  Trouvé ici
  Hero and search form · <h1>, <form>
  https://www.booking.com/
  Ce que nous avons constaté
  "Find deals for any season" followed by "Enter destination", "Select dates", and "Search"
  Comment le corriger
  Evaluate translated strings in the same surrounding component and workflow rather than in isolation.
Audience context
Échec88contextuel
Language should fit the intended audience, such as consumer, enterprise, or developer.
- infocontextual · 65 % de confiance
  Consumer travel audience is clear
  The page is explicitly framed for travelers booking accommodation and related services, with consumer-oriented navigation and actions.
  Trouvé ici
  Primary navigation and hero · <nav>, <h1>
  https://www.booking.com/
  Ce que nous avons constaté
  "Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "From cozy bed & breakfasts to luxury hotels"
  Comment le corriger
  Ensure localized wording remains accessible and consumer-friendly rather than becoming overly formal or technical.
Localized images and assets
Échec50visuel
Language-specific images and alt text should match the page locale.
- infovisual · 30 % de confiance
  Image localization cannot be assessed
  The supplied evidence contains no image markup, asset identifiers, or alt-text samples for any locale.
  Trouvé ici
  Page media · <img>
  https://www.booking.com/
  Comment le corriger
  Inspect localized pages for image asset selection and verify that every meaningful image has locale-appropriate alt text.
Visual hierarchy
Échec76visuel
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80 % de confiance
  Heading is excessively long
  A localized heading may crowd the visual hierarchy.
  Trouvé ici
  Page body · heading
  https://www.booking.com/index.pt-pt.html
  Ce que nous avons constaté
  Apoio ao cliente de confiança com o qual pode contar, 24 horas por dia e 7 dias por semana
  Comment le corriger
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Échec70visuel
Repeated components should stay visually consistent across locales.
- lowvisual · 95 % de confiance
  Repeated components differ across locales
  Button counts differ between the source locale and it.
  Trouvé ici
  Page body · <button>
  https://www.booking.com/index.it.html
  Ce que nous avons constaté
  Source locale has 19 buttons; it has 17.
  Comment le corriger
  Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Échec72visuel
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 45 % de confiance
  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.
  Trouvé ici
  Search form · <button>
  https://www.booking.com/
  Ce que nous avons constaté
  "Select datesCheck-in date — Check-out date"
  Comment le corriger
  Test translated labels at mobile and desktop widths, allowing wrapping or flexible control sizing where needed.
Layout breakage
Échec75visuel
Localized pages should not overlap, break grids, or overflow modals.
- infovisual · 45 % de confiance
  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.
  Trouvé ici
  https://www.booking.com/
  Ce que nous avons constaté
  The supplied evidence is a truncated structured preview containing URLs, headings, buttons, and text, with no rendered layout data.
  Comment le corriger
  Run visual checks for long translations, right-to-left locales, navigation, forms, and dialogs at representative viewport sizes.
Responsive localisation
Échec65visuel
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 45 % de confiance
  Responsive localization is unverified
  No mobile, tablet, or desktop screenshots or viewport results are included, so responsive behavior must be treated as an estimate.
  Trouvé ici
  https://www.booking.com/
  Ce que nous avons constaté
  The evidence lists page content but does not include viewport dimensions, screenshots, or responsive test outcomes.
  Comment le corriger
  Test representative locales across mobile, tablet, and desktop widths, including long labels and right-to-left layouts.

Audits réussis (5)

Non applicable (6)

Paramètres régionaux détectés

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)

Résultats complets

mediumtechnical · 95 % de confiance
og:locale does not match the page
og:locale is nb_NO on a no page.
Trouvé ici
Document head · <meta property="og:locale">
https://www.booking.com/index.no.html
Ce que nous avons constaté
<meta property="og:locale" content="nb_NO"> on a no page
Comment le corriger
Set og:locale to match the no page locale.
hightechnical · 100 % de confiance
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Trouvé ici
Sitemap · sitemap.xml
Ce que nous avons constaté
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
Comment le corriger
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
lowtechnical · 95 % de confiance
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Trouvé ici
JSON-LD · <script type="application/ld+json">
https://www.booking.com/
Ce que nous avons constaté
WebSite is present but inLanguage is missing
Comment le corriger
Set JSON-LD inLanguage to match each page locale.
hightechnical · 95 % de confiance
Currency does not match the locale
A de page still shows dollar amounts without a local currency. Affects 2 sampled pages.
Trouvé ici
Page body · sampled copy
https://www.booking.com/index.de.html
Ce que nous avons constaté
$301 Seen on 2 pages, e.g. https://www.booking.com/index.de.html, https://www.booking.com/index.fr.html
Comment le corriger
Use a de-appropriate currency instead of unlocalized dollar amounts.
highlinguistic · 92 % de confiance
Untranslated call to action
A de page still uses source-language CTA copy. Affects 3 sampled pages.
Trouvé ici
Primary action · <button>
https://www.booking.com/index.de.html
Ce que nous avons constaté
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
Comment le corriger
Translate leftover source-language CTAs to match the surrounding locale copy.
mediumlinguistic · 95 % de confiance
Terminology inconsistency
"Hotels" appears both untranslated and translated across de pages. Affects 9 sampled pages.
Trouvé ici
Header · <nav> or <button>
https://www.booking.com/index.de.html
Ce que nous avons constaté
"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
Comment le corriger
Use one translated label for "Hotels" across de pages.
mediumcontextual · 78 % de confiance
Possible cultural adaptation gap
A de page still uses US-style currency or contact details. Affects 12 sampled pages.
Trouvé ici
Page body · sampled copy
https://www.booking.com/index.de.html
Ce que nous avons constaté
$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
Comment le corriger
Use locale-appropriate currency and contact formats instead of US-style defaults.
lowvisual · 80 % de confiance
Heading is excessively long
A localized heading may crowd the visual hierarchy.
Trouvé ici
Page body · heading
https://www.booking.com/index.pt-pt.html
Ce que nous avons constaté
Apoio ao cliente de confiança com o qual pode contar, 24 horas por dia e 7 dias por semana
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
lowvisual · 95 % de confiance
Repeated components differ across locales
Button counts differ between the source locale and it.
Trouvé ici
Page body · <button>
https://www.booking.com/index.it.html
Ce que nous avons constaté
Source locale has 19 buttons; it has 17.
Comment le corriger
Keep the same repeated controls across locales, or drop unused ones on purpose.
infotechnical · 65 % de confiance
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.
Trouvé ici
Header · <nav>
https://www.booking.com/
Ce que nous avons constaté
"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"
Comment le corriger
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 % de confiance
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.
Trouvé ici
Document root · <html>
https://www.booking.com/
Ce que nous avons constaté
"htmlLang":"en-us","dir":"ltr"; buttons include "Select datesCheck-in date — Check-out date" and "Search"
Comment le corriger
Audit each localized document's <html lang>, accessible names, and image alt text against the active locale.
infolinguistic · 35 % de confiance
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.
Trouvé ici
Document body · <body>
https://www.booking.com/
Ce que nous avons constaté
The sampled text is English: "Find deals for any season ... Enter destination ... Search"; the evidence is marked "truncated":true.
Comment le corriger
Provide representative rendered content from each target locale and scan visible strings for retained English copy.
infolinguistic · 35 % de confiance
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.
Trouvé ici
Hero and search form · <h1>, <form>
https://www.booking.com/
Ce que nous avons constaté
The available strings are English, including "Find deals for any season" and "Search"; no target-language equivalent is shown.
Comment le corriger
Compare localized strings with the source for product meaning, quantities, and action semantics across the main booking flow.
infolinguistic · 55 % de confiance
English sample is fluent
The available English marketing and navigation copy reads naturally, but fluency of the listed target locales is not evidenced.
Trouvé ici
Hero · <h1>
https://www.booking.com/
Ce que nous avons constaté
"Find deals for any season" and "From cozy bed & breakfasts to luxury hotels"
Comment le corriger
Review native-language samples for each locale, especially headings, form labels, and date-related messages.
infolinguistic · 55 % de confiance
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.
Trouvé ici
Hero · <h1>
https://www.booking.com/
Ce que nous avons constaté
"Find deals for any season" and "Why Booking.com?"
Comment le corriger
Use native reviewers to compare localized headings and promotional copy with the source's welcoming, action-oriented tone.
infolinguistic · 55 % de confiance
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.
Trouvé ici
Primary navigation · <nav>
https://www.booking.com/
Ce que nous avons constaté
"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Find deals for any season"
Comment le corriger
Check capitalization, punctuation, agreement, and formality against each locale's editorial conventions.
infocontextual · 60 % de confiance
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.
Trouvé ici
Search form · <form>, <button>
https://www.booking.com/
Ce que nous avons constaté
Buttons include "Search", "Select datesCheck-in date — Check-out date", and "2 adults · 0 children · 1 room"
Comment le corriger
Verify that localized CTA labels retain the same search, date-selection, and guest-selection actions.
infocontextual · 60 % de confiance
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.
Trouvé ici
Search form · <button>
https://www.booking.com/
Ce que nous avons constaté
"Select datesCheck-in date — Check-out date", "2 adults · 0 children · 1 room", and "Search"
Comment le corriger
Review localized strings in their actual buttons, fields, navigation items, and dialogs to confirm each remains concise and contextually clear.
infocontextual · 60 % de confiance
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.
Trouvé ici
Primary navigation and search form · <nav>, <form>
https://www.booking.com/
Ce que nous avons constaté
"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "Select dates ... 2 adults · 0 children · 1 room"
Comment le corriger
Validate localized terminology against the product glossary for each booking workflow and category.
infocontextual · 60 % de confiance
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.
Trouvé ici
Hero and search form · <h1>, <form>
https://www.booking.com/
Ce que nous avons constaté
"Find deals for any season" followed by "Enter destination", "Select dates", and "Search"
Comment le corriger
Evaluate translated strings in the same surrounding component and workflow rather than in isolation.
infocontextual · 65 % de confiance
Consumer travel audience is clear
The page is explicitly framed for travelers booking accommodation and related services, with consumer-oriented navigation and actions.
Trouvé ici
Primary navigation and hero · <nav>, <h1>
https://www.booking.com/
Ce que nous avons constaté
"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "From cozy bed & breakfasts to luxury hotels"
Comment le corriger
Ensure localized wording remains accessible and consumer-friendly rather than becoming overly formal or technical.
infovisual · 30 % de confiance
Image localization cannot be assessed
The supplied evidence contains no image markup, asset identifiers, or alt-text samples for any locale.
Trouvé ici
Page media · <img>
https://www.booking.com/
Comment le corriger
Inspect localized pages for image asset selection and verify that every meaningful image has locale-appropriate alt text.
infovisual · 45 % de confiance
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.
Trouvé ici
Search form · <button>
https://www.booking.com/
Ce que nous avons constaté
"Select datesCheck-in date — Check-out date"
Comment le corriger
Test translated labels at mobile and desktop widths, allowing wrapping or flexible control sizing where needed.
infovisual · 45 % de confiance
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.
Trouvé ici
https://www.booking.com/
Ce que nous avons constaté
The supplied evidence is a truncated structured preview containing URLs, headings, buttons, and text, with no rendered layout data.
Comment le corriger
Run visual checks for long translations, right-to-left locales, navigation, forms, and dialogs at representative viewport sizes.
infovisual · 45 % de confiance
Responsive localization is unverified
No mobile, tablet, or desktop screenshots or viewport results are included, so responsive behavior must be treated as an estimate.
Trouvé ici
https://www.booking.com/
Ce que nous avons constaté
The evidence lists page content but does not include viewport dimensions, screenshots, or responsive test outcomes.
Comment le corriger
Test representative locales across mobile, tablet, and desktop widths, including long labels and right-to-left layouts.

Pages échantillonnées

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

Envoyez-moi un récapitulatif par e-mail

Facultatif. Saisissez votre adresse e-mail professionnelle et nous vous enverrons un résumé concis de ce rapport public.

Étape suivante

Bonne base, avec une marge d’amélioration. Créez un espace de travail pour un suivi continu de la localisation, ou réservez une revue d’audit.

Réserver un examen d’audit