WhoKnew Shield™ | Understanding Detection Strictness

Skip to main content
Table of Contents
Print

The Detection strictness setting controls how “broad” auto-detection is—whether it only catches obvious contact info or also looser patterns. Picking the right level helps you protect everything that matters without accidentally wrapping things that aren’t real emails or phone numbers (false positives).

The Three Levels

In Protection Settings, under Auto-Detection, you’ll see Detection strictness with a slider. The three options are:

  • 🔒 Strict — Only standard-looking contact info (e.g. typical email formats like name@domain.com). Fewest false positives. Use when your content has code samples, example text like “user@example,” or mixed prose where you want to be conservative.
  • ⚖️ Balanced — The default. Covers standard formats plus common variants. Good for most sites: blog posts, pages with a mix of real contact and other text.
  • 🎯 Aggressive — Casts a wider net so more unusual or “edge” formats get protected. Best when the page is mostly contact info (e.g. a dedicated Contact page) and the risk of catching something that isn’t a real email or phone is low.

Quick Reference

ModeBest forFalse positive risk
🔒 StrictMixed content, code examples, “user@example” style textLowest
⚖️ BalancedMost sites: posts, pages, general useLow to medium
🎯 AggressiveDedicated contact pages, “all contact here” layoutsHigher—test first

How to Choose

Start with Strict and test on a staging or test site. Check a few posts and pages: are your real emails and (in Pro) phones and addresses protected? If something real is missed, move to Balanced. Only move to Aggressive if you have contact-heavy pages and you’re sure there’s little or no “lookalike” text (e.g. example emails in documentation) that could be wrongly wrapped. For Pro users: phone and address auto-detection have their own strictness. Address detection has the highest risk of false positives—test thoroughly before enabling and consider shortcodes for precise control on sensitive pages.

💡 Save yourself a ticket: Auto-detection can cause false positives. Test on staging first. If you need one specific block protected and zero chance of touching other text, use a shortcode instead—they’re precise and don’t depend on strictness.

Where to Set It

Go to WhoKnew Shield → Settings (Protection Settings tab). Under Auto-Detection, turn on Enable Auto-Detection and the type you want (e.g. Email addresses). The Detection strictness slider appears for that type—Strict, Balanced, or Aggressive. In Pro, you’ll see separate strictness for email, phone, and (if enabled) physical addresses. Save settings and check the front end to confirm behavior.

Need Help?

For “something was protected that shouldn’t be” or “my email wasn’t detected”: Common Issues and What Gets Protected (And What Doesn’t). For when to use shortcodes instead: When to Use Shortcodes vs Auto-Detection. For a full overview of options: How Auto-Detection Works.

Share