A dated-looking website is not a diagnosis
Open with a hypothetical Canadian service business that has changed its services, service area, estimate process and visual identity, while its website still describes the older version of the company. Customers reach outdated pages, ask unsuitable questions or leave without enquiring.
Explain the consequence: a visual refresh may leave the real problem untouched, while repeated small fixes can become wasteful when customer paths, content and technical constraints all need to change together. The sensible decision is based on evidence, not appearance or an arbitrary website age.
Digital Transformation: A Practical Guide for Entrepreneurs - Innovation Canada
Four possible scopes of work
Define repair as a contained correction, such as fixing inaccurate information, improving one weak service page or resolving a confusing contact path. Define restructure as reorganizing existing content, navigation, homepage priorities or brand application while retaining a workable foundation.
Define rebuild as creating a new website foundation because the customer journey, information structure, technical limitations and business needs cannot be sensibly separated. Define investigate first as the appropriate option when the business cannot confirm essential account access, provider responsibilities or how customer information is handled.
Clarify that these are planning categories rather than promises about cost, timing, rankings or enquiry volume. A rebuild is one possible conclusion, not the default recommendation.
Security considerations for your website (ITSM.60.005) - Canadian Centre for Cyber Security
Test 1: Has the business changed more than the website can explain?
Ask whether valuable services, ideal customers, service areas, customer requirements or buying process have changed. Ask whether the site still promotes discontinued work, uses an old business name, or creates a different impression from current quotes, profiles and customer communications.
Explain that a content and structure project can be enough when the website can accommodate the current business cleanly. A rebuild becomes more plausible when needed changes affect nearly every important page and path, and the current structure prevents a clear explanation.
Digital Transformation: A Practical Guide for Entrepreneurs - Innovation Canada
Test 2: Can a suitable customer complete the most important task?
Tell readers to choose one valuable customer task: requesting a quote, booking an assessment, finding a location, comparing a service or calling for urgent help. They should test whether a first-time visitor can find the relevant service, understand who it is for, know what happens next and complete the task on a phone.
Include accessibility as part of a responsible decision, rather than a final polish step. A quick review can reveal obvious barriers, but it cannot establish that a website is fully accessible. If a key task is difficult for customers across several parts of the site, the owner should treat that as a broader scope question rather than merely redesigning a button or form.
Easy Checks – A First Review of Web Accessibility | Web Accessibility Initiative (WAI) | W3C
Test 3: Are the problems isolated or connected?
Set out the signs that a targeted repair may be sensible: one or two clear issues, understandable navigation, current business information, and changes that can be made without disrupting unrelated customer tasks.
Contrast this with connected problems: outdated messaging repeated across important pages, navigation based on internal labels rather than customer needs, service pages and enquiry paths that need to change together, or repeated workarounds whenever the business needs to add content or explain an offer. Connected problems do not automatically require a rebuild, but they call for a coherent plan rather than disconnected fixes.
Guideline on Service and Digital - Canada.ca
Test 4: Is the current foundation controllable enough to invest in?
Use measured questions: Can a named business person access or recover the domain, hosting, website administration, forms and related accounts? Can the business identify its providers and their responsibilities? Does it know where website form submissions or uploads go? Is the underlying software supported and able to receive appropriate updates?
Avoid diagnosing any individual site from the outside. Explain that an older website is not automatically insecure or unsuitable, but missing account access, unknown technical dependencies or unsupported components should be investigated before visual improvements are prioritized. Owners should ask providers for documented answers rather than make assumptions.
Security considerations for your website (ITSM.60.005) - Canadian Centre for Cyber Security
Make a one-page repair-or-rebuild decision record
Give readers a practical checklist: identify the most important customer task; list three examples of where the website fails that task; note what has changed in the business; record unknown accounts, providers or data flows; identify the smallest likely solution; and note what evidence would show that solution is too limited.
Close with an honest decision table: contained issues suggest repair; sound foundations with unclear pages or navigation suggest restructuring; interconnected customer, content, brand and technical problems justify rebuild planning; and unknown ownership or technical facts require investigation first.
Professional help makes sense when the business needs an objective scope, must coordinate brand, content and website changes, or cannot establish whether the current foundation can safely support the work. A completed decision record gives a designer or developer a stronger starting point than simply asking for a redesign.
Digital Transformation: A Practical Guide for Entrepreneurs - Innovation Canada
Security considerations for your website (ITSM.60.005) - Canadian Centre for Cyber Security