A website redesign SEO checklist is the ordered list of checks that keeps the rankings and traffic your old site earned while the new one goes live: measure before you change anything, list every address, map each old URL to its new home with a 301 redirect, keep the content that ranks, and watch the results for weeks after launch. Most traffic lost in a redesign is lost through skipped steps, not through the new design itself.
Last updated: 28 October 2026.
This checklist walks through every stage in order, from the benchmark to recovery monitoring, with the redirect rules, the launch-day checks and the questions buyers ask most.
Why do redesigns lose search traffic?
A redesign changes three things search engines rely on: the addresses of your pages, the words on them and the way they are built. Change any of the three carelessly and the search engine has to relearn the site. Change all three at once without a plan, and pages that ranked for years can drop out of the results.
The usual causes are plain. Old URLs return a 404 instead of redirecting. Pages that brought traffic are merged or removed because they looked dull in the new sitemap. Titles and descriptions are rewritten or left blank. A staging site’s noindex setting is carried into production. Internal links still point to old addresses, so every click goes through a redirect or fails.
None of these is a design problem. They are process problems, and a checklist fixes process.
What does an SEO website redesign involve?
An SEO website redesign treats search visibility as a requirement of the project from the first brief, not a task for launch week. At Odduel, a creative and technology agency in Barcelona and São Paulo, our website redesign work starts with the old site’s data before anyone draws a new page, because the old site tells you what must survive.
In short: decide what you are keeping before you decide what you are changing. Record how the site performs today. Keep every address that matters, or redirect it once to the closest new page. Launch at a quiet moment, check everything that day, and watch the numbers for at least two to three months.
Google describes the mechanics of a move in its guide to a site move with URL changes, and the checklist below follows the same logic, in the order a project actually runs.
The website redesign SEO checklist at a glance
The table sets out each stage, what it produces and when it happens. Each stage then has its own section below.
| Stage | What it produces | When |
|---|---|---|
| 1. Benchmark | Traffic, rankings and top pages recorded | Before design starts |
| 2. URL inventory | Every address of the old site in one list | Discovery |
| 3. Redirect map | Old URL, new URL and status for each row | Before build ends |
| 4. Content parity | Ranking content kept or improved | Design and copy |
| 5. Metadata | Title, description, headings per page | Build |
| 6. Structured data | Schema carried over and tested | Build |
| 7. Staging protection | Staging closed to search engines | Whole build |
| 8. Launch-day checks | Redirects, indexing, sitemap tested live | Launch day |
| 9. Search Console | New sitemap, errors and coverage watched | Launch week |
| 10. Recovery monitoring | Weekly comparison with the benchmark | Two to three months |
What should you measure before the redesign?
The benchmark is the only way to know, after launch, whether something has gone wrong. Without it, every dip becomes an argument. Record it before design starts and keep a copy that nobody edits.
- Export organic traffic per page for the last twelve months from your analytics, so seasonal patterns are visible.
- Export queries, clicks, impressions and average position per page from Google Search Console.
- List the pages that bring the most organic visits and the most enquiries or sales. These are the pages you protect first.
- Record the external links pointing at your site and which pages receive them; a backlink tool or the Search Console links report will do.
- Note Core Web Vitals and page speed for the main templates, so the new build can be held to at least the same standard.
- Save the current titles, descriptions and headings of every important page.
Keep the files with the project, not in someone’s inbox. They are the reference for every decision that follows.
How do you build the URL inventory?
The URL inventory is a full list of every address the old site answers to, not only the pages in its menu. Crawl the live site with a crawler, then add the addresses a crawl cannot find: URLs from the XML sitemap, pages with traffic in analytics, pages with backlinks, PDFs and images that rank, and old campaign landing pages.
Each row should carry the URL, its status code, its title, its organic visits and its backlinks. Sort by value. The top of the list is what the redesign must not break; the bottom is where you can safely prune.
Clean addresses make this easier for the rest of the site’s life. If the redesign changes the URL structure, our guide to SEO-friendly URL slugs explains how to choose addresses you will not need to change again.
How do you plan 301 redirects in a website redesign?
A 301 redirect tells browsers and search engines that a page has moved for good, and passes the signals of the old address to the new one. In a redesign it is the most important single safeguard. The redirect map is a spreadsheet with one row per old URL: old address, new address, redirect type and a check column.
The rules of a good redirect map
- Redirect each old URL to the most relevant new page, never to the home page by default. A mass redirect to the home page is treated much like a missing page.
- Use one hop. Old address to final address, with no chains through intermediate URLs.
- Use 301 (or 308) for permanent moves. Keep 302 for genuinely temporary situations.
- Let a page that has no equivalent and no value return 404 or 410, rather than redirecting it somewhere unrelated.
- Cover the variants: with and without the trailing slash, upper case, old parameters, http and www versions.
- Redirect old images and PDFs that rank or carry links.
- Keep the redirects in place for at least a year, and in practice for as long as the old addresses receive visits or links.
Where redirects should live
Redirects are fastest and safest at the server or the platform’s own redirect manager, not in page-level scripts. Google’s documentation on redirects and Google Search lists the methods it reads and their order of preference. Whatever the platform, test the whole map on staging before launch and again on the live site.
How do you keep content parity?
Content parity means the new site keeps the substance that made the old pages rank. A page that answered a question in eight hundred words and now offers a headline and a button will not keep its position, however good it looks.
Go through the protected pages from the benchmark one by one. For each, decide: keep as it is, improve, merge with a closely related page (and redirect), or retire. Keep the main heading close to the query it ranks for. Keep the answers, the specifics and the examples. Rewrite for clarity, not for brevity.
Watch the parts a design system tends to hide: copy inside tabs and sliders, text set as images, and content that only appears after a script runs. Search engines can read much of it, but plain, visible HTML text is the safest place for anything that should rank.
Which metadata and on-page elements must carry over?
Every page of the new site needs a unique title, a meta description, one H1 and headings in order. For the protected pages, start from the old title and description rather than a blank field; change them only where the change is clearly better.
Check, page by page:
- Title and meta description, unique and written for the query.
- One H1, then H2 and H3 in order.
- Canonical link pointing at the page’s own final address.
- Image file names, alt text and explicit dimensions.
- Internal links updated to the new addresses, so no click relies on a redirect.
- Open Graph title and image for sharing.
Internal links deserve a pass of their own. Menus are easy; links inside body text, footers and old articles are where the old addresses survive.
Does structured data need to be moved too?
Yes. Structured data (schema markup) is often generated by a plugin or a template, and a new theme or platform may drop it without anyone noticing. List the types the old site carries: company details, BreadcrumbList, Article, Product, FAQPage, LocalBusiness, JobPosting. Rebuild them on the new templates and test each type with Google’s Rich Results Test on staging.
Keep identifiers stable. If the node describing your company has an ID and a logo address, keep them the same across the move, and keep company details consistent with your other public profiles.
What about a multilingual site?
A site in several languages multiplies every step: each language version has its own URLs, titles and redirects. Map every language separately, and keep hreflang annotations complete and reciprocal, so each version names all the others and itself, plus an x-default.
Translated slugs need special care. If the English address changes, the translated addresses usually change too, and each one needs its own redirect. Check that canonical links point at the page in its own language, not at the English original, and that every language version has its own XML sitemap or appears in a shared one.
How do you keep the staging site out of search results?
The staging site holds a full copy of your new pages, so it must never be indexed: if it is, it competes with the live site. Protect it in two ways at once. Put it behind a password or an IP restriction, which keeps search engines and the public out, and send a noindex header as a second safeguard.
The danger runs the other way on launch day. A noindex tag, a disallow-all robots.txt or a “discourage search engines” setting copied from staging into production can remove the new site from the results within days. Put “remove staging protection” on the launch checklist, with a name next to it.
What should you check on launch day?
Launch early in the week, at a quiet hour for your traffic, with the people who can fix things available. Avoid launching just before a holiday or a peak sales period. Then work through the list on the live site, not on staging.
- Confirm the site is indexable: no noindex header or tag, robots.txt allows crawling, the platform’s search engine setting is off.
- Test the redirect map: crawl the full list of old URLs and confirm each returns a single 301 to the right page with a 200 at the end.
- Crawl the new site for 404s, redirect chains and internal links that still point to old addresses.
- Check canonical links, hreflang and titles on a sample of every template.
- Load the XML sitemap and confirm it lists only final, indexable addresses.
- Test forms, tracking and the consent banner, so enquiries and analytics keep flowing.
- Check speed and Core Web Vitals on the main templates against the benchmark.
Our website QA checklist covers the non-SEO side of the same day: browsers, devices, forms and accessibility.
What should you do in Google Search Console?
Search Console is where you see how Google reads the move. On launch day, submit the new XML sitemap. If the domain itself changes, verify the new property and use the Change of Address tool in the old property, as Google’s site-move guide describes.
Keep the old sitemap available for a short while too: it helps Google find the old URLs and discover their redirects sooner. Then watch the page indexing report for new 404s and pages excluded by noindex, the performance report for clicks and impressions on the protected pages, and the crawl stats for spikes in errors. Use URL Inspection on the most valuable pages to request indexing.
How long does SEO recovery take after a redesign?
Some movement in the first weeks is normal while search engines recrawl the site and process the redirects. A well-planned redesign usually settles within a few weeks; a larger move, such as a new domain or a new URL structure across thousands of pages, can take a few months. Google says as much in its own documentation.
Compare against the benchmark every week for at least two to three months: organic clicks per protected page, positions for the main queries, indexed pages and enquiries. A fall limited to a few pages points to a redirect or a content problem on those pages. A fall across the whole site points to an indexing problem, and that is the first thing to check.
What if traffic drops after the redesign?
Work from the most likely cause to the least likely, and fix rather than wait.
- Check indexing first: a stray noindex, a blocked robots.txt or wrong canonical links.
- Re-test the redirect map, looking for 404s, chains and redirects to the home page.
- Compare the content of pages that lost traffic with their old versions in the benchmark.
- Check titles and headings on those pages against the old ones.
- Look for internal links and sitemap entries still pointing to old addresses.
- Check speed: a heavier new template can slow every page.
If the cause is a removed page that ranked well, bring its content back, at its old address or redirected from it. Most recoveries come from putting back what the old site had, not from adding something new.
Questions people ask
Will a website redesign hurt my SEO?
It does not have to. Traffic is lost when addresses change without redirects, ranking content is removed or the new site is accidentally blocked from search engines. With a benchmark, a complete redirect map, content parity and launch-day checks, most redesigns hold their positions and many improve them once the faster, clearer pages are crawled.
Should I keep the same URLs when I redesign?
Keep them wherever they are already clean and descriptive, because an unchanged address needs no redirect and keeps its signals directly. Change them only where the structure is genuinely poor, for example dates, numbers or parameters in the path. Every changed address needs a 301 redirect to its closest new equivalent, tested before and after launch.
How long should 301 redirects stay in place?
Keep them for at least a year, and in practice for as long as the old addresses still receive visits or external links. Removing redirects saves almost nothing and can turn old backlinks into 404s. Review the redirect list once a year, and remove only rows whose old address has had no traffic or links for a long time.
When should SEO be involved in a redesign?
From the first brief. The benchmark and the URL inventory shape the sitemap, the content plan and the templates, so they must exist before design starts. SEO brought in during launch week can only check what has already been decided, and fixing a removed page or a missing template field at that point costs far more time.
Can I change domain and redesign at the same time?
You can, but it multiplies the risk, because search engines must process new addresses, a new domain and new content together, and any drop is harder to trace. Where you can, move the domain first with the same content, let it settle, then redesign. If both must happen together, the redirect map and monitoring become even more important.
Is a website redesign SEO checklist different for e-commerce?
The stages are the same, but the scale is larger. Product, category and filter pages multiply the URL inventory, discontinued products need a clear rule (redirect to a close alternative or the category, or let them return 410), and product structured data must carry prices and availability correctly. Test search and filter addresses carefully before launch.
If a redesign is on your plan, start with the benchmark and the URL inventory: they cost little and protect most of what the old site earned. If you are also wondering how much time to allow, our guide to how long it takes to build a website sets out the stages. We handle the full move, from the first crawl to the weeks of monitoring after launch; see our website redesign service or talk to us about your project.
Further reading: How to choose an SEO company: questions, red flags and contracts.
