← Back to portfolio All case studies
Editorial / locals' concierge · Case study
Everything worth doing in London, 2026
2026 London — Next.js editorial / locals' concierge with 148 curated listings across 9 categories, live event feed wired to TicketWave, geolocation-aware browsing, 60-second edge cache + 10-minute SWR. One author, every city — the radical transparency hero ('I haven't been to London yet') as positioning weapon.
- Next.js
- Vercel London (lhr1)
- OpenStreetMap / Google Places API
- TicketWave HQ feed
- Edge cache + SWR
The hero on 2026london.com is the case study. “Everything worth doing in London, 2026” — and then, six lines down: “I haven’t been to London yet. Guides here are research-led until I have.”
That second line is the entire strategic point.
The radical-transparency hero
Travel editorial in 2026 is a Wild West of fake “curated” content — AI-generated lists, affiliate-stuffed “top 10s”, scraped TripAdvisor copy. The dominant content pattern is dishonest by design.
2026 London opens with a single sentence of self-disclosure. The reader knows immediately:
- The content is editorial, not paid
- The author is one person
- “Research-led” means open data, named sources, and humility
- When the author has been to a place, they’ll say so
It’s the Bourdain move. The credibility comes from admitting what you don’t know, then doing the work anyway. Trust compounds because the contract is honest from line one.
One author, every city
The site is part of an eight-city network — 2026london.com, 2026paris.com, 2026rome.com, 2026athens.com, and so on (full list in the footer nav). All written by the same author, on the same editorial standard. The aggregated brand is a personal travel-and-recommendations network — Bourdain-across-cities, single voice, opinionated.
The architectural choice that makes the single-author model viable is aggressive content reuse. A category page (Restaurants, Fine Dining, Cafés, Boat Parties, Yoga, Wellness/Spa) is the same shape in every city; the listings are the variable. A “4 days in [city]” itinerary follows the same template. The author writes the schema once and fills cities into it.
What’s actually on the site
- 9 venue categories — Fitness, Tours, Restaurants, Cafés, Fine Dining, Beach Clubs, Wellness/Spa, Yoga, Boat Parties
- 148 curated listings — each with author notes, opening hours, price band, and a “why I picked this” rationale
- Long-form itinerary guides — “4 Days in London 2026” reads like an editorial feature, not a SEO long-tail trap
- Live event feed via TicketWave — bookable inventory wired in from the sister platform; 5% affiliate commission per ticket
≥4.5-star "top-rated" filter— the directory respects Google Maps consensus alongside the editor’s opinion- Newsletter — single sender, no cadence promises, no inbox spam
- Geolocation-aware browsing —
permissions-policy: geolocation=(self)is set (uniquely among the seven sites in this case-study set); “near me” filtering works without sending location off-device
The performance choice
The Cache-Control header is the architectural giveaway: public, s-maxage=60, stale-while-revalidate=600.
That’s a 60-second edge cache with 10-minute stale-while-revalidate. The rendered page sits in Vercel’s London edge for a minute; if a request comes in after expiry, the edge serves the stale page immediately and revalidates in the background. Within 10 minutes of last fetch, no request ever waits on a server roundtrip.
For editorial content that updates a few times a day (new listings, edits to existing ones, event-feed refresh), 60s edge cache plus 10min SWR is the perfect knob: feels live, costs nothing to serve. The home page loads in well under a second from a London IP.
The TicketWave event feed integration
The event listings on 2026 London are not a standalone CMS. They’re a live feed from the TicketWave HQ platform, pulled at build time and revalidated on a cron. A venue that lists on TicketWave for a specific London event automatically appears in 2026 London’s event grid, with a deep-link to the venue’s white-labelled booking page.
That’s the platform-pedigree story expressed as architecture: same company group, two surfaces (the editorial recommendation and the bookable inventory), connected without a third-party affiliate network in the middle.
Anti-marketplace, anti-middleman
The footer copy makes the positioning explicit: “No booking middlemen. No marketplace markup. No resold tickets.”
Every booking link points to the venue’s own white-labelled booking page (via TicketWave). Every restaurant link points to the restaurant’s own site. There’s no GetYourGuide affiliate, no Viator wrapper, no Klook commission rail. The 5% affiliate cut on TicketWave bookings is the only commercial flow, and it’s disclosed on the home page.
What UK Web Marketing learned from this build
Three transferable patterns:
-
One-author content scale via templated category pages — the same editorial spine reused per city is how the regulated-vertical pages on the UK Web Marketing site work too (clinic/solicitor/school/accountant share the same template, swap the specifics).
-
Aggressive edge caching for editorial content — the 60s+SWR pattern is what every small-business blog should use; it’s the difference between a £45/mo site that feels fast and a free WordPress site that feels sluggish.
-
Radical transparency as positioning — “I haven’t been to London yet” is the hero that converts trust-conscious readers. The equivalent on a UK Web Marketing site is “hand-coded by one developer, no agency overhead, here’s the price.” Both work for the same reason.
If you’re building an editorial brand, a directory, or a curated network of local content: WhatsApp me. The 2026 London pattern is replicable, and I’ve already built it once.