| 开发者 | pan4de |
|---|---|
| 更新时间 | 2026年9月23日 23:24 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0+ |
your-domain.com/llms.txtwp pan4-ai-visibility backfill recalculates the score for all published content (options: --post_type=post,page, --dry-run)Not for the AI visibility score – it runs entirely locally. Only the optional AI search (live citation test) needs its own, free account with Mistral, Perplexity, or OpenAI, since it queries a real AI search engine live.
Pan4 AI Visibility Toolkit itself is completely free, no pro version. The only possible cost: if you enable the optional AI search, the AI provider you chose (Mistral/Perplexity/OpenAI) may charge for your own queries – depending on their pricing model, often with free quotas included.
No, Pan4 AI Visibility Toolkit is fully standalone and comes with its own focus keyword field. It works just as well alongside Yoast, RankMath, Seo-Pan & co.
The score and AI crawler tracking run entirely on your own server; no data is sent to third parties. Only when AI search is active is your chosen query (focus keyword or post title) sent to the AI provider you selected – just like any other search there.
The score is an on-page heuristic: it evaluates the structure of your content (e.g. question headings, FAQ structure), regardless of whether an AI has actually found it yet. AI search is a real live test: it actually queries an AI search engine and checks whether your domain is cited as a source.
Yes. Dashboard toggles are protected with cache-busting, and /llms.txt is explicitly excluded from full-page caching. Only limitation: AI crawler tracking only captures visits where WordPress actually rebuilds the page – with an active caching plugin, the numbers are a lower bound.
<p> tags. Some page builder widgets (e.g. Elementor's Icon Box widget) output real body text wrapped in <div> elements without <p> tags, which caused this single check to incorrectly report "no paragraphs found" even for substantial written content. Added a fallback that reconstructs paragraphs from block-level boundaries when no <p> tags are present, with a minimum length filter so short UI fragments (button labels, menu items) aren't mistaken for real paragraphs. The other 4 score checks (headings, links, author bio) already extracted plain text safely regardless of markup structure and were not affected. 5 new automated tests added covering this casewp pan4-ai-visibility backfill for bulk score recalculation (including --post_type= and --dry-run), only loaded under WP-CLI