Support

February 24, 2017 at 8:07 am

Hi Frank,

We actually recommend breaking those up into separate events. You’ll run into server limits if you have more than 40 date times + tickets within one event.

February 24, 2017 at 12:14 pm

I’d need more information about the events to be able to give you a solid recommendation. In some cases it’s actually recommended to create an event for each date time.

So for example, if the attendees will be attending only one of the date times for the event, then that’s a good indication each date time should be a separate event.

Another example, if a class/event meets 5 times where 1 ticket gives access to those 5 date times, then it’s best to group those 5 date times into one event.

February 24, 2017 at 3:25 pm

It might depend on how much is duplicated from one event to another. The built JSON LD schema micro data will make it clear that the events all occur on different dates.

Here are some tips you can use to help with SEO where groups of your events are basically the same thing and the only difference is they’re occurring on different dates:

Tip 1

Create a landing page for the event that has all the information about the event. On this page you can include a list of links to all the dates available for registration, or include a link to a calendar, or list.

Then, you set the actual Event Espresso event post types to not be indexed by adding this code to your website:

https://gist.github.com/joshfeck/77682eb14a7b4f08e3180b9eb4827cb3

Tip 2

If you use the Yoast SEO plugin, it may be best to exclude expired events from the generated XML site map. You add this code to set those to be excluded:

https://gist.github.com/joshfeck/85dcc9947b8f406093498464f542e990

Tip 3

If you don’t put tip 1 into use, you can set all expired events to include a noindex meta tag:

https://gist.github.com/joshfeck/70979dc12f93ab25dd668ed4500be477

You can add the above code snippets to a functions plugin or into your WordPress theme’s functions.php file.