The Termageddon WordPress plugin is moving from a geolocation database stored on each WordPress website to Termageddon Hosted Geolocation. This article explains why the change is happening, what website owners should expect, and how each migration path works.

Beginning with plugin version 1.13.0, Termageddon Hosted Geolocation is the default geolocation service. When geolocation is enabled, the visitor's browser requests location information from geo.termageddon.com, and the plugin applies the country and state rules already selected in WordPress.

Previously, the plugin could download and maintain a MaxMind database on the WordPress server. That legacy method is being retired. A temporary MaxMind fallback remains available until August 20, 2026 at 00:00 UTC. At that time, the plugin will automatically use Termageddon Hosted Geolocation.

The local MaxMind method requires every WordPress website to download, store, read, and periodically update its own geolocation database. Website hosting environments vary, and file permissions, blocked downloads, disabled WP-Cron, security rules, or an outdated database can prevent that process from working reliably.

Termageddon Hosted Geolocation removes that server maintenance from the website. It provides a more consistent geolocation path across different WordPress hosts while preserving the website's existing geolocation settings.

The hosted service also allows a future plugin update to remove the retired MaxMind code and related software dependencies from the plugin.

No. The migration changes how the visitor's location is resolved. It does not change whether geolocation is enabled or which countries and states are selected.

For example, if the consent solution is currently configured to appear for visitors in the European Union, United Kingdom, Canada, California, Colorado, or another supported state, those selections remain in place after the update.

The plugin performs a one-time migration during normal WordPress initialization:

1. Termageddon Hosted Geolocation becomes the active location service.
2. Existing geolocation and region selections remain unchanged.
3. The local MaxMind database and its scheduled update event are removed when possible.
4. WordPress administrators see a notice explaining the migration.

No plugin reactivation is required. The migration runs during a normal plugin update, including on websites where WordPress does not run the plugin activation hook during the update.

New installations use Termageddon Hosted Geolocation from the beginning. No MaxMind database is downloaded or scheduled.

After activating the plugin, configure geolocation under Tools → Termageddon + Usercentrics → Geolocation. If geolocation is not enabled, the plugin will not use location rules to decide whether to display the consent solution.

The completed migration is not repeated, and reactivation does not overwrite an administrator's current temporary fallback choice. The website continues using the geolocation service selected before deactivation, subject to the August 20 cutoff.

Yes, before August 20, 2026 at 00:00 UTC:

1. In WordPress, go to Tools → Termageddon + Usercentrics → Geolocation.
2. Enable Temporarily use legacy MaxMind geolocation.
3. Review and accept the confirmation message.
4. Save the settings.

The plugin will first attempt to download and validate the MaxMind database. It enables the fallback only if a usable database can be prepared. MaxMind stores the database on the WordPress server and schedules monthly updates.

This option is intended as a short transition path, not a permanent configuration.

Termageddon Hosted Geolocation remains active. The plugin does not save a MaxMind selection unless it can prepare and validate a usable database.

Review the error shown in WordPress. Common causes include server file permissions, blocked outgoing downloads, or hosting security restrictions. Because MaxMind is only a temporary fallback, most websites should continue using the recommended hosted service.

At August 20, 2026 at 00:00 UTC, Termageddon Hosted Geolocation becomes mandatory. On the first WordPress request at or after that time, the plugin will:

1. Ignore and clear any remaining MaxMind fallback selection.
2. Prevent legacy MaxMind lookups and downloads.
3. Remove the MaxMind database when possible.
4. Remove the MaxMind scheduled update and cutoff events.
5. Continue using the website's existing country and state selections with Termageddon Hosted Geolocation.

The cutoff does not depend solely on WP-Cron. It is also enforced during normal plugin initialization, so it still takes effect on websites where WP-Cron is disabled or delayed.

Nothing needs to run at the exact second. The plugin enforces the cutoff during the first WordPress request on or after August 20, 2026 at 00:00 UTC.

Termageddon Hosted Geolocation remains active, so a cleanup problem does not reactivate MaxMind or stop the consent solution from using the hosted service.

WordPress administrators will see a cleanup warning with the database path. The plugin retries cleanup on later requests and only marks cleanup complete after the database is absent and the legacy scheduled update is cleared.

If the warning continues, contact Termageddon support and include the warning details and website URL.

The planned follow-up release removes the MaxMind implementation but retains an isolated, one-time cleanup process for legacy files, scheduled events, options, and migration metadata. Websites that skip the transition release will therefore still be moved to Termageddon Hosted Geolocation and have known legacy MaxMind data cleaned up when possible.

As always, create a current website backup before updating WordPress plugins.

When WordPress geolocation is enabled, the visitor's browser requests location information from geo.termageddon.com. The service returns country, region, and city information so the plugin can apply the website's selected location rules.

The plugin stores the location result in a first-party browser cookie for up to 365 days and stores the resulting show-or-hide decision in a session cookie.

The plugin fails safe by displaying the consent solution. A failed or blocked hosted lookup will not cause the plugin to hide the consent solution based on an unknown location.

Most websites should not require changes. If a browser privacy tool, Content Security Policy, firewall, or security service blocks requests to geo.termageddon.com, allow that hostname and test again in a fresh incognito or private browsing window.

After updating:

1. Clear the website's page cache and CDN cache, if applicable.
2. Open the website in a fresh incognito or private browsing window.
3. Test from a location where the consent solution should appear.
4. Confirm the consent solution appears and that consent-dependent forms and scripts still work.
5. Review Tools → Termageddon + Usercentrics → Geolocation to confirm the expected regions are still selected.

No. This migration only changes the WordPress plugin's geolocation implementation. It does not change Termageddon policy content, the Usercentrics Settings ID or embed configuration, consent categories, services, or the website's selected geolocation regions.

Reach out to Termageddon support and provide:

• The website URL.
• The installed Termageddon plugin version.
• A screenshot or copy of any WordPress warning.
• The geolocation regions that should display the consent solution.
• A description of the result you expected and what occurred instead.

We will need enough information to reproduce the issue before we can help troubleshoot it.