How to Redesign Your Website Without Losing Track of Your SEO

Describe what is actually moving

A new visual system with stable URLs is different from a domain migration, a CMS replacement and a complete content rewrite. List those changes separately before asking for an SEO-preserving redesign. Otherwise, a promise about ‘keeping the SEO’ has no agreed meaning.

Google’s site-move guidance recommends changing one major element at a time where practical and warns that rankings can fluctuate during a move. A careful migration reduces avoidable failures; it cannot promise that every query position will remain unchanged.

For a small company, the first deliverable can be a simple inventory. Export the current URLs, identify pages with relevant traffic or external links and ask the business which services, downloads and project examples remain accurate. Technical evidence and business relevance both matter.

Give each existing page a destination decision

Do not preserve a page solely because it is old, and do not delete it solely because its design looks dated. A useful explanation may deserve a better layout. An obsolete offer may need removal even if it once received traffic. Record the rationale so the decision survives the handoff between content and development.

Write and test the redirect map before launch

For changed URLs, map each old address to its closest relevant replacement. If a commercial-renovations page moves, send visitors to the new commercial-renovations explanation rather than a general homepage. Review chains, loops and URLs whose destinations were themselves removed.

Google’s move guide recommends server-side permanent redirects for permanent URL moves and keeping redirects for at least a year. Build that operating responsibility into the handover. A redirect that disappears when a hosting subscription is cancelled will not continue helping people who follow the old address.

Update the website’s own links to use final destinations. Redirects are useful for old links; they should not be the normal route through newly built navigation. Our URL naming guide explains how to avoid unnecessary changes when creating new slugs.

Use a launch checklist that tests public behaviour

• Confirm the public domain, HTTPS behaviour and preferred hostname.
• Remove staging restrictions from pages intended for discovery while preserving private areas.
• Check representative service, project, article and contact pages for correct responses.
• Verify titles, descriptions, canonical URLs and applicable structured data.
• Check final sitemap URLs and representative old-to-new redirects.
• Test navigation, mobile contact, form errors and accepted-inquiry confirmation.
• Verify analytics and record the launch date so later comparisons have context.

Assign a person to each check. ‘The team will review SEO’ is too vague to reveal whether anyone inspected canonicals or the contact result. Keep a short list of evidence: the tested URL, expected behaviour, observed result and any unresolved issue.

Monitor specific problems after launch

Watch for broken destinations, indexing changes, server errors and inquiry failures. Compare similar periods and annotate other changes such as campaigns or service availability. A traffic movement immediately after launch is a reason to investigate; it is not, by itself, a diagnosis of a particular design choice.

A useful handover includes the final content inventory, redirect ownership, account access and a recovery plan. Keep the information where the business can retrieve it. If ownership of those systems is unclear, see who owns an AI-built website.

Menerai’s website redesign and development work can include this continuity planning in the scope. Send us the current site and the reason for the redesign, including any planned domain or platform change, so the proposal reflects the actual migration.