Chillax TechieHK · DIGITAL
ATELIER

SEO Practice · 2026-10-14

Website Redesign SEO Checklist: Redirects and Launch QA

Website redesign SEO should start before the new site goes live. A redesign can change URLs, page content, navigation, and technical settings. If an old page still earns search visits, has useful links, or is used by customers, decide how the new site will handle it before launch. This checklist is designed for the people coordinating design, development, and marketing.

The short version: keep valuable URLs when practical. When a URL must change, map it to the closest relevant replacement, test a direct permanent redirect, and review canonicals, internal links, the sitemap, and Search Console. A redirect cannot guarantee unchanged rankings, but a clear map helps people and search engines avoid dead ends.

On this page

1. Define what is changing

Write down the scope rather than treating every project as “a new design”:

  • Visual refresh only: URLs and core content remain mostly the same. Check that titles, body copy, links, and working features survive the new templates.
  • Navigation or content restructuring: pages may be combined, split, or rewritten. Decide which new page best serves each old page’s purpose.
  • URL, domain, or language-path changes: prepare a URL map and test redirects; update the sitemap, canonicals, hreflang where used, and internal links.
  • Platform or hosting change: test robots rules, HTTPS, forms, analytics events, and server responses as well as URLs.

If the project only needs a visual refresh, avoid changing many URLs at the same time without a clear reason. Each extra change adds another variable to test. Save the old URL inventory, key template screenshots, important form flows, and whatever search-performance baseline is available before work begins.

2. Inventory old URLs and map redirects

List important old URLs: service pages, articles, portfolio pages, language versions, and any older pages that people or external sites still use. Sources may include the old sitemap, a site crawl, Search Console page data, analytics reports, and internal links. If a source is unavailable, note that the inventory may be incomplete rather than assuming it is exhaustive.

| Old URL | New URL | Action | Reason for mapping | Test result | | --- | --- | --- | --- | --- | | /old-service | /services/example | Direct 301 redirect | New page covers the same service | To test | | /old-guide | /insights/new-guide | Direct 301 redirect | New article answers the same need | To test | | /old-event | — | 404 or 410, as appropriate | Expired and has no relevant replacement | Confirm |

These are illustrative rows, not real site URLs or decisions. Map pages individually: an old service page should lead to its relevant new service page, and an old article to the closest useful article. Do not send every removed URL to the homepage; it may not answer the visitor’s original question.

Google treats permanent server-side redirects as an important signal. When a genuinely equivalent new URL exists, use a permanent redirect with a clear destination. For content that is gone and has no sensible replacement, use the correct removal response rather than pretending the homepage is the same page. See Google Search Central’s site-move guide and its guidance on redirects and Google Search.

3. Run pre-launch checks

Confirm important pages still exist and meet the same need

Compare old and new versions page by page. Check key services, pricing or packages, contact paths, work samples, articles, and policy pages. When pages are combined, make sure the new page retains useful answers from the old ones; there is no need to copy outdated or repetitive material just to preserve every sentence.

Prepare and test redirects

Configure redirects early enough to test them in a staging or preview environment. Confirm each old URL reaches the closest relevant new page directly, without an avoidable A-to-B-to-C chain. Test trailing slashes, language versions, case handling, and query parameters where they matter to real site behavior. Do not test only the homepage.

Check canonicals, language versions, and internal links

Each new page should identify the correct preferred URL. Chinese and English versions should point to the correct corresponding language pages. Update navigation, articles, buttons, images, and breadcrumbs to the new paths instead of making visitors pass through old URLs. Google considers multiple signals when selecting a canonical; a canonical tag is not a universal fix for a broken redirect or an unrelated destination. Read the official canonicalization guidance.

Keep the test site from replacing the live site

Protect staging with access controls or noindex as appropriate, then remove staging-only restrictions before the production launch. On the live site, review robots.txt, page robots metadata, canonicals, and the sitemap to make sure they refer to the production HTTPS domain.

Prepare the sitemap, forms, and analytics QA

The new sitemap should contain the intended production URLs—not staging pages, removed pages, or redirect sources. Submit a test enquiry through the complete form flow and confirm the success message and notification route work. If analytics events are configured, verify that a successful submission is counted once. Never send names, email addresses, or phone numbers entered by visitors to Google Analytics.

For a broader technical foundation, see the Hong Kong SME website SEO checklist. To scope the search work or a wider redesign, compare the SEO service with the website packages and pricing.

4. QA the launch

Select representative URLs: the homepage, each service type, articles, portfolio pages, and both Chinese and English pages. Check each one:

  1. The new URL returns a normal success response; an old URL that should redirect lands directly on the correct new page.
  2. The page works on mobile and desktop, including its main copy, images, navigation, and calls to action.
  3. The H1, title, description, and page content agree; canonicals and hreflang point to production URLs.
  4. Images load, and important internal links do not point to the old site, a staging site, or a dead path.
  5. robots.txt, the sitemap, and indexability settings match the launch plan.
  6. A test enquiry succeeds, the confirmation is clear, and the notification has an owner.

Record the URL, device, date, result, and owner. “Tested” without a list of what was checked is difficult to investigate when something breaks.

5. Monitor after launch

Use Search Console to review indexing status, URL Inspection, and the Page indexing report for old and new URLs; submit the updated sitemap when appropriate. Watch for 404s, redirect errors, blocked pages, canonical selection, and important landing pages. Also test the real visitor journey from a service page through to a working enquiry form.

Search visibility can fluctuate during a migration. Do not interpret a single day’s increase or decrease as proof of success or failure. First verify the technical setup and important content, then compare equivalent date ranges for organic clicks, impressions, key landing pages, and confirmed qualified enquiries. Redirects help preserve URL continuity; they are not a ranking guarantee.

Copyable website redesign SEO checklist

  • [ ] Record the domains, URLs, languages, platform, and content included in the redesign.
  • [ ] Save a list of important old URLs, including service pages, articles, and portfolio pages.
  • [ ] Give every changed old URL a clear new destination or an appropriate removal response.
  • [ ] Test redirects individually; avoid unnecessary chains and blanket homepage redirects.
  • [ ] Verify production canonicals, hreflang, robots directives, and sitemap URLs.
  • [ ] Update navigation, articles, images, and calls to action to the new paths.
  • [ ] Test mobile pages, forms, notifications, analytics events, and key journeys with test data.
  • [ ] Schedule post-launch Search Console checks for indexing, 404s, and key landing pages.

For search foundations, explore the SEO optimization service. If the redesign also changes the full site, list the required pages, features, languages, and handover scope before you review website packages or discuss the project.

Want to know how your business's SEO foundation stacks up right now?

Learn about our SEO service