A redesign is not automatically necessary because a website is old.
And a full rebuild is not automatically better than repairing what you already have.
The useful question is: does the current website still help people find what they need, and can your team still maintain it without constantly fighting the structure?
You can do a surprisingly useful first audit yourself.
Start with the visitor journey
Pick three common reasons someone visits the website.
For example: - a prospective student wants admissions information - a patient wants to book an appointment - a customer wants to compare services
Start from the homepage and try to complete each task.
Count how many decisions and clicks it takes.
If you regularly find yourself thinking “they need to know to click this first,” that is a warning sign. Good navigation should not depend on inside knowledge.
Check for broken links and dead ends
Go through the main navigation and important pages.
Look for: - 404 pages - old PDFs - forms that no longer work - expired event links - outdated booking systems - missing downloads - links to renamed or removed services
For a larger organization, assign different departments a small list of pages to check. This is much faster than asking one person to understand the entire site.
Make a spreadsheet with three columns: URL, problem, owner. Then work through it.
Look for too much content as well as too little
A page can fail because it does not explain enough. It can also fail because it tries to explain everything.
Watch for: - walls of text - paragraphs that run for half the page - five messages competing for attention at once - repeated explanations - giant image galleries - decorative sliders - too many banners
Try this rule: each section should have one main job.
If a hospital page contains ten paragraphs of useful information but the visitor only wants to know “Can I book an appointment here?”, make that answer easy to find first. The detailed information can still exist underneath.
Good hierarchy does not mean deleting important information. It means putting the most important answer where the visitor needs it.
Test the site on an actual phone
Do not rely only on resizing a desktop browser.
Use a real phone and test: - the menu - tables - forms - buttons - accordions - maps - downloads - long pages
Notice whether the page feels intentionally designed for the phone or merely squeezed into the screen.
If you need to pinch, zoom, scroll sideways, or carefully aim at tiny links, add those issues to your audit.
Check whether the information still matches the organization
Websites often accumulate old information quietly.
Review: - phone numbers - locations - departments - staff names - services - policies - pricing - program names - forms - old announcements
For larger organizations, give each department responsibility for confirming its own information. A central website team does not always know when a clinic, office, course, branch, or service changes.
Ask whether the architecture still fits the business
Sometimes the content is fine, but the original structure no longer matches the organization.
Maybe the business used to have one location and now has eight. Maybe the website started as a marketing site and now needs customer accounts, online payments, dashboards, document uploads, or employee tools.
Write down the capabilities the organization needs today.
Then ask: can the current platform support those cleanly, or does every new feature require another workaround?
That question helps separate a redesign from a rebuild.
When a redesign is probably enough
A redesign may be enough when: - the technology is still maintainable - the content system works - performance is acceptable - the main problem is layout, hierarchy, navigation, styling, or mobile usability - new requirements can fit the existing architecture without awkward workarounds
In that case, preserve the healthy foundation and improve the experience on top of it.
When a rebuild may be cleaner
A rebuild may make more sense when: - the platform is difficult or risky to maintain - the site is held together by many workarounds - performance problems are structural - the content model no longer fits the organization - major new workflows cannot be added cleanly - the mobile experience would require rebuilding most layouts anyway - nobody understands how parts of the old system work anymore
The decision should be based on long-term maintainability, not excitement about new technology.
Improve the information architecture before improving the styling
Before choosing a new color palette, sketch the site structure.
List the main audiences and what each one needs.
For example, a college may have: - prospective students - current students - parents - faculty - staff - partners
Each audience may need different paths through the same website.
Design those paths first. Styling comes after the structure makes sense.
Create a content budget for each page
This is a useful way to control both too many pictures and too much text.
For each page, decide: - the one main purpose - the one primary action - the three to five most important pieces of information - which images actually help explain or build trust - what detailed information can move lower on the page or into a separate page
This keeps pages from becoming storage rooms for everything a department wants to publish.
Do a five-person usability test
You do not need an expensive research project to find obvious navigation problems.
Ask five people who did not build the site to complete a few common tasks.
Examples: - Find the admissions requirements. - Book an appointment. - Find the nearest branch. - Download the correct form.
Watch where they hesitate. Do not tell them where to click.
Patterns will appear quickly.
Build a prioritized repair list
After the audit, group issues into: - broken - confusing - outdated - slow - difficult on mobile - difficult to maintain - missing capability
Then rank each item by impact and effort.
Fix high-impact, low-effort problems first. That may improve the site enough that a rebuild is unnecessary.
If most high-impact problems come from the underlying architecture, you now have evidence that a rebuild may be worth considering.
A practical do-it-yourself audit
Before deciding on a redesign or rebuild: - test the three most important visitor journeys - check every important link - remove or reorganize walls of text - remove images that do not help the visitor - test the site on real phones - ask departments to verify their own information - list new capabilities the organization now needs - map the main audiences and their paths - ask five people to complete common tasks - rank problems by impact and effort
The goal is not to rebuild for the sake of rebuilding. It is to make sure the website still fits the organization it is supposed to serve.
Our approach
Want a second set of eyes on whether your current site needs repair, redesign, or a clean rebuild?
We approach redesigns the same way this guide does: audit first, preserve what still works, and rebuild only when the structure is holding the organization back. If you want someone to examine the site and work through the decision like an extension of your own team, we would love to help.
Talk with EZDigital