A company should redesign its website when the existing structure, technology, content, credibility, or conversion system materially limits the business. Aesthetic age alone is not a sufficient reason. The project should begin with a documented business problem and a baseline for measuring improvement.
A redesign is a migration, not a graphic project
The website contains search equity, links, content relationships, analytics history, conversion paths, forms, integrations, and operational knowledge. Rebuilding without a migration plan can damage visibility and lead flow even when the new design looks better.
Messaging and architecture should precede visual design
Design cannot solve an unclear offer or disorganized service model. The company should define audiences, problems, offers, proof, page hierarchy, and conversion paths before page templates are finalized.
Not every website problem requires a rebuild
Focused changes may correct weak calls to action, outdated copy, slow pages, technical errors, or missing proof. A full redesign becomes more reasonable when the underlying templates, content model, navigation, or platform prevent systematic improvement.
The launch needs a measurement plan
Success should be evaluated using baseline and post-launch data for qualified traffic, visibility, conversion, page engagement, form performance, inquiry quality, and publishing efficiency. A redesign that cannot be measured becomes a subjective debate.
-
- Business alignment: Does the site reflect current strategy, markets, and offers?
- Buyer clarity: Can visitors understand fit, value, differentiation, and next steps?
- Discoverability: Can important pages be crawled, indexed, and found?
- Conversion: Do qualified visitors progress?
- Credibility: Does the site provide current proof and trustworthy information?
- Technology: Can the team publish, integrate, secure, and maintain the site?
- Migration risk: Are high-value URLs, links, content, and tracking protected?
- Measurement: Is there a baseline and post-launch evaluation plan?
Example: what this looks like in practice
A manufacturer may request a redesign because the site looks old. Discovery reveals a larger problem: product information is organized by internal divisions, distributors and end users need different paths, high-value technical pages are difficult to find, and every update requires a developer. The project should therefore address information architecture, audience journeys, content governance, search migration, and publishing workflows, not only appearance.
Complete article
A dated appearance can be a reason to review a website.
It should not be the only reason to rebuild one.
A website redesign requires time, money, decisions, content, technical work, and organizational attention. Before beginning, a company should identify the business problem the new website is expected to solve.
The website no longer reflects the company
Companies change faster than their websites.
Services are added. Markets shift. Buyers change. Positioning becomes outdated. New expertise is developed. Acquisitions or leadership changes alter the organization.
A redesign may be justified when the website describes a company that no longer exists.
The project should begin with current strategy and messaging. Starting with colors, layouts, or page templates can reproduce the old problems in a newer design.
Buyers cannot understand the offer
A website should help visitors answer basic questions…
-
- What does this company do?
- Who is it for?
- What problem does it solve?
- How is the offering different?
- What should I do next?
A redesign may be appropriate when the information structure prevents those answers from becoming clear.
The solution may involve new navigation, clearer service architecture, stronger page hierarchy, or a different way of organizing content around buyer problems.
Qualified traffic does not convert
A company receiving relevant traffic but few inquiries should investigate the conversion path.
The issue could involve weak calls to action, unclear offers, missing proof, difficult forms, poor mobile usability, slow pages, confusing navigation, or inadequate information.
Some of these problems can be corrected without rebuilding the whole site.
A redesign becomes more reasonable when conversion problems exist across the site and the current structure limits improvement.
The company cannot publish or update content efficiently
A website can become an operational constraint.
Employees may depend on a developer for routine changes. Page templates may be inflexible. Content may be difficult to organize. Integrations may fail. The system may no longer receive proper updates or support.
A redesign can create a more manageable publishing process.
The project should still define governance. Who can publish? Who reviews content? Which templates are available? How are old pages updated or removed?
A new content system does not automatically create a good content operation.
The website is difficult to find
Search performance can suffer when the site has weak architecture, thin content, technical errors, duplicated pages, poor internal linking, or pages that do not match buyer questions.
A redesign can improve those conditions.
It can also damage existing visibility when redirects, page content, metadata, internal links, and high-performing URLs are handled carelessly.
Search and AI discoverability should be part of the redesign from the beginning. They should not be added after the design has been approved.
The site creates credibility concerns
Buyers may question a company when the website looks neglected, contains broken pages, provides outdated information, performs poorly on mobile devices, or lacks basic trust information.
Credibility problems are especially serious when the company sells expertise, technology, financial services, healthcare services, or another offering that depends on trust.
A redesign should address both appearance and substance.
Professional design cannot compensate for vague messaging, weak proof, or incomplete information.
The website cannot support current marketing
Campaigns often require focused landing pages, audience-specific content, tracking, forms, integrations, experiments, and rapid updates.
A website may become a barrier when every campaign requires custom development or the available templates cannot support the offer.
The redesign should account for the marketing work the company expects to do over the next several years.
What should happen before the redesign?
Begin with an assessment.
Review the current site’s traffic, rankings, conversions, content, technical condition, user paths, forms, integrations, and high-performing pages.
Interview sales, marketing, leadership, customer service, and other teams that hear buyer questions.
Clarify the new positioning, audiences, offers, page requirements, conversion actions, and measurement plan.
Then determine whether the company needs a full rebuild, a structured redesign, or focused improvements to the current site.
What makes a redesign successful?
A successful redesign makes the business easier to find, understand, trust, and contact.
It also gives the internal team a practical system for publishing, testing, measuring, and improving the website after launch.
The launch is one stage.
The site should continue changing as the company learns which messages, offers, pages, and conversion paths work.
Macon Raine approaches website redesign through strategy, discoverability, conversion, content, data, and ongoing iteration. The objective is to create a business asset that can be measured and improved.
Frequently asked questions
How often should a website be redesigned?
There is no responsible universal schedule. Redesign when business, buyer, technical, or performance conditions justify it. Continuous improvement can extend the useful life of a strong site.
What should be measured before launch?
Record traffic and conversion by page and source, rankings, indexed pages, backlinks, form performance, inquiry quality, page speed, mobile behavior, and the time required to publish or update content.
Can a redesign hurt SEO?
Yes. Visibility can decline when URLs, redirects, internal links, metadata, content, canonicals, or technical settings are mishandled. Search migration should be planned before launch.
