A WordPress redesign should make your business easier to understand and contact. But a cleaner homepage is only part of the job: customers still need to reach the service pages, articles and downloads they already know.
This WordPress redesign SEO checklist helps you plan what stays, what moves and what needs checking before launch. It is a practical risk-reduction process, not a promise to preserve every ranking. Official documentation reviewed on 2 November 2026.
1. Record what the current website does well
Before reviewing mockups, make a simple inventory of important pages. Include the service or product pages that generate enquiries, useful articles, popular downloads and landing pages linked from campaigns. Ask whoever manages analytics and Search Console for the evidence available, then record the date range so later comparisons are meaningful.
For each page, note its address, purpose, main heading, page title and next step. Keep a screenshot or content copy for reference. This gives your designer a brief based on business needs rather than a folder of visual inspiration alone.
For example, a specialist repair page may look dated but answer exactly the questions prospects ask. Its new design can improve the presentation while retaining those useful answers and the enquiry route. Do not remove it simply because the new navigation has fewer items.
2. Agree which URLs need to change
A visual refresh does not automatically require new page addresses. As a practical planning choice, keep a useful existing URL unless there is a clear reason to change it. Separate design preferences from necessary changes to the site structure.
When addresses do change, prepare an old-to-new map before launch. Include relevant images and downloads as well as pages. Google’s site-move guidance describes URL mapping and recommends avoiding several major changes at once where possible.
| Illustrative situation | Decision to document |
|---|---|
| A service page gets a new layout | Keep its existing address if it still describes the service |
| Two overlapping guides become one stronger guide | Identify the relevant destination for each old URL |
| A brochure PDF has been shared with customers | Keep the download reachable or map it to the appropriate replacement |
| An old service is genuinely discontinued | Decide whether a relevant replacement exists; do not invent one |
3. Test redirects as journeys, not just settings
For a permanent move, Google recommends a permanent server-side redirect where possible, such as HTTP 301 or 308. See its redirect documentation. Ask your developer or host which method fits your setup rather than pasting generic server rules into production.
Open each important old address and confirm it reaches the intended final page directly. Look for loops, unnecessary intermediate stops and destinations that return errors. Check a sample of older campaign links and bookmarked downloads too.
Do not send every removed page to the homepage. A visitor searching for a specific service needs a relevant destination. Google warns against irrelevant mass redirects and recommends retaining move redirects for at least a year, and longer where useful. Keep that maintenance responsibility in your handover, following the migration guidance.
4. Carry useful content and page signals into the new design
Review the new version page by page. Has the explanation of the service survived? Are important specifications, location details and answers still present? Can someone identify the next step without opening several menus? Treat content removal as an editorial decision, not an accidental consequence of a shorter template.
Check that pages have descriptive titles rather than a repeated generic label. Google’s title-link guidance recommends concise, descriptive title text. A service name and business context are more useful than “Page 3” or an identical title across the website.
Ask your developer to review canonical tags, which indicate the preferred address among duplicate or similar pages. Production pages should not accidentally identify the staging domain as their preferred location. Align internal links and sitemap URLs with the intended live addresses. Google explains these signals in its canonical URL documentation.
5. Separate staging protection from launch visibility
Protect the development copy from unintended access. WordPress has a search-engine visibility setting under Settings → Reading, but its documentation makes clear that this does not block visitors. Use appropriate hosting access controls for a private staging site.
Before launch, check the live site for development restrictions. Inspect both page metadata and HTTP headers for unintended noindex rules, and review crawling restrictions. Google must be able to crawl a page to see its noindex rule; blocking it in robots.txt is not an equivalent instruction to remove it from search. See Google’s noindex explanation.
6. Run a focused launch checklist
- Confirm a recoverable backup and a named person responsible for launch decisions.
- Check important old and new URLs, including downloads and redirected pages.
- Review headings, titles, canonical addresses and intended indexing rules.
- Test menus, images and contact actions on desktop and mobile.
- Submit a controlled test enquiry and confirm it arrives where expected.
- For WooCommerce, test product selection, payment and the post-purchase outcome.
- Record the launch time and any known issues for follow-up.
Use the existing backup and recovery guide and checkout testing checklist for those parts of the work. A homepage review alone cannot confirm that a business website is ready.
7. Monitor after publication
Submit the current sitemap in Search Console and inspect a few priority URLs. Google supports individual recrawl requests through URL Inspection and sitemap submission for larger sets of pages. Neither guarantees immediate crawling or inclusion; repeated requests for the same URL do not speed the process up. See the recrawl guidance.
Compare enquiries, important landing-page visits and indexing reports with your baseline. Investigate broken journeys and unexpected exclusions before attributing every change to the new design. Search visibility can fluctuate after significant site changes, so assign someone to review the evidence and resolve specific problems.
Planning a redesign? Explore WordPress development and website support, or tell me what needs to improve on your website.