Changing WooCommerce Product URLs: Plan and Test Redirects
When WooCommerce product or category URLs change, map old addresses to relevant destinations and update the store’s own links. A redirect plan should preserve useful customer routes and avoid loops or blanket homepage redirects.
Read the guide
Search Field Notes
A useful next read.
36 field notes
No matching guide yet. Try “checkout”, “shipping” or “catalog”.
All Field NotesInventory the routes and choose which need to move
A new product name, category label or template does not automatically require a new slug. Keep useful URLs when they still fit the catalog. Every changed address adds a mapping and verification task, so the structural benefit should be clear.
List the specific product and category routes that need to move. Separate those from unchanged pages and discontinued products. This keeps a catalog reorganisation from becoming an unnecessary rewrite of the store’s entire URL structure.
Collect current product/category URLs, sitemap entries and internal links. Add older routes used in campaigns or external links, plus relevant first-party search and analytics evidence where available. A crawl of today’s site may miss an old address customers still use.
For each old URL, record its purpose, final destination and decision status. Mark missing or uncertain targets for review. Keep visitor identifiers out of the worksheet; the task needs page routes and aggregate evidence, not customer records.
Match each old page to a relevant result
Map a moved product to that product’s new address and a renamed category to the appropriate final category. Use a permanent redirect for a lasting move. Where possible, point directly to the final address rather than adding a chain through previous slugs.
A discontinued product needs an individual decision. Use a genuinely equivalent replacement when one exists. If the page is being removed and no relevant replacement exists, return a 404 or 410 response instead of sending it to an unrelated page. Sending all missing pages to the homepage does not preserve what the customer came to find.
Update links, canonicals and the sitemap together
Change menus, editorial links, generated catalog links and sitemap references to the approved final routes. Canonical references should agree with the final page addresses. A redirect works as a safety net, but the store should not rely on its own old links to reach current pages.
Include product feeds, campaign destinations and integration references that use the changed routes. For filter and variation URLs, review the existing indexing policy separately. A shopper’s useful filter state is not automatically a new search landing page.
Validate the full mapping before release
Test each old address, response status and final destination. Check loops, chains, missing targets and broad rules that capture unrelated routes. Include unchanged pages to confirm the redirect pattern leaves them alone.
Open the final content as well as checking the HTTP result. A successful response at the wrong category is still a bad redirect. Test the production routing layer or note where staging cannot reproduce it. Preserve the previous rules and backup before an approved live change.
Give each old URL a useful destination
Choose the closest relevant page before writing the redirect rule.
| Check | What to check | Next step |
|---|---|---|
| Moved product | The same product has a new final address. | Redirect directly to the corresponding product. |
| Unchanged route | The existing address still fits the catalog. | Preserve it and keep links consistent. |
| Discontinued product | No equivalent replacement is available. | If the page is removed, check its 404 or 410 response. |
Monitor the routes after the switch
Verify live redirects and final URLs, then review not-found reports and first-party indexing/search evidence against the change date. Keep the mapping so staff can investigate an old link reaching the wrong place.
A careful move reduces avoidable errors but cannot guarantee unchanged rankings or immediate recrawling. Investigate specific missing pages or inconsistent signals before attributing every search fluctuation to the redirects. Assign ownership of post-change checks while the old routes remain in use.
Common questions
Do we need a redirect after changing a WooCommerce product slug?
For a lasting move, check that the old URL reaches the relevant final address through an appropriate permanent redirect. Do not assume every theme or routing setup creates the required rule.
Should discontinued products redirect to the homepage?
Usually that is not a relevant replacement. Review an equivalent product or useful destination, or use the appropriate removal response when no replacement exists.
Are redirects enough for a URL change?
No. Update internal links, canonical references, sitemap entries and known feed/campaign routes so they use the final URLs consistently.