Website redesign without losing SEO
Preserve useful URLs and content, map necessary URL changes to relevant permanent redirects, and test the new site's indexability and inquiry paths before launch. Monitor the changed pages afterward. This process reduces avoidable mistakes; it cannot guarantee unchanged rankings during a redesign.
Branddirr editorial guide · Updated October 9, 2026
Record the baseline before changing anything
Export your current sitemap and important Search Console pages and queries. Record status codes, canonicals, titles and useful inbound links. Include pages that earn inquiries, referral traffic or links even when their organic clicks are small. Save the current source, assets, database and deployment configuration so the previous release can be restored.
For a professional-services firm, inventory the actual service hierarchy. Do tax, advisory and CFO services have distinct useful pages, or are they hidden in a generic paragraph? Preserve existing strengths while improving clarity. The redesign should not erase an established service page simply because the new menu is shorter.
Make a decision for each old URL
| Existing page | Decision | Validation |
|---|---|---|
| Useful page with the same purpose | Keep the URL and improve it | 200 response, self-canonical, approved content and internal links. |
| Page genuinely moved or merged | Redirect permanently to a relevant replacement | One direct hop to a working destination; update internal links. |
| Retired page with no relevant replacement | Return a genuine 404 or 410 | Remove from navigation and sitemap; avoid blanket home redirects. |
| Tracking or form-prefill URL | Keep its functional context and canonicalize appropriately | Prefill still works; the canonical points to the intended public page. |
A redirect or canonical exclusion in Search Console may be the expected result of this mapping. The important question is whether Google can access and index the intended destination. Keep a written URL register so each decision is reviewable.
Check staging with real visitor behavior
- Protect staging from indexing while preserving authenticated access for review. Check that staging restrictions will not carry into production.
- Review rendered HTML, descriptive headings, independent metadata, image descriptions where informative, and structured data that matches visible facts.
- Test phones and desktops for overflow, readable contrast, usable controls and sticky elements that obstruct content. Check keyboard and reduced-motion behavior.
- Submit disposable test inquiries through the full storage and notification path. If booking is offered, verify conflicts, real calendar events and failure messages.
- Confirm account ownership, content editing and the recovery procedure with the people who will operate the site.
Release with a small, explicit checklist
- Retain the previous deployable release and a verified database backup. Use additive migrations where possible.
- Confirm HTTPS, redirects, production canonicals, crawl permissions and successful public responses for every intended sitemap page.
- Update internal links and the sitemap to final URLs. Keep modification dates tied to actual changes.
- Check working images, forms, analytics consent and notifications on each production deployment.
- Inspect a small set of repaired priority pages in Search Console, submit the sitemap if needed and request indexing selectively.
Monitor the changed pages and the business outcome
Compare the same queries and pages over comparable periods. Separate a tracking change from a real loss of search visibility. Review crawl errors, selected canonicals, received inquiries and qualified opportunities. Record the date of each change so later investigations have usable evidence.
Ranking fluctuations can occur while Google revisits changed pages. Resist repeated site-wide edits based on one day of data. Investigate an observed issue, make a bounded correction and record what changed. If a high-value inquiry route breaks, repair it immediately; search monitoring should not delay a conversion fix.
Google's site-move guidance is the primary reference when URLs change. A visual redesign with stable URLs is a narrower job, but the same inventory, testing and monitoring discipline helps protect what already works.