| 开发者 | whoknewio |
|---|---|
| 更新时间 | 2026年3月4日 17:15 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPL-3.0-or-later |
| 版权网址: | 版权信息 |
[whoknew_shield] for precise control when neededNo coding. Works with any WordPress theme. Set it once, protect everything.Upgrade to Pro → | View Features Why Auto-Detection Matters Manual shortcode plugins require wrapping every contact individually:
[encode] shortcodes work immediately[obfuscate_email] supported[eeb_protect_emails], [eeb_mailto] compatiblewhoknew-shield folder to /wp-content/plugins/It protects your email addresses, phone numbers, and physical addresses from spam bots and scrapers by encoding them in a way that real visitors can still see and use (with one click), but automated tools have a much harder time harvesting. Uses dual-layer obfuscation (HTML entities + CSS reversal + JavaScript).
Yes. Obfuscation is applied when the page is generated, so cached pages still show protected content. Compatible with WP Rocket, LiteSpeed Cache, W3 Total Cache, SiteGround Speed Optimizer, and other major caching solutions.
Yes. In Protection Settings you can turn auto-detection on or off for emails (free), phones (Pro), and addresses (Pro) separately. Shortcodes let you protect specific pieces of content regardless of auto-detection settings.
Yes. The free plugin has no locked features. You get dual-layer protection, email auto-detection, click-to-reveal, and all shortcodes. Pro adds phone/address auto-detection, Scraper Trap WAF with honeypots, IP blocking, analytics dashboard, and competitor shortcode support.
Scraper Trap is a Pro feature that functions as a Web Application Firewall (WAF) to actively catch and block bots. It uses hidden honeypots (invisible links/forms that only bots trigger). When a bot takes the bait, their IP is automatically blocked site-wide. This is active defense vs passive hiding — it protects your entire WordPress site by identifying and blocking threats before they can harvest any data.
Yes! WhoKnew Shield Pro supports shortcodes from other popular plugins, making migration straightforward. If you're using Email Address Encoder ([encode]), Neotrendy's Email Address Obfuscation ([obfuscate_email]), Email Encoder Bundle ([eeb_protect_emails], [eeb_mailto]), or Antispambot, just activate Shield Pro and deactivate the old plugin. All existing shortcodes work immediately. No find-and-replace needed.
Manual shortcode plugins require you to wrap every contact individually, which is easy to miss — especially in old posts, footer widgets, or page builder sections. Shield's auto-detection handles this automatically — set it once and contacts are protected everywhere.
The dual-layer protection includes HTML entity encoding that works without JavaScript, but the click-to-reveal feature and full obfuscation require JavaScript to be enabled. Most modern users have JavaScript enabled. Pro includes advanced encryption that also requires JavaScript.
Yes. The plugin is designed to be GDPR-compliant. All protection runs locally on your WordPress server. No external services are used for obfuscation. The free plugin has zero external dependencies — no CDN scripts, no API calls, no data transmission. Everything stays in your database. However, you should review your specific privacy requirements and ensure compliance with applicable regulations.
Yes. Shield works with Elementor, Divi, Beaver Builder, WPBakery, Gutenberg, Classic Editor, and any WordPress theme or page builder. Auto-detection finds contacts regardless of how your content was created.
No. Obfuscation processing is minimal and happens during page generation (cached by your caching plugin). No external scripts or CDN dependencies in the free version means zero external HTTP requests. Protection is lightweight and fast.
Yes! Protected contacts show a simple click-to-reveal button. One click reveals the full contact information (email link, phone number, etc.). This is easy for real humans but blocks automated scrapers. You can customize the button text and styling.
Your content returns to normal. Auto-detected contacts appear as plain text. Shortcodes will not render (you'll see the raw shortcode text), so you may want to remove them if you permanently deactivate. No data is lost — deactivation is completely safe.
[whoknew_shield] for precise control when needed