WordPress website redesign checklist for small businesses

A WordPress website redesign starts with a clear decision about what your business needs next. Keep the pages, content and customer journeys that still do their job, then define what needs to change.

This checklist covers the work before, during and after launch: choosing the scope, recording the existing site, planning URLs, checking inquiries and preparing the handover. Our Aloha Florals 808 and Birdsong Kyoto projects show why those details matter alongside the design.

Decide what the redesign needs to change

Write down one useful outcome, such as helping visitors understand your services or making a wedding inquiry easier to complete. Use that outcome to choose the work.

You may need more than one of these. Our guide to when a redesign needs workflow changes helps you trace the work beyond the public pages.

Record the existing WordPress site

Make an inventory before changing the theme or moving content. Include:

• Pages and URLs. Record service pages, posts, landing pages, downloadable files and language versions. Mark the pages customers use and any that bring relevant search visits.
• Content and assets. Identify useful copy, photography, logos and documents, their source files, and permission to keep using them.
• Customer actions. List forms, bookings, purchases, confirmation messages, saved records and notifications. Name the person responsible for the next step.
• WordPress dependencies. Note the theme, page builder if used, plugins, custom fields and connections that support those actions. Record which accounts own paid licenses.
• Accounts and access. Identify who controls the domain, hosting, WordPress, email delivery, analytics and Search Console. Share an account inventory during scoping; transfer access through an agreed secure method.

Search Console and analytics can help identify useful pages to retain. If the site has little reporting data, start with its sitemap, existing navigation and the pages your customers rely on. A redesign plan should name what is being retained as well as what is being replaced.

Carry the customer journey into the new design

For Aloha Florals 808, we brought flower photography and published pricing together so visitors can explore the work with a budget in mind. Wedding and lei inquiries ask different questions. For a site like this, a redesign needs to carry those service details and request-specific questions into the new layouts. A working homepage link is only the start of the check.

At Birdsong Kyoto, parents can read complete Japanese or English pages, choose an available trial date and receive a confirmation email in the language they used. The owner can keep both languages current through the editor. That journey gives the redesign team concrete things to check: language links, date choices, form details, email language and the owner's editing tasks.

Choose a journey from your own business and write down its steps. Decide what must carry over, what should improve, and what evidence will show that the new version works. This turns a broad request for a better website into a scope you can review.

Map URLs before changing them

Keep an existing URL when it still describes the right page. If a URL needs to change, record its relevant destination in a page-by-page map. Include important files and language routes as well as pages.

Permanent moves should use an appropriate permanent redirect. Send an old service page to its replacement; sending unrelated pages to the homepage can confuse visitors and search engines. Google's site-move guidance explains URL mapping and relevant destinations, while its redirect guidance explains the available redirect types.

Update internal links to the final URLs and check them after launch. If content has been removed without a suitable replacement, agree how its old URL will be handled. Include the redirect map and its checks in the build scope.

Prepare the build and handover

Use a separate development or staging environment so the new design can be reviewed before it replaces the live site. Keep that review environment out of public search, then check the production site's indexing settings at launch.

Back up the existing database and files, and agree how recovery will work. WordPress's migration documentation covers both. If new inquiries, orders or bookings continue during development, the launch plan must preserve those newer live records when the design is deployed.

Agree who supplies and approves content, who checks customer actions, and who can authorize launch. The handover should cover the editing tasks the owner will use, account ownership, ongoing software costs, maintenance responsibilities and the person to contact when something fails.

Check these items before launch

Use the checkboxes while reading, or copy the list into your project notes. Your selections are not saved.

• The approved services, prices, contact details and content are present on the right pages.
• Existing URLs are retained or have agreed destinations, and redirects reach the intended pages.
• Navigation, buttons, links and forms work on a phone and with a keyboard.
• Each inquiry or booking journey has been tested with agreed sample data, including what the customer sees and what reaches the team.
• Every published language version has working navigation, forms and the correct confirmation language where applicable.
• The owner can complete the agreed WordPress editing tasks with the correct access.
• Production pages can be crawled and indexed as intended, with correct preferred URLs (canonicals) and sitemap entries.
• The agreed analytics and inquiry events work with the site's consent choices.
• Newer live inquiries, orders, bookings and owner edits are preserved through deployment.
• Backups, recovery steps, launch approval and responsibility for issues are agreed.

Do we need to change hosting too?

Review the current hosting against the project's needs before deciding. A redesign may use the same host, while another project may need a different setup for reliability, support or technical requirements. Define the move, domain settings, email dependencies and recovery separately if hosting changes.

Should we change the domain at the same time?

Google recommends separating major changes where practical, such as a domain move, a change of publishing platform and a layout redesign. If a new domain is necessary, give its URL mapping, redirects, verification and monitoring their own plan. Keep the domain change out of scope when the current address still serves the business.

Review the site after launch

Check important pages, redirects and customer actions again on the live site. Look for missing pages, incorrect links, failed notifications and editing problems. Compare against the inventory and test plan you agreed before the build.

Review Search Console for crawling and indexing, and compare its page and query performance over useful periods. Search visibility can fluctuate as Google processes substantial changes. Combine those reports with genuine inquiries or bookings and note other changes that could affect the comparison. The new site's launch date alone does not demonstrate an SEO gain.

Plan your WordPress redesign

Bring your current website, the customer action that matters most, and the parts that are difficult to manage. We can help turn those into an agreed website design and redesign project, including content, implementation, checks and handover.

For the budget conversation, read what changes the cost of a small-business website. When you are ready, tell us about your website. Your current URL and priorities are enough to begin.