| 开发者 | peterbeko |
|---|---|
| 更新时间 | 2026年8月15日 03:11 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[wellcited_answer] shortcode) for a clearly delimited, machine-extractable direct answer near the top of the content.No — it is built to coexist and is tested alongside each of them. WellCited detects the structured data your SEO plugin already outputs and skips those types instead of duplicating them. FAQ schema is skipped per post, only when that post uses your SEO plugin's own FAQ block.
No. Audits run only in the admin area, on demand. On the frontend the plugin adds no extra database queries and at most a few hundred bytes: the JSON-LD graph, the capsule stylesheet (loaded only on pages that use a capsule) and the optional last-updated line.
Nothing. Every audit runs locally in PHP on your server. The plugin makes no external requests of any kind and collects no usage data.
The /llms.txt address needs pretty permalinks (Settings → Permalinks, anything except "Plain"); re-save the permalink settings once after activating the plugin. On plain permalinks the same content is available at /?wellcited_llms=1.
From nineteen local, rule-based checks with fixed category weights — no AI call, no black box. Checks that do not apply to a post are excluded instead of counting against it, and the sidebar lists every check behind the score.
wellcited.editor.fixAction JavaScript filter (@wordpress/hooks) for each failed finding, called as applyFilters( 'wellcited.editor.fixAction', null, { finding, postId } ). An add-on can return a React node to attach a per-finding action; the core plugin renders nothing here on its own.