Marketing Agency

A website redesign is a chance to make your site easier to use, update its content and support new business goals. It can also change the things search engines and visitors already rely on: page URLs, links, headings, copy, images and technical settings.

The safest approach is not to freeze your old site in place. It is to understand what is working, decide what should change, and test the transition deliberately. This SEO checklist for website redesign is written for small teams that may not have a developer or SEO specialist watching every detail.

Imagine a local accounting firm replacing a dated five-page site. Its redesign includes a new homepage and service pages, but the old site already gets inquiries from searches for “small business tax preparation.” The goal is to improve the experience without accidentally removing the page that answers that query.

Before the redesign: establish what you need to protect

1. Crawl and record the existing site

Start by making a list of every indexable URL on the current site. A crawl tool can help, but for a small site you can also combine the XML sitemap, navigation, analytics landing pages and Search Console data. Include important pages that are not linked from the main menu.

For each URL, record its page title, H1, indexability, canonical URL, status code and intended replacement. Note whether the page has organic visits, conversions, useful backlinks or a role in the customer journey. A page with little traffic may still explain a service that customers ask about before they call.

Keep a copy of the current sitemap and, if possible, a crawl export. These provide a practical baseline for comparison after launch. They also help you catch pages that were missed when the new site was planned.

2. Identify pages and content worth preserving

Do not judge a page only by its last month of traffic. Look at a reasonable period, such as the previous year, and consider seasonal patterns. Check Search Console for queries and impressions, analytics for landing-page activity, and your sales or inquiry records for leads that began on the site.

Make three decisions for each old URL: keep it, combine it with another page, or retire it. If you combine pages, decide which destination best serves the old page’s visitors. If a page has no useful replacement, it may be better to return a genuine 404 or 410 than to send visitors to an unrelated homepage.

If an older article still attracts relevant visitors, consider updating it rather than removing it. Nomao’s guide to triaging and refreshing old blog posts can help you decide what needs a full rewrite and what only needs a careful update.

3. Decide whether URLs really need to change

Changing a URL creates extra work and risk, so do not do it just to make a redesign feel complete. If the existing URLs are clear, short enough and technically sound, keeping them is often the simpler option. You can update the design, navigation and content without changing the address of every page.

Sometimes a new structure is justified: perhaps several thin pages are being consolidated, or the old URLs are confusing and inconsistent. In that case, create a URL mapping before development begins. Every old URL should have a planned outcome: the same URL, a relevant new destination, or an intentional removal.

During the redesign: preserve meaning, not just appearance

4. Keep the purpose and useful substance of important pages

A redesign often brings pressure to shorten copy to fit a new layout. Editing is useful, but do not strip out the details that made a page relevant. Preserve the service area, audience, process, requirements, answers to common questions and other information that distinguishes the business from a generic competitor.

For example, a repair shop’s page about brake service may explain which vehicles it works on, what an inspection includes and how customers can book. Replacing that with “We offer expert brake services” may look cleaner, but it gives visitors less help and changes the page’s substance.

Keep the main topic and intent clear in the page title, heading and visible copy. You can improve wording, but avoid changing a page about one specific service into a broad page that mentions many unrelated services.

5. Plan redirects for every URL that changes

When a page moves, use a permanent server-side redirect—usually a 301—from the old URL to the closest relevant new page. Map redirects one-to-one where possible. Sending several old service pages to the homepage is rarely a good substitute for building appropriate destinations.

Google’s guidance on how redirects affect Google Search explains that redirects are a way to indicate that a page has moved. Google also advises site owners handling URL changes to prepare mappings and update links, as described in its site move guidance. These processes take time to be crawled, so a redirect is not a guarantee that search performance will remain unchanged.

Avoid redirect chains, such as old page A redirecting to B, which then redirects to C. Point A directly to C. Keep redirects in place for the long term, especially if old URLs may still appear in search results or be linked from other websites.

6. Check navigation and internal links

Make sure important pages remain reachable through clear navigation and relevant links within the site. A page can exist in the new sitemap and still be hard for people to find if it is buried or disconnected from related content.

Update internal links to point directly to the new URLs rather than relying on redirects. Check links in the header, footer, service pages, articles, buttons and downloadable resources. For a step-by-step approach, see Nomao’s guide to internal linking for a small website.

7. Preserve page-level search basics

For each important page, review the title tag, meta description, H1, image alt text and canonical URL. These do not all work in the same way: for example, a meta description can help describe a result to searchers, but it is not a reliable way to control rankings. The practical aim is to keep each page accurate, distinct and understandable.

Check that each indexable page has a canonical pointing to the preferred URL, usually itself. Confirm that the new site does not accidentally include staging-domain URLs or canonicals that point back to the old site. If the redesign changes language or regional versions, review those relationships separately rather than copying tags without understanding them.

Before launch: test the site in a safe environment

8. Make sure staging is private, but production is crawlable

Development sites should not be treated as public versions of the business site. Use access controls or an appropriate noindex setting to keep staging pages out of search results. Before launch, make a specific checklist item to remove those restrictions from production.

Check the robots.txt file, page-level robots directives and HTTP headers. One overlooked “noindex” setting can block an entire site or an important section. Do not rely on a robots.txt disallow as a way to keep a URL out of search results; it can prevent crawling while still leaving the URL discoverable in some circumstances.

9. Test redirects, links and page responses

Before launch, test every URL in your mapping. Confirm that old URLs return the intended permanent redirect and that the final destination loads successfully. Check for redirect loops, broken links, soft 404s and pages that unexpectedly return a 200 status while displaying an error message.

Test the site on a phone as well as a desktop. Review menus, forms, phone links, booking tools and consent notices. A technically valid page is not useful if a visitor cannot find the contact details or submit an inquiry on a small screen.

10. Compare the new pages with the old ones

Review a sample of high-value pages side by side. Ask whether the new version still answers the same search intent, includes the essential information and has a clear next step. Check that images have not become excessively large and that key content is not hidden behind interactions that are difficult to use.

Confirm that analytics and conversion tracking are still installed and that important events work. Test a real form submission, phone-number click or booking completion where possible. If your measurement setup is basic, record what you can reliably track before launch; Nomao’s guide to setting marketing goals when you cannot track every sale offers a useful way to think about that limitation.

Launch day: use a short, ordered checklist

1. Publish the production site and confirm the correct domain, HTTPS certificate and preferred hostname are working.

2. Remove staging-only password protection and noindex settings. Check robots.txt and representative page source or headers.

3. Run the redirect map and check a sample of old URLs, including the most important landing pages.

4. Check that internal links and canonical tags use the live URLs, not staging or obsolete addresses.

5. Submit or update the XML sitemap in Search Console and confirm it contains the intended canonical URLs.

6. Test forms, calls to action, analytics events and mobile navigation on the live site.

Keep the old URL list, redirect map and launch date together. If something goes wrong, these records help you distinguish a technical issue from a normal change in search demand.

After launch: monitor and fix problems in order

11. Check technical health first

In the first few days, crawl the live site and compare it with your baseline. Look for unexpected 404s, missing pages, redirect errors, blocked URLs and canonical mismatches. Use Search Console’s indexing reports and URL inspection for specific pages, but remember that reports may not update instantly.

If an important old page is now broken, fix the destination or redirect promptly. If a page is indexed with the wrong canonical, investigate the page markup, internal links and sitemap rather than repeatedly submitting the URL for indexing.

12. Judge performance over a sensible period

Compare organic clicks, impressions, landing pages and conversions with an appropriate period before launch. Account for seasonality and any marketing campaigns that changed at the same time. A short-term dip can happen while search engines process changes; it is a reason to investigate, not proof that the redesign has failed.

Look at page-level patterns. If the whole site loses visibility, check indexing, robots directives, server availability and migration settings. If only a few pages decline, compare their old and new content, redirects, internal links and search intent. Avoid making several major edits at once, because that makes it harder to identify what helped.

For a small business, the useful question is not simply “Did traffic go up?” Ask whether the redesign preserved the pages that attract relevant people, made the site easier to use and supported the actions that matter—calls, bookings, quote requests or sales. Search visibility is one part of that outcome, not the only one.

SEO checklist for website redesign: quick review

• Inventory current URLs and record their purpose, performance and intended destination.

• Keep valuable URLs where practical; map every URL that changes.

• Preserve the useful topic coverage and intent of important pages.

• Redirect moved pages to the closest relevant destination and avoid chains.

• Update internal links, canonicals, titles, headings and the XML sitemap.

• Keep staging private and verify that production is indexable.

• Test mobile usability, forms, analytics, status codes and redirects before launch.

• Monitor indexing and performance after launch, then investigate specific problems methodically.

Frequently asked questions

Will a website redesign hurt SEO?

It can, especially if useful pages disappear, URLs change without redirects, or the live site is blocked from crawling. A redesign does not automatically harm search visibility. Inventorying the old site, mapping changes and testing the new version reduces avoidable risk.

Should I keep my existing URLs during a redesign?

Keep them when they are clear and fit the new structure. Changing URLs adds migration work, so there should be a good reason, such as consolidating duplicate pages or correcting a confusing structure. If a URL changes, redirect it to a relevant replacement.

How long should I keep redirects?

Keep them for the long term. Old URLs may remain in search results, bookmarks or links from other websites. Removing redirects too early can send visitors and crawlers to dead pages.

How soon should I expect search performance to recover?

There is no fixed timetable. Crawling and processing vary by site, and results also depend on the scale and quality of the changes. Check technical issues promptly, then assess performance over a meaningful period rather than drawing conclusions from a few days of data.

What should I do if traffic drops after launch?

First check for site-wide technical problems: indexing blocks, server errors, broken redirects or incorrect canonicals. Then compare affected pages with their replacements and review Search Console data. Make targeted fixes rather than rewriting the whole site at once.