內容簡介
Content Signal 是一款只讀的 WordPress 內容健康審核外掛，能與 Yoast SEO 和 Rank Math 一起使用。它可以在本地運行，無需帳戶、API 金鑰或外部請求，幫助用戶檢查網站內容的 SEO 健康狀態。
【主要功能】
• 掃描已發佈的文章、頁面及 WooCommerce 產品
• 發現缺失的 SEO 標題和 meta 描述
• 標記指向其他 URL 的 canonical
• 識別薄弱內容及孤立內容
• 支援每日或每週本地審核排程
• 將最新審核結果匯出為 CSV
外掛標籤
開發者團隊
② 後台搜尋「Content Signal — SEO Content Audit」→ 直接安裝（推薦）
原文外掛簡介
Content Signal is a read-only WordPress content health audit that works alongside Yoast SEO and Rank Math. Run it locally without an account, API key, URL quota, or external request.
The free local audit can:
scan published posts, pages, and other public content types (including WooCommerce products) in bounded background batches;
find published content marked noindex;
find missing SEO titles and meta descriptions;
flag canonicals that point to another URL;
identify thin content, content without internal links, and stale content;
identify orphan content and pages with only one inbound internal link;
compare the latest scan with the previous result to show new and resolved findings;
schedule daily or weekly local audits, disabled by default;
ignore intentional findings and restore them later;
search and filter findings by issue, severity, content type, change, and active/ignored state;
link directly to Edit and View actions for every affected URL;
export the complete latest audit to CSV;
show critical content health status in the WordPress Dashboard and Site Health.
The optional Content Signal platform connection can:
exchange a one-time connection challenge for a site-scoped connection;
sync bounded content metadata and active findings from the latest completed local audit in paginated batches;
materialize local findings as platform audit issues and combine them with Google Search Console traffic loss and opportunity data;
deep-link connected findings into matching platform Content and Audit views;
identify findings that can gain Search Console evidence and supported Yoast/Rank Math fields that can enter the safe-preview workflow;
prioritize work in a multi-site team backlog with audit history;
schedule recurring sync through Action Scheduler, with an hourly WP-Cron fallback;
show sanitized sync history in the WordPress admin;
receive signed, review-first SEO title/meta-description operations plus bounded self-canonical and individual noindex/nofollow repairs from the SaaS worker.
The local audit does not contact an external service or change content. When the optional platform is connected, the plugin does not send post bodies during sync. Risky SEO changes are never made from the platform without a preview, dry run, explicit confirmation, signed request, and recorded result.
External services
This plugin connects your WordPress site to the Content Signal SaaS workspace, an account-based service you sign up for separately. No SaaS endpoint is contacted until an administrator enters one on the settings screen and completes the one-time connection exchange.
Once connected, the plugin sends requests to the SaaS endpoint you configured in these cases:
Connecting the site — the one-time connection challenge you paste in is exchanged for a signed, site-scoped connection token.
Scheduled and manual sync — bounded post/page metadata (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) is sent in paginated batches. Each finding is limited to an allow-listed code, label, severity, short evidence, and fingerprint. Full post/page content bodies, the full internal-link graph, and ignored findings are never sent.
Receiving SEO operations — the SaaS worker sends signed, review-first title/meta-description/canonical/noindex-nofollow proposals for an administrator to preview and confirm before anything is written back to WordPress.
Disconnecting the site — a request invalidates the stored connection token on the SaaS side.
Every outbound request is signed with a per-site secret and rejected by the SaaS if tampered with. No data is sent to any third party besides the SaaS endpoint you explicitly configure.
See the Content Signal Terms of Service and Privacy Policy for how the connected SaaS handles data.
