Features

Discontinued Product Pages: Replacements, Manuals and Enquiries

Plan discontinued product pages around existing customers: choose URL handling, verify replacement compatibility, preserve manual revisions and test bilingual s

When a product is discontinued, first establish what existing customers still need. A model with manuals, spare-parts enquiries or compatibility questions usually benefits from a useful support page at its original URL. Where the information has genuinely moved to an equivalent destination, plan a permanent redirect. Make the decision for both language versions, their files and the enquiry journey.

This guide is for manufacturers, equipment suppliers and export websites. It extends the product catalogue guide with a model retirement workflow. The steps are project recommendations. The example is fictional; your company must approve actual discontinuation dates, support commitments and replacement conditions.

1. Choose between four business situations

Bring product management, sales, support and website maintenance together. Ending new sales and continuing support can coexist. Visitors should be able to see both decisions.

SituationPage and customer journey
Temporary supply interruptionKeep useful product information, explain availability, provide a contact route and set a review date. Sales confirms delivery expectations.
Discontinued with continuing supportRetain substantial support information at the original URL, identify the status and explain manuals and support. Decide catalogue visibility separately.
Information moved to an equivalent pageCheck that the destination serves the same need and retains necessary information, then implement a permanent redirect and update internal links.
Content withdrawn without a relevant replacementReturn the agreed real 404 or 410 response with a useful error page. A dedicated 410 response requires project configuration.

Google’s redirect guidance distinguishes permanent and temporary moves. Its crawling error guidance recommends 404 or 410 when removed content has no similar replacement. A retained 200 support page should contain substantial information. Your customers’ support needs determine the decision for each model.

2. Assign ownership with a retirement register

Start with one model. Record its content ID, existing and translated URLs, category, business status, effective date, spare-parts or service commitments, files, proposed successor, enquiry owner and next review date. Use the company’s approved notice and retain its approver and revision.

Sales owns the new purchase route. Engineering confirms replacement conditions. Support confirms obligations for installed equipment. Editors verify both languages, while the technical team checks page behaviour. Publish service periods from actual commitments. Where information awaits confirmation, provide a contact route and assign the missing decision to an owner.

Include links printed in brochures, QR codes and historic emails. Attach dated traffic evidence when available. Otherwise, prioritise important customer tasks and leave performance figures for actual measurement.

3. Verify replacement compatibility

A successor model describes a product relationship. Engineering should review dimensions and mounting, power and connectors, range and accuracy, communication protocols, operating environment, accompanying software and applicable certification. Keep the conclusion, conditions and approval date so sales and customers can refer to the same evidence.

For a verified replacement, explain which original configurations it supports and which accessories or site changes it requires. Pending assessment, label it “candidate model; engineering confirmation required” and provide a contact route. Similar names or improved specifications alone leave important installation questions unanswered.

Retain an old page when its manuals and support information have an independent purpose. Before redirecting it, place necessary legacy information at an accessible destination and check every link. Review new purchase information and old equipment support separately.

4. Preserve manual languages and revisions

For each historical file, record a document identifier, revision, language, supported model and hardware or software version, actual URL and publication scope. Save a separate revision when installation instructions or applicability change. Preserve the identity of earlier versions, using the download centre guide to organise them.

Show applicability beside the download button, such as “PX-100 hardware A installation manual, English R1”. Verify the translated page and the file itself. When the Chinese document advances first, the English page can explain the actual available revision, its applicability and how to request help.

Check the public page and direct file URL separately. Withdraw restricted files through the company’s authorised process, with technical checks for actual storage access and caches. Establish an old manual’s applicability from technical evidence and its publication permission from the company’s authorisation record.

5. Separate purchase, replacement and support enquiries

Give visitors clear choices: new product selection, replacing installed equipment, and repairs or documentation. Request the contact details, original model, relevant hardware or software revision and problem description needed for follow-up. Collect serial numbers or site photographs according to actual need and information handling requirements.

Customers should be able to verify their original model before submitting. If a theme prepopulates a model, source URL or candidate replacement, include those values in submission testing. With a manual entry workflow, sales can confirm the supplied values. Preserve the original and recommended models separately.

CatchCMS provides custom forms and submission records; see the enquiry form and notification guide. Automatic assignment, CRM synchronisation and service reminders require project implementation. Test the saved record, notification result and actual inbox delivery, and appoint someone to review records routinely.

6. Implement one model before expanding

CatchCMS content models and custom fields can hold project-defined information. The current official website model has no product lifecycle fields. Lifecycle values, support dates, replacement relationships and archive filtering require modelling and theme integration. Multilingual management provides the editing foundation; people verify technical accuracy and consistency.

The content enable setting controls public availability. In the current runtime, disabled content and content awaiting its publication time are excluded, so the original detail URL can return 404. Keep a retained support page accessible. The current content redirect field produces a temporary 302 and depends on the source content remaining resolvable. Permanent 301 or 308 mappings and dedicated 410 responses require project or server configuration followed by HTTP testing.

  1. Save originals. Retain the record, translations, file addresses, relevant rules and screenshots or acceptance evidence.
  2. Approve the decision. Confirm status, support scope, files and destinations, with separate language changes.
  3. Prepare the journey. Complete support information, replacement conditions, downloads and contact routes, then check the theme.
  4. Publish a small sample. Validate one model in the agreed environment, apply the approved production changes and read the data back.
  5. Retest publicly. Enter through old links, listings and language switching; record HTTP responses and customer tasks.
  6. Hand over. Save differences, owners and remaining issues. Restore original values and rules when the agreed rollback conditions apply, then retest.

Before restoration, preserve enquiries and edits received after publication. Review the change list before a larger update, using the URL and content migration checklist for batch work.

7. Fictional example: PX-100 retirement, PX-200 assessment

This exercise uses invented models, documents and events. A company stops accepting new PX-100 purchases. Existing customers still need Chinese R1 and English R1 installation manuals for hardware A. PX-200 is a candidate successor with compatibility awaiting engineering review.

The team keeps both PX-100 pages at their existing URLs, explains discontinuation and the available support scope, and retains the two R1 files. It labels PX-200 as awaiting engineering confirmation. A replacement enquiry preserves PX-100 as the original model and PX-200 as a separate candidate. Engineering reviews connectors and mounting before providing an applicability decision.

The expected outcome is that an old link leads to the correct manual, the English page leads to the English file, customers can submit the original model, and sales can trace the assessment evidence. Later changes follow the approved plan. Use your own models and source material in a real project and record the observed results.

8. Test the public page and customer journey

Use one row per language: time and environment | model and content ID | language | original URL | first HTTP status and Location | final URL and status | status explanation | manual language and revision | enquiry record | reviewer | open action.

  • URLs: retained pages return 200; redirect status, destination and final content match the approved decision; removed URLs return the agreed 404 or 410.
  • Content: title, description and body accurately identify the model and status. Specifications, replacement limits and support commitments have evidence.
  • Language and SEO: check self-canonical, corresponding language links and sitemap entries for retained pages. Adjust internal links and sitemaps for redirected or removed pages according to their strategy. Use the bilingual SEO checklist.
  • Files and contact: open actual files and verify their language, revision and applicability. With authorisation, submit a labelled test enquiry and check records and notifications.
  • Mobile use: enter the legacy model from a list, read status and compatibility conditions, open its manual and find contact options. Check tables, long model codes and buttons.

Schedule a follow-up review. Record indexing, rankings, organic visits and enquiry quality from actual reports. Keep AI crawler visits and real citations in AI answers as separate evidence.

9. Frequently asked questions

Is a discontinued product page worth keeping?

A useful support page serves customers who need manuals, repairs or replacement advice for installed equipment. Assign an owner, document scope and a review schedule.

Can every old model redirect to the latest model?

Check the customer’s task, retained information and engineering compatibility. Equivalent moves can use permanent redirects. Models with an independent support purpose can retain a detail page.

Does a lifecycle change automatically reach English pages and forms?

The project must connect fields, translations, theme output and form context, then test actual submissions. The configured model and theme determine the behaviour.

What should we prepare for implementation advice?

Bring one model’s old URLs in both languages, approved retirement decision, support files, candidate replacement conditions and enquiry workflow to project consultation. Confirm fields, pages, URL rules and delivery ownership item by item.