Blog / WordPress /

When a WooCommerce product should remain visible after retirement

A product is discontinued, and the first instinct is to delete its WooCommerce page. Tidy catalogue, job done.

Except someone still owns that product. They need the manual, a replacement part or the compatibility info, and they’re probably landing on that exact URL from Google or another site.

Keeping a retired product visible can help people. Leaving it looking buyable can mislead them. The choice depends on what the page is still worth, what alternatives exist and whether the page is accurate. I treat it as a customer-service decision, not catalogue housekeeping.

Understand why visitors still need the page

Review organic entrances, external links, support questions and internal navigation where data is available. A retired product may still help an owner identify a part or find a manual. It may also receive little use and have no suitable replacement.

Ask support and product teams what customers need once an item is discontinued. Can they repair or maintain it? Are compatible accessories still sold? Is there a newer model, and is it genuinely equivalent? I wouldn’t redirect anyone to a successor just because it has the closest name in the catalogue.

Check contractual, regulatory or safety requirements for keeping instructions. Some information may have to stay accessible or be updated, so ask the relevant owner when the product carries obligations.

Choose the page’s future state

Keep the page if it provides useful, accurate aftercare or identification information. Mark the product as discontinued clearly and remove purchase controls that imply availability. Provide links to compatible support or alternatives only when they are verified.

If a direct replacement exists, explain the differences and help the visitor decide. A redirect may be appropriate when the old page has no continuing purpose and the new page serves the same intent, but the mapping should be precise.

If there’s no replacement and nothing useful to keep, retire the URL with a proper response. Don’t send every retired product to the shop homepage. It strips the context and confuses visitors.

Update commerce and search details

In WooCommerce, make sure stock status, schema, feeds and structured data all agree with the visible page. A product shouldn’t look available in one channel and discontinued in another. After changing the template or status, check the price and availability markup.

Review internal links, related products, category listings, XML sitemaps and navigation, and update them for the chosen state. Remove dead purchase buttons and check that old campaign links still land somewhere sensible.

For a retained page, keep the specifications and documentation. An empty product shell with just a “discontinued” label helps nobody. Say what’s still available and how support can help, within the service the business can really provide.

Communicate clearly

Use plain language near the title and the buy area. Say whether the item can be ordered, whether support is still available and what the options are. A subtle badge or a colour change isn’t enough to say “discontinued”.

If you suggest a replacement, compare the differences that matter: compatibility, features, price or availability, where verified. Don’t imply equivalence when the customer needs to check a constraint.

Keep the page in step with customer service scripts. If someone contacts support from the page, the agent should know what they saw and what was promised.

Review after retirement

Watch broken links, search behaviour and support themes. A sudden rise in questions can mean the new state is unclear, or that a useful document vanished. Search metrics are signals, not the final verdict on whether keeping the page was worth it.

Write down the reason for the decision and any replacement mapping, so a future catalogue manager doesn’t reverse it blind.

Avoid thin retirement pages

A retained URL should offer enough value to justify staying. Keep accurate dimensions, manuals, compatibility notes and support guidance. Strip promotional language that makes the item sound current, and review structured data so it doesn’t advertise an offer that no longer exists.

If there’s a successor, explain how it differs and what a previous owner should verify before switching. A related-products widget helps discovery, but it shouldn’t call something compatible unless that’s confirmed. Keep the old SKU or model name visible where it helps people identify what they own.

Review the page after some real use. Search entrances, support requests and broken-link reports show whether it’s still useful. Low traffic alone isn’t a reason to delete a page that serves an important aftercare need.

Preserve useful historical context

Record the retirement date and reason. If the product was replaced, name the successor and the confirmed differences. If not, say so, so visitors don’t assume the page is broken.

Consider moving manuals, warranty information and safety notices to a stable support page instead of leaving them only on the product listing. The product page can link to that maintained source. Don’t park documents in a temporary file location that disappears in the next site redesign.

If the page stays indexed, make sure the search snippet doesn’t suggest current availability, and review feeds and recommendation modules after retirement. Then ask yourself: what would a previous owner expect to find when they search for this exact model a year from now?