To someone not familiar with the system, that message looks incredibly cryptic.
Here's a mock-up of how I'd suggest it was done:
View attachment 91355
That's much clearer, and doesn't require a complete redesign.
Indeed. As I mentioned upthread, surely not beyond the wit of National Rail's website staff to update the relevant webpage to make it much clearer that the '
Oxford Day Out' is now a discontinued/withdrawn product?
I absolutely agree that the warning needs to be more noticeable (like in py_megapixel's mock-up) and worded more clearly, e.g. "This is an archived page and the information may be outdated, please see ... for up-to-date information", but I disagree that it's reasonable to expect it to specifically mention that the product has been withdrawn.
Currently, the archive appears to be a vast collection of static html pages plus a simple word search functionality, covering promotions, railcards, rangers&rovers and plusbus with three NFM versions for each year going back seven years. Once a page is archived, it will never need to be modified again - even if the website is redesigned or the entire back-end system overhauled, the archived files can just be copied over and will show up with their outdated design and broken links (which there are plenty of already!).
I don't think it's reasonable to expect archived pages to change as the current information changes. If the updating is done manually, then every time a product is withdrawn (or changed in any way? E.g. region/time/TOC of validity which could lead to prosecution, or just something as simple as the price the passenger will expect to pay when they get to the ticket window?) someone would have to go through the ever-increasing number of archived pages to rewrite them with the new information. If it's done automatically, then you'd need to have a code/process that reads the latest information from a database, identifies which products need their archive page warning messages updated, and performs the update, and this would need to be maintained and also potentially kept in mind when products are updated to avoid false warnings e.g. that a product has been withdrawn when it has only changed name.
(Note that the top Google result for "Oxford evening out" is the NFM30 page but the product also has an NFM31 page as it was available throughout NFM31 before being withdrawn, so just posting a warning message on the latest NFM page when the product is withdrawn wouldn't work.)