The Elektriker network: one engine, seven cities

Seven towns, one engine repainted

The Elektriker network is seven independent local-electrician sites, one for each municipality in greater Stockholm: Täby, Tyresö, Järfälla, Solna, Bromma, Haninge and Sollentuna. Each presents itself as din lokala elfirma, the local firm with its heart in that specific town, with its own domain and brand, its own address and phone, its own Google Business presence, and content written around that town.

The strategy is programmatic local SEO at scale: rather than one site trying to rank everywhere, a dedicated hyper-local site per market. The engineering insight is that all seven are the same engine, repainted. One template, one optimisation recipe, one content architecture, localised seven times, which is what makes the network both fast to expand and cheap to operate.

One master template, localised seven times

Each site is a WordPress build on Elementor Pro over a lightweight base theme, where a single master template defines the structure and design system and each city is a repaint with local content. Every site is a complete local-SEO machine, not just a homepage: a town hub plus neighbourhood sub-area pages (for Täby, dedicated pages for Viggbyholm, Arninge-Ullna, Gribbylund and more) that capture electrician-near-me searches at the district level, a full set of service pages, a localised blog, local trust furniture (a Google Maps embed, local reviews, certification badges, an FAQ and a callback prompt), and local-business schema so each site reads as a distinct local entity.

Multi-tenant: isolated per site, managed as one

The network is a multi-tenant deployment: seven fully independent WordPress sites, each on its own domain in its own isolated environment, running side by side on shared, centrally managed and hardened infrastructure. Isolation means a problem on one site never touches another; central management means the whole fleet is maintained, updated and secured as one operation. Each site runs the same proven stack: Cloudflare at the edge, an in-memory full-page cache, Redis for object caching, and a tuned web server with PHP and MariaDB, so a typical visitor is served a fully cached page with effectively no database work.

Launch a market by repainting the engine

The network treats site creation as a repeatable system. A new market is launched by cloning the proven engine and localising it: town content, address and phone, district pages, local schema and a Google profile. The hard engineering is done once, so entering a new town is a content and configuration exercise. A single optimisation recipe is applied identically across the fleet (in-memory caching, CSS and JavaScript aggregation, font and icon optimisation, modern image formats), so tuning it once improves every site. Each site captures leads two ways, a quote form and a callback popup that promises a call within minutes, and cache purging, updates, security and backups run across all seven as one managed fleet.

Shared structure, isolated per town

Each site keeps its own data while the network shares a structure. MariaDB per site holds isolated content, pages and leads; Elementor template data and custom fields carry the shared architecture, localised; structured schema per site gives each town its own distinct name, address and phone; Redis caches per site; and each town runs its own form and callback intake. The valuable pattern is structural reuse with data isolation: every site shares the same content model and local-business schema shape, but each owns its town pages, reviews and lead pipeline, so the network compounds into broad local-search coverage while each town stays clean and self-contained.

Tuned once, shipped to all seven

Local-service buyers convert on speed and trust and are overwhelmingly on mobile, so the network is tuned hard for mobile Core Web Vitals. The shared recipe is the engine: in-memory full-page caching takes server response time to the floor, asset aggregation and minification cut the number and weight of files, font and icon handling removes render-blocking work, and modern image formats keep visually rich pages light. Applied uniformly, it lifts every site to strong mobile and desktop scores, and because it is shared, every improvement ships to all seven at once.