Title: FluentComments – AJAX Comments, Anti-Spam & Comment Email Notifications Author: Shahjahan Jewel Published: سپتامبر 30, 2023 Last modified: سپتامبر 1, 2026 --- Search plugins ![](https://ps.w.org/fluent-comments/assets/banner-772x250.png?rev=3673374) ![](https://ps.w.org/fluent-comments/assets/icon.svg?rev=2973271) # FluentComments – AJAX Comments, Anti-Spam & Comment Email Notifications By [Shahjahan Jewel](https://profiles.wordpress.org/techjewel/) [Download](https://downloads.wordpress.org/plugin/fluent-comments.2.1.1.zip) * [Details](https://haz.wordpress.org/plugins/fluent-comments/#description) * [Reviews](https://haz.wordpress.org/plugins/fluent-comments/#reviews) * [Installation](https://haz.wordpress.org/plugins/fluent-comments/#installation) * [Development](https://haz.wordpress.org/plugins/fluent-comments/#developers) [Support](https://wordpress.org/support/plugin/fluent-comments/) ## Description **FluentComments replaces the WordPress comment form with a fast, modern, AJAX powered one, and it stops comment spam before it ever reaches your moderation queue.** Comments post without a page reload. Replies thread properly. Spam is blocked by several layers working together, so your readers never have to solve a CAPTCHA. And every email your site sends because somebody commented, whether that email goes to the commenter, the post author or you, can be rewritten in your own words with your own logo and colors. FluentComments works on classic themes, block (FSE) themes and page builders. Every feature is free. **There is no pro version, no upsell and no paid add-on.** The whole plugin is open source on [GitHub](https://github.com/WPManageNinja/fluent-comments/). #### FluentComments at a glance * **AJAX comments.** Post a comment or a reply with no page reload. * **Comment spam protection.** Signed tokens, a honeypot, a timing check and rate limits, with no CAPTCHA for your readers. * **Threaded replies** that follow your WordPress discussion depth. * **“Load more” pagination** instead of 400 comments in one request. * **Five comment notification emails.** Each one can be edited, previewed and switched off. * **An email template designer.** Your logo, your colors, your footer and your From address, shared by all five. * **Block (FSE) theme support** with a real block, plus a `[fluent_comments]` shortcode for page builders. * **Cache friendly.** There is no security nonce anywhere in the plugin, so a cached comment form never expires. * **Light, dark and system** appearance for the admin screen. * **Developer friendly.** A small, documented set of actions and filters. * **100% free and open source**, GPLv2. #### Why FluentComments WordPress comments are a genuinely good feature buried under a form from 2010 and a spam problem that most people solve by turning comments off. FluentComments fixes both halves: how comments look and feel, and the flood of junk behind them. #### ⚡ Instant, AJAX powered commenting * Post a comment or a reply **without reloading the page** * Threaded replies that follow your WordPress discussion depth setting * **“Load more”** pagination instead of dumping 400 comments into one request * Gravatar avatars, relative timestamps and a clean, modern card layout * Fully responsive, and styled with CSS custom properties so your theme can restyle every part of it * The whole interface is translatable #### 🛡️ Comment spam protection, without a CAPTCHA Spam is scored, not guessed at. A borderline comment is **held for moderation**, and only a conclusive failure is turned away. Nobody is asked to identify a traffic light. * **Signed submission tokens.** Every comment needs a short lived, HMAC signed token that is issued in a separate request. A bot that posts blindly at your site never gets one. * **Single use tokens, bound to a session cookie.** A token cannot be replayed, or lifted from another visitor’s page. * **A honeypot field** whose name comes from your site’s own salt. It is different on every install, so it cannot be hard coded against. * **A timing check.** A form submitted faster than a human could type is scored as suspicious. * **Rate limiting**, keyed per session first and per IP only as a backstop. An office or a CDN exit address is never counted as one person. * **Native form rejection.** Once FluentComments handles a post type, anything posted to the default WordPress endpoint without our fields is refused. Bots that skip your page and POST straight to `wp-comments-post.php` get nothing. * Every threshold can be adjusted with a filter, and Akismet keeps working alongside it. #### ✉️ Five comment notification emails, all yours to rewrite FluentComments owns every notification your site sends about a comment, and puts them all on one screen: 1. **A held comment was approved.** Sent by FluentComments to the commenter. 2. **Someone replied in their thread.** Sent to everyone above the reply. 3. **A comment landed on their post.** Sent to the post author. 4. **A comment was posted.** WordPress’s own notice, rewritten. 5. **A comment is waiting for review.** WordPress’s own moderation notice, rewritten. * Switch each one on or off from its own row. The switch takes effect immediately, with no save button. * Edit the subject and body in a real WordPress editor. Smartcodes like `{{comment. author}}`, `{{post.title}}`, `{{receiver.name}}` and `{{comment.content}}` are filled in when the mail goes out. * **Preview an email against a real comment from your site** before you send anything. * A shared **template designer** for your logo, your colors, your footer text, and the From and Reply-To addresses. * WordPress’s own two notices are left completely alone until you explicitly ask to replace them. Upgrading the plugin never quietly changes an email your site was already sending. #### 🧩 Block themes, classic themes, page builders * A **FluentComments block** for the Site Editor, with its own title, avatar, color and border radius controls * A `[fluent_comments]` shortcode that works anywhere, including page builders * On a classic theme it takes over `comments_template` automatically, so there is nothing to place * On a block theme the plugin **never rewrites your templates for you**. Instead, the settings screen works out which template each of your post types renders through, follows its template parts and patterns, and tells you exactly which post types still need the block placed #### ⚙️ Settings that don’t fight WordPress The settings screen puts the WordPress Discussion options that actually matter next to the plugin’s own: the moderation word lists, the link limit, threading depth, who may comment, and closing comments on old posts. They are read and written **in place** as real WordPress options, never copied. This screen and Settings › Discussion can never disagree with each other. #### 🚀 Built for cached sites Assume every page on your site is served from a full page cache to somebody else. FluentComments does. * **Nothing visitor specific is ever printed into the HTML.** No identity, no token, and no security nonce anywhere in the plugin, so a comment form served from cache can never fail with a stale security token. * The first page of comments is **rendered into the page itself**, so a visitor who only reads never triggers an uncached request. * Everything per visitor is fetched **on intent**, when someone actually goes to comment. #### 🧑‍💻 For developers A small, documented extension API that works identically on both front ends: * `fluent_comments/form_fields`: render your own fields into the form * `fluent_comments/validate_submission`: reject a submission with a `WP_Error` * `fluent_comments/comment_data`: adjust the comment before it reaches WordPress * `fluent_comments/spam_score`: nudge the score up or down * `fluent_comments/before_process` and `fluent_comments/after_added_comment`: act around the insert Every comment goes through `wp_handle_comment_submission()`, the same function ` wp-comments-post.php` uses, so core’s validation, moderation rules and `comment_post` hook all behave exactly as they always did. #### 100% free, forever No pro version. No locked features. No “upgrade to unlock”. Every feature described on this page is in the plugin you are about to install, and the source is on [GitHub](https://github.com/WPManageNinja/fluent-comments/) under GPLv2. #### Contribute on GitHub FluentComments is fully open source. If you want to contribute, or just report a bug, you are very welcome. The repository is on [GitHub](https://github.com/WPManageNinja/fluent-comments/). #### Other plugins by the WPManageNinja team * [FluentCart – Simple and Powerful eCommerce Plugin for WordPress](https://wordpress.org/plugins/fluent-cart/) * [Fluent Forms – Fastest Contact Form Builder Plugin for WordPress](https://wordpress.org/plugins/fluentform/) * [FluentSMTP – The Most Advanced SMTP, SES Plugin for WordPress](https://wordpress.org/plugins/fluent-smtp/) * [FluentCRM – Email Marketing Automation and CRM Plugin for WordPress](https://wordpress.org/plugins/fluent-crm/) * [Ninja Tables – Best WP DataTables Plugin for WordPress](https://wordpress.org/plugins/ninja-tables/) ## Screenshots [⌊Comments load and post without reloading the page, with threaded replies and an inline reply form⌉⌊Comments load and post without reloading the page, with threaded replies and an inline reply form⌉[ Comments load and post without reloading the page, with threaded replies and an inline reply form [⌊The settings screen: which post types FluentComments runs on, and the rules every comment is held to⌉⌊The settings screen: which post types FluentComments runs on, and the rules every comment is held to⌉[ The settings screen: which post types FluentComments runs on, and the rules every comment is held to [⌊Every notification email in one place, each one switched on or off from the row⌉⌊ Every notification email in one place, each one switched on or off from the row⌉[ Every notification email in one place, each one switched on or off from the row [⌊Write your own subject and body in the WordPress editor, with placeholders for the comment, post and recipient⌉⌊Write your own subject and body in the WordPress editor, with placeholders for the comment, post and recipient⌉[ Write your own subject and body in the WordPress editor, with placeholders for the comment, post and recipient [⌊Every email previewed against a real comment from your own site before it goes out⌉⌊Every email previewed against a real comment from your own site before it goes out⌉[ Every email previewed against a real comment from your own site before it goes out [⌊One template design - logo, colors, footer and From address - shared by every email⌉⌊One template design - logo, colors, footer and From address - shared by every email⌉[ One template design – logo, colors, footer and From address – shared by every email [⌊The approval notice as the commenter receives it⌉⌊The approval notice as the commenter receives it⌉[ The approval notice as the commenter receives it [⌊The whole screen in dark mode, remembered per browser⌉⌊The whole screen in dark mode, remembered per browser⌉[ The whole screen in dark mode, remembered per browser ## Blocks This plugin provides 1 block. * FluentComments Display comments and comment form with AJAX loading and spam protection. ## Installation 1. Install FluentComments from the WordPress.org plugin directory, or upload the plugin folder to `/wp-content/plugins/`. 2. Activate FluentComments from the Plugins page. 3. Go to **Comments › FluentComments** and pick the post types it should handle. That is the whole setup. **If your theme is a block (FSE) theme**, there is one extra step. Open the Site Editor, edit the template your posts render through, replace the **Comments** block with the **FluentComments** block, and save. Or drop the `[fluent_comments]` shortcode wherever you want comments. The settings screen checks this for you and tells you which post types still need it. ## FAQ ### Is FluentComments really free? Is there a pro version? It is free, and there is no pro version. Every feature listed on this page is in the free plugin: the spam protection, all five emails, the template designer and the block. Nothing is held back, and the whole thing is GPLv2 open source on GitHub. ### How does FluentComments stop comment spam without a CAPTCHA? By making the submission itself expensive to fake. Posting a comment requires a short lived, cryptographically signed token that is issued in a separate request and tied to a session cookie, so it cannot be replayed or reused. On top of that there is a honeypot field with an install specific name, a minimum time between opening the form and submitting it, and rate limiting keyed per session with a per IP backstop. Anything posted straight to the default WordPress endpoint without our fields is refused outright. Suspicious submissions are scored and held for moderation rather than thrown away, and every threshold can be changed with a filter. ### Do I still need reCAPTCHA or a CAPTCHA plugin? No. FluentComments is built so your readers never have to prove they are human. The checks happen between the browser and your server, not in front of the person trying to leave a comment. ### Does it work with Akismet? Yes. Akismet inspects the comment itself and needs nothing from the form, so it runs normally alongside FluentComments. ### What if I use another anti-spam or CAPTCHA plugin on my comment form? FluentComments renders its own comment form, so a field another plugin wants to add, like a CAPTCHA or an extra question, is never printed on the page. Because nobody could fill that field in, running its validator anyway would reject every comment on your site. So those validators are skipped for the duration of a FluentComments submission. If you want to keep another plugin’s check, add its callback to the ` fluent_comments/allowed_comment_hooks` filter and render its field with the `fluent_comments/ form_fields` action. ### Does it work with block (FSE) themes? Yes. Add the **FluentComments** block in the Site Editor, or use the `[fluent_comments]` shortcode. The plugin never edits your templates on your behalf. But the settings screen does work out which template each post type renders through, looks inside it and its template parts, and tells you which ones still need the block. ### Does it work with Elementor, Divi, Bricks and other page builders? Yes. Drop the `[fluent_comments]` shortcode into any builder’s shortcode or text widget and the full comment list and form render there. ### Will it work with my caching plugin? Yes, and it is designed for it. Nothing visitor specific is printed into the page, so a cached comment form is still a valid one. There is no security nonce anywhere in the plugin, which means a form served from cache can never fail with the “your session has expired” error that nonce based forms hit. Everything per visitor is fetched on demand, only when someone actually goes to comment. ### Will it slow down my site? No. The first page of comments is rendered into the page itself, so a visitor who only reads never triggers an extra request. There is no webfont, no external service and no third party script. Comments load in pages rather than all at once. ### Can I keep my existing comments? Yes. FluentComments uses the normal WordPress comments table and the normal WordPress comment functions. Nothing is migrated, copied or moved. These are your existing comments, displayed and protected better. Deactivate the plugin and your comments are still exactly where they were. ### Can I restyle the comments to match my theme? Yes. Every color, spacing value and radius is a CSS custom property, so a handful of `--fcom-*` overrides in your theme will restyle the whole thing. The block also exposes its title, avatars, colors and border radius in the editor sidebar. ### Does it respect my WordPress Discussion settings? Yes, with one exception. Threading depth, moderation keywords, disallowed keywords, the link limit, “comment author must have a previously approved comment”, “users must be registered and logged in”: all of them are real WordPress options that FluentComments reads and writes in place. The most useful ones are surfaced on the FluentComments screen so you do not have to go hunting for them. The exception is “Comment author must fill out name and email”, which FluentComments always applies to its own form whatever that box is set to. See the question below for why. ### Can I customize the comment notification emails? Yes, all five of them. Rewrite the subject and body of any email, use smartcodes like `{{comment.author}}` and `{{post.title}}`, preview it against a real comment from your site, and set a shared logo, color scheme, footer and From/Reply-To address for all of them. WordPress’s own two notices are left untouched unless you explicitly choose to replace them. ### Can I add my own fields to the comment form? Yes. Use the `fluent_comments/form_fields` action to render them and `fluent_comments/ validate_submission` to check them. They work identically on the block, the shortcode and the classic template. Because fields ship with the per request session payload rather than the cached page, anything time sensitive in them stays fresh. ### Do commenters have to give a name and email address? Yes, unless they are logged in. FluentComments always asks a logged out commenter for both, and it does not follow the WordPress “Comment author must fill out name and email” setting, which is why that option is not on our settings screen. The reason is the notification emails: every one of them is addressed by the commenter’s email, so an anonymous comment quietly opts its author out of the reply notifications everybody else in the thread receives, and leaves you nothing to moderate on. Logged in commenters are never asked, because WordPress already has both from their account. The WordPress setting itself is untouched and still applies to any post type FluentComments is not handling. ### My site is behind Cloudflare or a load balancer. Do I need to do anything? Usually not. Most managed hosts, and the Cloudflare plugin, put the visitor’s real address into `REMOTE_ADDR` for you, and FluentComments reads it from there. If yours does not, every visitor looks like the same address. The limit that matters follows a per visitor cookie rather than the IP, so nobody gets locked out, but the loose per IP ceiling then applies to the whole site at once. You can opt into reading proxy headers: ``` add_filter('fluent_comments/trust_proxy_headers', '__return_true'); ``` Only do that when your origin server cannot be reached directly, bypassing the proxy. This setting trusts the header rather than verifying the proxy sent it, so on a directly reachable origin a visitor could set the header themselves and sidestep the per IP limit. It is also worth narrowing `fluent_comments/proxy_ip_headers` to the one header your proxy actually sets. ## Reviews ![](https://secure.gravatar.com/avatar/807225c3ea3b68a06bf38e9eeb36b47654652b4ba16c8f1148036daa3e649d0b? s=60&d=retro&r=g) ### 󠀁[Great Comment Plugin for WordPress](https://wordpress.org/support/topic/great-comment-plugin-for-wordpress/)󠁿 [DeepBlue](https://profiles.wordpress.org/deepblue5/) مارس 13, 2026 Hi Great plugin, simple and effective a great addition to the fluent suite for Wordpress Please add support for pages too (not only articles) ![](https://secure.gravatar.com/avatar/d8c04de7550b682ae58037fbc6c00def706aae1b3e6dbdec6a55208f31cc94a7? s=60&d=retro&r=g) ### 󠀁[This is how comments should be by default](https://wordpress.org/support/topic/this-is-how-comments-should-be-by-default/)󠁿 [ShabuShabu](https://profiles.wordpress.org/shabushabu/) آگوست 15, 2025 With FluentComments, the comments section finally looks modern and engaging. Great work! ![](https://secure.gravatar.com/avatar/5bfb3dbe47a382dd9b69cdee45002e1365eeaac43eae980dcad04576f63caa5e? s=60&d=retro&r=g) ### 󠀁[Great, underrated plugin](https://wordpress.org/support/topic/great-underrated-plugin/)󠁿 [kacper3355](https://profiles.wordpress.org/kacper3355/) جولای 28, 2025 Keep up the good work! Thanks for the plugin. ![](https://secure.gravatar.com/avatar/73a31e726e3c519d2c8940a0d56a1676979aac61d21dfec914ea21fad479c54f? s=60&d=retro&r=g) ### 󠀁[Not working in Bricks. 🙁](https://wordpress.org/support/topic/not-working-in-bricks/)󠁿 [mmikolas](https://profiles.wordpress.org/mmikolas/) ژوئن 27, 2025 1 reply It doesn’t work in Bricks. I only see “Loading.” ![](https://secure.gravatar.com/avatar/0c3666b7658ca9fd202d8683754176bd920db7a755db1e6b6bb53910ba82f82a? s=60&d=retro&r=g) ### 󠀁[any Update?](https://wordpress.org/support/topic/any-update-22/)󠁿 [amirhossein7](https://profiles.wordpress.org/amirhossein7/) ژانویه 19, 2025 Why, after all this time, has this good plugin not been developed at all, its bugs not been fixed, and no updates have been provided for it? ![](https://secure.gravatar.com/avatar/e6d4f62a2cbdfa58c28f53fc061951fe0e517c3f69b63658784123a66337b145? s=60&d=retro&r=g) ### 󠀁[Wonderfull free plugin for protect spam comment](https://wordpress.org/support/topic/wonderfull-free-plugin-for-protect-spam-comment/)󠁿 [smnurulislam](https://profiles.wordpress.org/smnurulislam/) می 6, 2024 This is the plugin I am looking for long time. I have a review in youtube about this plugin, I install it on site and get the result. Thank you [ Read all 6 reviews ](https://wordpress.org/support/plugin/fluent-comments/reviews/) ## Contributors & Developers “FluentComments – AJAX Comments, Anti-Spam & Comment Email Notifications” is open source software. The following people have contributed to this plugin. Contributors * [ Shahjahan Jewel ](https://profiles.wordpress.org/techjewel/) * [ WPManageNinja ](https://profiles.wordpress.org/wpmanageninja/) “FluentComments – AJAX Comments, Anti-Spam & Comment Email Notifications” has been translated into 2 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/fluent-comments/contributors) for their contributions. [Translate “FluentComments – AJAX Comments, Anti-Spam & Comment Email Notifications” into your language.](https://translate.wordpress.org/projects/wp-plugins/fluent-comments) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/fluent-comments/), check out the [SVN repository](https://plugins.svn.wordpress.org/fluent-comments/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/fluent-comments/) by [RSS](https://plugins.trac.wordpress.org/log/fluent-comments/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 2.1.1 * Fixed: UI color issues for the Radio Buttons. * Fixed: UI Flickering issues for the comment forms. #### 2.1.0 (Date: Aug 31, 2026) * New: an Emails screen. All five comment notification emails can be edited, previewed against a real comment, and switched on or off from one place. * New: a shared email template designer for your logo, colors, footer text and From address. * New: a FluentComments block for block (FSE) themes. The settings screen tells you which post types still need it. * New: comments load in pages with a “Load more” button instead of all at once. * New: the most useful WordPress Discussion settings now sit on the FluentComments screen. * New: a rebuilt admin screen with light, dark and system appearance modes. * Improved: much stronger spam protection, and a suspicious comment is now held for moderation instead of being turned away. * Improved: comments are now written into the page itself instead of being fetched by JavaScript after it loads, so search engines and link previews can read them. * Improved: the whole front end is translatable. Previously it was hard coded English. * Changed: a name and email address are now always required from commenters who are not logged in, whatever the WordPress “Comment author must fill out name and email” setting says. That setting has been removed from the FluentComments screen; it still applies to any post type FluentComments is not handling. Every notification email is addressed by the commenter’s email, so an anonymous comment quietly opts its author out of the replies everyone else in the thread receives. * Fixed: comments that WordPress or Akismet marked as spam or trash could still trigger notification emails containing their contents. * Fixed: re-approving a comment sent its notifications a second time. * Fixed: pingbacks and trackbacks were emailed as if somebody had left a comment. * Fixed: comments could be submitted on post types FluentComments was not switched on for. * Fixed: on a cached site, the comment form could be served to the wrong visitor– showing a logged in reader the login notice, or leaving an anonymous one without the name and email fields. * Fixed: comment times were saved in server time instead of UTC. * Fixed: post authors got two emails for the same comment. * Fixed: the comment form showed on posts with comments closed. * Fixed: reply depth ignored your WordPress discussion settings. * Fixed: the block’s “Show Avatars” option had no effect. * Fixed: pingbacks and trackbacks appeared in the comment list. * Please note: if you use another anti-spam or CAPTCHA plugin on your comment form, its check no longer runs on the FluentComments form. Akismet is not affected and keeps working. #### 2.0.0 (Date: Jul 07, 2025) * Added support for FSE themes * Added email notifications for admins, authors and commenters * Added an option to enable or disable email notifications * Advanced spam protection with cryptographic tokens #### 1.0.1 (Date: May 18, 2024) * Added shortcode support for FSE themes * Fixed minor CSS issues * Checking logged in requirement for the comment form #### 1.0.0 (Date: Sep 30, 2023) * Initial release ## Meta * Version **2.1.1** * Last updated **21 ساعت ago** * Active installations **700+** * WordPress version ** 6.5 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Languages * [English (US)](https://wordpress.org/plugins/fluent-comments/), [Russian](https://ru.wordpress.org/plugins/fluent-comments/), and [Vietnamese](https://vi.wordpress.org/plugins/fluent-comments/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/fluent-comments) * Tags * [ajax comments](https://haz.wordpress.org/plugins/tags/ajax-comments/)[antispam](https://haz.wordpress.org/plugins/tags/antispam/) [comment notification](https://haz.wordpress.org/plugins/tags/comment-notification/) [comments](https://haz.wordpress.org/plugins/tags/comments/)[spam protection](https://haz.wordpress.org/plugins/tags/spam-protection/) * [Advanced View](https://haz.wordpress.org/plugins/fluent-comments/advanced/) ## Ratings 4.3 out of 5 stars. * [ 5 5-star reviews ](https://wordpress.org/support/plugin/fluent-comments/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/fluent-comments/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/fluent-comments/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/fluent-comments/reviews/?filter=2) * [ 1 1-star review ](https://wordpress.org/support/plugin/fluent-comments/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/fluent-comments/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/fluent-comments/reviews/) ## Contributors * [ Shahjahan Jewel ](https://profiles.wordpress.org/techjewel/) * [ WPManageNinja ](https://profiles.wordpress.org/wpmanageninja/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/fluent-comments/)