How to use
- Enter the address of the site you want to check. You can leave out
https://and typeexample.com. - Press Detect WordPress. The tool does not look anything up while you type; it reads the page once when you press the button.
- At the top you get a verdict such as “looks likely” or “could be WordPress” together with a trace score. It is a pile of clues, not a confirmation.
- The tables below show which traces were found and the evidence, the theme and plugin folders visible in file addresses, and version hints. Copy result puts the summary on your clipboard.
Which traces are looked for
WordPress leaves paths and tags with fixed names all over a page’s HTML. This tool looks for the traces below in the attribute values, the inline scripts and styles, and the response headers, then adds up a weight for each trace found.
| Trace | Strength | Weight |
|---|---|---|
| WordPress in the generator meta tag | Strong | 35 |
REST API address (api.w.org link or a Link response header) |
Strong | 30 |
wp-content paths (themes, plugins, uploads) |
Strong | 25 |
wp-includes paths (core scripts and styles) |
Strong | 25 |
xmlrpc.php, RSD, wlwmanifest, X-Pingback header |
Medium | 15 |
Emoji settings script, admin-ajax.php reference, block editor classes, body classes |
Medium | 10 each |
Short link (?p=number) |
Weak | 5 |
The sum is capped at 100. 50 or more reads “looks likely”, 20 or more “could be WordPress”, 1 or more “a few faint traces”, and 0 “no traces found”. For example, a REST API Link header plus an X-Pingback header alone gives 30 plus 15, which is 45 and reads “could be WordPress”. A single wp-content path gives 25.
Theme and plugin folders
When a file address looks like /wp-content/themes/folder-name/ or /wp-content/plugins/folder-name/, the folder names are collected and listed with how often they appeared. Widely used plugins such as WooCommerce, Elementor, Yoast SEO and Contact Form 7 get their known name next to the folder. The name is only a lookup of the folder name, so it can be wrong if a site renames the folder.
Only plugins that output files on the page are visible. Plugins that work only on the server, or that load only after login, cannot be found, and a theme folder may be a child theme or a leftover from an old theme.
About the version hints
If a generator meta tag exists, the version the site states is shown, together with the most common ver= value found in wp-includes file addresses. Both are only hints. Security plugins can remove the generator or replace it, and ver= is a number used to refresh caches, so it can differ from the real version. This tool does not judge which versions are vulnerable. Check updates and security notices in the site admin and in WordPress’s official announcements.
Limits of accuracy
- A site that removed its traces, changed its path rules, or splits the front end from the admin (static site generators, headless setups) can be WordPress and still go undetected.
- The reverse also happens. Other tools can use the same folder names as WordPress, and files copied from a WordPress site can produce traces on a site that is not WordPress.
- Sentences in the article text are not read, only attribute values and inline scripts and styles. A post that merely explains WordPress will not be flagged.
- Only the first HTML response is read, so files that JavaScript loads later are not seen.
What goes to the server
Only the address you type is sent to the server for the lookup, and it is not stored. The server reads the address once, gives up after 8 seconds, and reads at most 1 MiB of the body. Private addresses and raw IP addresses cannot be looked up. Lookups are limited to 6 per minute per IP address and 30 per minute in total to the same site, and you are asked to retry shortly if you go over. Redirects are followed at most 5 times, and only the default ports (80 and 443) are allowed. This is not meant for probing other sites’ setups to attack them or for loading them.
Frequently asked questions
How can I tell whether my site runs WordPress?
Enter the address and run the check. Usually several of wp-content, wp-includes, the generator meta tag and the REST API link show up together. You can also try opening /wp-admin on the site yourself.
The result says nothing was found. Could it still be WordPress?
Yes. Trace-removal plugins, security settings that change paths, and setups split across domains can hide every trace. The result is not evidence that the site is not WordPress.
If I know the theme name, can I build the same site?
A folder name alone rarely identifies a theme exactly, and the same theme can look different depending on settings, plugins and custom code. Treat the folder name as a starting point for searching.
Does it tell me whether a plugin version is vulnerable?
No. It shows folder names and how often they appeared. Whether a version is vulnerable has to be checked against official security notices, and this tool does not make that call.
Can I also check the SEO of a WordPress site?
Enter the same address in the Blog SEO Checker to check the basic items such as title, heading structure and image alt text.
Related tools
- Basic on-page SEO items with the Blog SEO Checker
- Check tags from pasted source with the Meta Tag Checker
- List every link on a page with the Link Extractor
- Pull image addresses with the Webpage Image URL Extractor
- Server config files with the .htaccess Generator, crawler rules with the robots.txt Generator
The address you type is sent to a server for the lookup and is not stored. The analysis of the returned HTML runs in this browser.