

Settings → Yozigo GEO: paste the API Key, Org ID and Brand ID from your Yozigo GEO dashboard. Nothing is sent until the API key is saved.
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.
This plugin connects to the Yozigo GEO collector, an API operated by Yozigo (https://www.yozigo.ai), to report your site’s front-end page visits so that your Yozigo GEO dashboard can identify AI crawlers, AI-referred visits and your AI traffic share. The plugin cannot do this locally: the crawler registry lives in the service and is updated centrally.
What is sent and when: on every front-end page view (never admin, AJAX, cron or REST requests) the plugin sends one HTTPS POST to https://yozigo-geo-backend-service.fly.dev/api/v1/crawl/track containing the visitor’s IP address, user agent, referer, request path and query parameters, a timestamp, and your API key, organisation ID and brand ID. Human visits are reported as well as bot visits, because the AI-traffic-share figure needs both. Nothing is sent until you enter your API key on the settings page; without a key the plugin does nothing. The request is non-blocking, so it never delays the visitor’s page.
This service is provided by Yozigo: terms of service, privacy policy.
Because visitor IP addresses are transmitted, you are responsible for disclosing this plugin’s data collection in your own site’s privacy policy where your local law requires it.