Search: hide theme

… also hide IDs from META tags to remove plugin and theme identifiers from element IDs, change and hide plugin paths so directory names don’t reveal your plugin stack, and change and hide theme paths so your theme name doesn’t appear in the source. Together with version hiding, these features make your WordPress installation extremely difficult to identify.

For a comprehensive guide to removing every detection signal, see the hide from theme detectors tutorial.

Frequently Asked Questions

Does this also remove the meta generator tag?

Yes. The “Hide Version from Images, CSS, and JS” feature removes the tag …

… theme includes a style.css file with a standardized header that contains the theme name, version number, author URL, and description. This is a complete fingerprint that any scanner can read with a single request. Hiding the theme name means removing all of these signals from your site.

How to Hide the Theme Name with WP Ghost

WP Ghost offers six layers of theme protection. For complete theme hiding, enable them all. Start by activating Safe Mode or Ghost Mode at WP Ghost > Change Paths > Level of Security, then configure the theme-specific options.

Change the themes path. Go to …

… path, hide theme names (replaces each theme directory with a random code), hide all themes (includes inactive themes whose files can still be exploited), hide the old themes path (blocks the original URL), and rename the theme style file (changes to a custom name like ).

Renaming is especially effective. Every theme detector specifically looks for this file because its header contains the theme name, version, and author in a standardized format. Rename it, and that detection method fails completely.

For the full walkthrough, see the change themes path tutorial.

Should I Also Hide WordPress Common Paths?

Yes. Hiding plugin and …

… with real-time detection tools to verify you’re actually invisible. Use sites like wpthemedetector.com, whatwpthemeisthat.com, or whatcms.org. If WP Ghost is configured correctly, these tools won’t be able to identify WordPress, your theme, or your plugins.

For the complete hiding checklist covering every signal detectors look for, see the hide from theme detectors guide.

Can I Also Block AI Crawlers from Scraping My Content?

Yes. WP Ghost includes a dedicated Block AI Crawler Bots toggle in the Firewall settings. When enabled, it blocks GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider, and over 30 other known AI …

… they can’t identify WordPress, your configuration is solid, regardless of what IsItWP or BuiltWith show from their cache.

Never test with browser extensions while logged in. Chrome extensions like Wappalyzer, WhatRuns, and BuiltWith detect WordPress through admin-only signals when you’re logged in. They may cache that result permanently and show WordPress every time, even when public visitors see a fully hidden site. Always use a separate browser profile or incognito window for testing.

For the complete hiding checklist and testing methodology, see the hide from theme detectors guide.

Can I Block Theme Detector Crawlers Entirely?

Yes. WP

… to WP Ghost > Security Check > Start Scan to see your security score and fix any remaining issues with the “Fix it” buttons.

WP Ghost is designed to work alongside other security tools. You can run it together with Wordfence, Solid Security, Sucuri, or your hosting’s built-in firewall. WP Ghost handles prevention (blocking attacks at the door) while other plugins handle detection and response (scanning for malware, monitoring file changes).

For a complete recommended configuration, follow the WP Ghost best practice guide. For the full hiding checklist, see hide from theme detectors.

Frequently Asked Questions

Is WP Ghost …

… label sites, hiding the WordPress identity from clients and their visitors can be important.

WP Ghost’s CMS Simulator takes detector-hiding one step further. Instead of just removing WordPress signals, it injects fake Drupal or Joomla fingerprints. Scanners don’t report “unknown.” They confidently identify the wrong CMS. For theme detector setup, see the Hide From Theme Detectors tutorial.

The Good News: Security Covers Both

When you set up WP Ghost for security (by activating Safe Mode or Ghost Mode and changing your WordPress paths), you automatically hide from theme detectors as a side effect. The path changes that …

… your login path, save, and bookmark the new login URL.

For step-by-step configuration, the process is: select a security level (Safe Mode or Ghost Mode), customize your paths, enable Hide WordPress Common Paths and Hide WordPress Common Files, activate the hiding options in WP Ghost > Tweaks (version numbers, generator META, DNS prefetch, HTML comments, emojis, embed scripts), use Text Mapping to replace WordPress class names, enable sitemap and robots.txt cleanup, block theme detector crawlers, and run a Security Check to verify everything.

For the complete 9-step hiding checklist, see the hide from theme detectors tutorial …

… wp-content.

Plugin-specific class names and IDs. Some plugins add recognizable class names to the HTML (like for Contact Form 7). WP Ghost’s Text Mapping feature at WP Ghost > Mapping > Text Mapping lets you replace these class names with custom strings. This removes the final fingerprints that detectors could use to identify specific plugins.

For the complete plugin-hiding setup, see the Change Plugins Path tutorial. For the full detector-hiding guide covering themes and CMS identity as well, see the Hide From Theme Detectors tutorial.

Quick Setup

The fastest approach is to activate Ghost Mode at …

… should either report a different CMS (if you enabled the CMS Simulator), report “Unknown,” or fail to detect WordPress entirely. If they still identify WordPress, see the troubleshooting section below.

What to Do If WordPress Is Still Detected

If external tools still identify your site as WordPress after activating WP Ghost, one or more WordPress signals are leaking through. The most common causes and their fixes are listed here.

wp-content or wp-includes still visible in the source. Go to WP Ghost > Change Paths > WP Core Security and make sure both the Custom wp-content Path and Custom …