testymo.

Integrations

One tag, fourteen editors

A Testymo widget is a single script tag, and it is the same single script tag on every platform — there is no plugin, no app store listing and no account to connect. What changes from one site builder to the next is only what that builder calls its custom-code box, where it hides it, and which of its plans will execute a script at all.

This is the whole install, on all fourteen. The address is your widget’s own; the line below is the live demo one, and it renders on each of the pages below.

<script src="https://testymo.com/w/demo.js" async></script>

01 Pick your platform

Platform What the box is called Which plans run it
WordPress Custom HTML block No plan gate when self-hosted — an Administrator or Editor account on a single-site install. WordPress.com needs a paid plan with hosting features activated.
Webflow Code Embed element A Core, Growth, Agency or Freelancer Workspace, or an active Site plan. The free Starter plan runs no custom code at all.
Wix Embed HTML element No documented plan gate on the element itself. The separate site-wide Custom Code route needs a published site with a connected domain, which needs a paid plan.
Squarespace Code block Core, Plus, Advanced, Business, Commerce Basic or Commerce Advanced. Lower plans take HTML and CSS in a Code block but will not run JavaScript.
Shopify Custom Liquid section Every standard plan — the real check is the theme offering the section, which Shopify's own free themes all do. The legacy Starter plan cannot customize themes.
Framer Embed component No documented plan requirement. Paid plans buy the custom domain and branding removal, not script execution.
Ghost HTML card None documented — no plan requirement on Ghost(Pro), and none self-hosted.
Carrd Embed element Pro Standard ($19/year) or Pro Plus. Not the free plan, not Pro Lite — and not the Pro trial, which excludes Embeds.
Notion None — the embed block takes a URL only No Notion plan runs custom code. What works: Super's custom code on its Personal plan ($16/month) and up, or an embed block showing a page you host.
Bubble HTML element No documented gate on the element. Going live at all is the Starter plan's job — the Free plan is for development.
Kajabi Custom Code block Every plan — no documented gate on the block. Only the theme-template code editor is Pro-only, and a widget embed never touches it.
Teachable Custom HTML block No plan gate on the block, but new schools must ask Teachable Support to enable it. Site-wide Code Snippets need Builder or above — and are head-only.
Podia None per-page — the Embed tool takes URLs only A script tag fits only the site-wide Third-party code field (paid plans), injected before the closing body tag. The native Testimonials section covers in-page proof.
Skool None — images and links only No plan runs custom code — Hobby and Pro differ on the transaction fee, not features. What works: images on the About page, and the widget on the site you link out to.

Every gate above comes from the platform’s own documentation, quoted and linked on each page. Plan names and menu labels are theirs to change; if what you see differs, the linked page is the authority.

02 Why the platform barely matters

What that one line does is the same story on every platform — one request and no follow-up fetches, a shadow root that keeps your theme’s styling and the widget’s on their own sides of the boundary, no cookies, no third party, and a newly approved testimonial appearing on the next page load with no edit anywhere. Rather than tell it ten times over, each walkthrough tells it once: the WordPress page has it in full, and the others say the same thing in their own editor’s vocabulary.

Which is the honest reason these pages are nearly the same page. The install does not vary; only the editor around it does. So what each one is actually for is the narrow part — what that builder calls its custom-code box, where it keeps it, and which of its plans will execute a script at all.

Two rows above deserve their asterisk said out loud: Notion and Skool cannot run the tag at all — no plan, no setting. Their pages do not pretend otherwise; each covers the routes that genuinely work instead.

03 Somewhere else entirely

If your site is hand-built, or runs on a platform not listed above, the answer is the same line pasted wherever your HTML lives — there is nothing platform-specific in it to adapt. And an embed is not automatically the right route: the full guide to adding testimonials to a website prices all three, including hand-coding the section yourself, which is the better call for a handful of quotes that will not change for a year.