Control where WordPress plugins load
Freesoul Deactivate Plugins PRO is a conditional plugin-management tool for WordPress sites that need more control over which plugins run in particular contexts. It extends selective deactivation across pages, posts, custom post types, archives, backend pages and custom URL patterns.
Loading only the plugins needed for a specific location can help reduce unnecessary assets, PHP execution, HTTP requests and database queries. The plugin can also be used during debugging and problem-solving: preview a page with selected plugins active, identify possible conflicts, and compare a page without changing the public site.
PRO tools for cleanup and diagnostics
- Unused-plugin suggestions: receive automatic suggestions for unused plugins on both the frontend and backend.
- Automatic checks after content updates: check for unused plugins after updating content.
- Activity recording: record Ajax activities and Post activities to identify the actions where specific plugins may need to be disabled.
- WordPress cleanup: clean up REST APIs, translated URLs and cron jobs, along with general bloat deactivation.
- Options autoload management: manage the autoloading of options as part of the optimization workflow.
- Asset controls: deactivate stylesheets and scripts from remaining active plugins, the theme and WordPress core.
- Settings management: import and export FDP settings, and use bulk actions to activate or deactivate plugins within FDP settings.
- Performance reports: generate automatic GTMetrix and Google PageSpeed Insights reports.
Frontend and backend control
PRO adds the ability to deactivate plugins in the backend, including by custom backend URL. Plugins can also be deactivated by custom frontend URL. Rules can account for logged-in and logged-out users, which supports different plugin-loading arrangements for different access states.
The broader rule set covers individual pages, blog posts, publicly queryable custom posts, post types, archives, term archives, search results and devices. Plugin deactivation on mobile is available, although disabling a plugin on mobile disables it across all mobile pages. For selective mobile page rules, the source describes integration with Specific Content For Mobile.
Practical optimization workflow
Begin by reviewing where each plugin is needed. Use automatic suggestions to identify possible unused plugins, then create conditional rules for pages, post types, archives or URLs. Preview the result before applying changes to the public site, and record Ajax or Post activity when a conflict or unexpected behavior needs investigation.
After the initial cleanup, use REST API, translated URL, cron job and asset controls for further refinement. Import and export settings when moving or reviewing configurations, and generate GTMetrix or Google PageSpeed Insights reports to compare the effects of changes.
Installation and requirements
Install and activate Freesoul Deactivate Plugins PRO, then open its settings to define plugin-loading rules and review the available PRO controls. Permanent plugin deactivation supports the permalink structures Day and name, Month and name, Post name and custom structures ending with %postname%. Other permalink structures are not supported for permanent deactivation, and permalink-changing plugins such as Permalink Manager Lite may prevent it.
Use the preview and diagnostic tools carefully when testing changes, particularly on sites with complex frontend and backend workflows.
