Home / Find Websites Using a WordPress Theme
Use case
Find Websites Using a WordPress Theme
A WordPress site loads its active theme's stylesheet and assets from a predictable folder, /wp-content/themes/<theme-slug>/, so the theme a site runs is written, in plain text, into its homepage source. Searching that path surfaces every indexed site on a given theme: useful for sizing a theme's real-world install base, building outreach lists for theme-adjacent products, and checking what successful sites in a niche are built with.
The footprint
wp-content/themes/<theme-slug>, for example wp-content/themes/astra or wp-content/themes/divi. To learn a theme's slug, view the source of any site running it (the theme's own demo site works) and find the stylesheet link: /wp-content/themes/<slug>/style.css. For context, WordPress overall is detectable via wp-content on 24,899,751 domains in the August 2026 index, the theme path narrows that to one theme.
A worked example
Searching wp-content/themes/astra returns the indexed sites whose homepage loads the Astra theme's assets. Each result shows the domain plus the matched line, typically the <link rel="stylesheet"> pulling the theme's CSS, and opens to the full source, where the surrounding markup also reveals the site's plugins, page builder, and tracking stack. Add a TLD filter (e.g. site:.de) to cut the list to one market.
Step by step
- Get the slug from any known install: look for
/wp-content/themes/<slug>/in its source. - Search the path as an exact string.
- Narrow it. Filter by TLD, or add a second footprint with AND,
"wp-content/themes/astra" AND woocommercefinds Astra stores. - Verify a sample. Open results and check the theme loads from the site's own domain; the
?ver=query string on the stylesheet often dates the install. - Export the domain list as CSV.
False positives and gaps
Two things inflate a naive count and two shrink it. Inflating: pages that mention the path in article text or code samples without loading it (rare for obscure slugs, common for famous ones), and child themes, which keep the parent theme's folder in source, usually what you want, since the parent is genuinely installed. Shrinking: sites that rename the theme directory or run white-labeled builds, and optimization plugins or CDNs that rewrite asset URLs so the literal path never appears in the HTML. Treat the count as a reliable floor rather than a census, and open the source of anything you plan to act on.
Related fingerprints
Plugins follow the same pattern at wp-content/plugins/<plugin-slug>, combine a theme path with a plugin path to target very specific setups. See also Elementor, WooCommerce, and WordPress results, or the guide to building technographic lead lists for turning matches into a prospect list.
Search Astra sites → WordPress results →
Frequently asked questions
How do I find a theme's slug if I only know its name?
Open any site running the theme, the vendor's demo site is easiest, and view its source. The slug is the folder name in /wp-content/themes/<slug>/style.css. It's usually the lowercased theme name, but premium themes sometimes differ.
Can I find sites on an outdated version of a theme?
Often, yes. Many themes version their stylesheet (style.css?ver=1.2.3), so a regex that pins the version range will match only dated installs. Note some sites strip or override the ver parameter, so use it as a strong hint rather than proof.
Why is a popular theme's count lower than its claimed install base?
The index stores one homepage per domain, and asset-rewriting plugins, CDNs, and renamed theme folders all hide the literal path. The count is a floor of visibly matching homepages, not a census of every installation.
Does this work for themes active only on a subsite or inner pages?
No, the index covers each domain's homepage, so a theme that only appears deeper in a site won't match. If the homepage runs a different theme, that's the one you'll see.