WordPress Theme and Plugin Detector
Enter a WordPress site and see which theme and plugins it uses, with version numbers. Each one is checked against the WordPress.org directory for the latest version, the last update and active installs, so you can spot outdated and abandoned code.
- Theme, plugins and WordPress version
- Checked against WordPress.org
- Flags outdated and abandoned plugins
Want the wider stack? Use the Website Technology Checker, or check speed with the Website Performance Checker.
The theme, the plugins and how current they are
Everything comes from public clues in the page, then WordPress.org adds the version facts.
Theme and child theme
The active theme, a child theme and its parent, with the installed version and, for free themes, the latest one.
Plugins
Every plugin that loads a file on the page, with a friendly name, a category and the installed version where it shows.
Update status
Whether each plugin or theme is the latest version, with the last update date and number of active installs.
Risk flags
Plugins not updated in two years, out-of-date versions, and plugins that don't belong in the directory.
Conflicts
More than one SEO, caching or page builder plugin, which often causes duplicate tags and slow pages.
Exposure
A visible WordPress version, xmlrpc.php and a very long plugin list.
What the status labels mean
Each plugin and theme gets one status, based on the WordPress.org directory.
| Status | Meaning | What to do |
|---|---|---|
| Up to date | The installed version matches the latest release | Nothing. Keep auto-updates or a monthly check in place. |
| Update available | A newer version exists | Back up, test on staging if you can, then update. |
| Not updated in 2+ years | The author has stopped maintaining it | Replace it with a maintained alternative. Unfixed flaws are common in abandoned plugins. |
| Not checked | Premium, custom or removed, or the directory was unreachable | Check the vendor's own update channel. |
How to find a WordPress site's theme and plugins
Three steps from a URL to a plugin audit.
Enter the site
Use the home page or any page. The tool reads the page and tests WordPress's own login and REST address if the page hides its paths.
Review the theme and the list
See which plugins are old or abandoned, and which categories overlap.
Act on the notes
Update, replace or remove what is flagged, keep one plugin per job, then re-check.
Plugin habits that save trouble
Most WordPress problems trace back to plugins.
Update on a schedule
Review updates weekly and apply security releases fast, with a backup first.
Delete what you don't use
A deactivated plugin still sits on the server. Delete it rather than leaving it.
One plugin per job
One SEO plugin, one cache plugin, one form plugin. Overlap causes conflicts.
Check the last update
Prefer plugins updated in the last year with many active installs.
Hide the version
Remove the generator tag so attackers can't see which release you run.
Use a child theme
Customise a child theme so parent theme updates don't wipe your changes.
What a WordPress theme and plugin detector shows and where it stops
WordPress sites are assembled from a theme and a set of plugins, and those parts decide most of how the site looks, performs and stays safe. A WordPress theme and plugin detector finds which ones a site uses by reading public clues. WordPress loads theme and plugin files from predictable folders under /wp-content/, file addresses often carry a ?ver= version number, and some plugins leave a comment or generator tag in the page.
This tool lists the active theme, any child theme and its parent, and the plugins that load a file on the page. It then asks the public WordPress.org directory about each one: the latest version, the last update date and the number of active installs. That makes outdated, abandoned and overlapping plugins easy to spot. It works on your own site, a client's, a site you are about to inherit or a competitor's, since it only reads what any visitor can see.
Detection has hard limits. Only plugins that load a file or leave a mark on the front end can be seen, so plugins that work only in the admin area or on the server stay hidden and the real number is usually higher. Premium and custom plugins are not in the WordPress.org directory, so they are marked Not checked. Hosts and security plugins can also hide the usual paths. Treat the list as a strong starting point, then confirm inside the dashboard. For the broader security picture, keep the WordPress hardening guide at hand.
When to list a site's WordPress theme and plugins
Use it when you need a plugin inventory fast, or want to see how current a site's parts are.
Before taking on a client's site
Get the theme and plugin list before the first call. Old or abandoned plugins and duplicate functions are easy to spot and set the scope of the cleanup.
Ahead of a speed or security clean-up
See which plugins load files on every page, which are outdated and which do the same job as another one. Then decide what to update, replace or delete.
To find overlapping plugins
Two SEO, caching or page builder plugins can output duplicate tags or fight over the same task. The conflicts section flags categories with more than one.
To see what a competitor uses
Find out which theme and plugins a competing WordPress site relies on, such as its page builder, forms, booking or e-commerce plugin.
After an update round
Run it again after updating to confirm the visible versions moved to the latest release and nothing outdated is still loading.
When inheriting a site from a previous developer
Check which theme is active, whether it is a child theme, and which plugins were left behind. It gives you a checklist to verify in the dashboard.
Theme and plugin mistakes and how to fix them
Most plugin trouble comes from having too many, keeping them too long or updating them carelessly.
Keeping plugins that are switched off
What goes wrong: A deactivated plugin is still on the server, and if it has a weakness, the files may still be reachable. They also add clutter and updates to manage.
The fix: Delete plugins you do not use instead of deactivating them, as WordPress's own hardening advice says, and remove unused themes too. Keep a backup before removing anything.
Running abandoned plugins
What goes wrong: A plugin the author stopped maintaining gets no more security fixes and may break with new WordPress or PHP versions. The directory shows its last update date.
The fix: Check the last update date and active installs. Replace plugins that have not been updated for a long time with maintained alternatives, and plan the switch on a staging copy.
Several plugins doing one job
What goes wrong: Two SEO plugins can each output a title tag, canonical and schema. Two caching plugins can fight over the same files. The result is duplicate tags, conflicts and slower pages.
The fix: Keep one plugin per job: one for SEO, one for caching, one for forms. Deactivate the extra one, test the key pages, then delete it.
Installing from untrusted sources
What goes wrong: Free copies of premium plugins and themes from unofficial sites can contain hidden code, and they never receive proper updates. WordPress advises against getting them from untrusted sources.
The fix: Buy premium plugins from the vendor, and install free ones from the WordPress.org directory. Keep a licence for any premium plugin so you keep getting updates.
Editing the parent theme directly
What goes wrong: Changes made in the main theme files are overwritten when the theme updates, so people either lose their edits or stop updating, which leaves the theme out of date.
The fix: Make custom changes in a child theme. WordPress describes child themes as a way to let the parent update without losing your modifications.
Updating blindly on a live site
What goes wrong: An update can conflict with another plugin or the theme and break a page, a checkout or a form. Skipping updates to avoid that leaves known flaws in place.
The fix: Take a backup first, test on a staging copy when the site earns money, and update on a regular schedule. Apply security releases quickly and review the key pages afterwards.
WordPress theme and plugin terms explained
- Theme
- The set of template and style files that control how a WordPress site looks and how its pages are built. Only one theme is active at a time.
- Child theme
- A theme that inherits the look and functions of a parent theme and holds your own changes. Updating the parent does not erase what is in the child.
- Plugin
- A package of code that adds features to WordPress, such as SEO, forms, caching or e-commerce. Each plugin is extra code that must be kept updated.
?ver=version string- A number added to the address of a theme or plugin file, such as
style.css?ver=2.1. Detectors read it to estimate the installed version, but it can be changed or removed. - WordPress.org directory
- The public library of free plugins and themes. It records the latest version, last update date and active installs for each one, which this tool uses to judge how current they are.
- Active installs
- An approximate count of sites using a plugin or theme, shown in the directory. It is a rough signal of use, not a guarantee of quality or safety.
- Abandoned plugin
- A plugin whose author has stopped updating it. The tool flags plugins not updated in over two years, since flaws in them are unlikely to be fixed.
- Premium plugin
- A paid or custom plugin that is distributed outside the WordPress.org directory. It has no public version data here, so it appears as Not checked and needs its vendor's update channel.
Related tools, guides and services
A plugin list is one part of the WordPress picture. These cover the rest.
WordPress Security Checker
Run passive checks for exposed files, public usernames, XML-RPC and outdated components.
ToolWordPress Version Checker
Find the WordPress core version and see whether it is current, outdated or insecure.
ToolWebsite Technology Checker
Look beyond WordPress at the CDN, analytics, frameworks and server behind a site.
ToolWebsite Performance Checker
See how much weight and blocking code your plugins add to a page.
ServiceTechnical SEO service
Get plugin conflicts, duplicate tags and speed problems on a WordPress site reviewed and fixed.
ServiceSEO audit service
Get a prioritised audit covering the technical, content and structural issues on your site.
Built by
Madhav Kushwaha
SEO, AEO, GEO & Digital Marketing Consultant in Kathmandu, Nepal, and trainer at ODcrU Academy and TechAxis Institute. Before I audit a WordPress site, I want its theme and plugin list, and I want to know which ones are old. I built this detector to give that list in seconds, whether it's a client's site, a competitor's, or one I'm about to inherit.
WordPress Theme & Plugin Detector: Frequently Asked Questions
More free SEO tools
WordPress sites live or die by their plugins. These tools check the results.