| 开发者 | decaraoy |
|---|---|
| 更新时间 | 2026年5月6日 05:36 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-json/decaroy/v1/head-meta<meta name="google-site-verification" ...>
in the <head> via wp_head actiondecaroy_gsc_verification_token). On every page render, the plugin
hooks into wp_head and emits a meta tag with the token. Google can
then read that meta tag during the verification step, after which the
domain becomes available to the verifying account in Search Console.
Authentication uses standard WordPress capabilities: the requesting
user must have manage_options (typically administrators). Pair with
WordPress Application Passwords for headless authentication.
/wp-content/plugins/ or install
directly through the WordPress plugins screen.POST /wp-json/decaroy/v1/head-meta
Content-Type: application/json
Body: {"gsc_verification_token": "abcd...your-token..."}No. The plugin makes no remote calls and stores no data beyond the single Google Site Verification token in WordPress options.
Yes. By design, Google Site Verification meta tags are visible in the HTML source — that is how Google verifies them. The token itself is not sensitive: knowing it does not grant any access.
manage_options. Only administrators can read or write the token.
Currently the plugin handles only the google-site-verification meta
tag. Future versions may add support for additional meta tags.
wp_head injection of the configured tag.