I was told this was NOT a glitch and rather had to be submitted as an enhancement request.
So, without further delay, and belonging in the "duh" category for enhancement requests:
Please set events for onMessage Front End sites to automatically expire when the event date has passed. Currently, prospective families searching, for example, for Open House dates on our public site have to weed through old dates from 2014?! This makes absolutely no sense. Events behind the password expire, yet events on Front End do not? This seemed like a glitch, but oh well. There you have it. Enhancement Requested.
I concur that past events should expire so that Google does not continue to pick them up. This is crazy and in fact is swaying our google analytics etc. Please fix this!
How are events that are several years old become "visible" for google to crawl? Our front end calendar blocks show current/future events, with a few days or months range, but the calendar "previous" button would have to be used many times to reveals these old events.
I would like to vote for this but am getting an error message.
Hi Janet, I think you guys solved this already, but to close the loop: calendar events are the only content type that don't have an expiration date. When the event is over, whether it's a single date or a date range, it should disappear. We don't need it to be available in a search. It makes it too difficult for people to find an event they are looking for if they have to sort through years of past events to do so.
Hi Carolyn,
We might move forward better if we work on a solution that doesn't depend on expiration dates. For all content types, adding an expiration date means they will no longer appear in search or archived content. Leaving the expiration date blank does leave any content available for 'historical' searches; this way users can control whether they truly want to expire content like a deleted 'as of date'. We have improved the app search to prioritize events in results based on their proximity to today's date. Is there a specific place on the front end pages that old events are still being visible that we can make smarter?