testymo.

Integrations  ★  Carrd

Testimonials on Carrd, in one Embed element

Carrd takes the tag in an Embed element and renders it inline, exactly where the element sits. Two things to know before you paste: Embeds need the Pro Standard plan — 19 dollars a year, not a month — and the builder shows nothing at all. The widget only exists on the published site.

Where the tag goes
An Embed element with Type set to Code and Style set to Inline, dragged to where the testimonial section belongs.
Plan needed
Pro Standard ($19/year) or Pro Plus. Not the free plan, not Pro Lite — and not the 7-day Pro trial, which does not include Embeds.

01 Where the tag goes in the Carrd builder

Carrd calls it the Embed element, and describes it as the way to “insert custom HTML, CSS, and even Javascript code practically anywhere on a site”. Carrd also has a separate Widget element — that one is a fixed menu of payment and form services, so it is not the one you want. Embed is.

  1. Click Add Element — the + icon in the menu bar, top right — and click Embed.
  2. Set Type to Code and paste the script tag into the Code field.
  3. Leave Style on Inline, which inserts your code “exactly where the embed appears on the site (just like any other element)”. The other option, Hidden, files the code away in the page’s head or body ends, where a widget has no place to render.
  4. New elements land at the end of the site, so drag the Embed to where the testimonial section belongs — a green bar marks where it will drop.
  5. Publish.
Carrd's builder menu bar, with the + Add Element icon as its first control
The builder’s menu bar — Add Element is the +, first in the row. Screenshot from Carrd’s own builder overview.

02 Which Carrd plans can run it

Both of Carrd’s embed documentation pages carry the same banner: “Requires Pro Standard or higher.” And Pro Standard’s own feature list names the case exactly: “Embeds — Directly embed your own code (including script tags) as well as external content.”

  • Free and Pro Lite ($9/year) — no Embeds. There is no workaround at the widget end; the platform will not publish the element.
  • Pro Standard ($19/year) — Embeds included. Carrd’s docs call it “by far the most popular Pro plan”, and the prices really are per year.
  • Pro Plus ($49/year) — Embeds included.

One trap worth naming: the 7-day Pro trial does not include Embeds. Carrd’s trial covers “a subset” of Pro features and Embeds is not on the list — so you cannot test the tag on a trial account. The plan has to be live before the element will publish.

Sources

Plan names and menu labels are the platform’s to change. If what you see differs from what is written here, the linked page is the authority — and tell us so this page gets fixed.

03 When the widget doesn’t show up

The builder shows nothing where the Embed sits.
Expected, and documented in exactly these words: “the embed element will not actually output anything in the builder so you’ll need to publish the site to see it in action.” Publish first; judge from the live page only.
Published, and still nothing.
Check the plan before the code: Free, Pro Lite and trial sites do not publish Embeds. If the plan is Pro Standard or above and the section is still empty, confirm the tag survived the paste intact — the whole line, both angle brackets, one src.
The whole site stopped loading after you added custom code.
Carrd is unusual here and says so itself: make sure embedded code is “100% valid Javascript as even a simple syntax error will break the site and prevent it from loading”. A mangled paste is enough. Re-paste the tag as one clean line — and if the site carries other embeds, suspect those too before anything else.
You republished, and the live site looks unchanged.
Usually your own browser cache. Carrd’s troubleshooting answer is a hard refresh — Ctrl+Shift+R, or Cmd+Shift+R on a Mac. The widget itself cannot go stale: it is served fresh on every page load, so a newly approved testimonial appears without any republish at all.

04 What the one tag actually does

The line you paste is a plain external script. There is no plugin, no app to install, no account to connect on the Carrd side, and nothing to configure in the editor afterwards. Testymo generates the tag when you create a widget; the address in it is your widget’s own, and this is the live demo one:

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

The server builds that script per request: the rendering code and your approved testimonials arrive together in one response, so the page makes one request and no follow-up fetches. The demo tag printed above weighs 16.7 KB of JavaScript, about 6 KB over the wire. That figure covers the demo widget's eight quotes. The testimonials ride inside the script rather than arriving in a second request, so a wall carrying thirty of them weighs thirty quotes' worth of text — measure the embed you paste in, not this one. The page-speed guide has the method behind that number, and the case for measuring whatever you embed rather than trusting the category.

It renders into an open shadow root at the exact spot the tag sits, which makes the styling isolation work in both directions: your Carrd theme cannot restyle the widget by accident, and the widget’s CSS cannot leak into your page. It sets no cookies, calls no third party, and reads nothing about your visitors. When you approve a new testimonial, it appears on the next page load — you never touch the site again.

05 The widget, running on this page

Everything below this line was drawn by that one script tag — the same file, on the same terms, that you would paste into Carrd. Eight approved testimonials in the wall design, rendered as a free plan renders them, footer link and all.

06 Where to go next

An embed script is one of three ways to put testimonials on a site, and it is not always the right one — a handful of quotes that will not change for a year are better hand-coded. The full guide to adding testimonials to a website prices all three routes: setup, upkeep, and page weight. Once you know the quotes are arriving, the layout patterns guide covers which shape to show them in, and getting permission first covers the part most sites skip.

The same tag, in another editor