Website Redesign SEO Checklist: Keep Your Rankings
A website redesign SEO checklist for small businesses: URL inventory, redirect mapping, staging pitfalls, launch-day checks and what to monitor afterwards.
- Published
- Reading time
- 6 min read
This checklist is organised in three phases: before, during and after launch.
Why relaunches lose traffic
Search engines know your site by its URLs and the content behind them. A redesign often changes both. The most common causes of lost traffic:
- URLs change without redirects. Old links and rankings point to pages that no longer exist.
- Content is shortened or removed. Pages that ranked well lose the text that made them relevant.
- Titles and meta descriptions are reset. The new CMS uses defaults.
- The new site is blocked. A noindex tag or a robots.txt block from the staging environment goes live.
- Internal links change. Important pages get fewer links in the new navigation.
- Performance gets worse. Heavier pages load slowly, especially on mobile.
Who should be involved
Even in a small business, a relaunch touches several roles. Clarify who covers each one before work starts:
| Role | Responsibility |
|---|---|
| Project owner | Decisions, timeline, final approval of the launch |
| Web designer or developer | Templates, redirects, technical settings, performance |
| Content owner | Carrying over and updating texts, titles and descriptions |
| SEO check (internal or external) | URL inventory, redirect map review, launch-day checks |
| Analytics owner | Tracking setup, before-and-after comparison |
One person can hold several roles, but each responsibility should have a name next to it. Most relaunch problems happen in the gaps between roles, for example when the designer assumes the content owner handles redirects and vice versa.
Phase 1: Before launch
1. Create a URL inventory
Collect every URL of the current site:
- Crawl the site with an SEO crawler.
- Export URLs from your sitemap and CMS.
- Export pages with traffic and pages with backlinks from your analytics and search console.
Combine the lists and remove duplicates. Add for each URL: monthly visits, clicks from search, number of backlinks if known, title tag and meta description.
2. Identify your most valuable pages
Sort the inventory by traffic, conversions and backlinks. The top pages need extra care: keep their content (or improve it), keep their URLs if possible and test their redirects first.
3. Build the redirect map
Pair every old URL with the best matching new URL.
| Old URL | New URL | Redirect | Note |
|---|---|---|---|
| /services/it-support.html | /services/it-support/ | 301 | Same content, new URL format |
| /news/2023/office-move | /blog/office-move/ | 301 | Moved to blog section |
| /team-anna | /about/ | 301 | Individual team pages merged |
| /old-product-x | /products/product-y/ | 301 | Successor product |
| /holiday-hours-2022 | — | 410 or 404 | Outdated, no equivalent |
Rules for the map:
- Redirect to the most relevant page, not to the homepage by default.
- Avoid redirect chains (old → intermediate → new). Point directly to the final URL.
- Only let pages return 404 or 410 when there is truly no equivalent.
4. Review content and on-page elements
- Carry over or rewrite the content of important pages; do not shorten them drastically without reason.
- Write or migrate title tags and meta descriptions for every important page. Check them in the SERP snippet preview and see our guides on title tag length in pixels and how to write meta descriptions.
- Keep heading structure, image alt texts and structured data.
5. Prepare the staging site correctly
- Protect the staging site with a password or block it from indexing (noindex).
- Write down every setting you used to block it, so you can remove each one at launch.
- Crawl the staging site to find broken links, missing titles and redirect errors before launch.
6. Check performance and mobile usability
Test key templates on staging for loading speed and mobile layout. Fix heavy images, unnecessary scripts and layout shifts before going live.
7. Plan tracking
- Make sure the analytics and conversion tracking code is on the new site and tested.
- Verify that search console access stays intact (same domain property or new verification if needed).
- Note the launch date in analytics so you can compare before and after.
Phase 2: Launch day
Go through this list immediately after the new site is live:
- Remove noindex and staging blocks. Check the source of key pages and the robots.txt file.
- Test redirects. Check a sample of old URLs, starting with the most valuable ones. Tools can test lists of URLs in bulk.
- Check canonical tags. They should point to the new live URLs, not to staging.
- Submit the new XML sitemap in search console.
- Test forms and conversions with a real submission.
- Crawl the live site to catch broken links and missing titles.
- Check HTTPS and that all versions (with and without www) redirect to one preferred version.
Phase 3: After launch
First two weeks
- Check search console daily or every few days for crawl errors and pages excluded from the index.
- Fix 404 errors for URLs that were missed in the redirect map.
- Watch traffic and conversions; compare with the same weekdays before launch.
First three months
- Compare traffic and rankings for your top pages with the pre-launch inventory.
- Update important external links (directories, partner sites, social profiles) to the new URLs where possible.
- Keep the redirects in place for the long term. Removing them later breaks old links again.
Monitoring table
| What | Where | How often |
|---|---|---|
| Crawl and indexing errors | Search console | Daily for 2 weeks, then weekly |
| 404 errors | Server logs, search console, crawler | Weekly |
| Organic clicks for top pages | Search console | Weekly for 3 months |
| Conversions | Analytics | Weekly |
| Page speed of key templates | Performance testing tool | After launch and after major changes |
Common mistakes
Redirecting everything to the homepage. Search engines may treat such redirects like missing pages, and visitors land somewhere irrelevant.
Leaving noindex on the live site. This is one of the most damaging and most common relaunch errors. Check it explicitly.
Changing too much at once. New domain, new URLs, new content and new design at the same time make problems hard to diagnose.
Launching on a Friday afternoon. Choose a day when the team is available to fix issues.
Removing old redirects after a few months. Old links and bookmarks keep working only if redirects stay.
Forgetting landing pages for ads. Paid campaigns pointing to old URLs may break or lose quality. Update them; our landing page checklist helps you review those pages.
Summary
A relaunch does not have to cost rankings. This website redesign SEO checklist comes down to three habits: document everything before you change it, redirect every old URL to its best new equivalent and verify the technical basics on launch day, especially that indexing is allowed. Then monitor errors and traffic closely for several weeks. Small businesses that follow these steps usually keep the visibility they had and often gain from a faster, clearer new site.
FAQ
Will a website redesign hurt my SEO?
It can, mainly when URLs change without redirects, content is removed, or technical settings such as noindex are carried over from the staging site. With careful planning and redirects, most of these risks can be avoided.
What is a redirect map?
A redirect map is a list that pairs every old URL with its new URL. It is used to set up permanent (301) redirects so visitors and search engines are sent to the right new page.
How long does it take for rankings to settle after a relaunch?
Search engines need time to recrawl and process the changes, so some fluctuation in the first weeks is common. The duration depends on the size of the site and how much changed.
Should I change my domain at the same time as the redesign?
Avoid combining a domain change with a redesign if you can. Changing several things at once makes it harder to find the cause if traffic drops.