Download websites that use The Events Calendar

About The Events Calendar

Most rows in a technology dataset describe how a site was built. The Events Calendar describes what its owner does away from the website, which makes it a different kind of filter.

The plugin adds event listings to a WordPress site: single and recurring dates, calendar views, venues, and hooks into ticketing. Liquid Web has shipped it since 2008, written in PHP and released under GPL v2, which is why it sits in the WordPress plugins group rather than under marketing tooling. As of October 2026 we detect it on 82,418 sites. A detection carries a second fact for free, because the plugin only runs inside WordPress.

Installing a calendar is a commitment to maintaining it, which narrows the population in a way a generic content system row cannot. Organisations that publish dates on a schedule are venues, theatres, churches, universities, municipalities, museums, clubs, conference organisers and membership bodies. 31,989 of the sites we see sit in United States, and the suffix attached to much of the population is .com, both consistent with a mix of commercial venues and non-profit institutions rather than personal blogs.

A working calendar also says something about whether the site is alive. Event listings decay in public, since a page whose next date has already passed looks abandoned to every visitor, so an organisation with a maintained calendar is an organisation where somebody still logs in. Very few rows in a technology dataset double as a freshness signal, and this one does it without any extra inference.

For a commercial researcher the value is the adjacency. A site that runs a public calendar is a candidate for ticketing and registration platforms, for sponsorship and local advertising sales, for event marketing and email tooling, and for aggregators that need a feed of real dates rather than a scrape of press releases. The core plugin is free and the money sits in add-ons for ticket sales, filtering and virtual events, so presence marks a qualified prospect rather than a confirmed spender. Separating the two takes cross-referencing against payment and ecommerce columns. A ticketed conference programme and a village noticeboard are different businesses to sell to, and the plugin looks identical on both, so the useful segmentation always comes from the rest of the row rather than from this column alone.

Detection has a floor worth knowing about. Recognition depends on the plugin's front-end assets appearing in the served markup, so a site that keeps its calendar behind a login, or one whose optimisation layer renames and merges scripts, can be missed. Undercounting is the failure mode here rather than overcounting. A lookup on a single domain tells you whether one venue runs the plugin. The downloadable list is what lets you assemble the whole population, cut it by country and suffix, and treat public event programming as a segment instead of a guess.