Booking.com

Header · <nav>

"locales":["ar","bg","ca","cs","da","de","el","en-gb","en-us","es-ar","es-mx",...], with page samples only showing "https://www.booking.com/" and "https://www.booking.com/region/gb/england.html"

Verify that switching locale from a deep page retains the same path and relevant query or booking state.

Sitemap · sitemap.xml

robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty

Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.

JSON-LD · <script type="application/ld+json">

WebSite is present but inLanguage is missing

Set JSON-LD inLanguage to match each page locale.

Document root · <html>

"htmlLang":"en-us","dir":"ltr"

Audit each locale’s <html lang>, accessible names, and image alt text against its rendered language.

Primary action · <button>

Primary CTA: "Arts & Culture"

Translate leftover source-language CTAs to match the surrounding locale copy.

Page content · <body>

"htmlLang":"en-us" and visible copy including "Find deals for any season" and "Why Booking.com?"

Sample the same pages in each target locale and check navigation, headings, controls, and supporting copy for remaining source-language strings.

Header · <nav> or <button>

"Arts & Culture" appears untranslated on some fr pages and translated on others Seen on 2 pages, e.g. https://www.booking.com/index.fr.html, https://www.booking.com/index.es.html

Use one translated label for "Arts & Culture" across fr pages.

Hero · <h1>

"Find deals for any season" and controls including "Select datesCheck-in date — Check-out date"

Compare localized strings with the source for intent, quantities, dates, and booking actions in their surrounding components.

Page content · <body>

"htmlLang":"en-us" with visible text "Skip to main content ... Find deals for any season"

Review representative localized pages with native speakers for natural phrasing and locale-specific idioms.

Hero · <h1>

"Find deals for any season" and "From cozy bed & breakfasts to luxury hotels"

Compare localized marketing copy with the English source and preserve its welcoming, consumer-oriented tone without literal phrasing.

Search form · <form>

"Select datesCheck-in date — Check-out date" and "2 adults · 0 children · 1 room"

Review each locale’s capitalization, punctuation, date conventions, formality, and plural or agreement rules in the rendered UI.

Search form · <button>

"buttons":["HUF","Select datesCheck-in date — Check-out date","2 adults · 0 children · 1 room","Search",...]

Verify that every locale keeps the distinction between selecting inputs and submitting the search action.

Search form · <form>

"buttons":["HUF","Select datesCheck-in date — Check-out date","2 adults · 0 children · 1 room","Search",...]

Test localized labels in their actual buttons, navigation items, fields, and date controls, including long and inflected translations.

Header and search form · <nav> / <form>

"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "2 adults · 0 children · 1 room"

Create a locale glossary for booking concepts and verify consistent terminology across navigation, search, checkout, and account workflows.

Homepage · <body>

"Find deals for any season", "Enter destination", "Select dates", and "Search" appear together in the sampled page content.

Review translations in their rendered page and component context rather than approving isolated string values.

Page content · <img>

Inspect image sources and alt attributes on each locale and replace or translate assets where the visual or embedded text is language-specific.

Header and search form · <nav> / <form>

Labels include "Select datesCheck-in date — Check-out date" and "300M+ reviews from fellow travelers".

Run visual checks across locales and widths, allowing controls and headings to wrap or expand without clipping.

Homepage · <body>

The evidence provides page status, headings, buttons, and text, but no layout measurements or rendered screenshots.

Test long translations in navigation, search controls, cards, and dialogs at representative viewport sizes.

Homepage · <body>

The preview lists page content but contains no viewport dimensions or responsive render results.

Capture each locale at mobile, tablet, and desktop widths and verify wrapping, stacking, and control accessibility.