The detector examines public page references. Custom themes, renamed paths and optimization can hide the original theme, so an inconclusive result is possible.
- Public markup
- Theme asset paths
- Possible matches
How to use this tool
- Enter the public WordPress website domain.
- Run the detector to inspect public HTML and linked theme assets.
- Review the detected platform, candidate theme folders and any metadata returned.
Understanding the results
- Theme folders
- A wp-content/themes path can identify a candidate theme directory, including a child theme. A folder name is evidence, not a guaranteed commercial product name.
- Theme metadata
- Available public theme metadata can add a theme name or other context. Not every website exposes it.
- Multiple candidates
- A page may reference parent and child themes or cached assets. Review the evidence before deciding which theme powers the site.
What this check covers
Custom asset paths, combined files, caching and headless delivery can hide WordPress clues. The shared detector can also identify Joomla evidence when present; it reports what it finds without assuming the platform from this page’s title. No administrator login or private theme files are accessed.
Common questions
Can it identify a custom WordPress theme?
It may find a directory or available metadata, but a custom theme may have no public product page or recognizable name.
Does no result mean the site is not WordPress?
No. It means the fetched homepage did not expose enough supported evidence. The site may hide or rewrite its theme asset paths.