I'm trying to find the best way to let expired entries display.

My client has jobs that are filled / expire.

A typical job url looks like this:


In the section settings I've got:

Entry URL format set to:


And the entry template set to:


Everything works great. When a job expires/entry expires it no longer appears, but of course the google index remains and so I'd like the page to still 'exist' rather than redirect to a 404.

I've done a bit of work with the 404 so that the /jobs/ part is recognised in the URL and I change the content, as well as fetch expired job data, such as the jobTitle and integrate it into the content. The problem is, Google still sees a 404 page, and the content of the page is different which will invariably create some negative page rank issues given the number of expired jobs that are accruing.

So rather than a 404, I'd like the expired:


Entry to go to the _entry template and show the original unexpired layout (albeit with some tweaks to explain the job has expired).

But despite following the details found here:

Is it possible to view 'Expired' entrys on the front end?

The _entry still redirects to the 404 page when an entry is expired.

Is there any way to stop this so I can perform some .status('expired') voodoo on it?

Many thanks.

  • Maybe I'm thinking too simple now, but what about adding just another "job expiration" date field and not using the entry expiration date at all? You can simply use that in your _entry template to show/do something else when the job has expired. – user155 Sep 8 '15 at 13:35
  • Thanks Jeroen, creative thinking, thank you, it is definitely one way to go about it. However, in the dashboard this would remove the ability to filter expired jobs/entries and over time create pages and pages of entries we don't need to see. – Pathfinder Sep 8 '15 at 13:51
  • 1
    status(null) will give you all entries irregardless of status – Luke Holder Sep 8 '15 at 15:28
  • 1
    Hey Pathfinder, have a look at my answer to the related question! ^^ – carlcs Sep 8 '15 at 16:18
  • 1
    This question/answer does a great job of walking through a similar issue. She's tackling future entries, while you're tackling past entries, but other than that the solution is the same. – Lindsey D Sep 8 '15 at 17:18

Browse other questions tagged or ask your own question.