Redesigning your company website in 2026: costs, timelines and how not to lose your rankings

The signs it's time to redo your website

There's no rule that says "redo your website every X years". There are concrete signs that indicate the current website is costing more than it's worth — and that delaying has a real cost.

The website doesn't generate leads

A company website that doesn't generate business inquiries isn't doing its job. If there's organic traffic but conversions are close to zero, the problem lies in the page structure, the copy, or a contact form that isn't working properly. If there's no traffic, the problem runs deeper — wrong SEO structure, inadequate speed, or unoptimized content.

Before deciding to redo everything, check with Google Analytics 4 how many sessions reach the website each month and how many complete an action — filling out a form, clicking on email or phone, visiting the contact page. If the conversion rate is below 0.5% on qualified organic traffic, the website has a structural problem.

The website is slow on mobile

Google uses mobile-first indexing — it evaluates the website's mobile version to determine ranking. A website that takes more than 3 seconds to load on mobile loses positions in organic search compared to faster competitors. Check your website on PageSpeed Insights: if the mobile score is below 50, the problem is structural and hardly solvable with superficial optimizations.

Time to First Byte — the time it takes the server to respond to the first request — is the most important indicator. If it exceeds 600ms, the problem can't be solved with a caching plugin: it lies in the system's architecture.

The design is dated and communicates little

A website stuck in 2018 with small fonts, a layout not optimized for mobile, and generic stock images communicates neglect before the visitor even reads a single line of text. In B2B, the website is often the first point of contact with a potential customer — a negative impression in the first 3 seconds is hard to recover from.

Day-to-day management has become dependence on the agency

If updating a text, publishing an article, or changing a schedule requires contacting the agency and waiting — and paying — every time, the chosen CMS wasn't suited to operational needs. This isn't a usage problem: it's a problem with the solution's architecture.

Updates keep breaking something

If every WordPress update breaks a plugin, every month requires technical intervention, and the website has been left on an outdated version because the last update caused problems — this is the clearest sign that the current architecture doesn't scale. The problem isn't solved by optimizing: it's solved by changing approach.

The website has recurring security issues

Unauthorized access attempts, contact forms used for spam, Google warnings about suspicious content, or — in the worst case — an actual breach: these are all signs that the current website's security measures aren't adequate. Adding security plugins on top of a structurally vulnerable system doesn't solve the problem at its root.

When redoing everything isn't worth it

Redoing the website isn't always the right answer. In some cases, a targeted intervention solves the problem at less cost and less risk.

If the website has good organic traffic and good rankings on important keywords, a complete redesign without rigorous SEO planning can destroy years of work in a few weeks. In this case, it's worth considering a conservative redesign — same CMS, same URL structure, improved content — before moving to a different platform.

If the problem is only the design but the technical structure is solid, a graphic restyling without changing platform may be enough. If the problem is only speed, a targeted technical optimization — better hosting, caching configuration, image optimization — can deliver results without a complete overhaul.

The right question is: can the problem be solved with a surgical intervention, or does it require a change of architecture? The answer determines whether it's worth redoing or optimizing.

How not to lose rankings during the redesign

Redesigning a website is one of the riskiest moments for Google rankings. An incorrect implementation can destroy in weeks a ranking built over years. The rules for protecting ranking during the process are few but non-negotiable.

Map all URLs before starting

Before touching anything, do a full scan of the current website with Screaming Frog or an equivalent tool. The resulting file is the map of all public URLs — pages, articles, images, PDFs. Cross-reference it with Google Search Console data to identify which URLs have significant organic traffic and rankings.

These URLs are the website's SEO asset. They can't be abandoned without redirects.

Implement 301 redirects for every URL that changes

If a URL changes structure on the new website — from the old to the new-url — a 301 redirect must exist that transfers traffic and authority from the old to the new destination. A 301 redirect tells Google: "this content has permanently moved here". Without a redirect, Google interprets the missing URL as a deleted page and the ranking is lost.

The rule has no exceptions: every URL with organic traffic must have a redirect. Even a single forgotten URL can cause a visible drop in the weeks following the go-live.

Preserve the SEO metadata of every page

The title tag and meta description of each page represent the optimization work done over time. They must be transferred in full to the new site — not rewritten without analysis, not left to the new theme's defaults.

If the old site uses Yoast or RankMath, the metadata is stored in the WordPress database in specific tables. It must be exported before migration — the standard WordPress XML export often doesn't include it correctly.

Test the new site in staging before going live

The new site must be fully built and tested in a staging environment — separate from the live site — before any DNS change. The current site remains online and operational throughout this phase. The go-live only happens once all redirects are mapped and tested, all metadata is configured, and speed has been verified with PageSpeed Insights.

Actively monitor during the first 4 weeks

In the first weeks after go-live, Google is recrawling the site and updating its index. Monitor Google Search Console daily for 404 errors, sudden drops in impressions, and pages dropping out of the index. A problem identified at this stage can be fixed quickly — an ignored problem can become entrenched and take months to recover from.

What to absolutely preserve from the old site

When redoing a site, there's a temptation to start from scratch — new content, new structure, new URLs. This is often a costly mistake.

URLs that have organic traffic and rankings must be preserved where possible — same structure, same slug. If the new architecture prevents this, they must be redirected with a 301. They can't simply disappear.

Content on key pages — product or service page copy, company descriptions, blog articles with traffic — must be migrated and improved, not deleted. Google evaluates the depth and quality of content: deleting pages with existing content impoverishes the site in the eyes of crawlers.

Backlinks pointing to specific URLs on the old site are automatically preserved if the URLs remain unchanged, or carried over through 301 redirects. Backlinks are one of the most important ranking factors — losing them means losing authority that took years to build.

The mistakes that destroy rankings

Changing all URLs without redirects

This is the most common and most devastating mistake. A new site with a completely different URL structure — without a redirect map — appears to Google as a brand new site. All the rankings built by the old site disappear. Recovery takes months, often more than a year.

Putting the new site online with noindex active

During staging development, the site is often configured with a noindex tag to prevent Google from indexing an incomplete version. The problem is when this configuration remains active after go-live. Google stops indexing all the site's pages — organic traffic drops to zero. This must be explicitly checked before every go-live.

Not updating Google Search Console

After go-live, the new site's XML sitemap must be submitted to Google Search Console. If the domain has changed or there have been significant changes to the structure, Google must be actively notified — it doesn't wait to discover the changes on its own.

Deleting pages with traffic without redirects

Pages that are removed in the new site — reorganized categories, discontinued products, outdated articles — must receive a redirect to the most relevant available page. A page deleted without a redirect becomes a 404 error — lost traffic and scattered authority.

Redoing with WordPress or switching platform

When deciding to redo the site, one of the most important questions is whether to keep the same platform or switch. This is a decision with consequences on long-term cost, not just initial cost.

Keeping WordPress makes sense if the old site's problem was the implementation — a poorly configured theme, too many conflicting plugins, inadequate hosting — and not the underlying architecture. In this case, a redesign on well-configured WordPress can solve the problems without the risk of migration.

Switching platform makes sense when the problems are structural: security that requires constant attention, performance that degrades with complexity, maintenance costs that grow every year, dependency on plugins that breaks with every update. In these cases, redoing the site on WordPress means reproducing the same problems with a graphically more modern site.

A managed proprietary CMS solves these problems at the root — not by adding layers of optimization on top of a system that tends toward complexity, but by starting from an architecture designed for stability. The initial cost may be higher, but the total cost of ownership over 3 years is often equivalent or lower. The detailed technical comparison between WordPress and KeideaCMS is available here.

How to manage the process correctly

A properly managed site redesign follows a defined process with sequential phases — not a series of decisions made as problems arise.

The first phase is the analysis of the existing site: URL scanning, organic traffic analysis per page, identification of the keywords the site ranks for, content audit to understand what's worth preserving and what needs rewriting. This phase takes time, but it's the one that protects rankings.

The second phase is the design of the new structure: information architecture, page hierarchy, URL structure, redirect plan. Before writing a single line of code or creating a layout, the structure must be defined and validated against SEO requirements.

The third phase is development in staging: building the new site, migrating content, configuring redirects, speed testing. The current site remains online throughout this entire phase.

The fourth phase is pre-go-live testing: systematic verification of every redirect, every high-traffic page with correct metadata, speed with PageSpeed Insights, form functionality, Analytics tracking. This phase cannot be shortened.

The fifth phase is go-live and monitoring: DNS switch, sitemap submission to Search Console, active monitoring for at least 4 weeks.

If you've decided to start from scratch, rely on someone who manages the entire process: from building the corporate website to hosting, security and maintenance, all included in a transparent subscription fee.

How much does it cost to redo a corporate website

The cost of a redesign varies depending on the complexity of the current site, the amount of content to migrate, and the platform chosen. An approximate estimate for the Italian market in 2026.

A redesign of a standard corporate site — homepage, 5-10 service or product pages, blog, contact form — ranges between 4,000 and 10,000 euros. The main variable isn't the number of pages but the complexity of the SEO migration: how many URLs need to be mapped and redirected, how much metadata needs to be transferred, how much organic traffic is at risk.

A redesign with a platform change — from WordPress to a different CMS — requires an additional investment for migration planning, redirect testing and post-go-live monitoring. This extra cost is recovered in the following months through reduced maintenance costs.

The cost nobody calculates in advance is the traffic drop after a redesign if the SEO migration is handled poorly. A site with 1,000 organic visits per month that loses 50% of its traffic for 6 months due to a poorly managed migration loses the equivalent of 3,000 visits — which for a B2B site with a high average deal value can represent significant business opportunities.

Investing in the SEO planning of the redesign isn't an additional cost — it's insurance on the organic equity the old site has built up over time.

If you want to understand concretely what redesigning your site would involve — analysis of current traffic, SEO risks, cost and time estimates — you can request a free audit.

Request a Free Audit of Your Site →