WhoKnew Shield™ | When to Use Shortcodes vs Auto-Detection

Skip to main content
Table of Contents
Print

Shortcodes and auto-detection both protect your contact info—they just work in different ways. You don’t have to choose one forever: most sites use both. Here’s when to reach for each so you get the right mix of “set it and forget it” and “I want this exact thing protected.”

The Quick Answer

🔹 Auto-detection — Best when you already have lots of emails (and in Pro, phones and addresses) in posts, pages, or widgets. Turn it on, set strictness, and Shield finds and protects them as the page loads. No editing required.

🔹 Shortcodes — Best when you’re adding new content, need one specific contact protected, or want zero chance of a false positive. You wrap the content yourself: [whoknew-shield type="email"]you@site.com[/whoknew-shield]. Precise and reliable.

Use both. Auto-detection handles the bulk; shortcodes handle the exceptions and the places where you want total control.

Scenario Guide

Match your situation to the table below—then pick the approach (or combo) that fits.

ScenarioBest choice
📄 You have dozens of posts/pages with plain emails in the textAuto-detection — Enable it and check Email addresses (and in Pro, phones/addresses). One toggle, full coverage.
✉️ You’re adding a single “Contact us” email to a new pageShortcode — Wrap it in [whoknew-shield type="email"]. No risk of missing it or catching something else.
🧩 Contact info lives in a widget or footer templateShortcode — Widgets are scanned when they output content, but if the widget is custom or the text is in code, shortcodes are the safe bet.
🛡️ You want everything possible protected with minimal effortBoth — Auto-detect for existing content; use shortcodes for new or critical spots. They don’t conflict.
⚠️ You’re worried about false positives (e.g. “user@example” in a sentence)Shortcodes — Or use auto-detection with Strict strictness and test on a staging site first.
📞📍 Pro: phones and addresses everywhere in contentAuto-detection — Enable Phone numbers and Physical addresses in Protection Settings; set strictness. Use shortcodes only where you need a specific one guaranteed.

They Work Together

Shield does not double-process. Content that’s already inside a [whoknew-shield] shortcode is skipped by auto-detection, so you never get “wrapped twice.” You can safely turn on auto-detection and keep using shortcodes in the same post or page. Many users run both: auto-detect for the bulk of existing emails and phones, shortcodes for new blocks or high-value contact blocks (e.g. a prominent “Email us” in the sidebar).

💡 Pro tip: Start with Enable Auto-Detection and Email addresses (and in Pro, add phones/addresses). Check the Dashboard to see how many items are protected. If something important isn’t being caught or you’re seeing a false positive, drop in a shortcode for that spot or tweak strictness. You get the best of both worlds.

At a Glance

  • ✅ Auto-detection — Bulk protection, no editing. Enable in Protection Settings and choose which types (email, phone, address) to scan for.
  • ✅ Shortcodes — Exact control. Wrap the contact in [whoknew-shield type="email"] (or phone/address). Always protected, no pattern-matching.
  • ✅ Both — Standard setup. Auto-detect for existing content; shortcodes for new or must-have spots. No conflict.

Need Help?

For how auto-detection finds and protects content: How Auto-Detection Works. For shortcode syntax and types: Basic Shortcodes. For strictness (Strict / Balanced / Aggressive): How Auto-Detection Works (Detection strictness section). For a smooth overall setup: Best Practices: Getting the Most Out of WhoKnew Shield™.

Share