Testimonials work because they’re proof from someone who isn’t you. A WordPress testimonial plugin handles the collection form, storage, and display, sliders, grids, carousels, without you hand-coding a review section into your theme.
Worth flagging first: three plugins that used to top this list are dead
Testimonials Widget (closed June 2024, security issue), Easy Testimonials (closed July 2024, security issue), and AP Custom Testimonial (closed March 2023, guideline violation) were all commonly recommended a few years back and are no longer available on WordPress.org at all. If you’re running any of them, replace them, a closed-for-security-issue plugin isn’t getting patched. That’s not a hypothetical risk either: a shuttered plugin sitting in your active plugins list is a known, unfixed entry point, and it will stay that way until you remove it. Check your plugins screen against those three names today if you haven’t looked recently.
Why testimonials actually move the numbers
It’s easy to treat a testimonials section as decoration, something that fills a gap on the homepage between the hero and the pricing table. That undersells what it’s doing. A visitor lands on a site with no history with the brand, no relationship, nothing but the page in front of them, and every claim the site makes about itself carries less weight than the same claim coming from someone with no reason to lie. That’s the entire mechanic behind why review platforms, case studies, and testimonial widgets keep showing up on conversion-focused pages: they borrow credibility a brand can’t generate on its own.
Where this actually shows up in practice is further down the funnel than most people assume. A testimonial near a call-to-action button, right before a pricing decision, or on a checkout page tends to do more work than one buried in a dedicated “Testimonials” page nobody visits. If you’re only running these plugins to populate one static page, you’re using maybe a third of what the format is capable of.
What makes a testimonial worth featuring
Not every submission deserves a spot on your homepage, and a plugin that lets anything through without curation will eventually hurt more than it helps. A few things separate a testimonial that actually persuades from one that just sits there:
Specificity beats enthusiasm
“Great product, highly recommend” reads like it could have been written about anything. “Cut our support ticket volume by about a third in the first month after we switched” reads like it happened. The second one is more useful even though it’s less effusive, because specificity is what makes a reader believe the person behind it is real and had a real experience.
A name and a face change how it’s read
An anonymous quote gets read with more skepticism than one attached to a real name, a photo, and ideally a company or role. This is part of why the video testimonial support in Strong Testimonials matters more than it might seem, a face and a voice are harder to dismiss than text on a page, even a well-written line of text.
Recency matters more than most people account for
A testimonial dated three years ago, especially for a product that’s changed a lot since, can work against you if a visitor notices the date. Rotate stale ones out periodically rather than treating a testimonials section as something you set up once and forget.
What’s actually still active
1. Strong Testimonials
Strong Testimonials is the most fully-featured free option here, grid, slider, and masonry layouts, video testimonial support, submission approval before anything goes public, and integration with Elementor, Divi, and Beaver Builder. 90,000+ installs, updated within the last week as of this writing.
Setup is a submission form you embed with a shortcode or block, testimonials come in as a custom post type, and you approve or reject each one before it goes live. The moderation queue alone is worth the install if you’ve ever had a plugin that publishes submissions directly, unmoderated testimonials are a liability waiting to happen, whether that’s a competitor submitting something fake or a genuine customer venting about an unrelated issue in the same form meant for praise.
2. Thrive Ovation
Thrive Ovation automates the collection side, it can pull testimonials from social mentions, email, and other sources instead of relying entirely on a submission form, then send automated follow-ups asking customers to leave feedback. $49/year standalone, or bundled into the $299/year Thrive Suite.
The follow-up automation is the actual selling point. Most site owners know they should be asking happy customers for feedback and don’t, because it means remembering to send an email at the right moment, which after the fifth or sixth customer stops happening consistently. Ovation handles the “remembering” part, which in practice means you end up with more testimonials over time than a manual process would produce, simply because the ask happens reliably instead of when you get around to it.
3. BNE Testimonials
BNE Testimonials is a smaller, simpler plugin, grid, slider, and list layouts, CSV/social import, multi-language support. Smaller install base (1,000+) than the others here, but genuinely active: last updated hours before this was written.
The CSV import is a genuinely useful feature if you’re migrating from a spreadsheet where you’ve been tracking customer quotes manually, or moving off one of the discontinued plugins mentioned above and want to bring existing testimonials with you instead of re-entering everything by hand.
4. Testimonial Slider and Showcase
Testimonial Slider and Showcase covers the slider-specific use case directly, with schema markup support for search result rich snippets. 30,000+ installs. Worth a note: WordPress.org currently shows a “not tested with the latest 3 major WordPress releases” flag on this one even though the changelog shows updates into late 2025, test it on staging before relying on it.
The schema markup piece is worth understanding even if you don’t pick this plugin: structured data on testimonials or reviews can surface star ratings directly in Google search results, which is a genuine click-through-rate advantage over a plain blue link. Not every testimonial plugin bothers with this, so if search visibility for the page hosting your testimonials matters to you, check whether schema output is included before you commit to one.
5. WPForms (for collecting testimonials, not displaying them)
WPForms isn’t a testimonial display plugin, but it’s worth including for the collection side: a form with conditional logic and file upload support (for photos) is often the easiest way to actually gather testimonials in the first place, before feeding them into whichever display plugin you pick. 5 million+ installs.
A well-built intake form asks for more than just the quote itself, name, role, company, permission to use a photo, and ideally a specific result or number if the customer has one. Building that structure into the form up front means less back-and-forth editing later, and it means the testimonials that come in are already close to publish-ready instead of needing a rewrite pass.
6. Site Reviews
Site Reviews is built more for product/service reviews (Amazon or Tripadvisor-style) than dedicated testimonials, but it works as a testimonial tool too, and it’s actively maintained with 60,000+ installs and a recent update. Worth considering if you want reviews and testimonials handled by the same system.
The star-rating format changes how a testimonial reads compared to a plain quote. A five-star rating next to a short comment gets processed faster by a visitor skimming a page than a paragraph of prose, which makes Site Reviews a reasonable pick if your audience is scanning rather than reading closely, product pages in particular.
Display without hurting page speed
A testimonial slider is one of the more common places a WordPress site quietly picks up extra JavaScript and CSS it doesn’t need. Sliders in particular tend to load a full carousel library even when a site is only ever going to show three or four testimonials, which almost never needs a full carousel to begin with. A simple grid with lazy-loaded images does the same persuasive job without the extra render-blocking weight. If you do want a slider for the visual motion, check whether the plugin lazy-loads images below the fold and whether it’s loading its JS only on pages that actually use the shortcode, not sitewide. That second part matters more than people expect: a lot of plugins load their assets globally by default and only give you a page-specific option if you go looking for it in settings.
A common mistake worth avoiding
Site owners sometimes load every testimonial they’ve ever collected onto one page, on the theory that more is more persuasive. In practice, a wall of ten or fifteen quotes gets skimmed past, while three or four well-chosen ones, specific, recent, attached to a real name, get actually read. If you’re sitting on a large collection, rotate a curated set rather than displaying everything at once, and let the plugin’s category or tag feature (most of the ones above support this) show different testimonials on different pages depending on what that page is trying to convince someone of.
Consent and attribution, the part people skip
Publishing a customer’s name, photo, and words on your site is publishing someone else’s likeness and quote, and while most customers are happy to be featured, that’s a decision that should be documented rather than assumed. A submission form that includes an explicit checkbox, something like “I agree this testimonial and my name/photo can be published on this website”, covers you if a customer later asks why their information is up somewhere they don’t remember agreeing to. Strong Testimonials and WPForms both let you add a required checkbox field to the submission form for exactly this reason, and it’s worth doing even if it feels like unnecessary friction on a short form. It’s a five-minute addition against a real, if uncommon, headache later.
The same logic applies if you’re pulling testimonials from public sources, a tweet, a review left on a third-party site, a comment on a Facebook post, rather than a direct submission. Screenshotting someone’s public post and republishing it on your marketing page sits in a legal gray area depending on where you and the customer are located, and the safer move is a quick message asking permission before featuring it, even when the content was already public elsewhere.
Mobile display is where most testimonial sections actually fail
A three-column grid that looks clean on desktop often collapses into something unreadable on a phone, text overflowing a card, photos cropped awkwardly, or a carousel that requires a precise swipe gesture that half of visitors won’t figure out. Since a meaningful share of traffic to most sites now arrives on mobile, a testimonial plugin that hasn’t been checked at a 390px viewport is a plugin that’s failing a large slice of visitors without you knowing it. Before committing to a layout, pull the page up on an actual phone, not just a resized browser window, and check that: cards stack in a single column rather than squeezing three across, star ratings and quote marks don’t overlap the text, and any carousel has visible next/previous controls a thumb can actually hit rather than relying purely on swipe.
Building a collection habit instead of a one-time push
Most sites collect a burst of testimonials early, right after launch or right after a product update, and then the well runs dry because nobody’s asking anymore. A better pattern is tying the ask to a specific moment in the customer relationship, right after a support ticket gets resolved well, a set number of days after a purchase, or right after a customer renews. Thrive Ovation automates this by design, but you can approximate the same thing with any of the other plugins by adding a manual step to your process, an email template you send at that trigger moment with a direct link to your testimonial form. The plugin choice matters less here than the discipline of actually sending the ask consistently; a great plugin sitting on a stale intake form full of testimonials from two years ago is worse for conversion than a mediocre plugin fed by a steady trickle of recent ones.
Where testimonials tend to underperform
Not every page benefits equally from a testimonial block. On a page where a visitor is already fairly convinced, the confirmation step of a checkout flow, for instance, a testimonial can slow things down more than it helps, since it’s introducing a new thing to read at the exact moment a decisive visitor wants friction removed, not added. Testimonials do the most work earlier in the decision: a pricing page where someone’s still weighing whether to commit, a features page comparing you to alternatives, or a landing page for a specific campaign where the visitor has no prior context on the brand at all. If you’re only going to place testimonials in one or two spots rather than scattering them everywhere, those higher-doubt, lower-context pages are where to put them.
Picking one
Strong Testimonials covers the most ground for free and is the safest default. Thrive Ovation is worth the cost specifically if manually asking every customer for a testimonial isn’t realistic and you want the collection automated. BNE Testimonials and Testimonial Slider and Showcase are fine, lighter-weight options if you just need a simple display. Site Reviews makes sense if reviews and testimonials can share one system on your site.
If you’re running a BuddyPress or BuddyBoss community rather than a standard business site, the same logic applies but the source shifts, member success stories and group testimonials tend to convert prospective members better than generic marketing copy, since a visitor evaluating whether to join is asking a version of the same question a customer asks before buying: did this actually work for someone like me.
A rough way to decide between the free options
If you’re choosing among the free plugins specifically rather than paying for Thrive Ovation, it helps to think about it less as “which is best” in the abstract and more as which limitation you can live with. Strong Testimonials asks more of you upfront, more settings, more layout choices, but rewards that with the fewest gaps later. BNE Testimonials gets you running faster with less to configure, at the cost of a smaller community around it if you hit an edge case and go looking for a forum thread on how someone else solved it. Testimonial Slider and Showcase is worth it specifically for the schema markup, but the compatibility flag on WordPress.org means you shouldn’t push it straight to a production site without a staging check first, particularly after a WordPress core update. None of these are wrong choices; they’re trade-offs, and the right one depends more on how much time you have to configure it than on any meaningful gap in what they can eventually do.
A quick accessibility check before you publish
Testimonial sliders are a common place for accessibility to get overlooked, mostly because the default behavior of a lot of carousel scripts is to auto-advance on a timer, which is genuinely disruptive for anyone using a screen reader or trying to read at their own pace, the content changes out from under them mid-read. If the plugin you pick includes an autoplay option, check that it can be paused or disabled, and ideally that it stops automatically once a user interacts with it. Beyond that, confirm that photos attached to testimonials have meaningful alt text rather than a blank attribute or the filename dumped in as a placeholder, and that slider navigation, next and previous controls specifically, can be reached and activated with a keyboard alone, not just a mouse or a touchscreen swipe. None of this takes long to verify once a plugin is installed, but it’s the kind of thing that’s easy to skip when you’re focused on how the section looks rather than how it behaves for someone not using a mouse.
