Independent SiteAuditLint analysis
SiteAuditLint crawled 100 URLs on booking.com. The 96 critical items come from two tracking patterns: a /pxgo redirect link carrying a token parameter on 89 pages, and one Tag Manager container loading twice on 6 pages. The core city and region pages scored well.
| Metric | Result |
|---|---|
| Pages crawled | 100 |
| Crawl time | 2m 21s |
| Health score | 91 / 100 (Excellent) |
| Issue types detected | 25 |
| Critical / warnings / opportunities / info | 96 / 54 / 363 / 12 |
| Audit date | October 4, 2026 |
What stood out
Overall assessment
booking.com's city and region pages are in strong shape. 88 of 89 analyzed pages carry self-referencing canonicals and hreflang, 85 use question-led headings, 49 carry FAQ markup, and all nine AI crawlers are allowed.
The critical count reflects tracking rather than page quality. Header links to cruises and other partner products route through booking.com/pxgo with an encrypted token parameter, which SiteAuditLint flags as a potential token in a URL. Six region and car pages also load the same Tag Manager container twice.
Page weight and response time deserve attention next. 86 pages exceed 500 KB, with a median of 1,037 KB, and 42 URLs took longer than one second.
Audit methodology
SiteAuditLint started from the website's homepage and crawled up to 100 URLs by following discoverable internal links and the URLs listed in the XML sitemap. Results represent the URLs reached during the crawl and do not constitute a complete audit of the entire website.
| Starting URL | https://booking.com/ |
|---|---|
| Crawl limit | 100 URLs |
| URLs crawled | 100 (90 HTML) |
| Crawl date | October 4, 2026, 12:04 UTC |
| Crawl duration | 2m 21s |
| Crawl method | Homepage start, internal link and sitemap discovery, robots.txt respected, raw HTML analysis |
| Tool | SiteAuditLint Desktop SEO Crawler |
| Scope | Publicly accessible URLs reached during the crawl |
Technical SEO scorecard
Scores are the category scores SiteAuditLint calculates as part of its Site Health Score.
| Area | Score | Key finding |
|---|---|---|
| Overall health | 91 | Excellent rating from SiteAuditLint |
| Technical | 99 | pxgo redirect links in the header |
| Content | 97 | 1 empty pxgo page |
| Performance | 88 | 86 pages over 500 KB, 42 slow responses |
| AEO | 99 | All 9 AI crawlers allowed, no llms.txt |
Major findings
1. Token parameters in header links
MediumFinding: 89 pages link to booking.com/pxgo URLs that carry a token= parameter and, on some links, a session id inside the encoded destination.
Why it matters: URLs with tokens or session ids can be logged, shared or cached. These appear to be outbound tracking redirects to partner products. The flag is a prompt to confirm the tokens are not tied to an individual visitor.
| URL | Evidence |
|---|---|
https://www.booking.com/cars/index.html | Links to booking.com/pxgo?token=... |
https://www.booking.com/city/ca/montreal.html | Links to booking.com/pxgo?aid=304142&...&token=... |
Recommended fix: Confirm the tokens are generic campaign values. If any are visitor-specific, move them out of the URL.
2. Tag Manager loaded twice
MediumFinding: GTM-5Q664QZ loads 2 times on 6 pages, including /cars/index.html, /region/gr/santorini.html and /region/jp/kyoto.html.
Why it matters: A container that loads twice can fire tags twice, which inflates analytics and conversion data.
| URL | Evidence |
|---|---|
https://www.booking.com/cars/index.html | GTM-5Q664QZ loaded 2 times |
https://www.booking.com/region/jp/kyoto.html | GTM-5Q664QZ loaded 2 times |
Recommended fix: Remove the duplicate container snippet from the region and cars templates.
3. Large HTML documents
MediumFinding: 86 pages exceed 500 KB of HTML. The median is 1,037 KB and the largest is 1,345 KB.
Why it matters: Large documents take longer to download and parse, particularly on mobile.
| URL | HTML size |
|---|---|
https://www.booking.com/cars/index.html | 1,198 KB |
https://www.booking.com/city/ca/montreal.html | 1,080 KB |
Recommended fix: Reduce inlined data in the city template.
4. Slow server responses
MediumFinding: 42 URLs took longer than 1,000 ms. The median among them was 1,109 ms and the slowest was 1,505 ms.
Why it matters: City pages are primary entry points from search.
| URL | Result |
|---|---|
https://www.booking.com/city/ch/zermatt.html | 1,276 ms |
https://www.booking.com/city/ca/niagara-falls.html | 1,063 ms |
Recommended fix: Review caching on the city template.
5. Missing viewport on region and cars pages
LowFinding: 7 pages have no viewport meta tag. The same pages lack Open Graph tags, and 6 of them are the pages that load Tag Manager twice.
Why it matters: Without a viewport tag, mobile browsers render the page at desktop width. The overlap suggests these pages use a separate, older template.
| URL | Evidence |
|---|---|
https://www.booking.com/region/gr/santorini.html | No viewport |
https://www.booking.com/cars/index.html | No viewport |
Recommended fix: Move the region and cars pages onto the main page template.
6. Header link to a redirecting URL
LowFinding: 82 pages link to https://booking.com/packages.html, which 301 redirects to the www version.
Why it matters: A non-www link in shared navigation adds a redirect on every page.
Recommended fix: Link to https://www.booking.com/packages.html directly.
What's working well
- No 4xx or 5xx responses across 100 URLs.
- 88 pages carry self-referencing canonicals and hreflang.
- 49 pages carry FAQ or Q&A structured data and 85 use question-led headings.
- Only 1 page lacks a title, meta description or H1, and it is the pxgo redirect.
- All nine AI crawlers are allowed.
Priority fixes
- Remove the duplicate Tag Manager snippet6 pages. Pages affected: 6
- Confirm pxgo tokens are not visitor-specific89 pages. Pages affected: 89
- Move region and cars pages to the main templateViewport and Open Graph. Pages affected: 7
- Reduce HTML size on city pages86 pages. Pages affected: 86
- Link to www for packages82 pages. Pages affected: 82
Crawl data
| Metric | Result |
|---|---|
| URLs crawled | 100 |
| HTML pages | 90 |
| 2xx responses | 90 |
| 3xx redirects | 10 |
| 4xx responses | 0 |
| 5xx responses | 0 |
| Missing titles | 1 |
| Missing meta descriptions | 1 |
| Missing H1s | 1 |
| Self-referencing canonicals | 88 |
| Pages with FAQ / Q&A markup | 49 |
| Missing viewport | 7 |
| HTML over 500 KB | 86 |
| Slow responses (over 1,000 ms) | 42 |
| AI crawlers allowed | 9 of 9 |
On-page counts (titles, descriptions, headings, canonicals) are measured across the 89 URLs that returned an HTML page with a 200 status.
Audit limitations
The crawl was limited to 100 URLs and started from the homepage, so only URLs discovered through internal links and the XML sitemap are represented. A 100-URL crawl does not represent the entire website. Findings reflect the site at the time of the crawl on October 4, 2026. SiteAuditLint analyzed the HTML returned by the server, so content added later by JavaScript and responses that differ for automated clients may not match what a browser shows. This audit evaluates technical observations, not overall business or search performance.
This is an independent SiteAuditLint analysis of publicly accessible pages. It was not requested or endorsed by Booking.com, and it does not imply that Booking.com uses SiteAuditLint.