Kodakod Team
Your website was great a few years ago; but what about today? An outdated site quietly costs you customers. Here are 7 clear signs it is time for a redesign, and the steps to move to a new site without losing your Google rankings.
In short: If your site breaks on a phone, loads slowly, looks dated, makes you wait for a developer to change small things, doesn't show up in search, gets visits but no inquiries, or runs on infrastructure that is never updated, it may be time for a redesign. If several of these signs appear together, don't postpone it. But plan the redesign properly: keep your URLs wherever possible, set up a permanent (301) redirect for every URL that changes, and monitor the move in Search Console. That way you move to the new site without losing your search visibility.
A website is modern the day it goes live; but the internet moves fast. A corporate site that drew praise a few years ago can, in a visitor's eyes, make your company look more dated than it really is. The most insidious part is that no one tells you — the customer quietly closes the site and goes to your competitor.
So how do you know when it is time for a redesign? Here are seven signs to watch for.
7 signs it is time for a redesign
- It looks bad on a phone — under mobile-first indexing, Google uses the mobile version of your site for indexing and ranking. If your site breaks on a phone, you lose both your mobile visitors and the version Google sees. Check the share of mobile visits in your analytics tool; it shows how much the problem is costing you.
- It loads slowly — speed is no longer a luxury but an expectation. According to web.dev's Core Web Vitals thresholds, a good experience means the main content (LCP) loads within 2.5 seconds, the response to interaction (INP) stays at or under 200 milliseconds and visual shifting (CLS) stays at or under 0.1.
- The design shows its age — a dated-looking site gives a “left behind” impression, even if your product is up to date.
- Updating content is torture — if you have to wait for a developer to change a small piece of text, your infrastructure is slowing you down.
- You do not show up in search engines — if the people looking for you cannot find you, the site practically does not exist; your technical SEO foundation may be outdated.
- Traffic yes, conversions no — people arrive but do not fill out a form or call, which means the flow is not carrying them toward action.
- Security and maintenance risk — infrastructure that is never updated is both a security vulnerability and a constant source of failures.
An old site may seem like it costs you nothing; in reality it quietly leaks customers every single day.
How do you measure the signs?
“I think the site looks old” is a feeling; the decision should be made with data. For each sign there is a concrete place to look:
- Mobile and speed: Open your site on your own phone, over mobile data. Then test your most important pages in PageSpeed Insights; if you have enough traffic, you'll see real-user data there too.
- Search visibility: In Search Console's performance report, check whether you appear for searches using the names of the services you offer. If people only find you by your company name, those who don't know you yet can't find you.
- Conversion: In your analytics tool, track form submissions, phone clicks and email clicks as separate events. If you're not measuring them, that's the first gap.
- Content management: Count how many of the changes you wanted over the last few months you could make yourself, and how many you had to wait on someone for.
- Security: Check whether your content management system, plugins and server software still receive security updates.
Fix it or redesign it?
Not every sign calls for a full redesign. You can use this table to make the call:
| Sign | A fix is often enough | Consider a redesign |
|---|---|---|
| Slow loading | If the problem is large images, unnecessary plugins or server settings | If the problem is the template or the infrastructure itself |
| Breaks on mobile | If it's a limited problem on a few pages | If the design was never built with mobile in mind |
| Search visibility | If titles, internal links and the sitemap can be fixed | If the platform doesn't allow basic technical SEO settings |
| Content management | If there's an admin panel but it's hard to use | If every change requires code |
| Security | If updates can still be applied | If the version you run no longer receives updates |
If you land in the right-hand column on more than one row, seriously consider a redesign instead of patching things piece by piece.
A redesign is not starting from scratch
The decision to redesign feels frightening to most people because it is imagined as “redoing everything.” Yet a good redesign preserves the value you already have and builds on top of it:
- Measure what works — use data to see your current traffic, your converting pages and your weak points.
- Carry the content, drop the clutter — content that creates value is kept; the parts that do not work are streamlined away.
- Migrate while protecting your SEO — with the right redirects, you move to the new site without losing your existing search rankings.
Redesigning without losing rankings: step by step
A new site only inherits the value the old one built up in Google if that value is moved over correctly. The steps below are based on Google's guide to site moves with URL changes.
Before launch
- Take an inventory. Collect every URL of the old site from the sitemap, server logs and your content management system. Flag the pages with the most clicks and impressions in Search Console, and the pages that bring in inquiries in your analytics.
- Keep URLs wherever possible. A page whose URL doesn't change needs no redirect. The safest redesign changes the design and leaves the URL structure as it is.
- Build a redirect map. Map every old URL that changes to its closest equivalent on the new site. Google stresses the importance of this mapping and recommends saving it so you can reuse it for both redirects and sitemaps.
- Don't send everything to the homepage. Google says not to redirect many old URLs to a single irrelevant destination, such as the new homepage. Merging several old pages into one relevant new page is fine.
- Keep the staging site closed. The new site should be tested before launch in a password-protected environment; we explained why a staging site closed only with robots.txt isn't enough in our technical SEO audit article.
Launch day
- Switch on permanent redirects. Google recommends permanent HTTP redirects such as 301 or 308 where possible. Keep chains short; an old URL should go straight to its final destination.
- Update internal links. Links on the new site should point directly to the new URLs, not to the old ones.
- Check canonical and hreflang. Each new page's canonical tag should point to itself; if your site is multilingual, the hreflang annotations should be updated to the new URLs.
- Submit sitemaps. Google recommends submitting sitemaps with both the old and the new URLs during the move, then continuing with the new sitemap as the move progresses.
After launch
- Monitor Search Console. The page indexing report, the sitemaps report and search performance show which URLs are having problems. If the domain changes, both sites need to be verified.
- Don't remove the redirects. Google recommends keeping redirects for as long as possible, generally at least one year.
- Expect fluctuation. Google says plainly that rankings may fluctuate temporarily during a move; on larger sites it can take longer to settle.
One note: the Change of Address tool in Search Console is only needed when moving from one domain or subdomain to another. You don't need it to redesign the site and its URLs on the same domain.
Common redesign mistakes
- Launching without redirects: Old URLs return 404, and inbound links and search visibility go to waste.
- Deleting valuable content in the name of “streamlining”: Removing a page that brings traffic without looking at the data removes its rankings too.
- Letting the staging site get indexed: If the new site appears in search before launch, the same content can end up competing at two addresses.
- Stopping measurement after launch: Most problems show up in Search Console in the first weeks; an error caught early is cheap to fix.
The right time is before it is too late
If a few of these signs felt familiar, a redesign has stopped being a task “for later.” Your website is your company's face in the digital world; keeping it current, fast and conversion-focused is not a cost but an investment. We explained what a good corporate site is made of in our corporate website article, and why speed matters so much in our Core Web Vitals article. At Kodakod, we first examine your existing site with data, decide together what to keep and what to renew, and move you to a modern, mobile-first corporate site without losing your SEO value.
Frequently asked questions
The clearest signs are a site that looks bad on a phone, loads slowly and has a dated design. Waiting for a developer to change a small piece of text, not showing up in search engines, getting visits but no forms or calls, and running infrastructure that is never updated and carries security risk also show it is time. If several of these signs appear together, the redesign should not be postponed.
No, a good redesign preserves the value you already have and builds on it. Content that creates value is carried over to the new site, and the parts that do not work are streamlined away. Because the pages that perform well are identified with data beforehand, the redesign focuses on fixing weak points rather than erasing what already works.
Not if it is planned correctly; the key is setting up the right redirects from old URLs to new ones. Every page whose address changes should be linked to its new equivalent with a permanent redirect, and content that creates value should be kept. A migration without redirects, on the other hand, can cost you your existing search visibility.
This usually means the site's flow is not carrying visitors toward action. Pages that break on a phone, slow loading, a dated design, or a quote and contact step that is hard to find can make visitors leave quietly. Seeing in the data which page and which step loses them shows where to start fixing.
The first step is to measure the existing site with data: current traffic, the pages that bring conversions, and the weak points. That picture determines what to keep, what to streamline and which URLs will need redirects. Kodakod also starts redesign projects by reviewing the existing site this way and decides together with the company what to keep and what to renew.
