WordPress Theme Detector
How the detection works
WordPress serves theme assets from /wp-content/themes/<slug>/ and plugin assets from
/wp-content/plugins/<slug>/. Every stylesheet and script the page loads carries the
slug in its path, so the theme name is written into the page that anyone can view.
Nothing here probes for files, guesses paths or tests for vulnerabilities. Only the HTML the server chose to send is read.
Why a child theme shows two names
A child theme loads its own style.css and the parent's, so both slugs appear. The
parent is reported as the theme because that is what determines the templates; the
child is where the customisations live. This is also why
creating a child theme is the correct way to
modify a theme you did not write.
Where the method fails
- A caching or optimisation plugin rewrote the paths. Combined and minified assets are often served from a neutral directory, which erases the slug.
- The theme is custom. A slug tells you the folder name, not whether the theme is public, commercial or built for that one site.
- Plugins that load nothing on this page stay invisible. An empty plugin list means nothing loaded here, not that the site is lean. Check a page that does more work — a shop page rather than a text page.
- The generator tag is often removed. Its absence says nothing.
What to do with the answer
Finding the theme is usually the start of a different question. If you liked the layout, what you actually want is the pattern, not the product — the honest version of that question is in how to find what theme a site is using, and the selection criteria are in choosing a WordPress theme.
If you are auditing your own site, the plugin list is the more useful half. Every plugin loading assets on a page is weight you are paying for, which is where speeding up a WordPress site begins.