Updated October 10, 2026.
Is your website making it harder for customers to understand your business, contact you or complete a task?
That's a better starting question than how old the site is. A well-maintained older website may still do its job. A new website can have broken forms, unclear content or serious access problems. Check the actual experience before deciding what to fix or replace.
Websites need maintenance, not an expiration date
The useful checks are practical: can visitors read your content on a phone, reach the right page, trust the information and finish what they came to do?
Google uses the mobile version of a site's content for indexing and ranking. Keep important service information available on mobile as well as desktop. Google's mobile-first guidance
Core Web Vitals also matter, but a good performance score doesn't guarantee high rankings. Google recommends looking at the overall page experience rather than chasing a perfect score in isolation. Google's page-experience guidance
Five warning signs worth checking
1. Important pages are slow or difficult to use
Run your homepage and an important service page through PageSpeed Insights. Keep the URLs, test date and device setting with the results.
Separate real-user data from the simulated lab test. PageSpeed Insights provides both when data is available; a smaller site may not have enough real-user data for a field report. Use the lab findings to investigate, rather than treating one score as a prediction of lost sales. About PageSpeed Insights
Then try the page yourself. Does the main content appear promptly? Can you tap a button without the layout jumping? Does a form respond when you use it?
2. The mobile experience gets in the way
Pull up the site on your phone. Is text readable without zooming? Are buttons easy to tap? Does the navigation work? Can you finish the contact form without fighting the keyboard or a popup?
Compare the mobile and desktop versions. A service description, price qualification or contact option shouldn't disappear just because the screen is smaller.
3. Customers and search tools can't find clear information
Make sure a visitor can tell what you do, where you work, who the service is for and how to contact you. Replace outdated hours, broken links and vague claims with accurate information.
If a public page isn't appearing in search, inspect its indexing and access controls. A missing mention in one AI answer doesn't prove the business is invisible or that the website needs rebuilding.
4. Keeping the content accurate is unnecessarily difficult
Can the person responsible for the site correct an opening time, update a service or remove an expired offer? If routine changes regularly get delayed, improve the publishing process or tools.
Working with a developer isn't itself a problem. The question is whether somebody has a clear, reliable way to maintain the information customers depend on. Changing a date without improving the content is not a meaningful update.
5. You don't know whether the contact path works
Test the form, phone link and booking route with an approved test submission. Check that the right person receives it and that the visitor sees an accurate confirmation.
Then distinguish visitors, inquiries, qualified leads and customers in your records. A low lead count can reflect traffic, demand, targeting, the offer or a broken journey. It doesn't establish a website defect on its own, and there is no useful universal quota of leads every site should generate each week.
Measure the cost of a problem before promising a return
A broken contact form can interrupt an inquiry. An inaccurate service page can create confusion. Those are concrete issues to investigate, rather than reasons to assume every older website is losing a fixed amount of revenue.
Start with a baseline for one important journey: relevant visits, completed inquiries, qualified leads and any customers that can be reliably connected to those inquiries. Note the measurement period and changes in advertising or the offer.
Here is a hypothetical example, using invented numbers:
- 1,000 measured visits and 20 completed inquiries gives an inquiry rate of 2%.
- In a later period, 1,000 measured visits and 30 inquiries gives a rate of 3%.
- The difference is 10 inquiries and one percentage point. It is not proof of 10 extra customers or a particular amount of profit.
Check traffic quality, seasonality, tracking changes and other explanations before attributing the difference to a redesign. Include build costs, maintenance and staff time when evaluating whether a change was worthwhile. This example is not an EAC client result or a forecast.
Check AI search visibility without the scare claims
AI-powered search is another place to check whether your public information is accessible and accurate. It doesn't make ordinary SEO irrelevant.
Google's current guidance applies SEO fundamentals to its generative AI features. It emphasizes useful, original content and says special AI schema isn't required. Eligibility also depends on indexing, snippet eligibility and the site's effective Search generative AI inclusion setting in Search Console. Meeting the conditions doesn't guarantee appearance. Google's current AI optimization guide
Use structured data when it accurately describes the page. Don't assume that missing markup makes readable text incomprehensible to AI, or that adding it guarantees a recommendation.
Our practical AI search visibility guide explains crawler checks, Google's inclusion control and a repeatable way to record what you observe.
What to expect from a well-maintained website
- Performance: assess loading, responsiveness and layout stability. Current good Core Web Vitals thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, evaluated at the 75th percentile. These are specific metrics, not a promise that every page fully loads within a fixed time. Web Vitals guidance
- Mobile: readable content, usable navigation and working forms across relevant screen sizes.
- Connection security: HTTPS without certificate warnings. HTTPS alone doesn't establish that the entire application is secure.
- Accessibility: check keyboard use, text alternatives, contrast and form labels. W3C's Easy Checks are a starting point, not a complete accessibility evaluation or a legal-compliance determination.
- Content: accurate service details, useful examples and clear next steps.
- Measurement: reliable tracking of the actions you actually care about, with appropriate privacy choices.
- Maintenance: named responsibility for updates, backups, recovery and fixing broken journeys.
Your path forward: repair or rebuild
Option 1: Make targeted improvements
If the foundation works, fix the specific problems: simplify a form, improve images and scripts, correct content or repair navigation. Record the change and repeat the checks. A focused repair can be the right choice for an older site too.
Option 2: Rebuild when the constraints justify it
Consider a rebuild when the existing system makes essential changes impractical, cannot support the required workflow or creates maintenance problems that smaller repairs won't address.
Before committing, define what the new site must do, which URLs and content should be preserved, how forms and integrations will be tested, who will maintain it and what it will cost. Compare that plan with the cost of targeted repairs. Don't assume a fixed payback period.
If you'd like help deciding which route fits your site, let's talk about your website. Start with the problems you can demonstrate and the outcomes you need.




