IPGeolocation.io – Geo Redirects & Content Control

Ownership

Held by IPGeolocation throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.

Full observed history, including every field transition

Committing accounts

Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.

This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.

Adoption

How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.

Very early-stage: 20+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.

12 downloads a day over the last 7 days, rising 80% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.

Install band rose to 20+ on 31 Oct 2026, from 10+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.

Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.

Unchanged throughout: ratings total (0) · support threads (0) · threads resolved (0)

91 days of observation, most recent 14 shown.

Maintenance

When it was last released, and how far its declared compatibility has drifted from current WordPress.

History

Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.

Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.

1. 30 Oct 20269 days ago
   Install band moved to 10+Bands are rounded to one significant digit, so the size of the change is not knowable.
2. 27 Oct 202612 days ago
   Version 1.5.0 released
3. 25 Oct 202614 days ago
   Install band moved to 20+Bands are rounded to one significant digit, so the size of the change is not knowable.
4. 30 Sep 20261 month ago
   Version 1.4.0 released
5. 29 Sep 20261 month ago
   Version 1.3.0 released
6. 03 Sep 20262 months ago
   Version 1.2.0 released
7. 13 Aug 20263 months ago
   Version 1.1.0 released
8. 02 Aug 20263 months ago
   Install band moved to 10+Bands are rounded to one significant digit, so the size of the change is not knowable.
9. 02 Aug 20263 months ago
   First observed by PluginsPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
10. 05 Jan 202610 months ago
    Version 1.0.0 releasedfrom the release logCommitted by ipgeolocation.
11. 05 Jan 202610 months ago
    Added to the WordPress.org directoryReported by the plugin API as the date this plugin was added.

What we know, and what we don’t

Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.

Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see

Similar plugins

Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.

Geo Blocker – Control Site Access by Region and IP

🔐 Block or allow visitors by country. Track access attempts. View analytics. Stay in control — effortlessly.

1,000+ installs5.0★ (1)updated 18 May 2025

access-controlgeolocation

Advanced Country Blocker

An advanced security plugin that blocks website visitors by country, with additional features like blacklisting, logging blocked attempts, admin bypas …

2,000+ installs5.0★ (6)updated 06 Feb 2026

ip-blockinggeolocation

Geo Redirect

Redirect visitors based on geolocation (country, state, city, lat/lng/radius)

1,000+ installs4.3★ (11)updated 01 Dec 2025

geo redirect

WorkflowDone Geo Blocker

Block website access based on visitor's geographical location. Simple and effective geo-blocking for WordPress.

100+ installs5.0★ (3)updated 20 Jun 2026

country blockingip-blocking

Country Based Restrictions for WooCommerce

Restrict WooCommerce products by country using geolocation. Hide them, block the purchase or show your own message — per product or variation.

5,000+ installs4.5★ (52)updated 22 Oct 2026

geolocation

Geo Controller – Geolocation & Geotargeting

WordPress geolocation and geotargeting with IP lookup, geo redirects, dynamic content, WooCommerce localization and visitor blocking.

1,000+ installs4.4★ (31)updated 22 Oct 2026

geolocation

Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.

Reach out about this record

Corrections, missing context, or anything else about IPGeolocation.io – Geo Redirects & Content Control: a person reads every submission, and corrections get a reply within 5 business days.