24 July 2026·14 minute read

Redesign the business system—not just the homepage.

A complete pre-redesign audit for analytics, content, search visibility, user journeys, integrations, accessibility, migration and launch risk.

The direct answer

A visual redesign can make a website look new while preserving every reason it underperforms. Evidence and architecture must change before decoration.

Decision snapshot

Before designAnalytics and content audit
Before buildURL and integration map
Before launchRedirect and tracking test
After launchSearch and conversion monitoring

01 · Evidence

Establish a baseline that survives the redesign.

Export Search Console queries and landing pages, analytics conversions and top journeys, form quality, site-search terms and performance data. Record the date range and known tracking limitations.

Qualitative evidence matters too: sales objections, support questions, stakeholder interviews and usability sessions explain why a number changed.

  • Organic landing pages and backlinks
  • Conversions by page and device
  • High-exit journeys and failed searches
  • Core Web Vitals field data
  • Qualified lead and sales feedback
  • Accessibility and content-quality issues

02 · Content

Inventory every URL before choosing what the new site needs.

Mark each page keep, improve, consolidate, redirect or remove. Record owner, audience, purpose, traffic, backlinks and migration destination. This prevents valuable pages from disappearing because they were absent from a new navigation mockup.

Create content models for repeatable services, industries, people, resources and case studies. Good WordPress development gives editors structured fields and controlled components instead of cloned pages.

03 · Experience

Prototype the difficult journeys with real content.

Test service discovery, product comparison, search, forms, accounts and mobile navigation before expanding the visual system. A beautiful homepage does not prove that a technical product page or long insight article works.

Accessibility belongs in component decisions: heading order, keyboard behavior, focus visibility, contrast, labels, error messages and reduced motion should be verified during design and development.

04 · Migration

Treat every changed URL as a controlled move.

Google recommends mapping old URLs to corresponding new destinations, using server redirects, updating internal links and testing the new site thoroughly. Redirecting everything to the homepage destroys relevance and produces a poor visitor experience.

Freeze content at an agreed point, rehearse migration, crawl staging, compare inventories and prepare rollback. Keep the old crawl, mapping and launch log for diagnosis.

05 · Measurement

Define what improvement means before launch.

Rebuild analytics and consent configuration on staging, verify events and annotate launch. Monitor index coverage, redirects, rankings, forms, transactions and real-user performance after release.

Expect search engines to recrawl changed URLs. A temporary fluctuation is different from preventable loss caused by missing pages, incorrect canonicals or broken redirects.

Questions answered

No open loops.

The short answer appears first. Open each item for the reasoning and practical consequence.

Should every redesign change the URL structure?+

No. Keep stable, meaningful URLs when possible. Change them only when the new architecture provides a clear user or search benefit and implement one-to-one redirects.

Should we rewrite all content?+

No. Preserve accurate, valuable material and improve what is unclear or poorly structured. Rewrite based on intent and evidence, not a desire to make every sentence sound new.

Can design begin before the content audit?+

Early visual exploration can, but final templates should use representative real content. Otherwise content problems surface after the system is already constrained.

How long should post-launch monitoring continue?+

Intensively for the first days and weeks, then through at least one normal reporting cycle. Large migrations deserve longer search and conversion comparison.

Research basis

Sources used for this guide.

Platform limits and documentation change. These references were reviewed for this July 2026 edition; commercial recommendations are GoLiveQuick’s professional interpretation.