현지화 보고서

Booking.com

Online travel

booking.com

제품: 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.

브랜드 보이스: helpful, trustworthy, value-focused

현지화 점수

64/100

개선 필요

사용자는 눈에 띄는 현지화 문제를 겪을 수 있습니다.

73기술 감사
48언어 품질 감사
70맥락 감사
64시각적 감사

감사 완료일: 2026. 8. 25.범위: 공개 스마트 샘플 · 기술·언어·맥락·시각적 크레딧신뢰도: 샘플링한 페이지를 기반으로 한 개략적인 상태 점검 — 전체 사이트 크롤링은 아닙니다.

기술, 언어, 맥락 및 시각적 현지화 크레딧 전반에서 15개 페이지를 표본으로 추출했습니다. 현지화 감사 점수 산정 방법

다른 사람들과의 비교

공개 감사 23개 중 #18위

Ahead of 5 other public audits공개 평균: 70/100

전체 순위표 보기

우선 수정할 항목

1
high
Valid sitemap not found
No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
See details
2
high
Untranslated call to action
A fr page still uses source-language CTA copy.
See details
3
medium
Terminology inconsistency
"Arts & Culture" appears both untranslated and translated across fr pages. Affects 4 sampled pages.
See details

감사 기준

7 passed · 1 to watch · 19 to fix · 8 not applicable

확인 필요 (19)

Language switcher
실패55기술적
Visitors should move between locales without losing the current page.
- infotechnical · 신뢰도 42%
  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.
  발견 위치
  Header · <nav>
  https://www.booking.com/
  확인한 내용
  "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
실패18기술적
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%
  Valid sitemap not found
  No fetchable XML sitemap with URL entries was found at /sitemap.xml or via robots.txt.
  발견 위치
  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.
Structured data
실패0기술적
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 신뢰도 95%
  Structured data omits inLanguage
  JSON-LD is present but does not declare inLanguage on sampled pages.
  발견 위치
  JSON-LD · <script type="application/ld+json">
  https://www.booking.com/
  확인한 내용
  WebSite is present but inLanguage is missing
  해결 방법
  Set JSON-LD inLanguage to match each page locale.
Accessibility localisation
실패65기술적
lang, aria-label, and alt text should match the page locale.
- infotechnical · 신뢰도 62%
  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.
  발견 위치
  Document root · <html>
  https://www.booking.com/
  확인한 내용
  "htmlLang":"en-us","dir":"ltr"
  해결 방법
  Audit each locale’s <html lang>, accessible names, and image alt text against its rendered language.
Translation completeness
실패50언어적
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 신뢰도 92%
  Untranslated call to action
  A fr page still uses source-language CTA copy.
  발견 위치
  Primary action · <button>
  https://www.booking.com/index.fr.html
  확인한 내용
  Primary CTA: "Arts & Culture"
  해결 방법
  Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 신뢰도 25%
  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.
  발견 위치
  Page content · <body>
  https://www.booking.com/
  확인한 내용
  "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.
Terminology consistency
실패40언어적
Important concepts should not be translated differently across pages.
- mediumlinguistic · 신뢰도 95%
  Terminology inconsistency
  "Arts & Culture" appears both untranslated and translated across fr pages. Affects 4 sampled pages.
  발견 위치
  Header · <nav> or <button>
  https://www.booking.com/index.fr.html
  확인한 내용
  "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.
Translation accuracy
실패50언어적
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 신뢰도 25%
  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.
  발견 위치
  Hero · <h1>
  https://www.booking.com/
  확인한 내용
  "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.
Fluency
실패50언어적
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 신뢰도 25%
  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.
  발견 위치
  Page content · <body>
  https://www.booking.com/
  확인한 내용
  "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.
Brand voice
실패50언어적
Localized copy should preserve the intended tone of the source.
- infolinguistic · 신뢰도 25%
  Localized brand voice cannot be compared
  The sample provides English brand copy but no localized variants, so consistency of tone across locales is unverified.
  발견 위치
  Hero · <h1>
  https://www.booking.com/
  확인한 내용
  "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.
Grammar and style
실패50언어적
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 신뢰도 25%
  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.
  발견 위치
  Search form · <form>
  https://www.booking.com/
  확인한 내용
  "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.
CTA intent
실패65맥락적
Localized calls to action should communicate the intended product action.
- infocontextual · 신뢰도 48%
  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.
  발견 위치
  Search form · <button>
  https://www.booking.com/
  확인한 내용
  "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.
UI context
실패65맥락적
Translations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 신뢰도 48%
  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.
  발견 위치
  Search form · <form>
  https://www.booking.com/
  확인한 내용
  "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.
Product context
실패65맥락적
Language should match product concepts such as plans, settings, and workflows.
- infocontextual · 신뢰도 45%
  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.
  발견 위치
  Header and search form · <nav> / <form>
  https://www.booking.com/
  확인한 내용
  "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.
Contextual meaning
실패65맥락적
Strings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 신뢰도 45%
  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.
  발견 위치
  Homepage · <body>
  https://www.booking.com/
  확인한 내용
  "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.
Audience context
실패70맥락적
Language should fit the intended audience, such as consumer, enterprise, or developer.
Localized images and assets
실패50시각적
Language-specific images and alt text should match the page locale.
- infovisual · 신뢰도 22%
  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.
  발견 위치
  Page content · <img>
  https://www.booking.com/
  해결 방법
  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
실패60시각적
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 신뢰도 40%
  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.
  발견 위치
  Header and search form · <nav> / <form>
  https://www.booking.com/
  확인한 내용
  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.
Layout breakage
실패60시각적
Localized pages should not overlap, break grids, or overflow modals.
- infovisual · 신뢰도 40%
  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.
  발견 위치
  Homepage · <body>
  https://www.booking.com/
  확인한 내용
  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.
Responsive localisation
실패60시각적
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 신뢰도 40%
  Responsive behavior is not demonstrated
  The evidence contains no viewport-specific captures or responsive measurements, so mobile, tablet, and desktop behavior remains unverified.
  발견 위치
  Homepage · <body>
  https://www.booking.com/
  확인한 내용
  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.

Worth a look (1)

Cultural adaptation
Watch88맥락적
Currency, dates, addresses, and local examples should fit the market.

통과한 감사 항목 (7)

해당 없음 (8)

감지된 로캘

아랍어
ar · hreflang
불가리아어
bg · hreflang
카탈로니아어
ca · hreflang
체코어
cs · hreflang
덴마크어
da · hreflang
독일어
de · hreflang
그리스어
el · hreflang
영어(영국)
en-gb · hreflang
영어(미국)
en-us · page language
스페인어(아르헨티나)
es-ar · hreflang
스페인어(멕시코)
es-mx · hreflang
에스토니아어
et · hreflang
핀란드어
fi · hreflang
프랑스어
fr · hreflang
히브리어
he · hreflang
힌디어
hi · hreflang
크로아티아어
hr · hreflang
헝가리어
hu · you asked
인도네시아어
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

표본 페이지#+#+#+#+

다음 단계

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.