A site should not be remade because it has been three or five years. Age alone is not a diagnosis. A dated but clear, fast and easy to manage project can still be valid; a published recently can already hinder customers and teams.
The correct decision arises from concrete signals.
1. The activity has changed
Services, public and positioning evolve. If the site still tells the company of years ago, it generates wrong expectations and little relevant requests.
Check if pages and navigation reflect current priorities, not only if logo and colors are updated.
2. People don’t understand what you offer
Open the homepage and try to respond in five seconds:
- who are you;
- what you offer;
- to whom;
- because to consider you;
- what to do next.
If you need generic paragraphs before you understand, the problem is of message and structure.
3. From smartphone it is difficult to use the site
Head menus, texts, forms, buttons, tables and images on real devices. A technically responsive site can have too small elements or uncomfortable paths.
If the majority of visits come from mobile, these problems affect the contacts directly.
4. The pages are slow
Heavy images, scripts, plugins and hosting can slow down. Before remaking everything measure and identify the cause.
In some cases, optimization and cleaning are sufficient. In others technology makes every temporary improvement and a new base becomes more sustainable.
5. Update content is risky
Does the team avoid changes because they fear breaking layouts or functions? The information remains old because every intervention requires a developer?
Management must be proportional to the actual frequency of updates. It does not need a complex system if it changes little, but there must be a reliable process.
6. Few incorrect requests or requests arrive
A decline of contacts does not always depend on the site. It could be traffic, seasonality or offer. Analyze sources, pages and conversions.
If people arrive but do not contact, check clarity, evidence, CTA, form and consistency between search and page.
7. You can’t measure what works
Analytics and conversions must distinguish at least forms, calls, WhatsApp and main actions in compliance with consent.
Without data, every restyling is likely to rely only on aesthetic preferences.
8. The SEO structure is confused
Duplicate URLs, overlapping content, no destination pages and multiple redirects limit control.
Before migration export pages, Search Console data, backlink and traffic. Each useful URL must have an equivalent destination.
9. The site does not show up-to-date evidence
Projects, reviews, people and certifications can be changed. An old portfolio section communicates inactivity even when the company works well.
Predict a sustainable way to update the evidence without redesigning the page every time.
10. Technology is no longer supported
Abandoned plugins, outdated versions and non-updated dependencies increase risk and costs.
Ask for technical verification: sometimes it is possible to update, other times the path is more risky than a controlled reconstruction.
11. Every new function costs too much
If adding a form or page requires temporary solutions, the technical debt is affecting the business.
Compare the cost of the next interventions with that of a new base. Consider also internal time and risk of errors.
12. The site is not consistent with other channels
Campaigns, social media and Google card can promise one thing while the site shows another. This discontinuity reduces confidence.
The site must be the stable point where it offers, tests and contacts are confirmed.
Update or remake?
It should update when architecture and technology are healthy and the problem is about content or individual sections.
It is better to remake when more problems are connected: wrong structure, fragile technology, weak mobile, difficult to correct content and unordered SEO.
An assessment should compare:
- cost;
- time;
- risk;
- possibility of migration;
- future management;
- impact on customers.
How to prepare remaking
Before starting:
- Export all URLs.
- Locate traffic and backlink pages.
- Define goals and public.
- Draw the new structure.
- Collect content and evidence.
- Prepare redirect.
- Configure measurement.
- Head before publication.
- Monitor errors and indexing.
You can start with thefree check-up of the siteor see the E-ROE approach tocustom store sites.
