A useful business website should make life easier for its visitors and its owner. This guide from 507 Web Pros looks at practical choices, common mistakes, and a sensible way to decide what to do next.
Do not confuse a broken website with an outdated design
A site that feels frustrating may need a repair rather than a redesign. Broken forms, stale plugins, slow-loading images, and navigation errors are maintenance or technical problems. An unclear offer, confusing information architecture, weak mobile layouts, and an unsuitable visual direction may justify a redesign. Some sites have both kinds of problems.
The distinction matters because a redesign can introduce new risks and expenses without curing an underlying hosting or configuration issue. Conversely, repeated small fixes cannot always rescue a site whose structure no longer supports the business.
What routine maintenance should handle
Maintenance includes updating supported software, checking backups, testing critical forms, reviewing broken links, keeping business information current, and watching for security or performance problems. The exact checklist depends on the platform and features in use.
A form that silently stops sending messages needs diagnosis. A broken image path needs correction. An out-of-date phone number needs a content edit. None of those issues automatically requires replacing the entire layout. Keep a record of recurring failures so the team can spot patterns rather than treating each incident as isolated.
When focused repairs are the better investment
Choose targeted work when the site generally serves customers well but specific elements fail. Examples include a mobile dropdown that will not open, pages that scroll sideways, an oversized hero image, or conflicting headings added by a template. Fix the cause and retest the affected pages instead of rebuilding content unrelated to the defect.
A controlled repair should include a backup or rollback method, a description of what changed, and checks on desktop and mobile. If a sitewide theme adjustment is required, sample multiple page types because one change can affect templates in unexpected ways.
Signs a redesign may be justified
Consider a redesign when the business has changed its services or audience, the navigation no longer represents what it offers, key pages are difficult to understand, or the current layout cannot accommodate essential workflows. A new brand identity can also make selective or full design updates worthwhile.
A redesign case is strongest when you can name the visitor problem. ‘It looks old’ is less actionable than ‘customers cannot find our service details on a phone.’ Describe the problem before deciding how much of the site should change.
Build a decision matrix before spending
List the current problems, the people affected, their severity, the likely cause, and the cost of leaving them unresolved. Separate visual preferences from functional defects. Then classify each item as content correction, maintenance, targeted development, or structural redesign.
For a site with functional booking and clear navigation, a design refresh might be enough. For a company that now sells online but has a brochure-only website, an architectural rebuild may be appropriate. This is not a decision that can be made from a screenshot alone.
Protect existing pages and search visibility
Before a redesign, inventory page URLs, titles, major content, internal links, images, and existing forms. Identify pages that bring useful inquiries and preserve relevant content rather than replacing it indiscriminately. Map URLs that genuinely must change to appropriate new destinations and use permanent redirects where suitable.
Do not redirect every removed URL to the homepage without considering its meaning. Review canonical tags, XML sitemaps, robots instructions, and structured data after the move. A redesign is also a content migration and quality-assurance project.
How to evaluate proposals
Ask whether the scope includes mobile testing, content migration, accessibility, form testing, technical SEO, backup/restore preparation, and post-launch support. Find out what is excluded and who owns the content and assets. A low estimate that omits these tasks may not represent the full cost.
For maintenance proposals, ask how updates are tested, how failures are escalated, and how recovery works. For redesign proposals, ask for the proposed structure and how important existing URLs will be handled.
A sensible next step
Audit the site first and group issues into urgent functionality, recurring upkeep, and experience improvements. Fix outages and broken lead paths promptly. If the remaining issues are structural, define redesign goals and measurable acceptance criteria before production begins.
Keeping the scope honest prevents a simple repair from turning into an unnecessary rebuild. For background on 507 Web Pros, see the About page.