GigRoute Events

Recurring events

GigRoute Events supports recurring event templates for repeated shows, club nights, weekly performances, annual events, residencies, and other schedules where the same event repeats over time.

A parent recurring event stores the shared details and recurrence rule. Editors can generate dated recurring event posts with a one-time checkbox on update, so a normal save only stores recurrence settings and does not accidentally create or update event posts. Generated recurring events keep frontend lists, AJAX filters, REST requests, pagination, and Schema.org data working with normal event posts instead of calculating virtual dates on every request. Each sync is capped to protect the database from accidental daily schedules that span too far into the future.

Administrators can pause a recurring series to stop creating new generated events, resume it later, or end it and choose whether future generated events should be kept, cancelled, drafted, or moved to the trash. The Events admin list includes a recurrence filter and visual markers: recurring event templates are marked with a crown and generated recurring events have their own indicator. Individual generated events show a direct link back to the parent event and can be detached when a specific date needs its own ticket link, ticket price, venue, status, or other event-specific data.

Gutenberg block

The GigRoute Events block lets editors display events without writing code. Block options include title, title tag, layout styling, number of events, event mode, ticket link visibility, grouping, pagination, filters, and date format.

This is useful for building conversion-focused sections such as “Tour Dates”, “Upcoming Shows”, “Live Events”, “Get Tickets”, or “Next Performances”.

Event posters

GigRoute Events includes poster functionality for visually promoting events. You can use individual event posters or one global poster across the site.

Poster settings include:

• Enable or disable posters globally.
• Use individual event posters or one global poster.
• Set the poster display delay.
• Hide the poster for a selected number of days after a visitor closes it.
• Wrap poster media in a link when a valid destination is available.
• Use the global poster link or the individual event Ticket URL as the destination.

This can help promote ticket campaigns, new tour announcements, stand-up specials, festival appearances, or other show business events.

REST API

GigRoute Events provides a public JSON endpoint:

/wp-json/gigroute-events/v1/events

The endpoint returns published events and supports event discovery, external frontends, mobile apps, landing pages, and custom JavaScript interfaces.

Supported query examples:

/wp-json/gigroute-events/v1/events /wp-json/gigroute-events/v1/events?mode=upcoming /wp-json/gigroute-events/v1/events?mode=all&year=2026 /wp-json/gigroute-events/v1/events?mode=all&year=2026&month=4 /wp-json/gigroute-events/v1/events?country=ukraine&city=kyiv&event_type=concert /wp-json/gigroute-events/v1/events?start=2026-04-01&end=2026-04-30 /wp-json/gigroute-events/v1/events?mode=all&page=2&per_page=20

The response includes pagination data and event items. Empty values are removed from public event responses where possible. The public GigRoute endpoint exposes a curated event payload without private _gigroute_event_* keys. Registered event meta is restricted to edit context and protected by capabilities, while the editor, revision handling, integrations, and classic meta boxes continue to use the same underlying post meta keys instead of duplicated values.

SEO and marketing benefits

GigRoute Events helps structure event content in a way that supports marketing and organic discovery.

You can create dedicated content around live shows, city pages, tour schedules, artist announcements, and ticket calls to action. The plugin separates event metadata from normal post content, which makes it easier to reuse event information across blocks, templates, REST responses, filters, and promotional sections.

For SEO-focused event pages, you can use event titles, excerpts, content, featured images, event taxonomies, and location terms to create relevant pages around concerts, tours, stand-up shows, and entertainment events.

For events that should appear in lists but should not have a public single page, GigRoute Events includes event visibility controls. You can hide the direct event page and prevent search indexing while still keeping the event available in public lists and REST summaries when published.

External services

GigRoute Events can use the ipapi.co geolocation service when event-based posters are enabled on the frontend. The service is used to request approximate visitor location data from: https://ipapi.co/json/ The plugin uses this response to help choose a relevant upcoming event poster based on the visitor’s country, region, city, and approximate coordinates. The result may be cached in the visitor’s browser localStorage for up to 3 hours. Data sent: the visitor’s browser makes a request to ipapi.co, which means the visitor’s IP address is processed by that external service.

Service terms: https://ipapi.co/terms/

Privacy policy: https://ipapi.co/privacy/