SEO During a Website Redesign: How to Avoid Losing Traffic

A redesign can improve conversion and clarity — or it can quietly erase years of organic landing pages. Traffic loss after a redesign is rarely mysterious. It usually comes from changed URLs without redirects, weakened content, missing metadata, broken internal links, or tracking that no longer measures the same journeys.

This article focuses on during-the-project SEO controls. For the pre-design audit mindset, use the website redesign checklist. For the cutover mechanics, use the migration checklist.

Direct answer

Treat SEO as a workstream inside the redesign, not a launch-week patch. Before design freezes:

1. Inventory URLs that earn traffic or conversions
2. Decide keep / merge / redirect / retire for each
3. Preserve or deliberately improve content equity on those URLs
4. Maintain title/H1 intent where the page purpose stays the same
5. Test redirects, indexation and analytics before announcing the launch

Where redesigns lose organic performance

URL churn without a map

Designers rename paths for aesthetics. Developers ship new routes. Nobody owns the redirect spreadsheet. High-value URLs 404 or chain through three hops.

Content thinning

Long service pages become stylish stubs. The new design looks cleaner and ranks worse because the substance that matched search intent was deleted.

Template regressions

New templates drop canonicals, break heading hierarchy, hide primary content behind scripts, or omit unique metadata fields.

Internal link loss

Navigation and body links that previously distributed equity disappear in the new IA.

Measurement breaks

Goals, events and Search Console properties point at the wrong host or old paths, so teams “see a drop” that is partly instrumentation.

SEO workstream by project phase

Discovery

• Export Search Console landing pages and analytics landing pages
• Crawl the current site
• Note branded vs non-branded contribution
• Identify conversion paths tied to organic landings

Information architecture

• Prefer keeping strong URLs when the page purpose survives
• If a URL must change, assign a single 301 target with equivalent intent
• Avoid creating multiple new pages that compete for the same query the old page already won

Design and content

• Mark “protect” pages in the content inventory
• Rewrite for clarity without deleting the answers those pages ranked for
• Plan proof and CTA modules so conversion can improve with SEO continuity

Build

• Implement redirects as code/config, not a post-it note
• Preserve metadata fields in the CMS or MDX model
• Keep canonical host consistent
• Replicate critical structured data only when still accurate

QA and launch

• Spot-check top landing URLs resolve correctly
• Confirm titles/H1s on protected pages
• Validate analytics and conversion events
• Submit updated sitemap
• Monitor Search Console for spike in 404s and exclusions

Protect vs improve vs replace

“Replace everything because the new sitemap looks nicer” is a preference, not a strategy.

During-build checklist

• Top organic landing pages labeled protect / merge / redirect
• Redirect map drafted before development freeze
• Metadata fields present on new templates
• Internal links updated to final paths
• No accidental noindex on production templates
• Staging blocked from indexing
• Analytics events tested on new forms
• Sitemap regenerated for launch host

Tradeoffs worth making explicit

• Visual freedom vs URL stability: You can redesign surfaces without renaming every path.
• Consolidation vs coverage: Merging duplicates can help; merging distinct intents can hurt.
• Speed to launch vs verification: A one-day delay for redirect QA is cheaper than a three-month recovery.

Common mistakes

• Starting design before anyone exports Search Console data
• Leaving redirects to “we’ll fix SEO after”
• Changing titles on every page for brand voice and losing query match
• Launching on a different host without Search Console coverage
• Celebrating design launch while 404s pile up unnoticed

How this differs from a net-new SEO build

On a new site, you create equity. On a redesign, you also transfer equity. That transfer is a project deliverable. Summitstone’s website redesign and SEO work are deliberately linked for that reason: the experience can change while the findable paths remain intentional.

Related consideration

If the current site barely ranks, a redesign is still not a free pass to ignore structure. You may have less equity to lose — and still need service pages, technical foundations and measurement so the new site can earn traffic on purpose.

Decision framework before you approve design

Ask the team to show:

1. The list of URLs that must not break
2. The redirect rule for every changed path on that list
3. The content plan for those pages in the new templates
4. The launch QA owner for Search Console and analytics

If those four artifacts do not exist, the redesign is not ready — regardless of how polished the mockups look.