| 开发者 | jadeslair |
|---|---|
| 更新时间 | 2026年8月26日 07:00 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[Insert company name], "Word count: 1,450", stray SEO briefing fields)**bold**, ## headings)ai-slop-checker folder to /wp-content/plugins/.No, and it does not try to. It finds evidence of a specific, sloppy workflow: pasting a chat reply in without reading it. A high score means artifacts of a chat session survived into the published text. That is a real editorial problem whether or not you care how the draft was produced. A well-edited AI-assisted post scores clean here. That is the intended behaviour.
No. The pattern scan runs inline and takes milliseconds. If AI mode is on, the fact-check is queued to run just after the save completes, so hitting Publish never waits on a network call.
Yes. The scan keeps a cursor in the database and runs server-side on WP-Cron, so it survives page navigation and picks up where it stopped. If your host has WP-Cron disabled, or blocks the loopback requests it depends on, the scan still completes as long as the dashboard is open — the page drives the work itself rather than waiting on cron. Leaving the tab open is the reliable option; closing it relies on cron working. A scan that dies part way through, for any reason, loses at most the single post it was working on. If a particular post crashes the scanner twice, it is stepped over and reported at the end rather than retried forever.
Pattern-only scans are free and make no network requests, so running one across a whole site costs nothing. With AI fact-checking enabled, each post costs one call to your chosen provider — two if you have both selected — plus up to a couple of Google calls for contested claims. Across a large site that adds up, and free API tiers have rate limits a full crawl will hit. Check your provider's limits before starting one. "Skip posts already checked since their last edit" is on by default so repeat scans stay cheap, and API responses are cached for 24 hours. A practical approach on a large site is to run the pattern scan over everything first, then enable AI only for the posts it flags.