An SEO and CMS platform that scales editorial content across 9 languages
A WordPress Multisite platform that lets a small content team publish 150+ articles a year across 9 languages and drive 100K monthly visits.

The challenge
Indie Campers operates campervan rentals across multiple European markets. Their growth strategy depends on organic SEO content — city guides, route inspiration, vehicle reviews — and that content has to live in the language of every market they serve. A small content team trying to ship across nine languages on a single CMS hits a hard wall fast. Every publication becomes a coordination problem: translation, regional editorial standards, local SEO optimisation, and a CMS that wasn't built for distributed authorship.
The growth thesis required scaling editorial output without scaling team size proportionally. The CMS had to do the work the team couldn't.
What we learned
| Central publishing throttles growth | Every article passing through one team means one team's capacity caps publishing across all markets. |
| Distributed authority needs platform support | Letting regional teams publish autonomously requires infrastructure that enforces standards without requiring approval. |
| Independence creates fragmentation | Without shared infrastructure, regional teams building independently produce inconsistency faster than the velocity gain compensates. |
The solution
Twistag built the editorial backbone on WordPress Multisite. Each language market runs as its own site with shared templates, a shared component library, and shared SEO infrastructure — but with editorial autonomy at the regional level. A content lead in Spain doesn't need to wait on a central editor in Lisbon to publish. They have their own admin, their own queue, their own publishing cadence. The shared platform enforces consistency in design, schema, and analytics.
The SEO layer was the harder build. We integrated structured data templates for travel content (location pages, route guides, vehicle types), schema markup that surfaces in Google's travel-specific search features, and a content audit dashboard that flags gaps in coverage. The platform supports cross-market linking automatically — a city guide written in Portuguese can link to its Spanish counterpart without an editor doing the manual work.
We trained the team on the platform rather than embedding ourselves as the editorial backbone. The point was that Indie Campers' content team should be able to operate without us. So we documented workflows, built admin shortcuts, and set up enough automation that a regional editor's first day looks like "log in, write, publish" rather than "call Twistag."
What this shaped
| Decouple authority from control | Regions publish autonomously while shared code enforces SEO rules, theme updates, and brand standards underneath. |
| Training replaces gatekeeping | When teams understand the platform, they stop asking permission for what's already allowed. |
| One codebase, many properties | Multi-site infrastructure with one shared codebase lets a small core team govern many sites without proportional headcount. |
The impact
The platform now serves nine language markets with native editorial workflows. The content team ships 150+ articles per year — a pace they couldn't have hit on a non-distributed CMS. Organic search traffic runs at 100,000+ monthly visits, with the largest traffic sources being long-tail city and route queries that wouldn't have been possible to target without the multilingual SEO layer.
The architectural choice paid off in flexibility. When Indie Campers entered new markets, adding a tenth or eleventh language was an operational task, not an engineering project. The CMS scales with the business strategy.
What this proved
| Local voice beats central voice | People in a market read its dialect and search behaviour better than any central team. |
| Authenticity compounds in rankings | Articles in local voice rank and engage at rates that translated central content rarely matches. |
| Leverage scales lean teams | Two developers maintaining shared infrastructure can support nine languages because they're enabling, not gatekeeping. |
Technologies used
- WordPress
- GCP

