WP Manifestindependent plugin directory
manifest / content / wp-toolkit

Content Toolkit

WordPress tool manager for batch operations run by WP-CLI background workers, with progress, stop and restart from the dashboard.

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/overthinq/wp-toolkit/archive/refs/heads/main.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.

Clean up WordPress articles after a content audit or plugin removal. Long operations run in batches through a WP-CLI worker, with progress and execution logs in the dashboard.

Tools

  • Broken Link Manager: remove links listed in a CSV while keeping their inner markup. Optionally keep the original anchor in an HTML comment.
  • Broken Shortcode Manager: remove selected shortcode tags while keeping enclosed content. The cautious mode skips registered shortcodes without executing them.

Both tools offer a dry run. Back up your content before applying changes.

Setup

Requires WordPress 6.8+, PHP 8.3+, a Unix server, Bash, WP-CLI in the web user's PATH, and proc_open enabled.

  1. Copy toolkit into wp-content/plugins and activate it.
  2. Create a writable directory outside the public web root, owned by the PHP/worker user.
  3. Set its path in wp-config.php:
define('CONTENT_TOOLKIT_STORAGE_DIR', '/srv/private/content-toolkit');
  1. Open Content Toolkit, choose a tool and run a simulation first.

The CSV has a header row and two comma-separated columns: page URL, broken URL. Page URLs must belong to the current site. URL paths and queries are case sensitive.

Limits

The link tool consumes an audit report; it does not crawl or check remote URLs. Shortcode cleanup handles WordPress shortcode syntax, skips escaped examples and HTML comments, and may require another pass for nested tags. Jobs are serialized. CSV and execution logs contain content information and stay in private storage.

Worker command: wp content-toolkit run-job <tool> <job_id>.