1. Home
  2. WordPress Theme Detector
Enter any WordPress website URL
How this works: Detection is performed by fetching the site's public HTML source and style.css via a CORS proxy, then scanning for WordPress markers — the same signals used by WPThemeDetector and WPDetector. Results depend on the site's public accessibility. No data is stored.
Try a sample WordPress site:
🎨
—
—
How Detection Works
Fetch HTML Source
The page HTML is fetched via a CORS proxy and scanned for WordPress fingerprints.
Parse style.css
The theme's style.css header is fetched to extract name, version, author and URI.
Detect Plugins
All /wp-content/plugins/SLUG/ paths in scripts and links are extracted as plugin slugs.
Tech Fingerprint
WP version, page builder, cache plugin, CDN, and security plugin patterns are identified.

How to Detect a WordPress Theme in 5 Steps

Use this tool to identify any WordPress theme and its associated plugins in under 30 seconds. Here's exactly what happens at each stage.

Enter the Website URL

Type or paste the full URL of any website into the search field. The tool automatically prepends https:// if omitted. You can also click one of the sample site chips to run a demo detection immediately.

WordPress Is Verified

The tool fetches the page HTML via a CORS proxy and checks for WordPress fingerprints: /wp-content/, /wp-includes/, the generator meta tag, and the REST API endpoint. If none are found, the tool reports that this is not a WordPress site.

Theme Slug Is Extracted

All /wp-content/themes/SLUG/ occurrences in the source are tallied, and the most frequently referenced slug is identified as the active theme. The theme slug is then used to fetch the style.css file.

style.css Header Is Parsed

The WordPress theme header comment block inside style.css contains structured metadata: Theme Name, Version, Author, Author URI, Description, Template (parent theme slug), Text Domain, License and Tags. This tool extracts all available fields and presents them in the Theme CSS Info tab.

Plugins and Tech Stack Are Reported

All /wp-content/plugins/SLUG/ paths are extracted as installed plugin slugs and matched against a database of 60+ known plugins. Page builders, caching plugins, CDNs, analytics tools and security solutions are also identified through HTML fingerprinting. Use Copy Report to export all findings.

About This WordPress Theme Detector

The TechOreo WordPress Theme Detector is a free, browser-based tool that identifies the active theme, child theme, plugins and full technology stack of any publicly accessible WordPress website. Detection runs entirely client-side using JavaScript — your queries are never logged or stored on TechOreo's servers.

The tool works by fetching the target site's public HTML via a CORS proxy and applying the same source-scanning techniques used by tools like WPThemeDetector and WPDetector: locating theme paths in /wp-content/themes/, reading the style.css header comment, extracting plugin slugs from /wp-content/plugins/ paths, and fingerprinting technology stack signals through CSS class names, script handles and asset URL patterns.

What This Tool Detects

🎨Active theme name, slug, version & author
🔗Theme URI and Author URI from style.css
👶Child theme and parent theme relationship
🔌60+ known WordPress plugins by slug
🏷️WordPress core version number
🧱Page builders (Elementor, Divi, WPBakery, Beaver)
🚀Caching plugins (WP Rocket, W3TC, LiteSpeed)
☁️CDN providers (Cloudflare, jsDelivr)
📊Analytics & tracking (GA/GTM, Hotjar, FB Pixel)
🔒Security plugins (Wordfence, Really Simple SSL)
🛒eCommerce (WooCommerce, Easy Digital Downloads)
📄Exportable plain-text detection report

Frequently Asked Questions

Common questions about WordPress theme detection, how the tool works, and what to do when detection fails.

The easiest method is to use this tool — enter the URL and click Detect Theme. Alternatively, view the page source directly (Ctrl+U), search for /wp-content/themes/, and note the folder name immediately after /themes/ — that is the theme slug. Navigate to https://example.com/wp-content/themes/SLUG/style.css to read the full theme header with name, version and author.
Yes. WordPress plugins load their JavaScript and CSS assets from paths that follow the pattern /wp-content/plugins/PLUGIN-SLUG/. This tool scans all script and link tags in the page source for these paths and extracts each unique slug as a detected plugin. Results include a direct link to the plugin's WordPress.org page. Note that plugins which load no front-end assets will not appear — this is an inherent limitation of source-based detection.
Detection can fail for several reasons. Security plugins like WPS Hide Login, iThemes Security or WP Hide & Security Enhancer can rename or obfuscate the /wp-content/ directory path entirely. Sites using full-page caching may serve flat HTML that strips WordPress-specific markers. CDNs can rewrite asset URLs. Some servers block third-party fetch requests or return a 403 error. Heavily customised enterprise WordPress installs sometimes use non-standard directory structures. If automated detection fails, use the Manual How-To tab to inspect the source yourself.
A parent theme is a complete, standalone WordPress theme that provides all templates, stylesheets and functionality. A child theme inherits all of the parent theme's files but allows customisations (additional CSS, template overrides) to be applied safely — updates to the parent theme do not overwrite child theme customisations. In the style.css header, a child theme includes a Template: field containing the parent theme's folder slug. This tool detects both and reports the parent-child relationship under Theme CSS Info.
WordPress embeds its version number in several places. The most reliable is the generator meta tag: <meta name="generator" content="WordPress X.X.X">. The tool also checks ?ver= query strings appended to WordPress core scripts and stylesheets such as /wp-includes/js/wp-embed.min.js?ver=6.5. The version number found in these signals is reported. Note that some sites suppress the generator tag or strip version numbers via security plugins.
Yes, completely free — no signup, no subscription, no usage limits. All detection logic runs client-side in your browser. No queries, URLs or results are sent to or stored on TechOreo servers.
This tool detects: Elementor (via elementor class names and scripts), Divi Builder (via theme path and DiviBuilder JS), WPBakery Page Builder (formerly Visual Composer, via js_composer and vc_row classes), Beaver Builder (via fl-builder handles), and Brizy Page Builder (via brizy paths). Detection is based on distinctive class names, script handles and asset path patterns present in the rendered HTML source.
No. This tool works by fetching the site's publicly accessible HTML source. If a site is behind a login wall, HTTP authentication, or password protection, the fetch will fail and detection is not possible. This tool is designed for publicly accessible websites only.
There are several legitimate reasons: Designers use theme detection for creative inspiration and to identify themes they admire so they can purchase them. Developers use it for competitive research, security audits, and compatibility planning. Clients use it to understand what stack their existing website runs on before commissioning a redesign or migration. Freelancers use it to quickly assess a prospect's tech stack before quoting a project.
Beyond the theme and plugins, the tech fingerprint covers: caching plugins (WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache), CDNs (Cloudflare, jsDelivr, Google APIs CDN), analytics tools (Google Analytics/GTM, Hotjar, Facebook Pixel), eCommerce platforms (WooCommerce, Easy Digital Downloads), security plugins (Wordfence, Really Simple SSL), JavaScript libraries (jQuery, Bootstrap, Tailwind CSS), Google reCAPTCHA, and whether the WordPress REST API is publicly exposed.
🗺️ Sitemap Validator 🤖 Robots.txt Generator 🔍 SERP Simulator