No. The tracking API call is non-blocking ('blocking' => false<\/code>), so the plugin fires it and moves on without waiting for a response.<\/p><\/dd>\nWhich bots and AI crawlers does this track?<\/h3><\/dt>\nEvery front-end visit is reported, and the Yozigo GEO service classifies it against its own bot registry (Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot and more). That registry is updated centrally, so newly-launched crawlers are recognised without a plugin update.<\/p><\/dd>\n
Does this plugin add any JavaScript or cookies to my site?<\/h3><\/dt>\nNo. Tracking happens entirely in PHP when WordPress serves the page. No script is added to the front end and no cookie is set.<\/p><\/dd>\n
Will this work with a full-page caching plugin?<\/h3><\/dt>\nThe tracker runs on every request WordPress itself handles. If a caching plugin serves a page straight from disk before WordPress loads (a common setup for anonymous visitors), that specific page view will not reach the tracker. Pages served through WordPress's normal request handling are tracked as usual.<\/p><\/dd>\n
Does it track my own visits while I'm logged in as an admin?<\/h3><\/dt>\nYes. The plugin does not distinguish logged-in visitors from anonymous ones; every front-end page view is reported the same way. It never tracks wp-admin, AJAX, REST or cron requests.<\/p><\/dd>\n
What happens to my API key if I deactivate or delete the plugin?<\/h3><\/dt>\nDeactivating keeps your saved settings, so reactivating does not require re-entering your API key. Deleting the plugin removes the saved API Key, Org ID and Brand ID from the database.<\/p><\/dd>\n
Does this work on WordPress Multisite?<\/h3><\/dt>\nYes. Activate it on each site in the network and enter that site's own API Key, Org ID and Brand ID under Settings \u2192 Yozigo GEO, the same as a single-site install.<\/p><\/dd>\n
Where do I find my API Key, Org ID and Brand ID?<\/h3><\/dt>\nOn the Plugins page of your Yozigo GEO dashboard, under your organisation's account.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.1.4<\/h4>\n\n\n- 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.<\/li>\n
- 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.<\/li>\n
- Adds suggested wording to the site's Privacy Policy Guide (Settings \u2192 Privacy) describing what the tracker sends.<\/li>\n
- Reports each visitor IP together with its provenance (\"client\"), the same way the Vercel and Cloudflare collectors do.<\/li>\n<\/ul>\n\n
1.1.3<\/h4>\n\n\n- 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.<\/li>\n<\/ul>\n\n
1.1.2<\/h4>\n\n\n- 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.<\/li>\n<\/ul>\n\n
1.1.1<\/h4>\n\n\n- Added uninstall cleanup \u2014 deleting the plugin now removes its saved settings (including the API key) from the database instead of leaving them behind.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Send every page visit (not just bot-matched ones) and let the backend classify bot vs. human \u2014 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.<\/li>\n
- Send visitor IP address for accurate classification and geolocation.<\/li>\n
- Removed the WP-Cron retry queue (and its \"Enable Retry Queue\" setting) \u2014 matches the no-retry model used by our other integrations; a failed send is now logged via the
yozigo_geo_send_failed<\/code> action instead of queued.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n\n- Initial release \u2014 bot\/crawler tracking with an opt-in WP-Cron retry queue.<\/li>\n<\/ul>","raw_excerpt":"Tracks visits and sends them to your Yozigo GEO dashboard for bot\/AI-crawler and traffic-share analytics.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/371619","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=371619"}],"author":[{"embeddable":true,"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/yozigo"}],"wp:attachment":[{"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=371619"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=371619"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=371619"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=371619"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=371619"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/az-tr.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=371619"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}