Map what already brings traffic
Before a redesign, identify which pages already attract impressions, clicks, or qualified inquiries. The objective is not to preserve every old page equally; it is to preserve the pages and themes that already have search value.
This is where many redesigns quietly fail. Teams focus on visuals first, then remove or consolidate pages without understanding which URLs, headings, or keyword clusters were driving discoverability.
- Export top pages from Search Console and analytics
- Map current titles, meta descriptions, and H1s
- Document high-performing blog, service, and landing pages
Preserve intent, not just words
When copy is rewritten, the page still needs to satisfy the same search intent if you want to preserve or improve rankings. That means the new version should answer the same core questions, support the same user outcomes, and keep equivalent topical relevance.
- Retain core service keywords where relevant
- Keep supporting FAQ and proof sections
- Strengthen internal links instead of deleting context
Treat redirects as a revenue decision
Every removed or renamed page should have a destination. Redirects protect rankings, referral traffic, backlinks, and user trust.
A redirect map is one of the simplest ways to reduce traffic loss during launch.
- Create 301 redirects for replaced URLs
- Update internal links to final destinations
- Check for old HTML or misspelled route patterns
Review the launch like a search engine and a buyer
Once the redesigned site is live, verify that search crawlers can still understand the page structure and that real visitors can still reach the right information quickly. A visually cleaner site is not enough if internal linking, heading hierarchy, or conversion paths become weaker after launch.
- Recheck canonical URLs, indexing, and structured metadata output
- Validate service-page CTA paths, forms, and trust sections after launch
- Watch impression, click, and inquiry trends during the first few weeks