Plugin fatigue is real
A dedicated testimonials plugin adds another item to your update queue and another possible conflict with your page builder. An embed avoids the extra plugin entirely — it's just HTML and a script tag.
WordPress guide
How to add testimonials to WordPress
WordPress runs on plugins, but every extra plugin is one more thing that breaks after a core update. Adding testimonials doesn't need one: a Custom HTML block on any page, or a snippet in your theme's footer, is enough to show a live wall or widget that updates itself whenever a new testimonial comes in. Here's exactly where it goes and how to keep it from fighting your theme's CSS.
Free plan covers 10 testimonials and a badge widget — no credit card.
Why WordPress sites need this handled deliberately
WordPress themes vary wildly, so 'just add testimonials' means something different on a Divi landing page than on a plain Twenty Twenty-Four blog theme.
Themes fight inherited styles
Many WordPress themes apply global blockquote or paragraph styles that clash with widget layouts. A sandboxed embed keeps your testimonials looking the same regardless of theme CSS.
Static text pages don't convert
A lot of WordPress sites still have testimonials as hardcoded text pasted into a page years ago. A live wall shows freshness — visitors can tell when the last one is dated 2019.
Local businesses need proof above the fold
For a plumber or dentist site built on WordPress, testimonials near the booking button matter more than a dedicated testimonials page nobody clicks.
Adding the embed, step by step
Same method whether you're on the block editor, a classic editor install, or a page-builder theme that still uses core blocks for content areas.
1. Create your wall or widget in Plausa
Pick a variant — carousel, grid, or badge — set your brand color, and copy the embed snippet from the Plausa dashboard.
2. Open the page in the block editor
Edit the page or post where testimonials should appear (often the homepage or a services page), then add a block by clicking the + icon.
3. Insert a Custom HTML block
Search for 'Custom HTML' in the block picker. Paste the Plausa snippet directly into it — WordPress won't strip the script tag from this block type the way it does from a Paragraph block.
4. Or drop it in the theme footer for site-wide badges
For a small trust badge on every page, go to Appearance → Theme File Editor (or your theme's Customizer → Custom Code panel if using a builder theme) and paste the snippet just before the closing </body> tag.
5. Preview before publishing
Use the block editor's Preview button on both desktop and mobile widths — carousels can overflow narrow sidebars on some themes.
6. Publish and check page speed
The script loads async, so it won't block WordPress's render, but run PageSpeed Insights once to confirm nothing else on the page compounds load time.
The embed code for WordPress
This is the exact snippet the Custom HTML block accepts. Swap the slug for your own wall's identifier and pick a variant.
<div data-plausa="my-wall" data-variant="grid" data-lang="en"></div>
<script src="https://getplausa.com/plausa-widget.js" async></script>Works in the Custom HTML block, in a Custom HTML widget under Appearance → Widgets, or pasted into the theme footer.
Iframe fallback for locked-down setups
Some managed WordPress hosts strip inline scripts from certain block types for security. If your embed doesn't render, use the iframe version instead — it needs no script tag at all.
<iframe src="https://getplausa.com/embed/my-wall?variant=carousel&lang=en" title="Plausa" style="width:100%;border:0;height:320px" loading="lazy"></iframe>What it looks like on a WordPress page
A grid or carousel of short, real quotes reads naturally between a WordPress site's usual sections — services, pricing, then proof.
Called them for a leak on a Sunday and someone actually picked up. Fixed within two hours, fair price.
Our old site took forever to update. The new WordPress build they delivered lets our team edit it ourselves now.
The course platform migration was painless — everything, including the old testimonials, carried over cleanly.
Illustrative examples — not real companies.
Common WordPress mistakes
- Pasting the snippet into a Paragraph block instead of a Custom HTML block — WordPress escapes the script tags and nothing renders.
- Adding a testimonials plugin on top of an embed, causing duplicate widgets or CSS conflicts on the same page.
- Forgetting that some caching plugins (WP Rocket, W3 Total Cache) can defer or strip async scripts — whitelist the Plausa script domain if the widget flickers.
- Placing the widget below a heavy image slider, so it never gets scrolled to on mobile.
- Using a page builder's raw HTML widget without checking it isn't sandboxed in an iframe that blocks the script from loading.
- Leaving stale text testimonials on the same page as the new live wall, creating a confusing duplicate.
- Not testing on the actual theme's mobile breakpoint before publishing — some themes cap block width unexpectedly.
Frequently asked questions
Is there an official Plausa plugin for WordPress?
No. Plausa integrates through a small HTML/JS embed rather than a plugin, so there's nothing WordPress-specific to update after core or PHP version changes.
Will the Custom HTML block break with the Gutenberg editor?
No — the Custom HTML block is a native core block designed exactly for this: it renders raw HTML and script tags without modification.
Can I use this with Elementor or Divi instead of the block editor?
Yes, both accept an HTML widget/module that behaves the same way. If you're building the whole page in Elementor, see our dedicated Elementor guide for widget-specific placement tips.
Does the widget slow down my WordPress site?
The script loads with the async attribute, so it doesn't block the rest of the page from rendering. It's a single lightweight request.
Can I show different testimonials on different pages?
Yes — create separate walls in Plausa (or filter with tags) and use a different data-plausa slug per page.
What if my host strips inline scripts?
Use the iframe fallback instead — it doesn't rely on an inline <script> tag being present in the page's rendered HTML.
Related guides
Put testimonials on your WordPress site this afternoon
Create your wall, copy one snippet, paste it into a Custom HTML block. No plugin required.
Start for free