A redesign should improve the website without discarding the parts that already work. The safest process begins with an inventory of routes, content, search visibility, analytics, forms, integrations, and assets before a new layout is approved.
Before design starts
Write down what the current site does and where it fails. Review analytics, Search Console, customer questions, form quality, mobile behavior, speed, and maintenance problems. Record every public URL and identify which pages receive traffic or links.
Define the redesign around a small set of outcomes. Examples include making the offer easier to understand, presenting project proof better, improving qualified inquiries, supporting a new service, or reducing maintenance effort. "Make it modern" is not specific enough to guide tradeoffs.
Content and information architecture
- Keep accurate service, project, legal, and contact information.
- Remove or merge pages only when there is a clear replacement.
- Give each retained page one primary intent and a clear H1.
- Map old URLs to new URLs before development ends.
- Plan navigation from the visitor's questions, not the internal org chart.
- Confirm who owns copy, images, approvals, and future updates.
The Higgins Digital rebuild keeps retired route mappings in application configuration and tests them during releases. That prevents an old indexed URL from quietly becoming a 404 or a chain of redirects.
Design and build checks
The new visual system should work from 320px mobile through large desktop, with visible focus states, readable contrast, semantic controls, reduced-motion behavior, and no horizontal overflow. Images need reserved dimensions and useful alt text. Essential content and links should exist in server-rendered HTML rather than appearing only after interaction.
Preserve what makes the brand recognizable. A redesign can simplify a heavy animation, improve its loading strategy, or remove a distracting effect without flattening the entire site into a generic template.
Search and analytics migration
Before launch, verify:
- one preferred canonical host;
- self-referencing canonicals on indexable pages;
- unique titles and descriptions;
- a sitemap containing only final 200 routes;
- robots rules that do not block public content;
- specific permanent redirects for replaced URLs;
- valid Organization, Service, Article, and Breadcrumb schema where truthful;
- analytics events for the actions the business actually values;
- no accidental
noindexleft from staging.
Launch and follow-up
Run the production build and browser tests before deployment. After launch, fetch the final URLs independently, test redirects without relying on browser cache, submit the sitemap through authenticated webmaster tools, and watch errors and conversions. A launch is the start of measurement, not the end of the redesign.
See the Higgins Building Group case study for a real redesign example, or review Higgins Digital's Charlotte website redesign service. The website planning guide is useful if the project is still at the scoping stage.