Technical Redesign of a Real Estate Website in Switzerland: +110% Organic Traffic in 2 Months

By Gaël, Co-Founder / CTO

Technical redesign of a real estate website in Switzerland improving organic traffic and SEO performance

In competitive markets like real estate in Switzerland, website performance doesn’t depend solely on design or content quality. It primarily relies on its technical architecture. This approach aligns with a performance-first SEO-first website philosophy, where every architectural decision directly influences organic visibility. This often invisible foundation determines stability, speed, and a site’s ability to sustainably rank for strategic queries.

In late December, we undertook a complete redesign of a real estate website based on WordPress. The objective wasn’t to “do SEO” in the marketing sense, but to correct a technical structure that had become limiting. Two months after launch, the results were unambiguous.

Organic traffic increased by over 110%. More than 20 keywords positioned in top 3, whereas none were there previously. The site reached 1st position on major local queries like promoteur immobilier Lausanne and promoteur immobilier Vaud, while the national query promoteur immobilier Suisse settled at 6th position. During the same period, the Lighthouse performance score improved from approximately 74/100 to 97/100. The Largest Contentful Paint dropped from 3.8s to 1.3s, while the First Contentful Paint fell below 1.0s. These indicators reflect a real and measurable improvement in user experience.

No massive link building campaign. No radical editorial redesign. In paid acquisition contexts, this performance also directly impacts advertising profitability on Google Ads.

Only a comprehensive architectural modernization.

1. A Functional WordPress, but Structurally Improvable

The site initially relied on a standard WordPress installation, with a traditional theme and several plugins added over time. Nothing exceptionally problematic, but a progressive accumulation of technical debt that eventually weighed on performance.

Embedded JavaScript far exceeded actual needs, the DOM presented excessive depth, and the overall structure lacked coherence. Performance wasn’t catastrophic, but unstable. The Lighthouse performance score stagnated around 74/100, with a Largest Contentful Paint close to 4 seconds, which, in a competitive market, inevitably limits organic visibility potential.

The content existed, business legitimacy was there. However, the technical foundation didn’t allow the site to fully express its potential.

2. Modernizing Without Abandoning WordPress

Rather than migrating to a Headless architecture, we chose to deeply modernize WordPress by adopting the Roots ecosystem. We analyzed different WordPress alternatives, particularly headless architectures, before selecting the Roots ecosystem. The objective wasn’t to change tools, but to regain control over structure, rendering, and execution environment.

Bedrock enabled proper project organization and dependency management via Composer, eliminating the difficult-to-control plugin stacking logic. Sage served as the foundation for an entirely custom theme, offering total control over generated HTML. Tailwind CSS, combined with automatic purging, eliminated unused CSS, while Vite ensured modern and optimized asset bundling.

ACF Pro was integrated via Composer and used with ACF Builder to structure Gutenberg blocks cleanly and consistently. Acorn introduced Laravel-inspired organization within the theme, bringing more modular and maintainable logic. Trellis, finally, ensured stable and optimized server provisioning from the start, avoiding the approximate configurations often encountered on standard hosting.

Rank Math remained the sole SEO plugin, to limit dependencies while maintaining precise metadata control.

3. Controlled Gutenberg, Optimized Rendering

The choice to keep Gutenberg was deliberate. Rather than adding a page builder generating bloated HTML, we structured custom blocks via ACF Builder, ensuring semantic coherence and precise rendering control.

Each component had a reason to exist. Each script was loaded based on actual need. The HTML structure was designed to be readable, stable, and understandable, both for users and search engines.

The challenge wasn’t merely aesthetic, but structural: reduce dependencies, limit unnecessary code, and progressively eliminate accumulated technical debt.

4. A Global Redesign: Front-End, Back-End and Infrastructure

The transformation addressed the entire technical chain.

On the front-end, global JavaScript was considerably reduced, unused CSS eliminated, and the DOM simplified to avoid excessive depth. On the back-end, Bedrock and Acorn introduced clearer and more modular code organization, facilitating long-term maintainability.

Infrastructure-wise, Trellis guaranteed clean and optimized server configuration from the start. The objective wasn’t to achieve a flattering Lighthouse score, but to obtain real, stable and measurable performance under concrete usage conditions.

5. Solid and Rapid Organic Results

The effects of this modernization were visible in less than two months.

Organic traffic increased by over 110%, more than 20 keywords settled in top 3, and strategic local queries reached 1st position. The national query promoteur immobilier Suisse progressed to 6th position, demonstrating that the implemented structure was capable of sustaining competitive queries on a broader scale.

The Lighthouse performance score improved from approximately 74/100 to 97/100. The Largest Contentful Paint dropped from 3.8s to 1.3s, while the First Contentful Paint fell below 1.0s. These indicators confirm that performance wasn’t only perceived by search engines, but also by users.

These results are detailed in the complete study on real estate website SEO redesign.

6. Why This Architecture Enabled This Progress

Google doesn’t index marketing intent, it analyzes technical output. Clean HTML facilitates crawling, reduced response time improves crawl frequency, and coherent structure reinforces thematic understanding.

By modernizing the WordPress architecture, we simultaneously improved content accessibility, semantic coherence, and the site’s actual performance. SEO progress wasn’t achieved through a “hack” or isolated optimization, but through establishing a healthy and controlled technical foundation.

Conclusion

This redesign confirms an often underestimated reality: technical architecture directly influences organic visibility.

Modernizing WordPress with Roots, Acorn and Trellis isn’t simply about making a site “faster”. It’s about building a stable, scalable foundation capable of sustaining durable growth in a competitive market.

In Swiss real estate, this difference becomes decisive.

Technical performance isn’t an implementation detail; it’s an architectural decision that determines a site’s ability to rank, progress and endure. This is precisely the focus of our approach in architecture and technical modernization.

Related articles

Google Ads: Why your website performance determines profitability

Investing in Google Ads without a high-performance website costs you dearly. Discover why a slow site increases your cost-per-click and drastically reduces your advertising ROI.

Read the article

WordPress Alternatives: Which Solutions for a High-Performance, SEO-First Website?

Headless CMS, Roots and modern e-commerce: discover technical WordPress alternatives for high-performance websites with optimized Core Web Vitals and scalable architecture.

Read the article

Common Questions About WordPress Technical Redesigns

Considering a technical redesign of your WordPress site? Here are answers to questions our clients regularly ask us.

Contact us
Why modernize WordPress rather than switch CMS?
WordPress represents an investment in content and knowledge that would be costly to abandon. Modernizing the architecture with the Roots ecosystem (Bedrock, Sage, Trellis) achieves performance comparable to headless solutions while maintaining WordPress flexibility and ecosystem. This approach transforms WordPress into a modern, controlled and scalable infrastructure without requiring a complete migration.
How long does it take to see SEO results after a technical redesign?
Initial effects can be observed within a few weeks after launch for Core Web Vitals. Organic SEO results typically start manifesting between 4 and 8 weeks. In this specific case, we observed +110% organic traffic and 20+ keywords in top 3 in just 2 months. Speed depends on domain authority, existing content quality and sector competitiveness.
Is the Roots ecosystem suitable for all WordPress projects?
Roots is particularly suited for corporate sites, e-commerce and projects requiring performance and scalability. It requires modern development skills (Composer, Git workflow, command line). For simple sites managed by non-developers, a traditional WordPress approach may suffice. Roots targets technical teams or agencies seeking professional and maintainable architecture.
ACF Builder vs classic ACF: what difference for SEO?
ACF Builder allows defining fields and blocks via PHP code rather than through the admin interface. This approach guarantees complete Git versioning, consistency across environments and total control over HTML rendering. For SEO, this translates to controlled semantic structure, clean HTML without superfluous tags and optimal performance. Conditional code also allows loading scripts only when necessary.
How can Gutenberg be performant without a page builder?
Native Gutenberg, well-structured with custom ACF blocks, generates much lighter HTML than commercial page builders. The absence of heavy JavaScript, excessive inline CSS and redundant markup drastically improves Core Web Vitals. Custom blocks provide total control over rendering, eliminating all unnecessary code. This technical mastery guarantees performance, not the tool itself.
What are the SEO risks of a technical redesign?
Main risks include: loss of positions if URLs change without proper redirections, unintentional modification of HTML structure affecting crawl, Core Web Vitals regression during migration, and temporary loss of indexation. A well-planned redesign anticipates these risks with a 301 redirect plan, performance monitoring, progressive deployment and post-launch monitoring via Search Console.