Website Redesign Checklist: 12 Steps Before You Relaunch
- Arcitech
- 8th November 2026
1. Define the Business Problem and Success Measures
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
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
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
| 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 |
5. Preserve Search Intent and Page Signals
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
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
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
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
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
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
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
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