WordPress Theme Detector & CMS Checker

See which CMS a site runs on and, for WordPress, which theme (and parent theme) it uses and which plugins show up in the page code.

Need more than the CMS and theme — analytics, CDN, JS libraries, fonts? Open the website technology checker.

How to find out which CMS and WordPress theme a site uses

The tool loads the page and looks for CMS fingerprints in the HTML and headers: WordPress, Joomla, Drupal, Shopify, Wix, Tilda, Bitrix and more. On a WordPress site it finds the theme folder, reads the header of its style.css (name, version, author, parent theme) and lists the plugins whose files appear in the page code.

WordPress theme: name, version, author, Theme URI

Child theme and its parent theme

Plugins visible in the page code

CMS and site builders: Joomla, Drupal, Shopify, Wix, Tilda and more

How to Use

Enter the homepage or any page URL
Check the detected CMS and confidence level
For WordPress, review the theme, parent theme and plugin list

Use Cases

Quickly inspect competitor CMS and tech stack.
Prepare personalized agency outreach or migration offers.

Limitations

Heavily customized sites can be reported as Unknown.
Detection relies on signatures and public fingerprints.

Example Input / Output

Example Input

https://store.example.com

Example Output

Detected CMS: Shopify (confidence 0.92), plus Cloudflare CDN and analytics tags.

FAQ

Enter the site address above. The tool finds the /wp-content/themes/<folder>/ path in the code and reads that theme's style.css header. By hand: view the page source (Ctrl+U), search for “wp-content/themes” and open style.css in that folder.

The site uses a child theme: its style.css has a Template line naming the parent theme folder. Design and features come from the parent; the owner's customisations live in the child.

From the outside you only see plugins that load their own CSS, JS or images on the page. SEO, caching, security and backup plugins run on the server and usually leave no trace, and optimisation plugins often merge files.

This page covers the CMS, WordPress theme and plugins. The technology checker shows the whole stack: analytics, CDN, JS libraries, fonts and servers.

What CMS is this site? How detection works

Every content management system leaves recognisable traces in the page code. The detector loads the page once and checks for them:

The generator meta tag — <meta name="generator" content="WordPress 6.6">. The most direct signal, but often removed.
File paths — /wp-content/ for WordPress, /media/system/js/ for Joomla, /sites/default/files/ for Drupal, /bitrix/ for Bitrix.
Platform CDN domains — cdn.shopify.com, static.wixstatic.com, tildacdn.com.
HTTP headers — for example X-Generator: Drupal, or a link to the WordPress REST API in the Link header.

The more signals match, the higher the confidence score. A single weak signal is a reason to double-check, not a final answer.

How the WordPress theme detector finds a theme

A WordPress theme lives in /wp-content/themes/<folder-name>/, and the theme's stylesheets, scripts and images load from that path. The detector picks the folder name out of the page code, then opens the theme's style.css. Every WordPress theme must have this file, and it starts with a header comment:

/*
Theme Name: Astra Child
Theme URI: https://example.com/
Author: Studio Name
Version: 1.0.2
Template: astra
*/

Field	What it tells you
Theme Name	The theme name as the owner sees it in the dashboard
Theme URI	The theme's home: the developer's site, a marketplace or the wordpress.org directory
Author	The developer or agency
Version	The installed version — a hint at how recently it was updated
Template	Only in child themes: the parent theme's folder

To do the same by hand, view the page source (Ctrl+U, or Cmd+Option+U on a Mac), search for wp-content/themes and add style.css to the path you find.

Child themes and parent themes

Many sites run a child theme: a popular parent theme — Astra, GeneratePress, Kadence, Divi, Genesis — provides the design and features, while the owner's changes sit in the child theme so updates don't wipe them out. When the header has a Template line, the detector shows both themes and marks which one is active. If you want a similar site, the parent theme is what you can actually buy or download; the child is usually one of a kind.

The theme name returns nothing on Google

That happens a lot, and it isn't a detector error:

Custom theme. A folder like company-2024 and a Theme URI pointing at an agency site.
Renamed theme. Developers often change the Theme Name of a purchased theme. Author, Theme URI and the Template line give it away.
Premium marketplace theme. Search by Theme URI or author name; wordpress.org doesn't list these.

When no theme shows up

The detector says so plainly when there are no theme paths in the code. The usual reasons:

wp-content was renamed, or assets are served from a CDN under a different path.
An optimisation plugin merged all stylesheets into one file under /wp-content/cache/.
Headless WordPress: the front end is built with Next.js or another framework, and WordPress only serves an API.
style.css is blocked for bots or served without its header. In that case you get the folder name only.

Which WordPress plugins you can see from outside

Plugins live in /wp-content/plugins/<name>/, and the detector lists every plugin folder that appears in the page code. You'll see the ones that load their own styles, scripts or images: page builders (Elementor), forms (WPForms, Contact Form 7), shops (WooCommerce), sliders, chat widgets. Plugins that work only on the server — caching, security, backups, redirects — stay invisible. SEO plugins often reveal themselves in an HTML comment such as “This site is optimized with the Yoast SEO plugin”, even when they load no files on the page.

The list depends on the page: a form plugin may only load on the Contact page. Check a few page types — the homepage, a post, a product page.

Fingerprints of other CMSs and site builders

Platform	Typical sign in the code
Joomla	`/media/system/js/`, `/components/com_`, generator “Joomla!”
Drupal	`/sites/default/files/`, header `X-Generator: Drupal`
Shopify	`cdn.shopify.com`, the `Shopify.theme` object
Wix	`static.wixstatic.com`
Tilda	`tildacdn.com`, blocks with the `t-rec` class
Bitrix	`/bitrix/`, `BX.ready`

If you need the whole stack rather than just the CMS — analytics, CDN, JS libraries, fonts — use the website technology checker. For a detailed look at server headers, run the HTTP headers check.

If it's your site: what's worth hiding

Knowing the CMS isn't a vulnerability in itself, but outdated theme and plugin versions are a common way WordPress sites get hacked. Keep them updated and remove the ones you don't use. Many owners strip the WordPress version from the generator tag, yet ?ver= parameters on asset URLs still give it away. Updating is a better defence than hiding.