Find websites using a WordPress plugin

By SearchWebCode · Updated October 20, 2026 · WordPress · 3 min read

Search wp-content/plugins/<slug> for the plugin's asset folder. Open a result to check the path in the stored source. Confirm current use separately if it matters to your research.

WordPress plugins often serve CSS, JavaScript and images from wp-content/plugins/<slug>/. Searching this asset path is more specific than searching the plugin's marketing name. Paths can also appear in quoted code or copied templates, so inspect the source around a match.

What plugins does this site use?

For a WordPress plugin search on one website, open its homepage, choose View Page Source in your browser and find wp-content/plugins/. Each folder immediately after that path is a clue: woocommerce points to WooCommerce assets, and elementor points to Elementor assets. Record the folders you actually see in script and stylesheet URLs, then check the plugin's official listing to identify its name.

If a plugin loads after interaction, inspect the browser's Network panel while using the page. Repeat on the relevant product, form or checkout page. Plugins that run only on the server, use rewritten asset URLs or bundle their assets may leave no recognizable path. This method can identify visible plugin references; it cannot list every installed or active plugin.

Step-by-step example: find sites referencing WooCommerce

Start with a known WordPress store and inspect its source for wp-content/plugins/woocommerce/. This is an illustrative path, rather than a new live-site check.
Use the folder name woocommerce to build the search query wp-content/plugins/woocommerce. Open the WooCommerce page for retained source examples and its labeled count.
Run wp-content/plugins/woocommerce to find matching homepages in SearchWebCode. Open a returned domain's stored source and look for the path in an asset tag.
Check whether the reference belongs to the page itself. Exclude tutorials, quoted integration examples and unrelated embedded content.
Confirm the live store separately if you need current usage, then export the reviewed domain list. See search credits and export allowances before a larger run.

Get the folder slug

The slug is the last part of the plugin's WordPress.org URL, wordpress.org/plugins/akismet/ → akismet. For a plugin you can't find there, open one site you know runs it and search its source for wp-content/plugins/. Don't guess from the display name: "WP Rocket" ships as wp-rocket, punctuation gets dropped, and a Pro edition sometimes lives in a different directory than the free one.

Run it

Search the exact path, e.g. wp-content/plugins/woocommerce. The latest stored query sample reports 2,527,630 estimated matches, the same signal behind the WooCommerce technology page. For scale, the bare WordPress footprint wp-content covers 25,299,907 estimated matches, so the plugin path narrows a fifth-of-the-web population down to pages exposing the plugin path.

Page builders work the same way: wp-content/plugins/elementor finds every site styled with Elementor.

Verify, then export

Open a result to read its stored homepage source with the match highlighted. Check whether the path appears in an asset reference or unrelated text, then confirm current use separately if you need an active-installation claim. Export the matching hostnames as CSV from the results toolbar. Viewing source never costs an extra search.

Narrow further

Add a second term to profile the install. "wp-content/plugins/woocommerce" "static.klaviyo.com" gives you WooCommerce stores that also run Klaviyo, a much warmer list than either footprint alone. Or exclude: "wp-content/plugins/elementor" -"wp-content/plugins/woocommerce" for Elementor sites that aren't stores.

Count examples use retained query samples from 2026-10-14. Samples describe stored source from the current index; candidate bounds, estimates and exact matches have different meanings. Methods and author information.

← All guides · Browse technologies · Search and export pricing

Explore related technology categories: Analytics · Advertising & Pixels · CMS & Site Builders · JavaScript Frameworks · E-commerce Platforms · Payment Providers · CDN & Hosting · Fonts & UI · Marketing & CRM · Chat & Support · Consent & Security · Media & Video.

Frequently asked questions

What plugins does this site use?

Open the page source and find wp-content/plugins/. Folder names in script and stylesheet URLs identify visible plugin asset references. Check the Network panel for assets loaded after interaction. Server-only plugins, renamed paths and bundled assets may be invisible, so this does not reveal every installed or active plugin.

How do I run a WordPress plugin search across websites?

Find the plugin's folder slug, search wp-content/plugins/<slug> in SearchWebCode and inspect the stored source of the results. For example, wp-content/plugins/woocommerce finds homepages referencing that path. Confirm current usage separately before treating a source match as an active installation.

Can a plugin detector find all WordPress plugins?

No. Public source can expose plugins that load recognizable assets, but server-only plugins and hidden or rewritten paths may leave no visible signature. A missing reference is not evidence that a plugin is absent.

Why not just search the plugin's name?

The name shows up in reviews, tutorials, and marketing pages far more often than on sites that run it. A wp-content/plugins/<slug> asset reference is more specific than the display name, but it can still occur in quoted code or a copied template. Inspect the stored source and confirm current use separately.

How do I find a plugin's folder slug?

It's the last segment of its wordpress.org/plugins/<slug>/ URL. For plugins not listed there, open a site you know uses it and search its source for wp-content/plugins/ to read the directory name directly.

Does a match guarantee the plugin is active?

No. A match shows that the path is present in captured homepage HTML. It can be an asset reference, quoted code or a copied template. Read the surrounding source and check the current website before claiming an active installation.