| 开发者 | serhiivasyliev |
|---|---|
| 更新时间 | 2026年9月10日 14:44 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
seo-content-control-center-<version>.zip release artifact.No. Content Signal is an operations layer that connects WordPress metadata, Search Console evidence, audits, and a trackable backlog. It works with supported Yoast and Rank Math metadata fields for bounded operations.
No. The content health audit runs locally in WordPress and does not require an account, API key, URL quota, or external request. External communication starts only after an administrator explicitly connects the optional platform.
No. The local audit is read-only. It explains findings and links to the normal WordPress editor. Connected platform writes remain protected by preview, dry run, explicit confirmation, signed requests, and rollback support.
No. The plugin syncs bounded metadata and accepts only signed, supported operations after the SaaS has completed its preview, dry run, and explicit confirmation workflow.
It syncs bounded posts/pages inventory and metadata, including URL, title, status, modified time, author, publish date, featured-image presence, taxonomies, word count, link counts, supported SEO metadata signals, and active findings from the latest completed local audit. A finding contains only its allow-listed code, label, severity, short evidence, and fingerprint. It does not sync post bodies, the full link graph, or ignored findings.
Recurring and queued local sync jobs are removed. Disconnect the site from the settings page before deleting the plugin when you also need to invalidate its SaaS connection token.
WordPress removes the plugin's local audit results, sync log, stored connection token, and scheduled jobs. Disconnect first when you also need to invalidate the connection remotely on the platform.
GET /api/plugin/monitoring-summary platform call.wordpress:php8.4-apache, wordpress:7.0-php8.2-apache), replacing the WordPress 6.8 pin.content-signal-seo-content-audit).