Adds the Support Copilot, a Help button that answers PluginTidy questions in place. Read-only, consent first, and it never sends your plugin list or audit results.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3707999,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3707999,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3708056,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3708056,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3708056,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.16.5","0.17.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[49508,247327,23888,18932,255756],"plugin_category":[],"plugin_contributors":[273231],"plugin_business_model":[],"class_list":["post-369318","plugin","type-plugin","status-publish","hentry","plugin_tags-plugin-audit","plugin_tags-plugin-cleanup","plugin_tags-plugin-manager","plugin_tags-site-maintenance","plugin_tags-unused-plugins","plugin_contributors-publisherkits","plugin_committers-publisherkits"],"banners":{"banner":"https:\/\/ps.w.org\/publisherkits-plugintidy\/assets\/banner-772x250.png?rev=3708056","banner_2x":"https:\/\/ps.w.org\/publisherkits-plugintidy\/assets\/banner-1544x500.png?rev=3708056","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/publisherkits-plugintidy\/assets\/icon.svg?rev=3708056","icon":"https:\/\/ps.w.org\/publisherkits-plugintidy\/assets\/icon.svg?rev=3708056","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n
Most WordPress sites accumulate plugins. A developer installs one for a job that ended three years ago, someone else solves the same problem a different way, and nobody dares turn anything off in case it breaks the site.<\/p>\n\n
WordPress can only tell you what is active<\/strong>. It has no idea what is used<\/strong>. PluginTidy closes that gap.<\/p>\n\n It looks at each plugin and gathers evidence: whether its shortcodes and blocks appear in your content, whether it has scheduled work, whether the data it stores is still written to, whether anyone opens its settings, whether it is still maintained, and whether several plugins do the same job.<\/p>\n\n Then it tells you what it found \u2014 and shows you every reading behind it, so you can disagree.<\/p>\n\n Every assessment expands into the checks that produced it. Nothing is a recommendation on its own.<\/p>\n\n If scheduled tasks are not running on your site, every plugin looks idle. PluginTidy detects that and excludes<\/strong> scheduled activity from the assessment rather than holding it against everything. The same applies when WordPress.org cannot be reached: it says so, and the confidence figures show it.<\/p>\n\n From the moment you install it, PluginTidy records every plugin installed, activated, updated, deactivated or removed \u2014 who did it, when, and why, if you tell it. The history survives the plugin being deleted, so a problem that shows up later can be traced back to the change that caused it.<\/p>\n\n Everything above. The full audit, all the evidence, the redundancy findings, the notes, and the complete change log. Nothing is capped<\/strong> \u2014 an audit that stopped at ten plugins would be absurd for a tool whose whole purpose is having too many.<\/p>\n\n The free version never changes another plugin.<\/strong> It does not delete one, and it does not switch one on or off. It reads, it scores, and it records. When you decide to act, it links you to WordPress's own Plugins screen.<\/p>\n\n Pro does two things the free audit deliberately will not: it acts on what was found, and it keeps looking after you stop.<\/p>\n\n Acting on it safely<\/strong><\/p>\n\n Keeping it that way<\/strong><\/p>\n\n PluginTidy is one of a small range of tools built for people who actually run publications. Each works on its own, and all are free on WordPress.org:<\/p>\n\n This plugin contacts WordPress.org<\/strong> (api.wordpress.org) to find out whether each installed plugin is still maintained and whether it has been removed from the plugin directory.<\/p>\n\n What is sent: the folder name of each installed plugin. Nothing else \u2014 no site address, no email address, no content, no personal data. Answers are cached for twelve hours.<\/p>\n\n This happens when you run an audit. If WordPress.org cannot be reached, the audit still completes and says that this check was skipped.<\/p>\n\n WordPress.org privacy policy: https:\/\/wordpress.org\/about\/privacy\/<\/p>\n\n This plugin also uses Freemius<\/strong> (freemius.com) to handle licensing, and to offer an optional diagnostic opt-in.<\/p>\n\n What is sent, and only if you accept the opt-in when you activate the plugin: your site address, your WordPress administrator email address, and version information about WordPress, PHP and your site. You can decline this and the plugin works exactly the same. Nothing about your content, your visitors or your audit results is ever sent.<\/p>\n\n If you buy a licence, your licence key is checked with Freemius so the paid features can be switched on. That check happens whether or not you accepted the diagnostic opt-in, because it is what the licence is.<\/p>\n\n Freemius terms of service: https:\/\/freemius.com\/terms\/\nFreemius privacy policy: https:\/\/freemius.com\/privacy\/<\/p>\n\n This plugin also includes the PublisherKits Support Copilot<\/strong> (bwtlsupport.com, operated by Black and White Trading Ltd) - the Help button on PluginTidy's screens. Nothing is sent until someone with plugin permissions reads the privacy notice in the chat and agrees.<\/p>\n\n What is sent when you ask a question: your question and the recent chat; your site address and, where available, your licence installation identifier, used to authorise the request and apply fair-use limits; the PluginTidy version; the admin screen you are on; and a few non-sensitive diagnostics - how many plugins are active and inactive, whether an audit has run, whether scheduled tasks work, and whether WordPress.org could be reached. The names of the plugins on your site, your audit results, your notes and your change log are never sent.<\/strong> Choosing \"Send to support\" keeps the conversation as a ticket, with the email you give and your WordPress first and last name.<\/p>\n\n Terms of service: https:\/\/publisherkits.com\/terms\/\nPrivacy policy: https:\/\/publisherkits.com\/privacy-policy\/<\/p>\n\n\n The audit is done in small batches, so it cannot time out on a site with a lot of plugins.<\/p>\n\n\n The free version cannot: it never changes anything. It reads your plugins, your content and your database, and writes only its own records.<\/p><\/dd>\n Because it is being honest. Some of what it measures \u2014 whether anyone opens a plugin's settings, whether anything changes \u2014 can only be observed from the day it is installed. Leave it running and the picture fills in. Facts it can establish immediately, such as a plugin having been removed from the WordPress.org directory, are reported straight away.<\/p><\/dd>\n The free version contacts WordPress.org to ask whether your plugins are still maintained, sending only the plugin's folder name. Nothing else leaves your site.<\/p><\/dd>\n That is deliberately your decision. PluginTidy has no way of knowing which one your content is actually built with, so it names them all and does not guess.<\/p><\/dd>\n Yes, and it will tell you that it is. The audit never relies on WP-Cron, precisely because a broken scheduler is one of the things it detects.<\/p><\/dd>\n\n<\/dl>\n\n\n Versions before 0.16.5 were distributed directly by PublisherKits and were never listed on WordPress.org.<\/p>","raw_excerpt":"WordPress tells you which plugins are active. It never tells you which are used. PluginTidy works that out, and keeps working it out.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/369318","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=369318"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/publisherkits"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=369318"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=369318"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=369318"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=369318"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=369318"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=369318"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}It gives you evidence, not verdicts<\/h4>\n\n
\n
It knows when it cannot tell<\/h4>\n\n
It keeps a record<\/h4>\n\n
What is free<\/h4>\n\n
What PluginTidy Pro adds<\/h4>\n\n
\n
\n
More from PublisherKits<\/h4>\n\n
\n
External services<\/h3>\n\n
\n
\/wp-content\/plugins\/<\/code>.<\/li>\n\n
Will it break my site?<\/h3><\/dt>\n
Why does it say \"not enough evidence yet\" about so much?<\/h3><\/dt>\n
Does it send my data anywhere?<\/h3><\/dt>\n
It says three plugins do the same job. Which should I remove?<\/h3><\/dt>\n
Does it work if WP-Cron is broken on my site?<\/h3><\/dt>\n
0.17.0<\/h4>\n\n
\n
0.16.5<\/h4>\n\n
\n
Earlier versions<\/h4>\n\n