Steps to Take to Hide the Fact a Site is Using WordPress?

I have a website for which we are trying to be discreet about the fact that we are using WordPress. What steps can we take to make it less obvious?

Solutions Collecting From Web of "Steps to Take to Hide the Fact a Site is Using WordPress?"

The biggest WordPress giveaways are between the <head> </head> tags.

Example WordPress head content output by The Twentyten Theme and how to remove:

<link rel="profile" href="" /> 

Remove directly from header.php

 <link rel="stylesheet" type="text/css" media="all" href="" /> 

Hide WordPress by calling your stylesheet from another location and change the wp-content directory. WordPress requires your theme to include some basic information at the top of style.css (style.css must be in the themes root directory). You will need to create an alternate CSS and call it from your head. WordPress does not require you to use the themes style.css it only requires it to be in the themes directory.

Remove directly from header.php

<link rel="alternate" type="application/rss+xml" title="Example Blog &raquo; Feed" href="" /> 
<link rel="alternate" type="application/rss+xml" title="Example Blog &raquo; Comments Feed" href="" />    
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="" /> 
<link rel="wlwmanifest" type="application/wlwmanifest+xml" href="" /> 
<link rel='index' title='Example Blog' href='' /> 
<meta name="generator" content="WordPress 3.1-alpha" /> 

To remove these extra links you can add a filter to functions.php

// remove junk from head
remove_action('wp_head', 'rsd_link');
remove_action('wp_head', 'wp_generator');
remove_action('wp_head', 'feed_links', 2);
remove_action('wp_head', 'index_rel_link');
remove_action('wp_head', 'wlwmanifest_link');
remove_action('wp_head', 'feed_links_extra', 3);
remove_action('wp_head', 'start_post_rel_link', 10, 0);
remove_action('wp_head', 'parent_post_rel_link', 10, 0);
remove_action('wp_head', 'adjacent_posts_rel_link', 10, 0);

You can change your plugin directory and your wp-content directory in your wp-config.php file but you could have some problems if your theme or any plugins do not use the proper method to call files.

define( 'WP_CONTENT_DIR', $_SERVER['DOCUMENT_ROOT'] . '/new-wp-content' );

Set WP_CONTENT_URL to the full URI of this directory (no trailing slash), e.g.

define( 'WP_CONTENT_URL', 'http://example/new-wp-content');

Set WP_PLUGIN_DIR to the full local path of this directory (no trailing slash), e.g.

define( 'WP_PLUGIN_DIR', $_SERVER['DOCUMENT_ROOT'] . '/new-wp-content/new-plugins' );

Set WP_PLUGIN_URL to the full URI of this directory (no trailing slash), e.g.

define( 'WP_PLUGIN_URL', 'http://example/new-wp-content/new-plugins');


Be aware that some plugins like Akismat, All in One SEO, W3-Total-Cache, Super Cache, and many others add comments to the HTML output. Most are easy to modify to remove the comments but your changes will be overwritten anytime the plugins get updated.


The wp-includes directory holds jquery and various other js files that themes or plugins will call using wp_enqueue_script(). To change this you will need to deregister the default WordPress scripts and register the new location. Add to functions.php:

function my_init() {
    if (!is_admin()) {
        // comment out the next two lines to load the local copy of jQuery
        wp_register_script('jquery', '', false, '1.3.2');
add_action('init', 'my_init');

This will need to be done with each script used by your theme or plugins.

One bit that is often missed – delete readme.html in WordPress root. It not only identifies installation as WP but also has precise version. And don’t forget to repeat on updates.

Related Question: Prevent access or auto-delete readme.html, license.txt, wp-config-sample.php

I’ve always used the Roots Theme method.
But applying it to those ThemeJungle‘s out there is usually a big headache.

So, started to play with the WP_CONTENT_* constants. Which I believe is a much less error prone method and this is what I have working right now:

safari activity window
/m is the uploads folder, /t is the themes folder and /t/t is the active theme folder. The site is not complex, so few assets loaded…



Setting wp-content to the root (/public_html/) of the site.

 Inside WP_CONTENT, the following folders should exist: 
 /languages , /mu-plugins , /plugins , /themes , /upgrade , /uploads  

 The WP_CONTENT_* definitions bellow REMOVE the existence of the /wp-content folder 
 and makes its contents reside in the ROOT of your site

 UTTERMOST attention is necessary when doing file maintenance activities in the server (i.e.: WP upgrades, new Webmaster...), 
 as the Themes and Plugins folders are meant to be renamed to /t and /p (serious candidates for unthoughful removal)

 PLEASE note:
 - we change the Plugins folder in WP_PLUGIN_* definitions
 - the Themes folder is changed by a MustUse Plugin 
 - the Uploads folder is changed in WordPress settings page 
 - the hardcode path to be used in WP_CONTENT_DIR and WP_PLUGIN_DIR can be checked using an action inside the set-extra-themes-folder Plugin (check the comments in this file)
define( 'WP_CONTENT_DIR', '/www/htdocs/username/public_html' );
define( 'WP_CONTENT_URL', '' );

define( 'WP_PLUGIN_DIR', '/www/htdocs/username/public_html/p' );
define( 'WP_PLUGIN_URL', '' );

I’ve asked about it in [wp-hackers] – Any drawbacks in setting WP_CONTENT_DIR (and URL) to DOCUMENT_ROOT?, where John Blackbourn1, Mike Little2 and Otto3 were kindly enough as to advise:

I’ve had this structure active on a site for the last 18
months and haven’t seen any problems. As with any change to the
location of the content directory, you’ll need to double check any
plugins you add to the site don’t assume that the content directory is
at wp-content.

There are discussions around the net the $_SERVER['DOCUMENT_ROOT'] may be
susceptible to hacking. In which case this is extremely dangerous because
there are lots of places that require() or include() WP_CONTENT_DIR .

There are cases where the content in $_SERVER can be perfectly safe,
but for security purposes, it is better to always treat it as
untrusted data. For this specific case, hardcode the directory.

A New Themes Folder


As there’s no WP_THEMES_* constants, we need the function register_theme_directory() to “Register a directory that contains themes.
Tried to set the extra directory to the root but the results are funny (i.e.: it doesn’t work).

    Plugin Name: Set Extra Themes Folder
    Version: 1.0
    Description: Allows the directory - - to be used as an extra theme's directory
    Plugin URI:
    Author: brasofilo
    Author URI:

 * Remove the comment from the following line to know the correct path to put in register_theme_diretory()
//add_action( 'admin_head', 'brsfl_alert_directory_path' );

function brsfl_alert_directory_path()
    echo '<script type="text/javascript">
        alert("Directory: '.$_SERVER['DOCUMENT_ROOT'].'");

 * The following will enable the directory "t" to be used as an EXTRA Themes directory
register_theme_directory( '/www/htdocs/username/public_html/t' );

 * De-registering default scripts in wp-includes for CDN ones
add_action('init', 'brsfl_init_scripts');

function brsfl_init_scripts() 
    if ( !is_admin() ) 
        wp_deregister_script( 'jquery' );
        wp_deregister_script( 'swfobject' );
        wp_register_script( 'jquery', '', false, '1.7.1' );
        wp_register_script( 'swfobject', '', false, null, true );
        wp_enqueue_script( 'jquery' );
        wp_enqueue_script( 'swfobject' );

Uploads Folder


Instead of, it’ll be
Unchecking Organize my uploads into... will give a WPless appearance to the assets URLs.
If the site is live, a search/replace must be done in the database and files must be moved around.
uploads folder settings

Plugins and Head Content

Refer to Cris_O Answer in this Q&A.


Refer to Rarst Answer in this Q&A.

Other Steps

As usual, ThemeJungle themes may prompt specific hacks in the theme.
Like… TimThumb not working (!!!lol!!!).

You can have WordPress on one server and scrape your content from another only including the content you need.

If you need RSS your would have to do the same with that.

Effectively it would be like serving static pages from a proxy or CDN, but only the bits you want to serve.
You could then also just use a javascript based comment system such as Disqus.

Really low resource use, becaue here are no databases on the server serving the content.

You can create your custom address to login to your blog. By not using the classic “” path to get to your dashboard
This page will help you with creating stealth logins, this is also good for security measures.

So the ppl who append wp-admin to your blog, won’t be able to guess 🙂

In addition to the above, you need to lock down access to the various wp* files and directories. If someone wanted to see if you were running WP they could guess to see if you had wp-settings.php or if they could access some directory. Returning a 403 isn’t sufficient because it tells the user that the resource exists; they just don’t have access to it.

I’m not an apache expert so I asked this question over on serverfault.

I looked for a solution too, but it’s too complex. I purchased a plugin: Swift Security.

I hope it helped.

I don’t want to repeat the coding options since they have been exhaustively covered, the other option I know that works is using a plugin that hides wp. I have used this plugin before to satisfactory standards. Its called hide my WordPress.

So many high voted answers…. time to set the record straight, it is virtually impossible and even if it is,life is probably too short to put an effort into it.

The problem is not the obvious wp-* urls, the generator meta etc. The hard problems are with patterns that are associated with wordpress that an home grown system will not bother to implement like author pages, year,month,day apges, use p=nnn as a valid parameter, have comment form with the wordpress comment class, structure and link names, and then there is the self promotion of the caching plugins and yoast SEO and probably many other plugins that you see only when you inspect the HTML itself.

And even if you put the effort into cleaning up everything indicating that this is a wordpress, you might need to redo or at least recheck after every plugin or core upgrade. Life is just too short for that.

Just because some white hat tools do not detect your site a s wordpress do not mean that black hat do not do a better detection job. If this is done as a security measure then it is security by obscurity which is always wrong, and if you are just ashamed of using wordpress, then let me tell you something – no one cares, and even the very few that do probably will not know how to figure it out by themself.

This can be hard to achieve if you are new to php and mod_rewrite. I suggest so you check with the section of my response. Or try it yourself, you can use something like this to hide the wp-content/plugins path structure:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^modules/(.*) /wp-content/plugins/$1 [L,QSA]

This will change the path to /modules . Use something similar for other structure, you may need some advanced rewrites, see for additional mod_rewrite information’s.

If prefer something out of the box, there are few nice plugins, some commercial, also free at WordPress repository, i suggest to try WP Hide & Security Enhancer. This include lot’s of things and help to change pretty much everything to make your WordPress unrecognizable. Here are some features of the code:

  • Custom Admin Url
  • Custom Admin Url
  • Block default admin Url
  • Block any direct folder access to completely hide the structure
  • Custom wp-login.php filename
  • Block default wp-login.php
  • Block default wp-signup.php
  • Block XML-RPC API
  • New XML-RPC path
  • Adjustable theme url
  • New child Theme url
  • Change theme style file name
  • Custom wp-include
  • Block default wp-include paths
  • Block defalt wp-content
  • Custom plugins urls
  • Individual plugin url change
  • Block default plugins paths
  • New upload url
  • Block default upload urls
  • Remove wordpress version
  • Meta Generator block
  • Disble the emoji and required javascript code
  • Remove pingback tag
  • Remove wlwmanifest Meta
  • Remove rsd_link Meta
  • Remove wpemoji

and many more..

Most answers concentrate on obscuring WordPress in the source code of a page, but even before that WP has already given itself away in the http header of a standard installation. Just try your own site on a site like web-sniffer (pretend to be IE 6 and ask for a http 1.0 header) and you will see that among the returns is:

<>; rel=""

The latter is a link to the API. It’s there since the REST API was included in WP 4.4. You can remove it with this line right at the beginning of your functions.php:

remove_action( 'template_redirect', 'rest_output_link_header', 11, 0 );

Many plugins, like Jetpack for its shortlinks, may also insert links in the http header. They can do so, because WP has an HTTP API, which allows you to manipulate headers. You could use this interface to remove all header settings by plugins if you add your action late enough in the process.

Finally, you may use .htaccess header interface to intercept anything WP is doing. For instance, you can prevent any Link headers to be sent by including this line:

<IfModule mod_headers.c>
Header unset Link

Don’t forget that a lot of the http header information that is sent along with your request can identify your site as running on WordPress. For example, if you check the headers on the following sites, it’s obvious:

$ curl -I
Server: WP Engine/5.0

$ curl -I
X-Powered-By: W3 Total Cache/

$ curl -I
WP-Super-Cache: Served supercache file from PHP

Some of those are set by the server, some are set by plugins, so there’s no one way for me to say how to remove 100% of them, but if you’re using PHP 5.3 you can use

header_remove("X-Foo"); (

to remove a known PHP header before your content is being shoved out. I can’t say for a certainty where to place this (maybe someone else can pitch in with that info), but it’s probably safe to put it at the very top of your index.php BEFORE any content that is sent to the browser.

You can customize a theme to exclude all the WordPress information. Also remove meta widget and any widget that would output information about the platform.

Personally, I prefer to show my gratitude by displaying that I am using WordPress.

Its very difficult to hide the fact that the site is WordPress based. it will need a lot of effort and time. some folks has explained the topic very well here and i just want to contribute my part thought the answer is accepted.

modifying WP directories and file names will going to get you in trouble if you intend to upgrade core version with newer releases.

WordPress now has RESTful API included in core since version 4.7. so instead of modifying bunch of files and directories its an idea to simply use REST API and create a web service. then just create your own version of frontend with no WP footprints or even you can use it in your desktop and mobile applications too.

You can Use plugin WPS Hide Login.
You login to your wordpress using wp-admin. But you can change wp-admin to custom using this plugin.