Home / Guides / How to see what WordPress plugins a website uses

Guide · WordPress

How to see what WordPress plugins a website uses

By SearchWebCode · Updated November 19, 2026 · WordPress · 2 min read

A website window containing three plugin pieces.
Find wp-content/plugins/ in the page source and inspect the folders in real script or stylesheet URLs. Use Network for later-loaded assets. Public checks cannot reveal every installed plugin.

This check starts with one website and asks which plugin clues it exposes. If you already know the plugin and want a list of websites, use the reverse plugin lookup guide instead.

Find the folders in asset tags

Open View Page Source and search for wp-content/plugins/. In a default path, the next folder is a starting clue to the plugin. Keep the complete tag so you can see whether it loads a script or stylesheet.

<link rel="stylesheet"
  href="/wp-content/plugins/elementor/assets/css/frontend.min.css">

This illustrative tag points to an elementor folder. It is not a full plugin inventory or a checked installation on a named website. A folder in quoted code should be recorded as a mention rather than a loaded asset.

Inspect requests made after interaction

Open DevTools → Network, reload and filter for plugins/. Try the page feature you need to investigate, such as opening a form. Inspect the request URL, response and initiator.

Some plugins load assets only on certain pages. A form on a contact page can expose a different set from the homepage. Consent settings, lazy loading, caches and optimization tools can change what your session requests.

Turn a folder into a likely plugin name

  1. Copy the folder slug without inventing a product name from its appearance.
  2. Check the official plugin listing or vendor documentation.
  3. Compare a known installation when a paid edition or renamed folder is involved.
  4. Record the path as evidence, keeping uncertain names marked as uncertain.

The Elementor and WooCommerce pages provide source-reference examples. An asset version parameter may describe a build or cache key; do not assume it is a trustworthy installed-plugin version.

A small source-reading example

In this local example, two tags and one comment all contain folder names:

<link rel="stylesheet" href="/wp-content/plugins/elementor/example.css">
<script src="/wp-content/plugins/woocommerce/example.js"></script>
<!-- Tutorial example: /wp-content/plugins/example-only/file.js -->

The first two lines are asset references to inspect. The comment is a source mention. Neither the path text nor an unsuccessful asset request establishes a working plugin. The HTML and loaded-resource search guide helps keep these observations separate.

Know what a public check misses

Server-only plugins may expose no frontend assets. WordPress permits custom content and plugin URL arrangements; CDNs, bundlers and renamed directories can hide familiar paths. Public source also cannot reliably distinguish every active, inactive or must-use plugin.

If you administer the website, inspect its Plugins screen and deployment configuration for the inventory you control. For an external site, report visible clues and limitations. A missing folder is not proof that the plugin is absent.

Use the evidence in a broader check

Record the page URL, candidate plugin, asset URL, request outcome and date. Keep those observations alongside other layers in the technology-stack workflow. Once you confirm a useful folder, the cross-site plugin search can find stored homepages that reference it.

References

WordPress explains plugin and content directory URLs and the plugins_url function.

Source counts checked 2026-10-14. They describe stored homepages, not live installations. How the counts are measured.

Frequently asked questions

Can this method list every active WordPress plugin?

No. Server-only plugins and assets hidden by custom paths or bundling may not appear. An administrator has better inventory information than public source provides.

Is a folder name always the plugin product name?

No. Treat it as a slug to verify against official listings, vendor documentation or a known installation.