How to redesign a website without losing sight of SEO

A practical website redesign SEO checklist covering URL mapping, content preservation, launch checks and post-launch monitoring.

By Fortitudo21 September 20263 min read

A silver ribbon bending across the lower third of a deep black scene. — Conceptual artwork created for Fortitudo.

The best time to consider SEO in a website redesign is before pages are removed or URLs are changed. Keep the search value of the existing site visible throughout the project: what people find, which questions the pages answer and where visitors go next. No redesign can guarantee stable rankings, but avoidable migration errors can be reduced.

Capture the baseline before changing the design

Export the current page inventory and record titles, main headings, canonical URLs and indexability. Pair that with the available Search Console and analytics data. Identify pages that earn relevant impressions, clicks, enquiries or sales rather than judging every page by raw traffic alone.

A small service page that brings a few qualified enquiries may deserve more attention than a broadly popular article. Keep a record of the query themes each valuable page answers. That becomes a content brief for the new version, not a command to preserve every sentence.

Keep useful content and simplify its presentation

A redesign should improve clarity without removing the information that makes a page useful. Preserve the core service explanation, supporting detail and relevant proof. Give a visitor enough information to decide whether to enquire, including process, scope and practical limitations.

For example, replacing a detailed commercial booking page with a large photograph and a two-line slogan may remove answers visitors need. A better redesign can keep those answers while introducing a clearer hierarchy, stronger imagery and easier navigation. Visual restraint should not require informational emptiness.

Treat changed URLs as an explicit migration

Google’s site-move guidance calls for mapping old URLs to new destinations and implementing redirects when URLs change. Use permanent server-side redirects for permanent moves, and update internal links to the new addresses. Send each valuable old page to the most relevant replacement.

Keep a migration sheet with old URL, intended new URL, reason for change and test result. Identify genuinely retired pages separately. Do not redirect unrelated content to a generic landing page merely to make a spreadsheet look complete.

Check the rendered site before opening it to visitors

Review the actual production candidate, including mobile layouts, titles, descriptions, headings and canonical tags. Confirm that essential content is present in the rendered page and accessible through ordinary links. Test navigation and enquiry routes from the pages search visitors are most likely to land on.

Staging environments often use access controls or noindex directives. Confirm the intended production behavior deliberately rather than assuming the deployment removes them. Check the XML sitemap, robots directives, image loading and the HTTP response of representative pages. An attractive screenshot cannot establish any of those things.

Monitor specific signals after launch

Save a dated launch checklist and watch indexing, failed requests, important landing pages and conversions. Search engines need time to revisit changed pages. Compare patterns over a useful period rather than interpreting one quiet day as a definitive result.

When something drops, investigate the affected URLs and queries. A missing section, broken redirect or changed conversion event requires a different response from ordinary demand variation. Preserve the previous version and release details so that a specific regression can be corrected quickly.

Your checklist

01Export page and search-performance baselines.
02Preserve the purpose and useful detail of important pages.
03Approve an old-to-new URL map.
04Check redirects, canonicals, robots and sitemap behavior.
05Test mobile reading and enquiry journeys.
06Monitor landing pages and conversions after launch.

A few common questions

Should every website redesign change the URL structure?

No. Keep useful existing URLs when there is no strong reason to change them. A new visual design does not require a new address for each page.

Does a better-looking website automatically rank higher?

No. Visual quality can improve usability, but search visibility also depends on content, crawlability, relevance and many other factors. Evaluate design and search performance separately.