WordPress · free forever · no signup

Add a free comments widget to WordPress

One snippet, pasted into 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. WordPress runs roughly 43% of all websites, and almost none of those sites want another plugin just to render a small piece of live data. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.

Disqus is bloated (1 MB+), tracking-heavy, and ad-supported. We rebuilt the entire comments stack in 5 KB. No signup, no email required, optional moderation, beautiful themes.

How to install it on WordPress

  1. 1Go to Appearance → Editor → Templates → Single (or edit single.php on a classic theme).
  2. 2Place your cursor directly below the Post Content block.
  3. 3Insert a Custom HTML block and paste the snippet.
  4. 4Save — it now appears under every post automatically.
Block theme or a different editor? Prefer it on one post only? Use a Custom HTML block inside that post instead of touching the template.

Three things that trip people up on WordPress

Purge your cache after pasting

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.

Exclude it from JS minify / combine

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.

Use a Custom HTML block, never a paragraph

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.

What you get, and what it costs

  • Free forever — there is no paid tier, no trial and no card
  • No signup for the badge-style widgets; the live ones create a site ID inline from your URL
  • Async script — it never blocks your page from rendering
  • Works on any theme, classic or block, and inside every major page builder
  • Bots filtered server-side on every visitor-counting widget

WordPress questions

Do I need a plugin to add a comments widget to WordPress?

No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs. Installing a plugin for this would mean an extra dependency, an update cycle and a security surface to render one snippet. Paste it into your single-post template, under the content and you're done.

Where exactly does the snippet go on WordPress?

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. Go to Appearance → Editor → Templates → Single (or edit single.php on a classic theme). Place your cursor directly below the Post Content block. Insert a Custom HTML block and paste the snippet. Save — it now appears under every post automatically.

Will it slow my WordPress site down?

No. The script tag is async, so it never blocks your page from rendering, and the widget draws itself after your content is already on screen. 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.

Does it work with page builders like Elementor?

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, because there's nothing framework-specific in the snippet.