WooCommerce uses different designated pages for different parts of the shopping journey. After a redesign, those pages may look good while settings still point to an old destination. Check both content and assignment. The page title alone does not determine which page WooCommerce uses for a particular task.
Map the functional destinations
Record the pages used for the shop, basket, checkout and account. Then open the settings and compare the assignments with the intended pages. The official WooCommerce documentation explains where the different pages are configured and why basket, checkout and account must have separate destinations.
Use a simple overview containing function, title and address. This reveals duplicate names. A page called “New checkout”, for example, may only be a design version while the public route still leads to the original page. That is not automatically wrong during preparation, but must be deliberately resolved before launch.
Check each page through the shopping journey
Assignments for basket, checkout and account are under WooCommerce, Settings, Advanced. The shop page is selected in the product settings. This explains why not all destinations appear in the same overview. Always compare the selected page with its actual content and address before saving a setting; two pages may have almost identical titles.
In a fictional shop, the account page has been redesigned. A manual click from the menu opens the new version, but another link in the shop still uses the old assignment. Testing only the menu would miss that difference. Follow the routes WooCommerce itself provides.
Add an item, open the basket and proceed to checkout. Check an account task with a test user. Also start from a direct product link. The destination must function correctly, rather than merely be reachable from the homepage.
For a WooCommerce redesign this check belongs in the transition from design to working shop. Functional content must fit the setup in use, including the chosen basket and checkout formats. A visually recreated page cannot replace the required behaviour.
Only remove duplicate pages after assessment
An old page may still appear in menus, emails or external links. Decide which destinations must remain current and which old routes need an appropriate successor. Do not delete a page solely because a new design now exists. Check assignments and links first.
Also consider the shop page as a product overview. Its presentation may differ from an ordinary content page. Discuss with the developer which template or shop view determines the content. Otherwise, an editor may change text somewhere that does not control the visible result.
Keep a small functional map
After delivery, record the final pages and their roles. Add the most important test actions. New employees can then see which pages are freely editable content and which have a fixed shop role. This prevents unintended changes during a later content clean-up.
- Each fixed task has its intended assigned page.
- The shopping journey reaches that page without detours.
- Menus and internal links match the assignment.
- Old design versions have been deliberately dealt with.
- A test user can complete the relevant tasks.
Discuss uncertainties through a targeted technical review before merging or removing pages. The result need not be a complicated document. A clear overview of functions and destinations makes the webshop easier to hand over and supports future changes without accidentally breaking the basic routes.