Abhishek Sinha

Abhishek Site Cleanup Controls gives developers and site owners fine-grained control over 35+ WordPress features that are often unnecessary. Each feature has a simple on/off toggle, organised into five logical groups inside Settings -> Site Cleanup Controls.
No features are enabled by default — activate only what you need.
<h4>Security</h4>
<ul>
<li>User Enumeration — Block ?author=N redirect attacks that expose usernames.</li>
<li>Author Archives — Return 404 for author archive pages.</li>
<li>XML-RPC + Pingback — Fully disable the XML-RPC endpoint and remove the X-Pingback header.</li>
<li>Plugin and Theme Editor — Set DISALLOW_FILE_EDIT to prevent in-admin file editing.</li>
<li>Application Passwords — Disable the Application Passwords feature.</li>
<li>REST API — Restrict REST API access to authenticated users only.</li>
<li>Right Click — Disable the browser context menu on the frontend.</li>
</ul>
<h4>Performance</h4>
<ul>
<li>Emojis — Remove all emoji scripts, styles, and DNS prefetch hints.</li>
<li>Embed Objects — Disable WordPress oEmbed and embed scripts.</li>
<li>Dashicons — Prevent Dashicons from loading for non-logged-in visitors.</li>
<li>Heartbeat — Deregister the Heartbeat API script.</li>
<li>Block Library CSS — Remove wp-block-library and global-styles stylesheets on the frontend.</li>
<li>Version Var (?ver=) — Strip ?ver= query strings from enqueued asset URLs.</li>
<li>PDF Thumbnails — Skip thumbnail generation for uploaded PDF files.</li>
<li>oEmbed — Remove oEmbed discovery links and disable autoembed.</li>
<li>Remote Block Patterns — Stop WordPress fetching patterns from api.wordpress.org.</li>
</ul>
<h4>Head Cleanup</h4>
<ul>
<li>Generator Meta Tag — Remove the WordPress version meta tag from head.</li>
<li>WLW Manifest — Remove the Windows Live Writer manifest link.</li>
<li>Really Simple Discovery (RSD) — Remove the RSD link tag.</li>
<li>Short Link — Remove the shortlink tag and HTTP header.</li>
<li>Adjacent Posts Links — Remove prev/next link tags from single post heads.</li>
<li>RSS Feeds — Redirect all feed URLs to the homepage.</li>
</ul>
<h4>Admin Cleanup</h4>
<ul>
<li>capital_P_dangit — Remove WordPress forced capitalisation filter.</li>
<li>Screen Options and Help Tabs — Hide Screen Options and Help dropdowns.</li>
<li>Howdy to Welcome — Replace “Howdy,” with “Welcome,” in the admin bar.</li>
<li>Navigation Items in Admin Bar — Remove WP logo, site name, updates, and comments.</li>
<li>Clean Dashboard — Remove all default dashboard widgets.</li>
<li>Privacy Tools — Hide Export/Erase Personal Data from the Tools menu.</li>
<li>Site Health Page — Hide Site Health from the Tools menu.</li>
<li>WP Login Logo and Favicon — Hide the WordPress logo on the login page.</li>
<li>Admin Email Verification Prompt — Disable the admin email confirm interstitial.</li>
<li>Empty Trash (1 week) — Shorten automatic trash-emptying from 30 days to 7 days.</li>
</ul>
<h4>Content</h4>
<ul>
<li>Comments — Disable comments sitewide.</li>
<li>Post Revisions — Disable revision storage.</li>
<li>Search — Redirect all search queries to the homepage.</li>
</ul>
<h4>WordPress Features</h4>
<ul>
<li>Thumbnails / Featured Images — Remove post thumbnail support.</li>
<li>Widgets — Disable all widgets and sidebars.</li>
<li>Navigation Menus — Remove nav menu theme support.</li>
<li>Tags — Unregister tags from posts.</li>
<li>Categories — Unregister categories from posts.</li>
<li>Post Formats — Remove post format theme support.</li>
<li>Custom Fields — Remove custom fields meta box from editor.</li>
<li>Excerpts — Remove excerpt support from posts and pages.</li>
<li>Trackbacks — Remove trackback support from posts.</li>
<li>Attachment Pages — Redirect attachment URLs to the file directly.</li>
<li>Automatic Updates — Disable automatic core, plugin, and theme updates.</li>
<li>Self Pings — Stop WordPress pinging your own site.</li>
<li>jQuery Migrate — Remove jQuery Migrate script on the frontend.</li>
</ul>

Abhishek Site Cleanup Controls

Selectively disable WordPress features to improve performance, security, and cleanliness. Toggle each feature individually from a single settings page …

Guido Schad

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area.
Current prototype features include:
<ul>
<li>Manual security scans.</li>
<li>Weighted security score out of 100.</li>
<li>WordPress core file integrity checks using official checksums.</li>
<li>WordPress authentication key and salt checks, with an explicit action to generate missing salts.</li>
<li>Must-use plugin directory presence checks.</li>
<li>PHP version status using WordPress.org Serve Happy data.</li>
<li>HTTPS and HTTP security header checks.</li>
<li>WordPress core, plugin, and theme update posture checks.</li>
<li>Administrator account posture checks for default usernames, excess admins, inactive admins, user ID 1 exposure, and an admin username/email inventory.</li>
<li>Optional known vulnerability matching with a configured Wordfence Intelligence API key.</li>
<li>Optional AI client reports on WordPress 7.0+ when the site’s AI Connector is configured.</li>
<li>Reversible hardening toggles for XML-RPC, REST user routes, generator tag output, and basic security headers.</li>
</ul>
<h3>External Services</h3>
Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report.
WordPress.org APIs: 
* Used for WordPress core checksums, PHP version support status, and WordPress core/plugin/theme update data. 
* Data sent: the site’s WordPress version and locale for core checksums and PHP compatibility; WordPress itself may send installed plugin and theme slugs/versions to WordPress.org when update data is refreshed. 
* WordPress.org terms: https://wordpress.org/about/terms/ 
* WordPress.org privacy policy: https://wordpress.org/about/privacy/
Wordfence Intelligence: 
* Optional. 
* Used only when a Wordfence Intelligence API key is configured and an administrator runs a scan that includes vulnerability matching. 
* Used to retrieve vulnerability data and match it locally against installed WordPress core, plugin, and theme versions. 
* Data sent: the configured Wordfence Intelligence API key is sent in an Authorization header when requesting the vulnerability feed. Installed software details are not sent by this plugin to the Wordfence Intelligence endpoint; matching is performed locally after the feed is retrieved. 
* Wordfence Intelligence terms: https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/ 
* Wordfence privacy policy: https://www.wordfence.com/privacy-policy/
WordPress AI Client / Connectors: 
* Optional. 
* Used only when the administrator clicks Generate Client Report. 
* Data sent: sanitized scan findings, score, counts, and recommendations needed to generate a client-facing report. The plugin is designed not to send passwords, salts, API keys, raw logs, full user lists, or file contents. 
* The configured AI provider is controlled by the site owner’s WordPress Connector settings. 
* Terms and privacy policy: these depend on the AI provider configured by the site owner in WordPress. Site owners should review the selected provider’s terms and privacy policy before enabling AI reports.

Lockora Security Audit

Lockora Security Audit checks WordPress security posture, hardening, core integrity, vulnerabilities, and optional AI reports.

Abhishek Site Cleanup Controls vs Lockora Security Audit