Localist offers visibility settings that control where and how an event will be displayed to users. In this article you’ll find:

  • Visibility Options
  • Visibility Comparison
  • Assigning Visibility Options to Events
  • Search & Past Events

Visibility Options

1. Exclude From Trending

Checking this box will prevent the event from being included in the Trending list. This is ideal for events like holidays, internal meetings, repeating events that may receive a lot of traffic, but don’t add quality or content to the homepage. For example, this prevents a weekly repeating event from ranking above a cool one-time event because the repeating event has more lifetime traffic.


2. Public

By default, all events are Public which means they are displayed on the calendar at all times and to anyone who visits your calendar. Public events are also eligible to be curated into any Widgets and/or Channels.


3. Unlisted

This option will prevent the event from being displayed on the calendar. The only way to see the event is through the event URL, circulated by the event creator or an Event Admin. After creating and saving an Unlisted event, select View Event in the bar that appears. This will take you to the Unlisted event details page where you can access the URL.


4. Restricted

This option restricts the event’s visibility to specified locations. When selected, a few options will appear:

  • Place Pages:  The event will only be visible on the Place Page that it is linked to. For example, if an art gallery is having a year long exhibition, you may not want the event to appear on your All Events page every day for a year. If you mark it Place Page, users visiting the place landing page for the art gallery would still see the event, but the event won’t appear on the calendar homepage or the All Events page. Related Article: Place Pages
  • Widgets:  The event will appear in any widgets that are curating based on the classification assigned to the event, but it will not appear on the platform. For example, if you have internal meetings or events for a specific group of people, you can assign a tag, group, or filter that allow you to pull the events into the widget. Once the widget is created, this will be the only place the events will appear. Related ArticleWidgets
  • Logged in Users Only:  Users must be logged in to see the event. Google will not crawl these events, but anyone can see it once they login. Related ArticleSingle-Sign On
  • Channels:  Similar to restricted to Widgets, the event will only appear to Channels that are curating based on classification assigned to the event, but it will not appear on the platform. For example, this option can be helpful for announcements around festivals. Related Article: Channels

Visibility Comparisons

Visible Unlisted Place Pages Widgets Logged in Users Only Channels Exclude from Trending
Localist searches
Date pages
Group/Dept Pages
Place Pages
Trending Algorithm
Search Engines
Direct URL
Non-Logged in Users

Assigning Visibility Options to Events

Visibility is only available to Event Admins and is not available on the Public Event Submission Form.

1. Per-Event: In the event’s create/edit form you will see Visibility listed under the last section of the form, Settings.

2. Bulk Uploading: In a bulk upload CSV your template will include (or you can add) columns titled:

  • Visibility: Enter Unlisted or Restricted. Since events are Public by default you do not need to specify if they should remain public.
  • Sponsored: Enter 1/y/yes/true
  • Place page Only: Enter 1/y/yes/true
  • Widget Only: Enter 1/y/yes/true
  • Exclude from Trending: Enter 1/y/yes/true

Search & Past Events

Browsing Options

  • Search Bar: After entering a search term, the platform will display all events, places, and groups that have a match. After selecting “events,” a user can elect to sort the results, which can be found on the right hand side above the normal filter list. If a search term is not found in any future events, the user will be prompted to Search Past Events. Note:  The the list is sorted by relevance by default.
  • Mini-Cal: Users can navigate to past months or future months for the next three years to select a specific date. The current month will display dates with events in bold. Users can use the arrows to navigate between months.
  • Filters: Depending on your platform’s “Default Date Range,” users will be shown events matching the filter for today, this week or this month.
  • Place and Group Pages: Every place and group page displays the next five upcoming events as well as the most recent five past events.
  • All Events: Depending on your platform’s “Default Date Range,” users will be shown all events for today, this week, or the next 30 days.
  • Tags: Unlike filters, tags are free text and are not selected from a predetermined list so they are not listed anywhere except for on the event landing pages. If a user clicks a Tag on the Event Details Page, it will take them to a list of all other events with the same Tag.

BEST PRACTICE: Why Localist Doesn’t Purge Data

Where do we store data?

Everything is hosted in the cloud and is available to you at any time. There is no limit and your platform’s performance will not be negatively effected by the amount of data being stored.

Why don’t we purge data?

Besides storage not being a factor, there are two main reasons why we don’t purge data:

  1. It creates an archive for your organization. This is helpful for admins who want to recreate event listings or users who are curious about past events.
  2. It is a huge boost for SEO.
Here’s how these things work together:  Someone searches “5k race” + your organization’s name in Google. If there aren’t any future events matching that search, past events will still appear in the search results which will drive traffic to the calendar (increased SEO). Now since the past event is archived, it was picked up by the search engine allowing a user to learn that there was a “Race for the Cure 5k” last October so there could be one the next October. Both reasons go hand in hand.
That being said, this does only apply to outside searches. If a user searches for a past event in the calendar search box next to the login links they will be met with a message stating that no events were found and with a prompt to “search past events.”

Adding a “Past Event” Disclaimer

This can be done by using your platform’s Theme Editor.

  • Navigate to Settings > Appearance

    If you do not have a custom theme, select +Add Theme.

  • Select Edit Theme Files for your custom theme

    Scroll down to Shared Among Multiple Views and open _event_item

  • Add the following code in between lines 46 & 47

    {% if event_item.is_past %}

    This is a past event.{% endif %}
  • Save Changes
  • Next, open Page Shell under Events
  • Add the following code on line 52

    {% if event.is_past %}

    This is a past event.{% endif %}.
  • Save Changes
  • Style with Custom CSS

    From here you can style these messages with the selectors .pastitem and .pastpage