Overview
Executive summary
The operator sold guided tours across Europe and Asia but relied on an English-only WordPress site with poor mobile performance and no hreflang structure. German, French, and Japanese travelers landed on English pages — bounce rates were high and international organic search underperformed.
We designed and built a multilingual Next.js platform: locale-aware routing, translated tour and destination content via CMS workflow, technical SEO (hreflang, sitemaps, schema), and a performance budget that cut LCP in half — delivering 3.4× organic traffic growth within twelve months of launch.
Challenge
Business problems and how we solved them
1English-only site capped international demand
Non-English markets represented 60% of addressable demand but less than 20% of bookings.
Technique · 8-locale i18n + market-specific landing pages.
Solution · Full catalog in en, de, fr, es, it, ja, zh, ar with native copy review; geo-based default locale; language switcher on every template.
2SEO confusion and duplicate risk
No hreflang; translated PDFs linked externally; Google indexed thin duplicates.
Technique · hreflang cluster + canonical policy + locale sitemaps.
Solution · Every tour page emits alternates for all locales; x-default to English; 8 Search Console properties for monitoring.
3Slow WordPress hurt conversion
4.2s mobile LCP and heavy image carousels — high exit on tour detail pages.
Technique · Next.js ISR + image CDN + component-level code splitting.
Solution · 96 mobile Lighthouse on tour templates; WebP with responsive srcset; booking CTA above fold on mobile.
4Content updates required developers
Marketing could not launch seasonal tours without agency tickets.
Technique · Headless CMS + preview + locale publish.
Solution · Editors draft tours once; translation workflow per locale; ISR revalidation on publish — no deploy for content changes.
System design
Architecture diagrams
Locale routing, hreflang SEO, content pipeline, and the platform stack behind the global tour site.
Visitor locale detection through localized content to market-specific enquiry paths.
Eight language alternates linked to each canonical tour URL.
CMS authoring, translation, review, and publish to CDN-backed pages.
Next.js, CDN, headless CMS, search, images, and analytics.
Engineering
i18n, SEO, and performance
i18n architecture
Next.js App Router with [locale] segments; message catalogs in JSON; RTL layout support for Arabic.
- en
- de
- fr
- es
- it
- ja
- zh
- ar
SEO & discoverability
hreflang alternates on every tour URL; locale sitemaps; structured data for tours and organization.
Indexed URLs
4.2k+
Redirects
1.1k
Schema types
Tour, FAQ
GSC props
8
Performance
Static generation for catalog pages; ISR for CMS updates; WebP images; edge caching for HTML and assets.
- ISR
- WebP
- font_subset
- edge_cache
Content ops
Headless CMS with locale fields; translation vendor webhook; preview URLs per language before publish.
- Draft
- Translate
- Live
