This section provide methods to control the style links format being displayed on front side. An example of such link:
<style rel='stylesheet' id='id-of-style' type='text/css' media='all' href='http://-domain-name-/wp-content/themes/default/css/style.css?ver=1.12.4'></style>Remove Version
This option provides a method to remove the version number appended to CSS style file URLs (for example: style.css?ver=6.4.2). By default, WordPress adds these version parameters to help with cache busting and to indicate the version of the stylesheet in use. However, these values do not play any direct role in the execution of the CSS code itself.
Exposing version numbers can unintentionally provide useful information to attackers attempting to identify the WordPress core, theme, or plugin versions installed on a website. Such information is often used to match known vulnerabilities against specific versions, increasing the risk of targeted attacks.
By enabling Remove Version, WP Hide strips these version parameters from enqueued style URLs, reducing the amount of publicly available information about your site’s internal structure and software versions. This contributes to a stronger security posture by limiting fingerprinting opportunities, while preserving the normal functionality and visual appearance of the website.
Remove ID from link tags
This option provides a method to remove the id attribute from HTML <link> tags generated by WordPress, such as those used for stylesheets, feeds, and other linked resources. By default, WordPress assigns identifiable id values to these elements to manage dependencies and internal references.
While these id attributes are not required for the browser to load or apply the linked resources, they can expose implementation details about the active theme, plugins, or WordPress core components. Such identifiers may assist attackers in fingerprinting the site and determining the technologies and specific components in use.
By enabling Remove ID from Link Tags, WP Hide strips these identifiers from the front-end output, minimizing publicly exposed structural information without affecting how resources are loaded or rendered. This helps reduce the site’s visibility to automated scanners and manual reconnaissance efforts, contributing to an overall hardened security profile.
