Changing use_verbose_page_rules is no longer a useful fix for a Shop child-page routing problem in WooCommerce 11.2. Identify the intended page and the competing URL patterns before changing permalinks or adding redirects.
What changed
WooCommerce now determines Shop child-page rewrite behavior from the Shop path and product base when generating rules; it no longer uses the old option to make that decision. This is documented in the 11.2 developer advisories.
This guide addresses a narrow collision around Shop descendants. If most WordPress pages return 404 after a migration, start with the migration permalink checklist rather than assuming a WooCommerce-specific cause.
Draw the intended route map
On staging, list the Shop page ID and path, its intended child page ID and path, the product permalink base, and one representative product URL. Write the content type each URL should resolve to.
For example, a store may intend one path for a product archive and a nearby path for a buying guide. Similar-looking paths are not evidence that both resolve to the intended object. Inspect the response status, visible heading and canonical URL, not just whether the browser displays a page.
Map: Record Shop path and product base. Code: Find obsolete option dependencies. Refresh: Regenerate only after correction. Public test: No homepage fallback masking 404. Explanatory checklist, not a customer test result.
Test four requests before editing
| Request |
Record |
| Shop archive |
Status, archive heading and canonical |
| Intended child page |
Status and actual page ID/template |
| Ordinary product |
Product identity and canonical |
| Deliberately nonexistent path |
A genuine not-found response |
Include both direct navigation and a normal internal link. A catch-all application shell or a redirect to the homepage can look successful while concealing the original routing failure. A nonexistent URL should not become an unrelated successful page.
Find code that still depends on the old option
Ask a developer to search the custom plugin and theme code for use_verbose_page_rules. Record whether it is merely reading the option, writing it during setup or using it to trigger a flush. Remove obsolete behavior through a tested code change, not by repeatedly toggling the stored value.
After the intended route configuration is corrected, use the supported permalink regeneration process once. Avoid a rewrite flush on every request: that is not a substitute for a correct route definition and can add unnecessary work.
If a public URL must change, plan a targeted redirect from the old address to the corresponding new content, update internal links and verify the canonical. Do not send every missing Shop descendant to the Shop root; that hides broken references and misdirects visitors.
Verify outside the administrator session
Retest logged out after the relevant cache has been refreshed. Check the four-request set again, including the nonexistent route. Confirm the affected navigation link reaches the child page without a chain of redirects.
Keep the old/new route map and one example request for each result. HandL WP can trace a Shop routing conflict using these paths and the installed theme/plugin versions, without first changing every permalink on the site.
References reviewed October 16, 2026. Examples are explanatory, not customer test results.