A: Not completely. A browser extension runs on the visitor’s computer inside their browser, so your website cannot reliably disable it or prevent it from reading what the browser receives.
Why this is not possible
Technology detector extensions (such as WhatRuns, Wappalyzer, and similar tools) identify a site by checking things any visitor can see, including:
- The page source (HTML)
- Loaded CSS/JS file URLs
- Network requests
- Common WordPress patterns (paths, file names, classes, meta tags)
If your site publicly exposes WordPress clues (for example /wp-content/ or plugin file names), the extension can often detect WordPress and sometimes specific plugins/themes.
What you can do instead (the right approach)
You cannot “block the extension,” but you can reduce what it can detect by hiding fingerprints:
- Hide old WordPress paths
Enable Hide WordPress Common Paths so old paths return 404 to logged-out visitors. - Hide common WordPress files
Enable Hide WordPress Common Files so files likereadme.htmlare not publicly accessible. - Reduce source-code clues
Enable Tweaks that remove version strings, generator meta tags, HTML comments, and other signals. - Use Mapping when needed
- Text Mapping to reduce
wp-classes if detectors keep identifying WordPress from CSS/HTML patterns. - URL Mapping to hide plugin-named filenames or obvious asset URLs.
- Block scanners and crawlers
Enable Block Theme Detectors Crawlers in the firewall to reduce automated crawling from known detector bots.
Important: Why you may still see detection while logged in (Admin/Editor)
If you test using a detector extension while you are logged into WordPress:
- WordPress adds logged-in signals (admin bar, cookies, backend scripts).
- WP Ghost may not apply full hiding rules in admin context to avoid breaking the dashboard/editor.
- The extension may detect WordPress and it may keep a cached result.
Best practice: Do not install detector extensions in the same browser profile you use for wp-admin. Test in Incognito/Private mode while logged out or in a separate browser profile.
Conclusion
You cannot fully prevent browser extensions from inspecting what your site publicly sends to a browser. The practical solution is to hide WordPress fingerprints for logged-out visitors and block automated crawlers, while avoiding extension-based testing when logged into wp-admin.











































