Lokaliseringsrapport
Booking.com
Online travelbooking.com
Produkt: Booking.com is an online travel booking platform for finding and reserving accommodations, flights, car rentals, cruises, attractions, and airport taxis. It offers properties and travel services across destinations worldwide.
Brandstemme: helpful, trustworthy, value-focused
Lokaliseringsscore
64/100
Kræver forbedringBrugerne kan opleve mærkbare lokaliseringsproblemer.
- 73Teknisk audit
- 48Sproglig kontrol
- 70Kontekstaudit
- 64Visuel revision
Udvalgte 15 sider på tværs af tekniske, sproglige, kontekstuelle og visuelle lokaliseringskrediteringer. Sådan bedømmer vi lokaliseringsaudits
SÃ¥dan ligger du i forhold til andre
Placering nr. 18 af 23 offentlige audits
Ret først
- 1high
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
See details - 2
- 3medium
Terminology inconsistency
"Arts & Culture" appears both untranslated and translated across fr pages. Affects 4 sampled pages.
See details
Revisionskriterier
7 passed · 1 to watch · 19 to fix · 8 not applicable
Kræver opmærksomhed (19)
Language switcher
Ikke bestået55tekniskVisitors should move between locales without losing the current page.
- infotechnical · 42% sikkerhed
Locale availability is listed, but path preservation is not demonstrated
The evidence lists many supported locales but does not show the language-switcher control or destination URLs for a non-homepage path.
Fundet her
Header · <nav>
https://www.booking.com/Hvad vi så
"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"
Sådan løser du det
Verify that switching locale from a deep page retains the same path and relevant query or booking state.
Sitemap
Ikke bestået18tekniskLike 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% sikkerhed
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
Fundet her
Sitemap · sitemap.xml
Hvad vi så
robots.txt was found, but it does not reference a sitemap and /sitemap.xml was missing or empty
Sådan løser du det
Publish a valid XML sitemap and reference it from robots.txt with an absolute Sitemap: URL.
Structured data
Ikke bestået0tekniskJSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% sikkerhed
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Fundet her
JSON-LD · <script type="application/ld+json">
https://www.booking.com/Hvad vi så
WebSite is present but inLanguage is missing
Sådan løser du det
Set JSON-LD inLanguage to match each page locale.
Accessibility localisation
Ikke bestået65teknisklang, aria-label, and alt text should match the page locale.
- infotechnical · 62% sikkerhed
Accessibility localisation is only verified for English
The sampled page explicitly declares English, but the evidence does not provide localized aria-label or alt-text samples for the other locales.
Fundet her
Document root · <html>
https://www.booking.com/Hvad vi så
"htmlLang":"en-us","dir":"ltr"
Sådan løser du det
Audit each locale’s <html lang>, accessible names, and image alt text against its rendered language.
Translation completeness
Ikke bestået50sprogligLocalized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% sikkerhed
Untranslated call to action
A fr page still uses source-language CTA copy.
Fundet her
Primary action · <button>
https://www.booking.com/index.fr.htmlHvad vi så
Primary CTA: "Arts & Culture"
Sådan løser du det
Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 25% sikkerhed
No localized page copy is available for comparison
The provided preview contains only en-us page content, so untranslated source-language strings on localized pages cannot be confirmed or ruled out.
Fundet her
Page content · <body>
https://www.booking.com/Hvad vi så
"htmlLang":"en-us" and visible copy including "Find deals for any season" and "Why Booking.com?"
Sådan løser du det
Sample the same pages in each target locale and check navigation, headings, controls, and supporting copy for remaining source-language strings.
Terminology consistency
Ikke bestået40sprogligImportant concepts should not be translated differently across pages.
- mediumlinguistic · 95% sikkerhed
Terminology inconsistency
"Arts & Culture" appears both untranslated and translated across fr pages. Affects 4 sampled pages.
Fundet her
Header · <nav> or <button>
https://www.booking.com/index.fr.htmlHvad vi så
"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
Sådan løser du det
Use one translated label for "Arts & Culture" across fr pages.
Translation accuracy
Ikke bestået50sprogligTarget copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 25% sikkerhed
Cross-locale meaning cannot be assessed from the sample
The evidence shows English source strings but no target-language translations, so preservation of meaning, numbers, and product actions is not verifiable.
Fundet her
Hero · <h1>
https://www.booking.com/Hvad vi så
"Find deals for any season" and controls including "Select datesCheck-in date — Check-out date"
Sådan løser du det
Compare localized strings with the source for intent, quantities, dates, and booking actions in their surrounding components.
Fluency
Ikke bestået50sprogligCopy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 25% sikkerhed
Target-language fluency is not evidenced
Only en-us copy is shown; the evidence does not include target-language text that could be checked for grammar or machine-translation artifacts.
Fundet her
Page content · <body>
https://www.booking.com/Hvad vi så
"htmlLang":"en-us" with visible text "Skip to main content ... Find deals for any season"
Sådan løser du det
Review representative localized pages with native speakers for natural phrasing and locale-specific idioms.
Brand voice
Ikke bestået50sprogligLocalized copy should preserve the intended tone of the source.
- infolinguistic · 25% sikkerhed
Localized brand voice cannot be compared
The sample provides English brand copy but no localized variants, so consistency of tone across locales is unverified.
Fundet her
Hero · <h1>
https://www.booking.com/Hvad vi så
"Find deals for any season" and "From cozy bed & breakfasts to luxury hotels"
Sådan løser du det
Compare localized marketing copy with the English source and preserve its welcoming, consumer-oriented tone without literal phrasing.
Grammar and style
Ikke bestået50sprogligLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 25% sikkerhed
Locale-specific style is not assessable
The evidence contains only en-us text and does not provide other locales for checking capitalization, punctuation, formality, or agreement.
Fundet her
Search form · <form>
https://www.booking.com/Hvad vi så
"Select datesCheck-in date — Check-out date" and "2 adults · 0 children · 1 room"
Sådan løser du det
Review each locale’s capitalization, punctuation, date conventions, formality, and plural or agreement rules in the rendered UI.
CTA intent
Ikke bestået65kontekstuelLocalized calls to action should communicate the intended product action.
- infocontextual · 48% sikkerhed
CTA intent is explicit in the English sample only
The English sample includes a clear "Search" action, but localized CTA labels are not provided for comparison.
Fundet her
Search form · <button>
https://www.booking.com/Hvad vi så
"buttons":["HUF","Select datesCheck-in date — Check-out date","2 adults · 0 children · 1 room","Search",...]
Sådan løser du det
Verify that every locale keeps the distinction between selecting inputs and submitting the search action.
UI context
Ikke bestået65kontekstuelTranslations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 48% sikkerhed
Component context is visible only for English labels
The evidence identifies buttons, headings, and navigation-like text in the English page, but does not show whether translated strings fit their components.
Fundet her
Search form · <form>
https://www.booking.com/Hvad vi så
"buttons":["HUF","Select datesCheck-in date — Check-out date","2 adults · 0 children · 1 room","Search",...]
Sådan løser du det
Test localized labels in their actual buttons, navigation items, fields, and date controls, including long and inflected translations.
Product context
Ikke bestået65kontekstuelLanguage should match product concepts such as plans, settings, and workflows.
- infocontextual · 45% sikkerhed
Product terminology is not validated across locales
The sample exposes product concepts such as stays, flights, dates, guests, and rooms in English, but no localized terminology is supplied.
Fundet her
Header and search form · <nav> / <form>
https://www.booking.com/Hvad vi så
"Stays Flights Flight + Hotel Car rental Cruises Attractions Airport taxis" and "2 adults · 0 children · 1 room"
Sådan løser du det
Create a locale glossary for booking concepts and verify consistent terminology across navigation, search, checkout, and account workflows.
Contextual meaning
Ikke bestået65kontekstuelStrings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 45% sikkerhed
Context is present, but only in the source locale
The sample shows strings in surrounding navigation, headings, and form controls, but no translated strings are available for contextual review.
Fundet her
Homepage · <body>
https://www.booking.com/Hvad vi så
"Find deals for any season", "Enter destination", "Select dates", and "Search" appear together in the sampled page content.
Sådan løser du det
Review translations in their rendered page and component context rather than approving isolated string values.
Audience context
Ikke bestået70kontekstuelLanguage should fit the intended audience, such as consumer, enterprise, or developer.
Localized images and assets
Ikke bestået50visuelLanguage-specific images and alt text should match the page locale.
- infovisual · 22% sikkerhed
Localized imagery and alt text are not evidenced
The preview contains no image markup, image assets, or localized alt-text samples, so locale suitability cannot be assessed.
Fundet her
Page content · <img>
https://www.booking.com/Sådan løser du det
Inspect image sources and alt attributes on each locale and replace or translate assets where the visual or embedded text is language-specific.
Text overflow
Ikke bestået60visuelText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 40% sikkerhed
Overflow cannot be verified from the text preview
The evidence lists labels and headings but provides no rendered dimensions, screenshots, or CSS results to confirm clipping or overflow.
Fundet her
Header and search form · <nav> / <form>
https://www.booking.com/Hvad vi så
Labels include "Select datesCheck-in date — Check-out date" and "300M+ reviews from fellow travelers".
Sådan løser du det
Run visual checks across locales and widths, allowing controls and headings to wrap or expand without clipping.
Layout breakage
Ikke bestået60visuelLocalized pages should not overlap, break grids, or overflow modals.
- infovisual · 40% sikkerhed
Layout integrity is not demonstrated
The HTML/text preview does not include rendered geometry or screenshots, so overlap, broken grids, and modal overflow cannot be confirmed.
Fundet her
Homepage · <body>
https://www.booking.com/Hvad vi så
The evidence provides page status, headings, buttons, and text, but no layout measurements or rendered screenshots.
Sådan løser du det
Test long translations in navigation, search controls, cards, and dialogs at representative viewport sizes.
Responsive localisation
Ikke bestået60visuelLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 40% sikkerhed
Responsive behavior is not demonstrated
The evidence contains no viewport-specific captures or responsive measurements, so mobile, tablet, and desktop behavior remains unverified.
Fundet her
Homepage · <body>
https://www.booking.com/Hvad vi så
The preview lists page content but contains no viewport dimensions or responsive render results.
Sådan løser du det
Capture each locale at mobile, tablet, and desktop widths and verify wrapping, stacking, and control accessibility.
Worth a look (1)
Cultural adaptation
Watch88kontekstuelCurrency, dates, addresses, and local examples should fit the market.
Beståede audits (7)
Ikke relevant (8)
Registrerede lokaliteter
arabisk
ar · hreflang
bulgarsk
bg · hreflang
catalansk
ca · hreflang
tjekkisk
cs · hreflang
dansk
da · hreflang
tysk
de · hreflang
græsk
el · hreflang
britisk engelsk
en-gb · hreflang
amerikansk engelsk
en-us · page language
spansk (Argentina)
es-ar · hreflang
mexicansk spansk
es-mx · hreflang
estisk
et · hreflang
finsk
fi · hreflang
fransk
fr · hreflang
hebraisk
he · hreflang
hindi
hi · hreflang
kroatisk
hr · hreflang
ungarsk
hu · you asked
indonesisk
id · hreflang
islandsk
is · hreflang
italiensk
it · hreflang
japansk
ja · hreflang
koreansk
ko · hreflang
litauisk
lt · hreflang
lettisk
lv · hreflang
malajisk
ms · hreflang
nederlandsk
nl · hreflang
norsk
no · hreflang
polsk
pl · hreflang
brasiliansk portugisisk
pt-br · hreflang
europæisk portugisisk
pt-pt · hreflang
rumænsk
ro · hreflang
russisk
ru · hreflang
slovakisk
sk · hreflang
slovensk
sl · hreflang
serbisk
sr · hreflang
svensk
sv · hreflang
thai
th · hreflang
filippinsk
tl · hreflang
tyrkisk
tr · hreflang
ukrainsk
uk · hreflang
vietnamesisk
vi · hreflang
forenklet kinesisk
zh-hans · hreflang
traditionelt kinesisk
zh-hant · hreflang
Stikprøvekontrollerede sider
Næste skridt
Solid baseline with room to improve. Claim this domain to monitor locales as you ship, or book an audit review.
Send this to your team
We'll email a short summary — score, top fixes, and a link back to this report — so it's easy to forward.
