This guide shows how to add a WordPress comments widget in about a minute, with no plugin: you paste one snippet 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. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.
The comments widget adds a comment thread under your posts, as a lightweight alternative to Disqus. Readers can comment without creating an account, there are no ads in the thread, and the script is small. It's meant for blogs, newsletters and documentation pages where you want conversation without running a forum.
On WordPress, the right spot is your single-post template, under the content. Comments belong directly under the article, so the snippet goes into the post template rather than a sitewide area. That way every post gets its own thread automatically, and pages that don't need comments stay clean.
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.
Anonymous commenting is easy for readers but also easier for spammers, so check new threads regularly. It's not a full forum: there are no user profiles or private messages.
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.
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.
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.
No. Commenting is anonymous by default, so readers can join in without signing up for anything.