This guide shows how to add a WordPress trust badge in about a minute, with no plugin: you paste one snippet into a footer widget area, because trust badges are read at the moment of hesitation, which is usually the footer. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.
The verified traffic badge shows your site's monthly visitors as measured by FeedPulse, along with the share of traffic filtered out as bots. It's meant for sites that sell advertising or sponsorships, or that want to back up an audience claim with a number measured by a third party rather than typed in by you.
On WordPress, the right spot is a footer widget area. Trust badges get read at the moment someone is deciding whether to believe you, so the footer of your media kit, advertise-with-us page or sponsorship page is the natural place.
WordPress.org sites you host yourself can use every method on this page. On WordPress.com, adding scripts with a Custom HTML block or a header plugin needs a plan that allows plugins and custom code (the Business plan or above at the time of writing), because lower WordPress.com plans strip script tags. If you're not sure which you have, check whether your dashboard has a Plugins menu.
WP Rocket, W3 Total Cache, LiteSpeed Cache and your host's edge cache all serve a stored copy of your HTML. Until you purge, you'll be looking at the version from before you pasted and assuming the widget is broken. The widget's own data is fetched client-side on every load, so page caching never makes the numbers go stale — it only hides a freshly-added snippet.
Optimisation plugins that concatenate or defer every script can break an async third-party tag by moving it out of order. If the widget renders nothing after a purge, add the script URL to your plugin's JS exclusion list — in WP Rocket that's File Optimization → Excluded JavaScript Files. Nothing else needs changing.
WordPress sanitises script tags typed into a paragraph or the Visual editor tab, silently. The Custom HTML block, the Classic editor's Text tab, and Elementor's HTML widget all pass markup through untouched. If your snippet vanished on save, that's why.
It only counts visits FeedPulse has measured since you installed it, so a new install starts low. It complements, rather than replaces, analytics screenshots that advertisers may still ask for.
No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs. Installing a plugin for this would mean another dependency and update cycle just to show one widget.
A footer widget area, because trust badges are read at the moment of hesitation, which is usually the footer.
It adds one small script, loaded asynchronously, so it doesn't block your page from rendering. Any third-party script has some cost, so check your page speed before and after adding it. Your caching and optimisation plugins keep working exactly as before — the only thing to remember is to purge the cache after you paste, otherwise you'll be looking at the stored copy of your old HTML.
Elementor: drag in the HTML widget and paste there. Divi: use a Code module. Beaver Builder: use the HTML module. WPBakery: use the Raw HTML element. Any builder with a raw-HTML or code block will render it.
From visits FeedPulse has measured on your site since you installed it, with bots filtered out. It doesn't import numbers from other analytics tools.