Use this WordPress website redesign checklist to protect search visibility when rebuilding an existing site. Keep valuable URLs where possible, map changed URLs to relevant replacements, check the live site’s index settings and lead forms, and compare the same pages in Search Console after launch. A more polished design can still lose enquiries if an old landing page goes missing or a form stops working.
This checklist is for small-business owners rebuilding a site in place or moving an existing site to WordPress. Start with the website planning checklist if the new page list is still open. If you need a baseline for the existing site, use the WordPress SEO audit checklist before planning the move.
Record which pages already earn visits or enquiries
- Export the Pages report in Search Console. Start with the latest complete 28 days and compare the preceding period. Save page-level clicks and impressions before launch.
- Identify landing pages that lead to enquiries. Use your analytics and existing lead records where available. Note which pages receive referral links or get used in campaigns, even if their organic traffic is low.
- Save a working inventory. Record each old URL, page purpose, current status code, title, canonical, and a decision to keep, move, merge, or remove it. Add relevant PDFs and files that receive links or visits. Flag pages with external backlinks, campaign use, or important internal links so they receive an explicit destination decision.
For a service business, protect the pages where visitors book, call, or ask for a quote. An old blog URL with a strong referral link can also be worth keeping even if it looks minor in the menu.
Create the old-to-new URL map before building redirects
Keep an existing URL if the page still serves the same purpose and there’s no good reason to move it. For a permanent move, send the old URL directly to the closest useful replacement with a server-side 301 or 308 redirect. If several pages are merged, redirect them only when the new page genuinely covers their subject.
| Current URL path | Final path | Expected response | Launch check |
|---|---|---|---|
| /services/ac-repair/ | /services/ac-repair/ | 200 at the same URL | Copy, internal links, and self-canonical are correct. |
| /ac-installation/ | /services/ac-installation/ | 301 or 308 to the final URL | One redirect. Final page loads and serves the same purpose. |
| /blog/expired-rebate/ | None | 404 or 410 | No useful replacement. Remove the URL from the sitemap and internal links. |
Add two columns to your working copy for the owner and the actual launch result. Update internal links to point straight to the final URLs. For a site move with changed URLs, Google recommends leaving redirects in place for at least a year. Google Search Central’s URL move guidance covers mapping and rollout.
Use a phased redesign launch checklist
Turn the URL map into a release checklist. Each phase should have a named owner, a piece of evidence, and a clear pass or fix status. A small business can use this simple handoff table without buying a specialist project tool.
| Phase | Checks to complete | Owner and evidence |
|---|---|---|
| Before design and build | Save the Search Console page and query baseline; inventory important URLs, titles, canonicals, backlinks, forms and campaign landing pages; approve what stays, moves, merges or retires. | Business owner and SEO lead; dated export and approved URL map. |
| On staging | Compare priority-page content, headings, titles, descriptions, canonicals and internal links; test mobile navigation, enquiry routes, analytics and integrations; keep staging access restricted. | Developer and content owner; staging QA record and issue list. |
| At cutover | Apply one-hop permanent redirects for moved URLs; verify final pages return successfully; remove staging blocks only from production; check the sitemap, forms, inbox delivery and analytics. | Developer and business owner; redirect test, live-page checks and a labelled enquiry receipt. |
| First 48 hours and following month | Review redirect failures, 404s, index settings, form delivery and Search Console coverage; compare the same important pages with the saved baseline and investigate individual losses. | SEO lead and enquiry recipient; dated monitoring notes and confirmed test results. |
A site that keeps the same URL does not need a redirect just because its design changed. Redirect only when an address has genuinely moved, and do not send unrelated old pages to the homepage as a substitute for a relevant destination.
Protect staging and plan a rollback
- Restrict staging access. Keep the work-in-progress site behind authentication. Check that production pages are accessible once the new site goes live.
- Check the handoff. Agree who controls DNS, hosting, WordPress administrator access, analytics, and the redirect rules. Save a copy of the old URL map and working forms.
- Know how to restore the site. Confirm who can restore the files and database and what would trigger a rollback. Decide how any leads or orders received after launch would be preserved.
Run the launch checks on the real domain
- Open priority URLs and confirm their responses. Old moved URLs should redirect once to a relevant page. Final pages should return 200 and use the intended canonical URL.
- Check index settings and the XML sitemap. Verify that important live pages are crawlable and that staging URLs, redirects, and confirmation pages are excluded from the sitemap. Check that an accidental staging noindex has not carried over.
- Test the enquiry path on mobile and desktop. With permission, send a clearly labeled test submission. Confirm that it reaches the intended inbox and that the success message, redirect, and measurement behave as expected.
- Check shared site components. Test navigation, internal links, click-to-call links, images, tracking tags, and the pages people reach from ads or partner links.
For an important page, use Search Console’s URL Inspection tool to see the indexed status and run a live test. Check the sitemap and internal links for discovery. A live test checks eligibility and a request asks Google to recrawl. Google’s URL Inspection instructions explain the distinction.
Watch specific pages after launch
Check the important redirects, index settings, 404s, and form delivery in the first 48 hours. Over the next week and month, compare clicks, impressions, and enquiries against your saved baseline for the same landing pages. Look for isolated page losses before changing the entire site. Search traffic can fluctuate while Google recrawls changed URLs.
Do I need redirects if I keep the same URLs?
No. If the address stays the same and the page remains live, leave it at that address. Check its content, title, canonical, and internal links. Add a redirect only when the destination has actually moved.
What should I ask a WordPress redesign provider to quote?
Ask for the URL inventory, redirect map, launch checks, rollback responsibilities, and post-launch monitoring as separate deliverables. Use the WordPress website cost guide to compare one-time project work and ongoing costs.
Plan your WordPress redesign with Zevon
Share your current URL, the pages or enquiries you want to preserve, and your target launch window. See Zevon’s WordPress design and development service or send a redesign brief.

