Detect WordPress, its theme and visible plugins from page fingerprints
What is the WordPress Detector?
The wordpress detector works like this: it checks a page's HTML for WordPress fingerprints - wp-content paths, REST API links, generator tags - and names the theme and visible plugins. Everything happens on your device - the input never leaves your tab unless the tool clearly states it performs a server-side lookup.
How to use the WordPress Detector
Enter the full URL, domain or content the tool asks for.
Run the check - fetch-based tools query the page server-side.
Read the findings as a list, not a single score.
Fix one issue at a time and re-run to verify.
Features
Checks run server-side so protected pages can be read
Results explain the rule or value behind every finding
Copy and export options for every result list
No account needed for any check
Common mistakes to avoid
Auditing a staging or password-protected URL instead of production
Fixing everything at once instead of one change plus re-test
Getting a reliable answer for wordpress detector without installing an app
One-off tasks done in under a minute from any device
Checking results before committing them to something important
Working on a phone where desktop software is unavailable
Privacy
The URL you check is fetched once so the tool can read pages that block cross-origin browser requests. No browsing history is stored, and nothing from your own device is transmitted.
Frequently asked questions
Why does it say "no fingerprints" for a WordPress site?
Optimization plugins and headless frontends strip or rename the telltale paths - absence is not proof of absence.
What fingerprints does it look for?
wp-content paths, REST API links, generator meta tags and theme/plugin markers in the delivered HTML - the traces WordPress leaves in its own markup.
Can a detection be wrong?
Occasionally - heavily customised or cached sites can strip the usual markers. A negative result means no fingerprints found, not a guarantee the stack is absent.