Reduce Email Harvesting From WordPress Pages
- Publishing an email address on a website is often necessary. Businesses may need to display sales and support addresses, authors may publish contact details, and organizations frequently include department-specific emails throughout their pages.
- The downside is that the same address visible to a visitor is also present in the HTML received by automated tools.
- Simple email-harvesting bots can scan large numbers of pages looking for recognizable patterns such as name@example.com. Collected addresses may then end up in spam databases, marketing lists, or other automated datasets.
- Email Obfuscator makes those addresses less straightforward to extract by converting them into HTML entities before the final content reaches the visitor. A normal visitor's browser interprets the encoded characters and displays the familiar email address, while basic scrapers looking for plain email patterns in HTML may no longer find the same obvious string.
- It is a lightweight layer of harvest resistance that allows you to continue publishing useful contact information rather than hiding it behind images or forcing every visitor through a contact form.
Keep Email Addresses Visible and Clickable
- Protecting an email address should not make contacting you more difficult.
- When WP PowerSuite finds a valid plain-text email address in supported content, it converts that address into an obfuscated mailto: link. The individual characters are represented using HTML entities, but the browser renders them normally for the visitor.
- Instead of asking users to copy an image, decode a strange address such as name [at] example [dot] com, or enable JavaScript simply to see contact information, the email remains familiar and usable.
- Visitors can click the address and allow their browser or operating system to open the configured email application just as they would with an ordinary mailto: link.
- This makes Email Obfuscator particularly suitable for business websites where reducing simple harvesting matters but contact usability should not suffer in the process.
Protect Existing Mailto Links Too
- Many WordPress websites already contain clickable email links rather than plain email text.
- Email Obfuscator handles those existing mailto: links as well. The email address in the link destination is encoded, and when the visible link text itself contains the email address, that text is protected too.
- Useful mailto parameters can also be preserved. If a link contains a predefined subject, message body, CC, or BCC, WP PowerSuite sanitizes and retains those supported values rather than reducing every email link to a basic address.
- This is useful for contact links designed around a specific workflow. A support link might prefill a subject such as "Support Request," while a sales email could open with a predefined enquiry subject. Those conveniences do not have to disappear simply because the underlying email address is being obfuscated.
- Other unnecessary query parameters are discarded, and link attributes are restricted to an appropriate set of supported HTML attributes.
Avoid Breaking Code, Forms and Embedded Content
- Blindly searching every HTML string for an @ symbol can cause far more problems than it solves.
- Code examples may contain email-like strings. JavaScript and CSS can contain @ characters for completely unrelated reasons. Form values, embedded documents, SVG markup, and other structured content should not be rewritten simply because something resembles an email address.
- Email Obfuscator therefore avoids processing addresses inside elements such as script, style, code, pre, textarea, select, form, noscript, SVG, MathML, iframe, and input fields.
- Addresses are also validated before they are treated as emails, and already-obfuscated output is marked so the same address is not repeatedly processed as it passes through overlapping WordPress filters.
- This targeted approach is important because the goal is not to rewrite every possible @ character on the website. It is to protect normal public-facing email addresses without interfering with functional markup.
