Nest Worldwide covers real estate development, bespoke furniture manufacturing and corporate logistics. The three share a story but not a customer — the site was built to resolve exactly that tension.
A static website bringing three divisions — Nest Cihan Yapı (real estate development), Nest Cihan Mobilya (bespoke furniture) and Nest Global Transport (corporate logistics) — under one corporate identity. The construction group's projects are presented with a tabbed architecture where each project opens in a detail dialog rather than a separate page. The site is produced as static HTML and search visibility is structured per division.
Companies with several divisions face a classic dilemma when building a website: one site or separate sites?
Separate sites let each division speak in its own voice, but mean three maintenance loads, three domains and three separate search authorities — none of which can grow strong alone. One site consolidates authority, but loses visitors if structured badly: someone looking for furniture who lands among construction projects leaves.
Here the choice was one site, because the three divisions share an owner, a region and a corporate reputation. But the internal structure lets a visitor separate quickly into the division they care about.
The home page separates the three divisions with equal weight and clarity. A visitor can decide on the first screen which business they are looking for, and move from there into that division's own narrative.
This has an important consequence: the home page is not trying to sell, it is trying to route. On multi-brand sites there is a strong pull to fill the home page with every division's message; the result is a page where no message gets read. Here the home page's job is to send the visitor to the right section by the shortest path.
The construction side uses a tabbed structure: projects are split by category, and a selected project opens in a detail dialog without leaving the page.
The reason is navigation cost. A separate page per project forces constant back-and-forth, and visitors to construction projects typically compare several. Opening the detail in place keeps that comparison fluid.
Technically the dialog uses the browser's own dialog element — it closes with the keyboard, focus management works correctly and it stays meaningful to screen readers. Using the platform's primitive rather than rebuilding one gives a more robust result for both accessibility and maintenance.
The site is static HTML with no content management system behind it. For corporate sites that is often the right call:
The cost is that the client cannot edit content from a panel. For a corporate firm making a few updates a year, that cost is lower than permanent maintenance.
Search was structured per division. The three have completely different search behaviour: real estate queries are location-led, furniture queries are product- and production-led, logistics queries are service- and route-led.
So rather than targeting one "corporate" keyword set, content and title structure were built around each division's own search intent. Company name, region and division produce meaning together — and the site's title and description structure reflects that.
Nest Worldwide now presents three divisions under one domain without any of them suppressing the others. Maintenance is minimal because the site is static, and the project section can be browsed without page changes.
The transferable lesson: for multi-division companies the answer is not separate sites but clear separation within one site. The home page's job is not to explain everything at once but to route the visitor to the right division. Search should target division-level intent rather than a single corporate identity.
If the divisions share an owner, a region and a corporate reputation, one site is stronger: search authority accumulates in one place and maintenance is singular. Separate sites make sense only when divisions address different markets, different countries or genuinely independent brands.
The deciding question is how often you will update content yourself. Weekly publishing or frequent product changes need a CMS. For a corporate site updated a few times a year, static is faster, safer and cheaper to maintain — there is no queue of plugins waiting to be patched.
Visitors looking at construction projects usually compare several. With a page per project that comparison becomes constant back-and-forth. Opening the detail in place keeps it fluid — and because the dialog uses the browser's own element, keyboard and screen-reader support are preserved.
Not directly from a panel. Updates are made in the source content and the site is rebuilt and republished. For a business publishing frequently that is a constraint; for a corporate firm making a few updates a year, the speed, security and low maintenance received in return are usually worth more.