Does your site contain unprotected email addresses?
Use the page scanner to see whether all your email addresses are protected.
Emails in element attributes
The Premium version automatically protects email addresses inside element attributes using HTML entities. Other techniques wont’t work here unfortunately.
If you’re using the free version, you’ll have to manually obfuscate email addresses in attributes. Learn more →
Mailto links
If this section of your site is filtered by the primary WordPress filters,
such as the_content, widget_text and others, then
the free, open source version automatically obfuscates
these email addresses using HTML entities.
The Premium version also supports full-page parsing and finds and
protects all email addresses. It also supports JavaScript-based techniques
for mailto: links to protect against smart robots.
Emails in HTML comments
Text inside comments is not interpreted as HTML, which makes obfuscation difficult.
The Premium version automatically protects email addresses in comments using a human readable notation (also know as address munging) such as: steve [at] apple [dot] com
If you’re using the free version, you’ll have to manually obfuscate email addresses in comments. Learn more →
Emails in head element
The Premium version automatically protects email addresses inside
the <head> element using HTML entities.
Other techniques wont’t work here unfortunately.
If you’re using the free version, you’ll have to manually obfuscate these email addresses. Learn more →
Emails inside text
If this section of your site is filtered by the primary WordPress filters,
such as the_content, widget_text and others, then
the free, open source version automatically obfuscates
these email addresses using HTML entities.
The Premium version supports full-page parsing and finds and protects all email addresses. It also supports CSS and JavaScript-based techniques to against smart robots.
Emails in textareas
The Premium version automatically protects email addresses
inside <textarea> elements using HTML entities.
Other techniques wont’t work here unfortunately.
If you’re using the free version, you’ll have to manually obfuscate email addresses in textareas. Learn more →
Emails in example elements
Text inside <xmp> elements is not interpreted as HTML,
which makes obfuscation difficult.
The Premium version automatically protects email addresses
in <xmp> elements using a human readable notation
(also know as address munging), such as: steve [at] apple [dot] com
If you’re using the free version, you’ll have to manually obfuscate these email addresses. Learn more →
Emails in no-scripts
The Premium version automatically obfuscates email addresses
in <noscript> elements using either HTML entities or CSS-based techniques.
If you’re using the free version, you’ll have to manually obfuscate these email addresses. Learn more →
Emails in scripts
Replacing text inside <script> elements automatically
is very difficult and leads to problems in most scenarios.
The best approch is to manually obfuscate email addresses using octal,
hexadecimal or unicode escape sequences.