π©Ί DIAGNOSES THE WHY, NOT JUST THE WHAT β¦
π CATCHES SILENT SHORTCODE OVERWRITES β¦
π₯ CATCHES FATAL ERRORS BEFORE THEY HAPPEN β¦
π ERRORS ATTRIBUTED TO THE RIGHT PLUGIN β¦
πΈ FREE, SELF-HOSTED β¦
π©Ί DIAGNOSES THE WHY, NOT JUST THE WHAT β¦
π CATCHES SILENT SHORTCODE OVERWRITES β¦
π₯ CATCHES FATAL ERRORS BEFORE THEY HAPPEN β¦
π ERRORS ATTRIBUTED TO THE RIGHT PLUGIN β¦
πΈ FREE, SELF-HOSTED β¦
For sites running more than a handful of plugins
Your plugins aren't
just broken.
They're fighting.
Error logs tell you something crashed. This tells you why β two plugins registering the same shortcode, duplicate caching plugins fighting for control, or a fatal error waiting to happen before it ever fires.
Why not just use a generic query/debug plugin? Tools like Query Monitor show you what's happening on this one request. This tool cross-references your entire active plugin list against known conflict patterns and scans plugin source for collisions that haven't crashed yet β the difference between a stethoscope and an actual diagnosis.
R0
SELF-HOSTED TIER
5
DIAGNOSTIC LAYERS
0
CHANGES MADE FOR YOU
β±οΈ
CATCHES ISSUES EARLY
Sample scan
What a real diagnosis looks like.
2 Caching plugins active
wp-super-cache, litespeed-cache β pick one and deactivate the rest
Shortcode tag "gallery" registered twice
Found in: elementor, custom-gallery-plugin
Function format_price() unguarded
Found in: woocommerce, custom-pricing-addon
jquery-ui loaded via 2 handles
Detected on last front-end page view
No known SEO plugin conflicts
1 SEO plugin active β no duplication found
Diagnostic layers
Five layers, one dashboard.
βοΈ
Duplicate-purpose plugins
The most common real conflict β two plugins doing the same job, fighting for control.
π
Known pattern rules
Curated combos like Elementor + aggressive cache minification, with the actual fix.
π
Silent registration collisions
Catches shortcode, post type, and taxonomy slug clashes WordPress won't warn you about.
π₯
Redeclaration risk scan
Finds unguarded global function/class names shared across plugins β before the fatal error, not after.
π¦
Duplicate asset detector
Catches two plugins both loading jQuery UI, Slick, or Select2 separately.
π
Error-to-plugin attribution
Reads your debug.log and tallies which plugin's folder shows up in recent errors.
Setup
Install, run the scan.
1
Install & activate
Duplicate-purpose and known-pattern checks run instantly β no scan needed.
2
Visit your site once
Captures a real front-end snapshot to check for duplicate loaded assets.
3
Run the deep scan
One button scans active plugin source for silent collisions and redeclaration risk.
Licensing
Free for your sites. Sellable for clients.
Self-Hosted
R0
- All 5 diagnostic layers
- Unlimited sites you own
- On-demand deep scan
- Community support
Agency License
R499 / site / year
- Everything in Self-Hosted
- Licensed for client sites you maintain
- Priority setup support
- Custom known-pattern rule requests
Questions
FAQ.
Does it fix conflicts automatically?
No β it only diagnoses. Deactivating plugins or changing settings automatically is exactly the kind of surprise behavior that causes more problems on a live site. You stay in control of every fix.
Will the deep scan slow down my site?
It only runs when you click the button in wp-admin, has a built-in time budget so it won't run away on shared hosting, and results are cached for an hour. It doesn't run on every page load.
Does this replace testing in staging?
No β these are heuristic pattern checks, not a guarantee. Always test plugin changes in staging before touching a live site, especially for anything client-facing.
Stop guessing which plugin it is.
Five diagnostic layers, one dashboard, zero automatic changes to your site.
Get the Plugin β