| 开发者 | annimarketing |
|---|---|
| 更新时间 | 2026年9月15日 23:32 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
anni/v1) so the Anni app can read plugin status and set the two values above. All endpoints require the manage_options capability (administrators). Requests are authenticated with WordPress Application Passwords.anni_ga4_id, anni_gsc_verification). The Google Analytics tag is only loaded if a measurement ID has been explicitly configured; in that case Google's terms for Analytics apply.
No. It only prints the Google Analytics tag if you configure a measurement ID. Without configuration it outputs nothing.
Only authenticated WordPress administrators (manage_options), typically via an Application Password issued by you. All three endpoints require this — including reading the plugin status.
Yes — you can set the GA4 ID and the Search Console token yourself; the plugin is a minimal, dependency-free head-injector.
Anni connects to your site exclusively through WordPress Application Passwords (the built-in
authorize-application.php flow — you approve the connection yourself, no password typing).
Some security plugins disable Application Passwords globally, which silently breaks that
connection. If you install this plugin, you explicitly want the Anni connection, so it makes
the feature available again — but only for Anni: authorization requests from any other
application keep whatever policy your security plugin enforces. WordPress' own HTTPS
requirement for Application Passwords stays untouched.
wp_authorize_application_password_request_errors hook, scoped the same way).wp_is_application_passwords_available
filter (latest priority) — some security plugins disable the feature globally, which breaks
the Anni connection entirely. WordPress' HTTPS requirement stays untouched./status REST endpoint to require manage_options (was edit_posts), matching the other two endpoints and this readme's own description.anni/v1/gsc).