TripAdvisor

TripAdvisor's corporate blog ran on one WordPress install and served eight country domains in five languages, and I was the engineer who built it, kept it running through three rebrands, and eventually wrote the redirects that retired it into TripAdvisor's own publishing platform without losing the search equity it had earned.

Key Takeaways

  • Served eight country domains from a single WordPress install, no multisite, with the locale resolved from a header set by TripAdvisor's own reverse proxy.
  • Localized everything that mattered: per-domain content tagging, hard 404s for content not published to a domain, and canonical and hreflang generated from the same source of truth.
  • Generated UK English at request time, British spellings and local links applied from a curated word list, so no parallel copy of any post ever had to be maintained.
  • Scoped the editorial experience per editor, so a French editor's admin is French posts, without restricting administrators.
  • Carried the platform through three brand identities, including a full wordmark change applied across content, metadata and code, without a rebuild.
  • Retired the property responsibly, with per-article deep-linked redirects across seven country domains preserving the ranking value of a decade of content.

Organization

TripAdvisor operates dozens of country-specific domains, each with its own language, market and search results to compete in. The corporate blog served the marketing organization across eight of those domains in five languages, alongside sister properties: the engineering blog, a Japanese travel guide, and a custom Apple News plugin.

Challenge

Multi-market editorial usually means a multisite network and per-market maintenance overhead. TripAdvisor needed one platform serving every market correctly, locale-aware content, SEO signals that told Google exactly how the domains related, and an editorial workflow that let one team publish across all of them, and it had to survive nearly a decade of brand and platform change.

Solution

  • Locale architecture keyed off the proxy header, with a reference map of TripAdvisor's global domains driving the rollout.
  • A purpose-built JSON API, nine routes with parameter whitelisting, per-locale caching and public cache headers, feeding an Angular front end with server-side rendering for every page that matters to SEO.
  • Cache segmentation coordinated with the host so each country domain cached independently, with diagnostic tooling built in.
  • Custom Elementor widgets and locked page templates so landing pages stayed on brand.
  • Weighted SQL search ranking, title matches scored above body matches, replacing default WordPress search behavior.
  • At retirement, 109 hand-mapped deep-linked 301s across seven TLDs plus a host-aware catch-all.

Results

  • Eight country domains served for 8.5 years from one install, WordPress 4.x through 6.x.
  • Roughly 70% of multisite maintenance overhead avoided.
  • Roughly 90% of search equity preserved through retirement.
  • Zero duplicate posts required for UK English; zero cross-domain content leaks.
  • Three rebrands absorbed without a rebuild.