Skip to content

WordPress Plugin Detector

Try for free

Check a list of domains: does each site run WordPress, and which plugins (e.g. TranslatePress, WooCommerce, Elementor) does it use? One row per domain with the evidence, plugin versions, page languages and the page checked.

🔌 WordPress Plugin Detector

Give it a list of domains and find out, for each one, whether the site runs WordPress and whether it uses the plugins you care about, such as TranslatePress, WooCommerce, Elementor or Yoast SEO. You get one row per domain with a clear yes or no, the evidence behind it, the plugin and WordPress versions where the site shows them, the page's languages and the exact page that was checked. No login or API key needed.

✨ Why use WordPress Plugin Detector?

  • 🎯 Any plugin, by its slug: look for one plugin or many in the same run (translatepress-multilingual, woocommerce, elementor...), or leave the list empty to get every plugin the home page loads.
  • 🔍 Evidence you can check: every match says why: plugin files linked from the page, plugin markup (for example TranslatePress's language switcher and body class), or the plugin's public readme.txt.
  • 🧩 Finds plugins that caching hides: sites that merge their CSS and JavaScript still show plugin markup, and the readme.txt check finds plugins the page does not link at all.
  • 🟢 Active or just installed: activeOnPage tells you whether the page itself shows the plugin; pluginFilesFound tells you whether its files are on the site.
  • 🌍 Multilingual sites at a glance: the page's language versions (hreflang) come with every row.
  • ⚡ Fast: plain HTTP, 10 domains in parallel, one row per domain as soon as it is checked.

🎯 Use cases

  • 📇 Lead generation: build lists of sites that use a plugin you sell add-ons, translations, hosting or services for.
  • 🧪 Market research: measure how many sites in a list use a plugin and which versions they run.
  • 🔄 Migration and support work: find the sites in your client list that still run an old plugin version.
  • 🌐 Localization outreach: find multilingual WordPress sites (TranslatePress and their languages).

🚀 How to use

  1. Paste your domains into Domains or websites, one per line.
  2. Put the plugin slugs you want into Plugins to look for (the prefill is TranslatePress). The slug is the last part of the plugin's wordpress.org link, e.g. wordpress.org/plugins/woocommerce/ → woocommerce.
  3. Click Start.
  4. Download the rows as JSON, CSV or Excel, or read them through the API. The Plugin details view has one line per domain and plugin.

📥 Input

FieldWhat it does
domainsDomains or website addresses. example.com, www.example.com and https://example.com/blog/ all work.
pluginsPlugin slugs (or wordpress.org plugin links). Empty = only WordPress detection and the list of plugins the page loads.
checkPluginFilesOn WordPress sites, also look for each plugin's readme.txt (default on).
proxyConfigurationProxy settings; datacenter by default.
{
  "domains": ["translatepress.com", "wordpress.org", "stripe.com"],
  "plugins": ["translatepress-multilingual"],
  "checkPluginFiles": true
}

📤 Output

FieldMeaning
domainThe domain you gave (without www).
urlThe address that was requested for it.
pageCheckedThe page that was read, after redirects.
finalDomainWhere the site redirected to, if anywhere.
httpStatus / reachable / errorWhether the page could be opened, and why not (no answer, a refused request or a server error).
noteSet when https did not work and the page was read over http.
wordpressDetected / wordpressVersion / wordpressSignalsWordPress yes or no, its version when the site shows it, and the markers found.
detectedPluginsThe requested plugins found on the site.
allRequestedPluginsDetectedTrue when every requested plugin was found.
pluginsPer requested plugin: detected, activeOnPage, pluginFilesFound, version, name and the signals (evidence).
pluginsOnPageEvery plugin folder the page loads files from.
languagesThe page's language versions (hreflang).
pageTitle, checkedAtPage title and check time.

Example row (shortened):

{
  "domain": "vivafutura.org",
  "pageChecked": "https://vivafutura.org/",
  "httpStatus": 200,
  "reachable": true,
  "wordpressDetected": true,
  "wordpressVersion": "7.1.4",
  "detectedPlugins": ["translatepress-multilingual"],
  "allRequestedPluginsDetected": true,
  "plugins": [
    {
      "slug": "translatepress-multilingual",
      "name": "TranslatePress - Translate Multilingual sites with AI Translation",
      "detected": true,
      "activeOnPage": true,
      "pluginFilesFound": true,
      "version": "3.3.9",
      "signals": ["plugin files linked from the page", "TranslatePress body class", "TranslatePress language switcher", "plugin readme.txt found"]
    }
  ],
  "pluginsOnPage": ["masterstudy-lms-learning-management-system", "elementor", "translatepress-multilingual"],
  "languages": ["en-GB", "es-CO", "de-DE"]
}

❓ FAQ

Is it legal? It reads public pages and public files of each website, the same files every visitor's browser loads. Use the results in line with the laws that apply to you.

Do I need a login or proxy? No login. The default datacenter proxy works for most sites; a site that refuses it gets one more try through a residential address.

How many domains can I check? As many as you like in one run; they are checked 10 at a time.

Why does a plugin show pluginFilesFound: true but activeOnPage: false? Its files are on the site, but the checked page shows nothing from it. The plugin may be used only on other pages, or it may be installed but turned off.

What if the site is not WordPress? wordpressDetected is false and no plugin files are requested.

Can I schedule it or use the API? Yes. Save your input as a task and schedule it, or start runs through the Scrape.ly API, CLI or MCP server.

⚠️ Limits

  • One page per domain is read: the home page, or the address you give. A WordPress install that lives only in a sub-folder (e.g. /blog/) needs that address.
  • Sites that hide every WordPress and plugin marker (and block the plugin folders) show as not WordPress or not found.
  • Versions come from the plugin's readme.txt or its asset URLs; a site can show an outdated readme.
  • Sites that moved their plugin folder away from wp-content/plugins (security or hosting setups) show plugins only through their page markup, and the readme.txt check looks in the standard folder.
  • The actor checks the domains you give; it does not search the web for sites.
//From the blog\\

Latest articles

All articles

The internet is full of data.
Start owning yours.

Scrape.ly gives you the infrastructure, the tooling, and the team to extract, process, and operationalize web data at any scale. Setup takes minutes.

No credit card. No setup calls.