Yozigo GEO

Yozigo GEO is a lightweight plugin that reports front-end page visits on your WordPress site to the Yozigo GEO collector service, which classifies each one (bot vs. human, and which AI crawler) using its own regularly-updated bot registry. This plugin requires a Yozigo GEO account. It sends nothing until you enter your API key on its settings page; without a key it does not run at all. Features include:

• Bot & AI Crawler Tracking: Every page visit is reported to the collector, which classifies it against a centrally maintained bot registry (Googlebot, Bingbot, GPTBot, ClaudeBot, and more) — kept current without a plugin update.
• Accurate AI Traffic Share: Because human visits are reported too, the dashboard can compute real AI-traffic-share percentages, not just raw bot counts.
• Performance: The tracking call is non-blocking so it never slows down a real visitor's page load.

1.1.4

• Plugin review compliance: every $_SERVER read is sanitized, the page path and query string are both read from the request URI via esc_url_raw (which keeps percent-encoded and non-ASCII paths intact), hooks use named functions, and "Tested up to" is WordPress 7.1.
• Removed the function_exists() guards added in 1.1.3. WordPress already refuses to activate a second copy of a plugin that would redeclare its functions, so the guards protected nothing, and the plugin review guidelines discourage them.
• Adds suggested wording to the site's Privacy Policy Guide (Settings → Privacy) describing what the tracker sends.
• Reports each visitor IP together with its provenance ("client"), the same way the Vercel and Cloudflare collectors do.

1.1.3

• Guarded every plugin function against "Cannot redeclare" fatal errors if a stale second copy of the plugin (e.g. left over from an incomplete manual upgrade, installed under a different folder name) ever ends up active alongside this one. Previously this white-screened the entire site; now the duplicate copy just silently no-ops.

1.1.2

• Fixed the settings page showing a contradicting "Settings saved" success message at the same time as an "API Key is required" error on a failed save. Now uses WordPress's own settings-errors mechanism, which also removes a harmless but confusing double "Settings saved" message on a real successful save.

1.1.1

• Added uninstall cleanup — deleting the plugin now removes its saved settings (including the API key) from the database instead of leaving them behind.

1.1.0

• Send every page visit (not just bot-matched ones) and let the backend classify bot vs. human — the old local user-agent regex was missing many current AI crawlers (ClaudeBot, Google-Extended, and others) and couldn't support AI-traffic-share reporting.
• Send visitor IP address for accurate classification and geolocation.
• Removed the WP-Cron retry queue (and its "Enable Retry Queue" setting) — matches the no-retry model used by our other integrations; a failed send is now logged via the yozigo_geo_send_failed action instead of queued.

1.0.0

• Initial release — bot/crawler tracking with an opt-in WP-Cron retry queue.