Skip to content
Webify
WordPress detector

WordPress detector

Reads theme/plugin hints from public HTML.

Target

Reads theme/plugin hints from public HTML.

Guide

WordPress detectorCommon searches and answers

The WordPress detector reads theme and plugin hints from public HTML. Searches like “is this site WordPress”, “which theme” and “how to see plugins” land here. It uses source, generator tags, wp-content paths and known file traces. Only your site or written permission. The result is not a security scan or an exploit.

Where the traces come from

Many themes print /wp-content/themes/name/. Plugins leave /plugins/folder/ in CSS and JS. meta name=generator may still print the WordPress version; that is both a hint and a risk. Hiding the version is not security but it stops an unnecessary advert. The tool only reads the public body; it does not enter wp-admin.

Cache, minify and CDN scramble class names; some plugins stay invisible. A headless or custom theme leaves no trace, so the result can say “not WordPress”. That may be a false negative. Certainty is server files and the database.

Security note

Using a plugin list against someone else is attack prep. On your own site, update or remove stale plugins. Close wp-json and xmlrpc unless you need them. Webify WordPress hosting keeps themes and plugins lean; this tool is diagnosis.

When it is not enough

WooCommerce, membership and page-builder traces are scattered in HTML. A full inventory needs the server or the admin list. If you plan a move, attach the output to the technical brief; quotes are not written from guesses.

Updates, hiding traces and search intent

People search “is this site WordPress”, “find theme name”, “list plugins”. On your own site the real work is turning off the generator, deleting unused plugins and updating PHP in the hosting panel. The detector is a mirror: whatever the public sees, an attacker sees. A visible version plus a stale plugin is a known-CVE search.

A page builder (Elementor, WPBakery) bloats HTML and signs itself in class names. On a move that trace adds working days regardless of content volume. Multilingual, form and slider plugins sit the same way. Webify WordPress hosting keeps one theme and a short plugin list. This page does not write a setup; it reads the current trace. Do not scan a rival shop “for analysis”; without written permission it is reconnaissance.

Frequently asked questions

These are the queries people type for this tool. Answers match the visible text.

Enter the URL. wp-content, generator or a known file trace means WordPress is likely.

The /themes/folder/ path in HTML is the theme directory. A custom theme may use a random name.

Minify, CDN or a hiding plugin wipes traces. The list can be incomplete; it is not a full inventory.

It narrows the target for an attacker. Hiding it is not enough; updates are the real work.

No. Only public HTML and known public file traces.

Usually no. The front is separate so traces vanish. A false negative is possible.

Only your site or written permission. Otherwise it is reconnaissance.

Sometimes wc- classes and plugin paths appear. Their absence does not mean there is no shop.

No, it is a diagnostic summary. A migration quote needs server, plugin list and content volume.

Themes and plugins stay lean, PHP and backups are defined, login is restricted. This tool only shows the current trace.