Stalemender – Content Audit, Stale Post Finder & Content Decay Report

开发者	emtiazzahid
更新时间	2026年9月24日 01:16
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0

详情介绍:

Old posts quietly lose rankings. Stalemender audits everything you have published, gives each post a Freshness Score (0–100) and tells you why it scored that way, so refreshing content becomes a weekly habit instead of a yearly panic. What it looks at

Age since the last update (or last editorial review)
Search traffic trend from Google Search Console: clicks in the last 28 days vs the 28 before
Outdated mentions: old years, "this year", "recently", prices in headings – each one quoted in context, with a per-post ignore list
Length compared with the typical post of the same type
Internal links pointing in (orphan detection via a full link index)
Structure: H2 headings, images, featured image
Meta description (Yoast, Rank Math, AIOSEO, SEOPress, or the excerpt)
Broken outbound links (light HEAD checks, cached, throttled per host)
Duplicate titles, H1s and near-duplicate slugs

Weights are yours to change. Signals without data (no Search Console, outbound blocked) are skipped and their weight redistributed, so a score is never punished for a missing integration. Then it helps you act

Audit table: server-side pagination, sort and filter by type, category, author, band, status, assignee, traffic trend or modified date; save views per user; export the current view as CSV
Post drawer: full score breakdown, outdated phrases in context, who links here, notes, status (needs update, in progress, reviewed, merge, delete), assignee, "mark reviewed" which resets the age clock
Refresh next: a top-N list of non-fresh posts ranked by staleness × lost clicks (or × inbound links when Search Console is not connected), on the dashboard and in a widget
Weekly digest email with band counts, trend and the refresh list
AI refresh brief (optional, bring your own OpenAI / Anthropic / Gemini key): a Markdown brief saved as a note. Nothing is sent until you confirm the token estimate.

Built to be light

Custom tables; the only post meta written is your per-post list of ignored phrases, automatic pruning
Audits run in Action Scheduler batches that adapt to your server's time limit and resume where they left off
Re-scores a post when you save it; drops it when unpublished
Search Console via a service-account JSON key (stored encrypted); nightly sync
WP-CLI: wp stalemender audit run|status|cancel, wp stalemender gsc sync|status, wp stalemender export --file=, wp stalemender score <id> --explain

Hooks for developers stalemender_signals, stalemender_signal_weights, stalemender_post_types, stalemender_exclude_post, stalemender_score_computed, stalemender_outdated_phrases, stalemender_gsc_row, stalemender_refresh_list_size, stalemender_after_audit, stalemender_post_html, stalemender_builder_html, stalemender_http_args, stalemender_rescore_on_save, stalemender_capability.

安装:

Upload the plugin to /wp-content/plugins/stalemender or install it from the Plugins screen.
Activate it.
Open Stalemender and click Run first audit.
Optional: connect Search Console under Settings → Search Console to rank by lost traffic.

屏幕截图:

常见问题:

Does it need Google Search Console?

No. Without it the traffic signal is skipped and the refresh list ranks by staleness × internal links. With it you also get click trends and "decaying" flags.

How do I connect Search Console?

Create a service account in Google Cloud with the Search Console API enabled, download its JSON key, paste it under Settings → Search Console, then add the service-account email as a user on your property in Search Console. Pick the property and enable the nightly sync.

Will the audit slow down my site?

No. Posts are scored in background batches (default 50, halved automatically if a batch runs out of time) and outbound links are checked with cached HEAD requests, at most 20 per post and 100 per batch.

Does it work with page builders?

Elementor, Bricks, Beaver Builder and Oxygen data is read from post meta, Divi shortcodes from post content, so word counts and links are not zero on builder pages.

Is anything sent to an AI provider?

Only when you click "Generate brief" on a post and confirm the token estimate, and only if you have enabled AI assist and added your own key. Usage is logged locally.

Does the plugin send anything to its author?

No. Stalemender has no server of its own, sends no usage statistics or telemetry, and contacts no address that is not listed under "External services" above. Every one of those is off until you turn it on.

Does the bundled Action Scheduler conflict with other plugins?

No. Stalemender loads Action Scheduler 3.9.3 from lib/action-scheduler/. Action Scheduler is built for this: each copy registers its version with ActionScheduler_Versions behind function_exists() and class_exists() guards, and only the newest copy on the site boots. WooCommerce and other plugins that bundle it share the same mechanism.

Where is the JavaScript source?

The admin app ships un-minified in assets/src/; the files in assets/build/ are produced from them with npm install && npm run build (the package.json is included). The bundled Action Scheduler library in lib/ is unmodified upstream code under its own GPL licence. Nothing else is compiled or obfuscated.

Who can see the audit?

Users who can edit others' posts (filterable with stalemender_capability). Settings need manage_options.

更新日志: