Website Redesign Checklist: Keep Your SEO Rankings Intact

A new website should bring more leads, not fewer. Yet many businesses see organic traffic fall by a third or more in the weeks after a relaunch, simply because URLs changed, content was trimmed or pages were blocked from search engines by mistake. A website redesign SEO checklist turns that risk into a controlled process: you record what is working today, carry it across deliberately, and verify everything before and after go-live.

This guide is the checklist we use when we plan website development and redesign projects. It is split into the four phases where SEO is usually won or lost: before design starts, during build, on launch day and in the 90 days after.

Why Redesigns Lose Rankings

Rankings drop after a redesign mainly because URLs, content or crawl settings change without a plan. Search engines rank individual URLs, not brands. When a page that has earned links and rankings for years disappears or moves without a redirect, those signals are lost. The most common causes of a post-launch drop are:

• Changed URLs without 301 redirects, so old links and bookmarks return 404 errors.
• Removed or thinned content, often because a designer wanted shorter pages.
• Changed title tags, headings and internal links that weakened the page’s relevance for its main queries.
• Staging settings left on, such as a sitewide noindex tag or a robots.txt rule that blocks crawling.
• Slower pages caused by heavy images, new scripts or a new theme.
• JavaScript-rendered content that search engines struggle to see, especially on a switch to a single-page framework.

Almost all of these are preventable. The checklist below addresses each one.

Phase 1: Benchmark Before You Touch the Design

You cannot protect what you have not measured. Before wireframes are approved, capture a baseline.

1. Crawl the current site. Use a crawler such as Screaming Frog or Sitebulb to export every URL with its status code, title, meta description, H1, canonical tag and word count.
2. Export performance data. From Google Search Console, export the last 12–16 months of clicks, impressions and average position by page and by query. From your analytics tool, export sessions and conversions by landing page.
3. Identify your top pages. Rank URLs by organic clicks, conversions and number of referring domains. In most sites, 10–20% of pages bring 80% or more of organic value. These pages need the most care.
4. Record backlinks. Export linked pages from Search Console or a backlink tool. Any URL with external links must keep working or redirect.
5. Save keyword rankings for your 50–200 most important queries so you have a before-and-after comparison.
6. Measure speed. Record Core Web Vitals field data and lab scores for key templates. Google documents the metrics on web.dev, and our guide to passing Core Web Vitals explains how to improve them.

Phase 2: Plan Content and URL Structure

Decide what happens to every URL

Every existing URL needs a documented decision before launch. Each one should get one of three outcomes: keep (same URL), move (new URL with a 301 redirect) or retire (redirect to the closest relevant page, or return 410 only if there is truly no equivalent and no valuable links). Record this in a spreadsheet that becomes your redirect map.

Current situation	Recommended action	Notes
Page stays, URL unchanged	Keep	Preserve title, H1 and core copy unless improving deliberately
Page stays, URL changes	301 redirect old to new	Map one to one; avoid redirect chains
Two pages merged	301 both to the merged page	Combine the best content from each
Page removed, close equivalent exists	301 to the equivalent	Do not send everything to the homepage
Page removed, no equivalent, no links	410 or 404	Acceptable for genuinely obsolete content

Keep URLs where you can

The safest redirect is the one you never need. If the platform allows it, keep the existing URL structure. If you are moving to a new CMS, for example from a custom build to WordPress or to a headless CMS, configure its permalink rules to match the old patterns where practical.

Protect content on top pages

Designers and copywriters should see the list of top pages before they start. Content that ranks should not be cut to fit a layout. Improve it, restructure it, add visuals, but keep the topics, headings and depth that earned the rankings.

Plan internal linking and navigation

Navigation changes redistribute internal link equity. If a key service page moves from the main menu into a footer, it may lose visibility. Map the new navigation against your top pages and make sure each important page is still reachable within two or three clicks from the homepage.

Phase 3: Build and Test on Staging

During development, the staging site must be invisible to search engines but complete enough to test properly.

• Block staging correctly. Use HTTP authentication (password protection), as recommended in Google Search Central documentation, rather than relying only on robots.txt or noindex, which are easy to carry into production by accident.
• Migrate on-page elements. Title tags, meta descriptions, H1s, image alt text and structured data should be carried over or deliberately improved.
• Check canonical tags. Each page should point to its own production URL, not to the staging domain.
• Test the redirect map. Load every old URL on staging (or run them through a script) and confirm each returns a single 301 to the right destination.
• Check rendering. If the new site uses React, Vue or another JavaScript framework, make sure important content and links are in the server-rendered HTML. Server-side rendering or static generation avoids most problems.
• Test speed and accessibility. Compare key templates against the baseline. Address accessibility at the same time; the W3C WCAG standard sets the criteria, and our WCAG accessibility guide covers the common issues, many of which overlap with SEO (alt text, heading order, descriptive links).
• Prepare an XML sitemap containing only canonical, indexable 200-status URLs on the new site.

Phase 4: Launch Day Checklist

This is the part of the website redesign SEO checklist where small oversights do the most damage. Launch early in the week and at a quiet time for your business, so the team is available to fix issues. On the day:

1. Remove staging password protection and any sitewide noindex tag.
2. Confirm robots.txt allows crawling of important sections and references the new sitemap.
3. Deploy the redirect rules and spot-check your top 50 old URLs.
4. Confirm HTTPS works on every page and that HTTP and non-www (or www) variants redirect to the preferred version.
5. Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools.
6. Check that analytics, tag manager and conversion tracking fire correctly on key pages and forms.
7. Crawl the live site and fix any 404s, redirect chains or unexpected noindex tags.
8. If the domain itself changed, use the Change of Address tool in Search Console after redirects are live.

Post-Launch: Monitor for 90 Days

Some fluctuation in the first two to four weeks is normal while search engines recrawl and reprocess the site. What matters is the trend.

• Weekly for the first month: review the Search Console Pages report for new 404s and excluded pages, compare clicks for top pages against the baseline and watch server logs or crawl stats for errors.
• Track rankings for your saved keyword list. A page that drops sharply and stays down usually has a specific cause: a missing redirect, lost content or a changed title.
• Fix broken backlinks by adding redirects for any linked URLs you missed.
• Update internal links so they point directly to new URLs rather than through redirects.
• Keep redirects in place for at least a year, and ideally permanently. Removing them later throws away the link equity they carry.

Website Redesign SEO Checklist: Timeline and Budget

For a small business site of 20–100 pages, SEO migration work typically adds 15–30 hours to a redesign, which at blended offshore and onshore rates is roughly $1,000–$3,500. For larger sites with thousands of URLs, multiple languages or a platform change, expect $5,000–$20,000+ for audits, redirect mapping, rendering checks and post-launch monitoring. These are indicative ranges; the final figure depends on site size and complexity. Compared with the cost of losing a large share of organic leads for months, it is cheap insurance.

Frequently Asked Questions

Will a website redesign hurt my SEO?

Not if it is planned. A redesign that preserves URLs or redirects them correctly, keeps valuable content and improves speed often lifts rankings. Problems arise when SEO is treated as a launch-week task instead of being part of the project from the start.

How long does it take to recover rankings after a redesign?

With correct redirects and content, most sites stabilize within two to six weeks. If traffic is still well below baseline after two months, audit the redirect map and compare top pages before and after.

Should I redirect all old pages to the homepage?

No. Search engines often treat mass redirects to the homepage as soft 404s, so the link value is lost. Redirect each old URL to the most relevant new page.

Do I need to change my domain during a redesign?

Only if there is a strong business reason. Changing domain and design at the same time adds risk and makes it harder to diagnose problems. If you must do both, consider doing them in separate phases.

Plan Your Redesign With SEO Built In

Sigmato designs and builds business websites and web applications with SEO migration planned from the first workshop, from Figma design through redirect mapping and post-launch monitoring. Tell us about your current site and we will outline a safe migration plan.

Sources and References

• Google Search Central – Search documentation
• web.dev – Web Vitals
• W3C – WCAG 2 Overview
• Microsoft – Bing Webmaster Tools