WordPress Stack Detector
Deep WordPress stack inventory for handover — theme, plugins, builders, with evidence.
Deep public inventory · handover-ready
What is on this WordPress site?
Deep scan builds a clear brief: theme, builder, plugins by category, with evidence — so you know what a reference site actually runs.
Authorized-use only. Curated popular-plugin probes + public signals. No full-directory brute-force. No vulnerability claims.
Agency snapshot
Handover brief
Stack summary
Themes
Plugins
Public footprint + curated deep probes. Hidden plugins may still be absent.
Related tools
More from the same category
Meta Tag Generator
Generate SEO meta tags for a page.
OG Tag Generator
Generate Open Graph tags for sharing.
Robots Generator
Generate robots.txt rules.
Sitemap Generator
Generate an XML sitemap for SEO.
Twitter Card Generator
Generate Twitter Card meta tags.
UTM Builder
Build URLs with UTM campaign parameters.
Learn more — open a section when you need details
Deep WordPress Stack Detector builds a handover-ready inventory: theme, plugins, builders, SEO, security, cache and more — from public HTML/JS, REST namespaces and curated deep probes. Every item has evidence and confidence. No fake CVEs, no scare banners.
-
1
Paste a public WordPress site URL.
-
2
Click Deep scan — HTML fingerprints, REST map, curated plugin probes.
-
3
Read the handover brief, then drill into themes/plugins with evidence.
Client says “make me a site like this”
Deep-scan the reference URL and see theme, builder, WooCommerce, SEO stack, etc.
Agency handover
Copy the brief before taking over maintenance.
Pre-security audit
Inventory first, then open WordPress Security Scanner for exposure checks.
Deep scan probes popular plugin readme.txt files only — not the entire WP.org directory.
CONFIRMED = HTML path, fingerprint or verified readme. LIKELY = REST namespace.
Hidden plugins with zero public footprint can still be missing — we never invent them.
It lists what public signals prove — plus curated probes for popular plugins. Fully hidden plugins stay invisible by design.
It only requests public readme.txt paths for a curated popular list, with SSRF protection and rate limits.
Never claimed here. Use WordPress Security Scanner for exposure signals without fake CVEs.