Start with a decision, not a visual style
A redesign is easier to evaluate when you know what should improve. Write down the primary audience and the action that matters: requesting a quote, understanding a service, buying a product or finding support. Separate business goals from design preferences. “Make it modern” is a direction; “make the service and inquiry route easier to understand on a phone” is a task you can test.
Audit what already exists
List current pages, important downloads, contact forms and external integrations. Mark which pages should stay, merge or retire. Identify content you have permission to reuse and claims that need evidence. Preserve useful existing information rather than removing it because it does not fit a new template. Keep a copy of the old URL list before making structural changes.
Sketch the mobile journey first
Try the real journey on a narrow screen: open the menu, choose a service, read its scope and reach the contact option. Use descriptive labels and visible focus states. Check whether long headings wrap, whether form labels remain readable and whether fixed elements cover buttons. A beautiful first screen does not compensate for an unclear next step.
Prepare content alongside the layout
Write the core message, deliverables, process and common questions for each important page. Use examples to explain what the service includes, and distinguish a concept portfolio from commissioned work. Give images useful alternatives where they communicate information. Decorative artwork can use empty alt text; product or interface examples need context that a reader can understand without the image.
Protect URLs and technical signals
Map each retired URL to the most relevant replacement. Use permanent redirects for genuine moves, keep canonical links consistent and make sure the XML sitemap contains the preferred public URLs. Test old links as well as new menu links. A redirect is not a substitute for updating your own internal navigation. Confirm that production robots rules allow the intended crawlers.
Test beyond the homepage
Submit a controlled test inquiry, inspect error messages and verify where the submission arrives. Check image sizes, keyboard navigation, large text, reduced-motion preferences and a slow connection. Compare performance under consistent conditions; do not treat one speed score as a guarantee for every visitor. Check third-party scripts separately because they can change after launch.
Launch with a short review plan
After launch, inspect important URLs in Search Console and review real inquiries or usage signals. Record what changed so later improvements have a baseline. Correct broken links and confusing copy before adding more features. A redesign is a set of testable decisions, followed by observation and refinement—not a promise of an immediate ranking or sales increase.
Related tools and next steps
Technical reference: Read the supporting documentation.
For help applying these decisions to a project, contact WebHolick.