What we review first when we redesign an existing website
An existing website holds useful decisions and possible problems. We need to separate the two. We look at the pages and routes, how visitors move through them, what content still serves a purpose, and where the design or build creates friction. If analytics or search data are available and trustworthy, they can help identify priorities. They do not replace a direct review of the site and the business goal.
We also ask what cannot change. Your brand, platform, integrations, content ownership, current campaigns, and internal approval process can affect the direction. A redesign plan should make those dependencies visible before production starts.
How the redesign decision is made
Keep what still works.
Some content, functionality, or visual elements may continue to serve the audience. We identify them so the redesign protects useful work.
Improve what is unclear or difficult.
We may change hierarchy, navigation, page copy, responsive behavior, calls to action, or interface patterns. The recommendation should name the problem each change solves.
Consolidate or retire with care.
Overlapping or outdated pages may need to be combined or removed. Before changing routes, we map important URLs and decide whether redirects or other migration work is needed. We do not assume that deleting a page is harmless just because its design is old.
Build the approved direction.
Once the scope and priorities are agreed, the design and development stages can move forward with a clearer page map, content plan, and review path. The working site still needs checks before launch.
What we need from you
We will need to understand why you want the redesign and what must improve. Access to the current site, content inventory, brand materials, technical contacts, and relevant analytics can make the assessment more accurate. Tell us about routes, forms, integrations, or campaigns that cannot be interrupted. We will specify the required access and deliverables in the project scope.
A redesign does not by itself guarantee better rankings, faster pages, more leads, or a particular business result. Those are separate goals that require a baseline, an appropriate plan, and measurement after the work is released.
What happens to the old content and URLs?
Every important page needs a disposition: keep, improve, combine, redirect, or retire. We would map the current routes before the new page structure is finalized, especially for pages that receive search visits, earn links, support campaigns, or appear in customer materials. That map helps prevent a visual redesign from accidentally breaking useful paths.
Content migration also needs an owner. Existing copy may need factual updates or a different structure. Images and testimonials may need renewed permission. Forms may have destinations and notifications that are easy to overlook. A page is not finished merely because its text has been copied into a new template. It needs to work in the new experience.
How do we check the redesigned site before launch?
We should test the tasks people rely on: finding a service, reading on a phone, sending an inquiry, navigating from a campaign, and reaching any booking or checkout step in scope. If URLs change, redirects and internal links need checks. If the platform changes, account ownership, content editing, and integration behavior need a handoff. The exact QA list belongs in the agreed scope.
After launch, compare the site against the original goals and baseline rather than declaring success because the new design looks better. A redesign is most useful when the team knows what changed, why it changed, and how the next round of improvements will be decided.
Related reading on site redesigns
Next step for site redesigns
Send us the current website and describe what is not working for you or your visitors. We can help determine whether you need a focused improvement, a broader redesign, or a different first step.
