Home » Articles » Website Redesign Checklist: 12 Steps Before You Relaunch

Website Redesign Checklist: 12 Steps Before You Relaunch

website-redesign-checklist
A website redesign checklist helps your team preserve useful content, maintain working customer journeys, and verify technical changes before a new site goes live. It should cover more than visual approval: URLs, search signals, structured data, forms, tracking, and release ownership all need attention. Use these 12 steps to connect the website development process with launch evidence. Assign each step an owner, a completion status, and a link to its test results. Schedule production checks before approving the release, rather than treating launch day as the end of the project.

1. Define the Business Problem and Success Measures

State what the redesign must improve: clearer service positioning, qualified enquiries, completed purchases, or easier self-service. Avoid treating a new appearance as the only objective.
Record baseline conversion rates, lead quality, and task completion for important journeys. Choose measures that connect the design to business outcomes, with named owners for reporting.

2. Inventory Pages and Protect Valuable Content

Combine a crawl with CMS records, analytics landing pages, Search Console data, and known campaign destinations. Include downloads and other linked assets.
Identify pages that contribute enquiries, useful information, or referral visits. Review content before removing it; low recent traffic alone does not establish that a page has no business purpose.

3. Finalise Navigation and Content Responsibilities

Map services, audiences, and customer questions into a clear information structure. Decide which pages stay, merge, change, or retire.
Assign someone to approve each page’s copy, claims, CTA, and supporting evidence. For example, merging two service pages should preserve the information that helps their respective buyers make decisions. This is an illustrative planning scenario, not an Arcitech case study.

4. Build the URL and Redirect Map

Keep useful URLs where possible. For changed addresses, document the relevant replacement and use a permanent server-side redirect, such as 301 or 308. Avoid sending unrelated retired pages to the homepage.

Old URL decision Expected handling
Keep the page and address Serve the intended content successfully
Move or merge content Redirect to its relevant replacement
Remove without replacement Return an appropriate 404 or 410
Test the map for loops and chains. Google recommends keeping migration redirects for at least a year, generally longer where useful.

5. Preserve Search Intent and Page Signals

Review titles, descriptions, headings, and important page content against each page’s purpose. A shorter design should still answer the questions that qualify a buyer.
Check canonical URLs, language alternatives where used, and internal links. Google’s site-move guidance recommends updating these references to their intended destinations. Confirm template defaults do not point production pages to staging or obsolete addresses.

6. Audit and Rebuild Structured Data

Inventory existing schema by page type. Decide which entities remain accurate after the redesign rather than copying every old markup block.
Check organisation details, article authors, breadcrumbs, image URLs, and page references. Resolve duplicate entities created by overlapping plugins and templates. Structured data must describe the page accurately and match visible content, following Google’s guidance.
Use a schema validator for syntax and vocabulary checks, then the Rich Results Test for Google-supported features. Neither guarantees eligibility or display. Give schema checks their own owner in the launch plan.

7. Protect Staging and Review Production Indexing Rules

Use access controls to restrict staging, and review any indexing directives deliberately. A robots.txt block alone does not reliably prevent a URL appearing in search results.
Prepare an environment checklist for passwords, robots rules, meta directives, headers, canonical hosts, and asset paths. At launch, verify production is accessible and indexable where intended while staging remains protected. Do not remove intentional exclusions indiscriminately.

8. Test Accessibility and Mobile Journeys

Review navigation, keyboard operation, visible focus, form labels, error messages, and readable contrast. Test important flows at mobile widths and with assistive technology where appropriate.
Include real content rather than placeholder text. Check long headings, validation errors, menus, tables, and embedded tools. A visually polished homepage cannot compensate for an inaccessible enquiry form.

9. Verify Performance and Integration Reliability

Test representative page templates and important journeys on realistic devices and connections. Investigate slow images, unnecessary scripts, layout shifts, and blocked interactions.
Exercise CRM connections, search, chat, bookings, payment flows, and other relevant integrations. Include timeouts and failed submissions. Confirm that retrying an action does not create duplicate orders or leads.

10. Validate Tracking and Actual Lead Delivery

Document events and their business meaning before changing templates. Test analytics, tag triggers, consent behaviour, campaign parameters, and conversion deduplication.
Submit a clearly labelled test enquiry and verify receipt in the destination system, assignment, and any authorised notification workflow. Confirm successful submissions are measured only after success. A button click is not proof that a lead reached your team.

11. Approve the Launch and Rollback Plan

Name the release owner, decision-makers, and escalation contacts. Back up the application, content, database, configuration, and redirect rules, then verify restoration procedures.
Define launch-blocking issues, a deployment window, and the checks required immediately afterward. Explain how new submissions and orders will be preserved if rollback becomes necessary. Restoring an old database without reconciling new transactions can create data loss.

12. Run Production Checks and Monitor the Relaunch

Make Relaunch Approval Evidence Based

Complete the website redesign checklist before approving launch, with step 12 scheduled and owned. Treat release as a controlled handover followed by live verification.
Arcitech’s website development services cover responsive websites and web applications aligned with business workflows and growth goals. Discuss your redesign requirements to plan the build, integrations, and launch checks together.

Relaunch Your Website with Confidence

Plan your redesign around user journeys, search visibility, and technical checks. Build a website that’s ready for launch and easier to maintain.

Frequently Asked Questions

1. Does every redesign require redirects?

No. Redirects are needed when addresses move or content is consolidated into relevant replacements. A visual change with stable URLs may not require a migration.

2. Should all old schema be retained?

No. Keep or rebuild markup that accurately describes the current pages. Remove outdated, irrelevant, or conflicting entities.

3. Can a redesign guarantee better rankings?

No. Content, competition, technical implementation, and other factors affect visibility. Use baselines and monitoring to assess results.

4. Is a staging crawl enough?

No. Production configuration and integrations can differ. Repeat critical checks after deployment.

5. When should tracking be tested?

Test during development and again on production, including successful submissions and destination-system receipt.

6. What should delay a relaunch?

Examples include broken critical journeys, incorrect access controls, missing essential redirects, or an untested recovery process. Agree project-specific blockers in advance.

Check out our Social Media

Related Articles