WordPress · blog

Free WordPress widgets for a blog

A blog's problem is abandonment: a reader lands on one post from search and leaves without discovering anything else. Live signals — people reading right now, where they're from, a comment thread with real replies — are social proof that the post is worth finishing.

What you are trying to do here is keep a reader on the page and prove the blog is alive. Three widgets below do that; the other 15 in the set mostly do not, so they are not on this page. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.

The three worth adding

  1. 01

    free live traffic widget

    On WordPress this goes in a footer widget area — it works anywhere on the page.

  2. 02

    comments widget

    On WordPress this goes in your single-post template, under the content — it belongs directly under the article body, which means the blog-post template rather than a global widget area.

  3. 03

    flag counter

    On WordPress this goes in a footer widget area — a ranked country list belongs at the bottom, where its lazy-loaded flags stay below the fold.

Where to put them

Put the live feed and flag counter in the sidebar or footer so they persist across every post, and the comments widget directly under the article body where a reader has just finished reading.

How to add a widget to WordPress without a plugin

Every FeedPulse widget is one line of embed code, so WordPress needs no plugin. In the block editor, add a Custom HTML block where you want the widget, paste the code and update the page. To show it on every page, go to Appearance → Widgets and add a Custom HTML block to your sidebar or footer area. If you use a block theme without widget areas, open Appearance → Editor, edit the Footer template part, and add the Custom HTML block there.

WordPress caching and widgets

Caching plugins and hosts that cache full pages don't usually affect embedded widgets, because the widget loads its data in the visitor's browser after the page arrives. If a newly added widget doesn't appear, clear your caching plugin's cache and your host's cache, then check the page in a private window. Optimization plugins that combine or delay JavaScript can occasionally delay a widget; if that happens, exclude the widget's script from delay or combine settings.

Testing on WordPress before going live

If you have a staging site, add the widget there first. Otherwise add it to one page, check it on desktop and mobile, then roll it out to your sidebar or footer. Run a PageSpeed Insights test on that page before and after so you know the real effect on your site.

What a blog actually needs from widgets

A blog's job is to keep a reader who arrived from search reading a second post. Widgets help when they show that other people are reading too and give readers a reason to stay: a live traffic feed in the sidebar, an online-now count near the top of posts, and comments where readers can see real replies. Decoration that doesn't support reading, like tickers or unrelated badges, usually just adds weight.

Where blog widgets work best

Put the live traffic feed in the sidebar, below your author box or newsletter signup. Place an online-now button near the post title only if your posts get steady traffic; on quiet posts it will often show one visitor. Comments belong at the end of the post, where readers who finished it can respond.

Mistakes bloggers make with widgets

The most common mistakes are adding every widget at once, putting widgets above the first paragraph where they push content down on mobile, and leaving counters on pages with almost no traffic. Start with one widget, watch it for a few weeks, and add the next only if it earns its space.

How to tell if the widgets help your blog

Compare pages per visit and time spent on your most-read posts for a few weeks before and after. Your analytics tool shows both. If they don't move, try a different placement before adding more widgets.

Do widgets help a blog rank on Google?

Not directly. Google ranks posts on how well they answer a search, not on widgets. Widgets help indirectly when they keep readers on the site longer and encourage them to read more posts, and they hurt only if they slow the page down. Keep them light and below your content.

A starter setup for most blogs

For a typical blog, begin with a live traffic feed in the sidebar and comments at the end of each post. After a month, look at pages per visit on your most-read posts. If readers are staying longer, keep the setup; if not, try the feed lower in the sidebar or swap it for a flag counter that builds up over time.

Which widgets are free

Every FeedPulse widget and badge is free to use with no signup: copy the embed code from the widget's page, paste it into your site and it starts working. There's no trial period and no card required. Some widgets that rely on outside data, such as weather or market prices, refresh on a schedule rather than every second, so they stay fast and free to run.

Check the result after a month

Give any new widget about four weeks before judging it. Compare the action that matters for your site, such as inquiries, bookings, sales or pages per visit, with the four weeks before you added it. Keep widgets that clearly help, move ones that might help in a better spot, and remove ones that made no difference. A page with fewer, useful widgets usually beats a page with many.

Privacy and widgets

FeedPulse widgets show aggregate information such as visitor counts, countries and pages, not names or exact locations. Even so, mention any third-party widget in your privacy policy, and check whether your cookie notice needs updating for the tools you use.

Removing a widget later

Delete the block, section or embed element that contains the code and publish. Nothing else on your site depends on it. Your public FeedPulse stats page keeps the history it has already collected.

One widget or several?

Start with one. A single widget in the right place is easier to judge, keeps the page fast and doesn't compete with your content. Once you've seen whether it helps, add a second only if it does a different job, for example pairing a visitor count with a countdown for a real offer. Avoid stacking several widgets that all say the same thing, such as two different visitor counters, because they make the page busier without adding information.

Accessibility and widgets

Widgets should never hide important information that isn't available elsewhere on the page. Keep your opening hours, prices and contact details as normal text, not only inside a widget. Check that widget colors have enough contrast against your background, and that the page still makes sense if a visitor's browser blocks third-party scripts. A widget should add to the page, not be the only place key information lives.

Questions people ask

Which widget should a blog on WordPress add first?

free live traffic widget — A blog's problem is abandonment: a reader lands on one post from search and leaves without discovering anything else. Live signals — people reading right now, where they're from, a comment thread with real replies — are social proof that the post is worth finishing.

Where do the widgets go on a blog?

Put the live feed and flag counter in the sidebar or footer so they persist across every post, and the comments widget directly under the article body where a reader has just finished reading.

Do I need a plugin for this on WordPress?

No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.

Other site types on WordPress