Free tool
WordPress Plugin Detector
Paste any website address and see which WordPress plugins it runs. Free, no sign-up.
Trying to find out what plugins a WordPress site is using? Paste the address above. Every plugin that puts a stylesheet or a script on the page is served from a folder carrying its own name, so the list is readable straight from the HTML the site already sends to every visitor.
This is also how you check whether a site runs WooCommerce, and what it has bolted on around it — payment gateways, subscriptions, booking systems, cart recovery. If you have ever wondered how to know what a website is built with without asking its owner, this is the honest version of that answer.
One caveat we would rather state than bury: the count is a floor, not a total. Plugins with no front-end footprint leave no trace on a homepage, and a caching optimizer can bundle the visible ones out of sight entirely. When we can see the optimizer doing it, we name it.
Other ways people ask for this
- How to know what plugins a website is using
- WordPress plugin checker for any URL
- Find out what WordPress theme and plugins a site has
- Check if a website uses WooCommerce
- WP plugin finder / plugin lookup tool
- See which plugins a competitor’s site runs
- Detect page builders like Elementor or WPBakery
What people do with the answer
- Plugin developers size a market and see which competing plugin a prospect already runs.
- Agencies scope a takeover — know what you would inherit before you quote for it.
- Site owners see what comparable sites in your niche chose, and copy what works.
- Security reviewers spot an outdated plugin from the version string a site publishes with it.
What this can see, and what it cannot
WordPress leaves its plugins in plain sight. Every plugin that puts a stylesheet or a script on the page is served from a path carrying its own folder name, so the plugin list is readable from the same HTML any visitor receives. No scanning, no probing — one ordinary page request.
That is also the limit. A plugin with no front-end footprint leaves no path to read. Backup tools, security scanners, SEO admin screens, most server-side integrations: all invisible. The count you get is a floor, not a total, and any tool claiming otherwise is overstating what a homepage can tell it.
The other limit is optimizers. WP Rocket, LiteSpeed and friends exist precisely to merge those separate files into one — which is good for the site’s speed and fatal for this technique. We detect the optimizer and say so, because “this list is short because of that plugin” is a real answer where a short list on its own would be misleading.
What the detector reports
- Plugin list — display names, not raw folder slugs
- Theme — read from the same page, at no extra cost
- WooCommerce — confirmed from structural markers, never from the word appearing in the text
- The optimizer, when one is bundling the assets and shortening the list
- The optimizer, when one is shortening the list
A site we cannot read returns “could not check”, never “no plugins” and never “not WordPress”. A failure to measure is not a finding.
The most-installed WordPress plugins
Measured across 2.3 million WordPress sites. We hold a plugin list for 1,978,590 of them — 86.13%.
| Plugin | Sites | Share of sites with plugins |
|---|---|---|
| Elementor | 750,586 | 37.94% |
| Contact Form 7 | 749,301 | 37.87% |
| Elementor Pro | 402,236 | 20.33% |
| Slider Revolution | 390,290 | 19.73% |
| WPBakery Page Builder | 276,765 | 13.99% |
| Jetpack | 228,449 | 11.55% |
| WooCommerce Payments | 146,932 | 7.43% |
| WooCommerce Stripe Gateway | 118,355 | 5.98% |
| Instagram Feed | 110,679 | 5.59% |
| Essential Addons for Elementor Lite | 109,825 | 5.55% |
| Site Kit by Google | 102,324 | 5.17% |
| WP Rocket | 100,910 | 5.10% |
| YITH WooCommerce Wishlist | 98,817 | 4.99% |
| CookieYes | 98,051 | 4.96% |
| Mailchimp for WooCommerce | 94,527 | 4.78% |
The long tail is the real story. Those fifteen are the recognisable names, but the dataset holds 151,473 distinct plugin names across 1,978,590 sites. Most WordPress sites run at least one plugin you have never heard of.
Read these as a floor. Each figure counts sites where the plugin was visible from the homepage, so every one of them undercounts — by an unknown amount that is larger for plugins with a light front-end footprint. The ranking is reliable; the absolute numbers are minimums. Measured 16 August 2026.
More free tools
The other free tools
Same dataset, same rules about what counts as a measurement. No sign-up on any of them.
Shopify Theme Detector
Which theme a store runs, and whether it came from the Theme Store or was built custom.
Check a theme →Shopify App Detector
Which apps a store runs, read from the storefront it already serves everyone.
Check a store →WordPress Theme Detector
Which WordPress theme a site runs, read from the page it serves every visitor.
Check a theme →Wix App & Currency Detector
Which apps a Wix site installed from the App Market, and the currency its shop charges in.
Check a Wix site →All free tools
Everything we have opened up, and what each one reads to answer you.
Browse the tools →Frequently asked questions
How does the WordPress plugin detector work?
WordPress serves every plugin’s stylesheets and scripts from a path that contains the plugin’s own folder name — /wp-content/plugins/<name>/. Those paths are in the HTML the site sends to every visitor. The detector reads that one public page and lists the plugin names it finds. No login, no scanning, nothing that is not already public.
Is it free?
Yes. No sign-up, no credit card, no email required.
Why does it find fewer plugins than the site actually runs?
Because a homepage can only reveal plugins that put something on the homepage. Admin-only, backend and most server-side plugins emit no front-end asset and are invisible from outside. Treat the result as a floor, never a total — the number we find is the number that leave a trace, not the number installed.
It found a theme but no plugins at all. Is that right?
Usually that means an optimizer is bundling them. WP Rocket, LiteSpeed Cache, Autoptimize and SG Optimizer merge every plugin’s CSS and JavaScript into one combined file, which erases the individual plugin paths. Measured across our dataset, that explains 81.2% of the sites where we find a theme but zero plugins. When we can identify the optimizer, we name it in the result.
Does it work for a site you have never crawled?
Yes — any WordPress site, whether or not we have seen it before. Paste the address and you get an answer.
What is the difference between a plugin and an app?
They are the same idea under two platform vocabularies. WordPress calls its add-ons plugins; Shopify calls its add-ons apps. We use each platform’s own word rather than flattening both into one, because merchants and developers search for them separately.
Does it say whether the site is WooCommerce?
Yes. WooCommerce is itself a WordPress plugin, so it appears in the list — and we confirm it separately from structural markers in the page, not from the word “WooCommerce” appearing somewhere in the text.
The site did not respond. Does that mean it is not WordPress?
No, and we never report it that way. A timeout, a bot filter or a server error tells us nothing about what the site runs. Those return “we couldn’t check”, which is a different answer from “not WordPress” and from “no plugins found”.
Plugins across a whole market, not one site at a time
One lookup answers one question. MyLeadFox holds plugin data for 1,978,590 WordPress sites, filterable alongside 98 other fields — country, platform, currency, contact details. Browse the WooCommerce directory to see its shape, or check which theme a site runs with the companion tool.
Find sites by the plugins they run
Filter by plugin, theme, platform, country and 95 more fields — then export with verified contact data.
