Description
Fruti Shortcode Audit scans your posts and pages and reports:
- every shortcode tag found in your content, with how often it occurs and how many posts use it;
- whether the tag currently has a handler registered on your site, or whether no active plugin
handles it any more; - which posts contain shortcodes, with an edit link and a CSV export for the current window.
It is a diagnostic. It never edits, removes, rewrites or replaces anything, it does not touch your
content, and it writes nothing to your database.
Typical use: you are about to delete or replace a plugin that provided shortcodes, or you inherited a
site with unknown shortcodes, and you want to see the real footprint before you change anything. A tag
labelled “no active handler” only means that no plugin registers it right now. It does not mean the
shortcode text is unused or safe to remove.
The scan is bounded and manual: each run processes a configurable number of posts, nothing is loaded
into memory in full, and the screen tells you the window that was scanned so you can continue with a
higher offset. There is no cron job, no background worker and no queue.
Usage
- Open Tools -> Fruti Shortcode Audit.
- Leave the defaults (200 posts per run) or lower the window on very large sites.
- Press Run audit and read the two tables: tags found in content, and the posts that use them.
- Raise the post offset and run again to cover the rest of the site.
- Press Download CSV for this window to export what you just scanned. The CSV is generated on the
fly and is never stored.
Screenshots


Installation
- Upload the plugin folder to
/wp-content/plugins/, or install the ZIP through Plugins -> Add New -> Upload Plugin. - Activate the plugin.
- Go to Tools -> Fruti Shortcode Audit and press “Run audit”.
FAQ
-
Does this plugin delete or change shortcodes?
-
No. It is strictly read-only. It never edits post content, never removes shortcode text, and never
changes any setting. Removing or converting shortcodes is a decision you make with another tool after
reading this report, on a backup. -
What does “no active handler” mean?
-
It means no plugin currently registers that tag, so the shortcode would render as plain text. It is
not a statement that the content is unused: the plugin that provided it may simply be deactivated, and
reactivating it would make the tag work again. -
Does it scan drafts, revisions or custom post types?
-
No. By default it scans published posts and pages. Widening that is out of scope for this version.
-
What happens on very large sites?
-
Each run is bounded to the number of posts you choose, and the results show exactly which window was
scanned. There is no background processing and no automatic scanning of the whole site. -
Privacy
-
Everything runs locally inside your own admin request. Post titles, ids, tags and results are never
uploaded, never sent to any external service, never logged and never stored in the database. The
plugin makes no network requests and collects no telemetry.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Fruti Shortcode Audit” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Fruti Shortcode Audit” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.0
- First release: bounded read-only shortcode inventory with registered and no-active-handler
classification, per-post listing and CSV export for the current window.
