WordPress runs roughly 43% of all websites, and every one of those sites has the same problem: adding a small piece of live data — how many people are reading, which countries visit, where people click — usually means installing a plugin you'll have to maintain, update and trust.
No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs. Every widget below is one snippet, pasted in once. Pick one and the page tells you the exact menu path for WordPress, the gotchas, and what to do if you're on an older theme or a page builder.
Most small WordPress add-ons arrive as plugins: PHP code that runs on your server, adds settings screens and database tables, and needs updating every few weeks. For something as small as a visitor counter or a Discord badge, that's a lot of moving parts. A FeedPulse widget is a single script tag you paste into a Custom HTML block. Nothing runs on your server, nothing needs updating, and removing it is as simple as deleting the block.
WordPress gives you several places to paste HTML, and the right one depends on the widget. Sitewide widgets, such as a heatmap or page-speed badge, go into the theme header or a header-scripts plugin. Footer and sidebar widgets go into a Custom HTML block in Appearance → Widgets, or in the Site Editor's template parts on block themes. Widgets tied to a page, such as a countdown or a GitHub badge, go into a Custom HTML block inside that post or page. Each widget page below names the exact spot.
Goes in your theme's header, before </head>, because it has to load on every page before your clicks happen, and it renders nothing visible.
Goes in a footer widget area, because an all-time total is a footer artefact — nobody scrolls up to check it.
Goes in your sidebar, because local conditions are a glanceable sidebar item, not a content block.
Goes in your sidebar, because a ticker reads best as a persistent strip beside the content.
Goes in your sidebar, because quotes are reference data — visible, but never competing with the article.
Goes in the post or page itself, because a countdown works above the fold on the page that's actually selling the thing.
Goes in the post or page itself, because it's the most visual widget you have, so it earns a spot in the content rather than the chrome.
Goes in your single-post template, under the content, because it belongs directly under the article body, which means the blog-post template rather than a global widget area.
Goes in a footer widget area, because trust badges are read at the moment of hesitation, which is usually the footer.
Goes in your sidebar, because a live pill is only useful if it's visible before the visitor decides to leave.
Goes in your sidebar, because the whole point is catching someone while you're actually live.
Goes in the post or page itself, because it's social proof for a specific project, so it goes inline next to what it's vouching for.
Goes in the post or page itself, because it belongs beside the install command, in the post or docs page that teaches it.
Goes in your sidebar, because a live member count is a standing invitation, so it should follow the reader down every page.
Goes in a footer widget area, because it's a floating bubble, so it only needs to exist once per page and should load last.
Goes in your theme's header, before </head>, because one paste in the head gives every page its own score — the badge auto-detects which page it's on.
Goes in a footer widget area, because a ranked country list belongs at the bottom, where its lazy-loaded flags stay below the fold.
Goes in the post or page itself, because a live count only changes behaviour when it sits in the same line of sight as the price or the button.
Classic themes have a Widgets screen with sidebar and footer areas, and a header.php file you can edit. Block themes, such as Twenty Twenty-Four, replace both with the Site Editor: you edit templates and template parts like Header and Footer, and insert a Custom HTML block where you want the widget. If your theme has no Widgets menu, you're on a block theme, and the Site Editor is where to go.
Caching plugins such as WP Rocket, W3 Total Cache and LiteSpeed Cache serve a stored copy of your pages, so after you paste a snippet you need to purge the cache to see it. Optimisation settings that combine or defer every script can also move a third-party tag out of order. If a widget doesn't appear after purging, add its script URL to your plugin's JavaScript exclusion list.
Blogs tend to get the most from the comments widget, flag counter and hit counter. Online stores built with WooCommerce suit the online-now counter and countdown timer near products and offers. Agencies and developers can use the page speed badge, GitHub stars badge and npm downloads badge to back up their work. Community sites do well with the Discord, YouTube live and Twitch live widgets. Start with one widget that supports a goal you already have.
Because a widget is only a block of HTML, removing it is clean: delete the Custom HTML block, or the line in your header plugin, and purge your cache. There are no database tables or plugin settings left behind, and nothing else on your site depends on it.
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.