Website Redesign Checklist for an Existing Business
How to improve an old website without throwing away useful rankings, domains, email, analytics and content.
A redesign can improve a website dramatically, but it can also damage useful search visibility if the old site is replaced without understanding what Google and customers already know about it. The safest redesigns separate the visual problem from the assets worth keeping.
Before changing the design
- Export Search Console page and query data
- List indexable URLs and current redirects
- Identify pages with backlinks, impressions and enquiries
- Record analytics and conversion tracking
- Understand the domain, DNS, hosting and email setup
- Identify forms, integrations and third-party scripts
Keep the intent, not necessarily the old layout
A ranking service page can be completely redesigned while retaining its URL and core topic. Redesigning does not mean deleting everything that already works.
Do not move the domain just because the site is moving
Domain registration, website hosting and business email are separate. If the registrar and email service work well, a new website can often be connected without moving either of them.
Use redirects carefully
If a page genuinely moves, redirect it to the closest relevant replacement. Sending every deleted URL to the homepage is poor for both visitors and search engines. Keep the redirect map small, intentional and testable.
Preserve tracking and proof
Analytics, Search Console, review links, call tracking and other measurement tools should be understood before launch. A redesign should not create a period where nobody knows whether enquiries are working.
A practical launch checklist for a website redesign
Keep a written acceptance checklist alongside the design feedback. Test the public, logged-out website as well as the version you see while signed into WordPress. Cached pages, mobile navigation and real form delivery can behave differently from an editor preview.
1. Test important URLs and redirects
Open the pages that already receive search impressions, enquiries or links. A retained page should load normally. A moved page should lead directly to its relevant replacement, not an unrelated homepage or another redirect. Check old service and campaign URLs too; a redesign can look complete while those still lead to errors.
2. Check what search engines are allowed to see
Confirm that staging restrictions have not carried onto the live website. Review robots directives, canonical links and sitemap entries for the pages you want indexed. A sitemap entry is a discovery aid, not proof that Google has indexed the page. Check actual indexing through Search Console where access is available.
3. Complete the customer journey
Submit a clearly labelled test enquiry and confirm that it reaches the expected inbox and lead record. Test required fields, error messages, the success screen and a repeat page load. For an online shop, use the payment provider’s test environment to check checkout, delivery rules and customer notifications without creating an unintended charge.
4. Test consent and measurement separately
The form should work whether a visitor accepts or rejects optional tracking. Check that a successful enquiry is not counted merely because someone clicks a button or reloads a thank-you page. Keep enquiry records, advertising events and analytics reports distinct: consent choices can make their totals differ.
5. Check mobile layouts and performance
Try navigation, forms, images and buttons on a narrow screen. Look for content moving as images load, hidden calls to action and fields that are awkward to complete. Performance scores can help diagnose problems, but a score alone does not show whether a customer can complete the task.
6. Keep a rollback and monitoring record
Record the launch date, the changes made and who can restore the previous website and database. Compare search performance using consistent periods and page groups after launch. A short-term change should be investigated in context rather than automatically blamed on the redesign.
Example: protecting a specialist vehicle website
A business with vehicle sales, repairs and technical advice may have several distinct entry points from Google. Replacing all of them with one attractive services page would remove useful detail. The better brief identifies which URLs and topics to retain, then improves how customers move between them. See the Mazda Bongo Auto Centre redesign project for relevant specialist website work.
For a store, read about WooCommerce website design and redesign. For a service business, our website redesign service starts by reviewing the assets and pages worth keeping.
When a rebuild is actually justified
Repeated layout limitations, slow mobile performance, an unmaintainable theme, poor content structure, broken integrations or a brand that has significantly outgrown the site can justify a deeper rebuild. The decision should come from the problem, not the agency’s preferred platform.
Questions to ask your redesign agency
- Which URLs are you keeping?
- How will redirects be tested?
- What happens to the current domain and email?
- How will forms and tracking be verified?
- How will useful content be migrated?
- What is the rollback plan?
