Can I Create Custom CMS Footprints in WP Ghost?
This tutorial has moved to the new WP Ghost Knowledge Base where each feature is presented in detail.
Partly. Simulate CMS shows your site as Drupal (8 to 11) or Joomla (3 to 5), and the hmwp_emulate_cms filter lets you change the generator name. Use a real CMS name, because detectors only recognize platforms that are in their database.
How CMS detection works (and why custom names have limits)
CMS detectors like BuiltWith, Wappalyzer and WhatCMS compare your site’s headers, meta tags and source patterns with a database of known CMS fingerprints. Simulate CMS adds the generator meta tag of Drupal or Joomla (for Drupal, also the MobileOptimized and HandheldFriendly meta tags), so detectors that read those tags report Drupal or Joomla instead of WordPress.
If you inject a completely made-up generator name like “MyCoolCMS,” detectors won’t recognize it. They will either report “Unknown” or continue looking for other signals. A result of “Unknown” is still better than “WordPress” from a security perspective, since bots won’t load WordPress exploit toolkits against an unknown target. But a recognized CMS like Drupal actively sends attackers down the wrong path, which is more effective.
Using the built-in CMS simulator
The easiest approach is the built-in option. Go to WP Ghost > Tweaks > Change Options and pick a CMS in Simulate CMS: Drupal 8, 9, 10 or 11, or Joomla 3, 4 or 5. Safe Mode and Ghost Mode set Drupal 11 by default. Click Save, and WP Ghost adds the CMS meta tags to your page source. No code needed. For the full walkthrough, see the Simulate Drupal or Joomla CMS tutorial.
Adding a custom generator name with code
If you want a generator name that isn’t in the built-in list, use the hmwp_emulate_cms filter. It runs only when a CMS is selected in Simulate CMS, and it replaces the generator name. Add the following code to your theme’s functions.php file or a custom plugin:
add_filter('hmwp_emulate_cms', function(){
return 'Drupal 11';
});Replace 'Drupal 11' with whatever CMS name you want to display. For the best results, use a real CMS name that scanners already recognize (like a specific Drupal or Joomla version, Magento, Shopify, etc.). If you use a name that doesn’t exist in any detection database, scanners will simply report it as unknown. For the complete developer guide, see Adding a Custom CMS Simulator.
Frequently asked questions
Should I use a custom generator name or stick with the built-in Drupal/Joomla options?
Stick with the built-in options unless you have a specific reason to change. The Drupal options also add the MobileOptimized and HandheldFriendly meta tags that Drupal sites send; a custom name only changes the generator meta tag, which is one of many signals detectors look for.
Will a made-up CMS name still help with security?
Partially. Bots that rely on the generator tag to identify WordPress will not find a WordPress match, so they may skip your site. But most serious scanners check multiple signals, not just the generator tag. A made-up name results in “Unknown CMS” status, which is better than “WordPress” but less effective than a recognized CMS like Drupal that actively misdirects attackers.
Does the CMS Simulator work without changing paths?
Technically yes, but it won’t be effective. If your page source still contains /wp-content/, /wp-includes/, and /wp-admin/, scanners will detect WordPress regardless of the fake generator tag. The CMS Simulator is designed as the final layer: remove the real WordPress signals first with path security, then inject the fake CMS signals.
Does WP Ghost modify WordPress core files?
No. The CMS Simulator injects fake signatures through WordPress filters at runtime. No files are written to disk. Disabling the CMS Simulator or deactivating WP Ghost removes all fake signals instantly.