Most redesign losses are not caused by the new visual direction. They happen when a business changes URLs, removes useful content, weakens internal links or launches pages that search engines cannot crawl and understand.
Treat the project as two connected workstreams: experience improvement and search migration. The first shapes what visitors see; the second preserves the accumulated signals attached to existing pages and gives search engines a clear path to the new structure.
Google recommends accurate old-to-new URL mapping, server-side permanent redirects, updated internal links and canonicals, direct redirects without unnecessary chains, testing and a new sitemap. Those controls should be designed into the project, not added after rankings fall.
Benchmark the site before design or development starts
Export every indexable URL from the current sitemap, crawl and Google Search Console. Add organic clicks, impressions, queries, backlinks, conversions and the page template to one working inventory.
Mark pages that generate traffic, links, qualified enquiries or important brand demand. A low-traffic page may still support a valuable journey or rank for a narrow commercial query, so decisions need page-level evidence.
Capture the evidence you will need later
- Current URL and status code
- Canonical URL and indexability
- Primary query and search intent
- Clicks, impressions and conversions
- Backlinks and important internal links
- Current title, H1 and core copy
- Proposed action: keep, improve, merge or remove
No existing URL is deleted, renamed or consolidated without an explicit decision and destination.
Build an old-to-new URL map before changing slugs
Map every current indexable URL to its final destination. A one-to-one replacement is ideal. When content is genuinely consolidated, redirect to the closest relevant page—not automatically to the homepage.
Keep strong URLs when there is no compelling structural reason to change them. New navigation labels and a new page design do not require a new slug. Avoid chains such as old URL → temporary URL → final URL.
Use one migration sheet as the source of truth
The exact live address before launch.
The canonical destination after launch.
Keep, 301, merge, remove or review.
Protect content intent and on-page relevance
A visually cleaner page can become semantically weaker if useful copy, headings, FAQs, proof and contextual links disappear. Compare old and new pages by the questions they answer—not only by word count.
Preserve the page purpose, primary topic and evidence that earned visibility. Improve clarity and conversion flow, but do not turn a useful service page into a thin gallery. For wider planning, use the SEO checklist for 2026 alongside this migration process.
Review every priority template
- One clear and descriptive H1
- Logical H2 and H3 hierarchy
- Unique title and meta description
- Useful body copy retained or improved
- Descriptive image alt text
- Relevant FAQs and proof
- Contextual links to services, articles and cases
Prepare redirects, canonicals and technical controls
Implement server-side 301 or 308 redirects from each retired URL directly to its final relevant destination. Update internal links so users and crawlers do not depend on redirects during ordinary navigation.
Confirm that each new page has the intended self-referencing canonical, correct status code and no accidental noindex directive. Remove staging blocks only when the production domain is ready to be crawled.
Technical launch controls
Rebuild internal links around the new information architecture
Redirects preserve access, but updated internal links explain the new hierarchy more cleanly. Replace links in navigation, footers, service pages, articles, case studies, buttons and structured data.
Priority pages should not become deeper or more isolated after the redesign. Connect useful guides to the corresponding commercial pages and proof. See how the approach comes together in the website portfolio and case studies.
Check the paths that matter
- Homepage to priority services
- Service pages to relevant guides
- Articles back to commercial services
- Services and articles to proof or cases
- Every conversion page to a working contact route
- Breadcrumbs and mobile navigation
Crawl and test the production build before launch
Crawl the final production environment while access is controlled. Compare it with the approved URL map and flag missing pages, non-200 canonicals, duplicate titles, broken resources and accidental indexation rules.
Test representative pages manually on mobile and desktop. Submit every form, inspect success states, follow calls to action and confirm analytics or advertising events only if those tools are in scope.
Pre-launch acceptance test
Launch, submit and monitor the migration
After launch, republish the final site, verify robots.txt and sitemap.xml, submit the sitemap in Google Search Console and inspect the homepage plus representative service and article URLs.
Track the old and new URL sets separately. Watch indexing, clicks, impressions, rankings, 404s and redirect behaviour daily during the first week, then weekly while the migration settles. Google recommends keeping redirects for at least a year; longer is usually safer for users and old links.
Use a simple monitoring cadence
Diagnose losses by URL, query and template
Do not react to one aggregate traffic number. Compare equivalent periods and isolate the pages, queries, countries and devices where change occurred. Then match the pattern to a likely cause.
A single lost page may indicate content or redirect mismatch. Loss across one template can point to rendering, canonical or heading problems. Site-wide loss requires immediate review of robots, noindex, redirects, canonicals and server availability. If you need a redesign team that works across UX, development and search continuity, explore website design and development and SEO growth support.
Recovery order
- Confirm crawlability and status codes
- Verify canonical and redirect targets
- Restore lost content intent and internal links
- Check rendering and mobile usability
- Revalidate structured data
- Request indexing only after the page is correct
A redesign should transfer value, not reset it
The safest redesign keeps the existing search footprint visible throughout planning, design, development and launch. That does not mean freezing the old site; it means changing it with evidence and a controlled migration path.
Start the URL inventory before layouts are approved, make the redirect map part of development acceptance and assign one owner to post-launch monitoring. If those three controls exist, the team can improve the experience without treating organic visibility as collateral damage.
Frequently asked questions
Does a website redesign always hurt SEO?
Does a website redesign always hurt SEO?
No. Rankings can remain stable or improve when valuable URLs and content are preserved, redirects are mapped correctly, internal links are updated and the new site is crawlable. Temporary fluctuation can still occur while search engines process major changes.
Should we keep the same URLs during a redesign?
Should we keep the same URLs during a redesign?
Keep strong URLs whenever the page purpose remains the same. Change a slug only when the information architecture or topic genuinely requires it, then use a direct permanent redirect from the old URL.
How long should 301 redirects stay active?
How long should 301 redirects stay active?
Google recommends keeping migration redirects for at least one year. Keeping useful redirects longer protects visitors and backlinks that still use old addresses.
What should we monitor after launch?
What should we monitor after launch?
Monitor status codes, indexing, sitemap coverage, priority queries, page-level clicks and impressions, conversions, broken links and server errors. Compare old and new URL groups rather than relying only on total traffic.