WordPress Website Redesign Checklist for Small Businesses

This WordPress website redesign checklist helps small businesses plan a better website without overlooking existing content, search visibility or customer enquiries. It covers eight steps, from defining the scope to testing and launch.

A successful redesign should make your services easier to understand, your website easier to use and your content easier to manage. Whether you run a service business or a WooCommerce store, use the checklist below to brief your developer and assess the finished work.

1. Define your WordPress redesign goals

Start with the business problem behind the redesign. Are visitors struggling to find the right service? Is your team spending too long making simple updates? Are potential customers abandoning an enquiry form? Each problem calls for a different solution.

Choose one primary outcome, such as more qualified enquiries, a simpler buying journey or easier content management. Then decide how you will assess it.

A useful redesign brief explains what customers and your team should be able to do more easily when the project is finished.

If only one page or one form is causing trouble, a focused improvement may be enough. Ask your developer to explain why a full rebuild is needed before committing to one.

2. Audit your existing website before redesigning

Create an inventory of your existing pages. Include service pages, product categories, blog posts and landing pages used in advertising. Record each page's current URL and decide whether to keep, improve, combine or remove it.

Where available, use analytics and Google Search Console to identify pages that bring relevant visitors and enquiries. Preserve useful information on those pages as you improve their layout.

If tracking is not set up yet, start collecting a baseline now. Use customer feedback and enquiry records to guide initial decisions. Missing data does not prove that a page has no value.

Before development starts, collect:

• A list of existing URLs and their proposed destinations.
• Current page copy, images and downloadable files.
• Page titles and meta descriptions.
• A list of plugins, licences and external integrations.
• Details of forms, bookings, payments and email delivery.

This inventory helps prevent useful content or business functions from disappearing during the redesign.

3. Agree the scope before comparing quotes

Two quotes for a “five-page website” can cover very different work. One may include copywriting, mobile testing and migration; another may cover layout changes only.

Give each supplier the same brief so you can compare what is included. A useful WordPress redesign scope should cover:

• Pages and templates: the required pages and reusable layouts.
• Content: who supplies copy, photographs, product information and approved testimonials.
• Features: forms, bookings, payments, search and integrations.
• Migration: content and data that must be preserved.
• Testing: customer journeys, devices and functionality that must be checked.
• Approvals: who signs off the work and how many revision rounds are included.
• Ongoing costs: hosting, licences, maintenance and external service charges.

For example, a service business might need four service pages, a reusable case-study layout and an enquiry form connected to its CRM. That gives a developer a clearer starting point than a request for a website that simply “looks premium”.

4. Choose how your team will edit WordPress

Elementor, the WordPress block editor and custom development can each suit different projects. The right choice depends on your layouts, existing dependencies, editing skills and support arrangements.

Ask for a demonstration of everyday tasks before agreeing the approach:

• Changing a heading or service description.
• Replacing an image without breaking the layout.
• Adding a page using an existing template.
• Publishing and formatting a blog post.
• Updating a product, price or variation if you run a store.

Check whether reusable styles keep new pages consistent. A website that requires developer help for every small change may not suit a busy small team.

Also ask which plugins are essential and who owns their licences. Changing the editing system can mean rebuilding existing layouts, so include that work in the scope.

DevSpin's WordPress development service covers website builds, customisation and ongoing support.

5. Improve mobile usability and customer journeys

Each important page should answer three questions: what do you offer, who is it for, and what should the visitor do next?

Use descriptive headings, specific service information and a clear call to action. Keep enquiry forms short enough to complete while collecting the details your team needs to respond.

Review the website on a real phone. Check that:

• Navigation opens, closes and works without covering essential content.
• Text is readable without zooming.
• Buttons and links are easy to select.
• Forms have clear labels and useful error messages.
• Content fits the screen without unwanted horizontal scrolling.
• Contact details and the next step are easy to find.

Test keyboard navigation, visible focus indicators and colour contrast too. These checks help uncover barriers that a desktop design mockup can miss.

For international customers, make your service coverage, contact options and any displayed currency clear. For eCommerce, explain delivery information and the buying process before asking customers to commit.

6. Protect content and SEO during your redesign

Keep existing URLs where they still make sense. If a URL must change, map the old page to the closest relevant replacement and implement an appropriate permanent redirect.

Avoid sending every removed page to the homepage. Someone following an old service link should reach a relevant destination wherever one exists.

• Preserve useful page content and descriptive titles.
• Update internal links to point directly to the final URLs.
• Check canonical references and the XML sitemap.
• Confirm that important production pages are accessible to search engines.
• Check that staging restrictions have not been carried across accidentally.
• Test redirects from changed URLs.

Google's site-move guidance explains URL mapping and redirect checks. Search visibility may fluctuate while changed pages are reprocessed.

A cleaner layout is not a reason to remove information customers need. No developer can guarantee that a redesign will preserve every ranking or produce a particular search position.

7. Build safely and test complete journeys

Take a backup of the database and website files, confirm how it can be restored, and use a protected staging copy for development.

If the project also changes hosting or site location, WordPress's migration documentation provides a useful technical reference.

Test enquiries from beginning to end

Open a service page, follow the contact button, submit the form and check the confirmation. Then verify that the enquiry reaches the correct inbox or CRM.

A success message alone does not prove that your team received the enquiry. Check required fields, invalid entries and error messages as well.

Test the WooCommerce purchase process

Use the payment provider's test mode where available. Check successful and failed payments, order emails, shipping options and relevant product variations.

Plan how new orders and customer records will be protected during deployment. An older staging database must not overwrite recent live transactions.

Check performance and layout stability

Review representative pages for loading performance, broken links, missing images and unexpected layout movement. Optimise unnecessarily large images and review scripts or plugins that add weight.

Assess changes against real customer journeys. A performance score is useful diagnostic information, but the website must also work reliably for visitors.

8. Plan launch, handover and maintenance

Name the person responsible for launch, the rollback decision and the final checks. Confirm that business owners control the domain, hosting and appropriate administrator access.

Store credentials securely and give each person only the access needed for their role.

Your handover should explain:

• How to edit pages and publish content.
• Who manages WordPress, theme and plugin updates.
• How backups are created and restored.
• Which licences and subscriptions need renewal.
• How long launch support lasts.
• What counts as a defect and how future changes are quoted.

Check forms, orders and tracking immediately after launch. Review enquiries and search performance over subsequent weeks against your baseline, allowing for traffic levels and seasonal changes.

Keep this WordPress website redesign checklist with your project brief. It gives your team and developer a shared reference for what needs to be completed and checked.

Frequently asked questions