Construction

Cadisola Plus

Multi-site WordPress architecture — a house for each segment

The story — Cadisola Plus

The situation

Cadisola Plus works in construction, with the need to coherently cover several distinct market segments without diluting the message.

The diagnosis

A single site couldn't cover different segments without becoming a confusing compromise — for users and for search engines alike. It needed an architecture that gave each segment its own house.

What we built

A multi-site architecture on WordPress: each domain with its own content and relevance for its segment. We brought the traffic, with a clean structure and a consistent volume of content. The performance and crawl trade-offs — reported honestly, never hidden.

Insight

Several market segments call for several houses, not one site trying to be everything to everyone.

System Failure / Challenge

A single WordPress site couldn't coherently cover three distinct market segments without becoming a confusing compromise — for users and search engines alike. It needed an architecture that gave each segment its own house.

Active Protocol / Solution

Multi-site architecture: three domains, each with its own content and relevance for its own segment. We kept the existing stack (WordPress + Astra PRO) and optimised in a targeted way, rather than rebuilding for the score's sake. We brought the traffic, with a clean structure and a consistent volume of content; optimisation continued into 2026, measurable in Search Console — where we have documented access. The performance and crawl trade-offs we report honestly in the full audit, we don't hide them. The current logo is our rebuild.

5 of 19

Ranked #1 on Googletitle queries ranked #1 · weakest of 3 samples, 25 Jul 2026

216

Articles publishedtradesman · engineer · designer — separate intents

PROJECT.OVERVIEW

Client

Cadisola Plus

Industry

Construction

Delivered

August 2025

Status

Live

PROJECT.QUESTIONS

Questions about this project

Because Cadisola Plus serves three distinct market segments, and a single WordPress site would have become a confusing compromise — for users and search engines alike. Each domain carries its own content and its own relevance for its own segment. The rule we applied: several market segments call for several houses, not one site trying to be everything to everyone.

Fair question — we asked it ourselves. The difference: a PBN exists to pass links around; here, each domain serves a real customer segment, with its own content and its own relevance. We also publish no traffic figures on this project — the page keeps only what a reader can verify live, nothing that asks for blind trust.

A 100 SEO score in Lighthouse, on all domains — verifiable live, any time: open cadisola-sebes.ro (the main node), run Lighthouse in Chrome and compare. We don't publish traffic numbers on this project, because you couldn't check those yourself; the page only carries what anyone can measure today.

It was a KEEP decision: the existing stack was doing its job, so we chose targeted optimization over a rebuild for the score's sake. Honest all the way through: the solution comes with performance and crawl trade-offs, and we report those openly in the full audit rather than hiding them. A rebuild is only worth it when the problem actually calls for one.

We don't publish the value of individual contracts. For an honest reference point, our pricing grid is public at /preturi — a multi-site project starts from the price of a single WordPress site and depends on the number of domains and how much they share. We discuss your specific situation first; then you get a fixed figure, in writing.