Note: This page has been moved to here.
WordPress security is an important subject and we take it quite seriously. And so do our website visitors.
With version 4.6.0 of the plugin we added an optional “Plugin Badge”, where users of the plugin can add a small badge to the front-facing website to demonstrate to visitors that their websites are protected by the Shield Security plugin.
The Plugin Badge Is Optional
Displaying this plugin badge is completely, 100% optional.
It is not enabled by default, and you are free to remove it at any time if you either don’t like it, or it interferes with your website.
To enable or disable the plugin badge:
- Go to General Settings (for the Shield Security)
- Check or Uncheck the box for the option as desired.
Why would you want to display the plugin badge?
This serves 2 primary benefits:
- It lets visitors know that the owner of the website is taking security and protection seriously.
Visitors will know that the website is secured through various mechanisms and they’re much less likely to be compromised themselves.
- It helps promote the plugin to users who haven’t yet considered WordPress security, or users who are looking for WordPress security alternatives.
You can also use it for the Shield Security Affiliate Rewards Scheme.
We automatically integrate your affiliate referral IDs in the Shield Plugin Badge, so that for any visitor that clicks the badge on your sites and goes on to purchase Shield, you’ll get the affiliate reward for this (15%).
Unlike other referral schemes that only give you once-off rewards, our referrals are for life.
What will the plugin badge look like?
The badge released is very simple – it will be placed on the bottom-left of the page, with the plugin logo and a line of text. It will link back to a landing page outlining features of the plugin and a link to WordPress.org to download it.
The image shown here is how it will look and you can also see it on this site too.
Feedback and Ideas
If you like this little option, or you don’t, please let us know. We are happy to hear what our users think about this and if you have any ideas on how you would to see it implemented better, please tell us.