How to Add Testimonials to a Framer Website
Framer is a no-code site builder, but a testimonial wall still has to get onto the canvas somehow. There are two supported routes: paste a small React code component that loads the wall, or install the marketplace plugin and drop the widget in. The first gives you the snippet; the second keeps you inside the Framer editor. Both start from the same place — a published testimonial wall.
Before you touch Framer
Both methods assume a testimonial wall already exists and is published. In the testimonial dashboard, create the wall, arrange text, video and audio testimonials the way you want them to appear, then hit Publish Widget. The embed code option only appears after publishing, so an unpublished wall is the most common reason a step looks missing. If you have no testimonials yet, you can import them from the available sources or send customers a personalized collection link and gather them from scratch.
Method 1: Paste the embed as a Framer code component
This route is for anyone comfortable dropping a short React component into a Framer project and letting a script pull the wall in, rather than placing a plugin element on the canvas. Work through the steps in the order the editor expects them, and keep the supplied snippet intact apart from the one value you are meant to change. The full component is a fixed technical literal: import the React hooks, define a component that writes the embed container into a ref, remove any previously injected copy of the loader script, then append the loader script with defer set and render a full-width wrapper. Treat that code as supplied and do not retype it from memory; copy it from the dashboard's Get Embed Code panel so the script source, the container class, the data-format value and the width style all stay exactly as issued. The only edit is the wall address: the snippet arrives with a placeholder in the data-src attribute, and you replace that placeholder with the URL of the wall you published, so the component loads your testimonials instead of the demo. Leave data-format at its default grid unless you deliberately want another layout, and leave the script source and the 100% width style alone. Then, in Framer, open a template-based project or a blank canvas, use the Framer menu at the top left to reach Code → Create Code Component, give the component a name and confirm with Create. Paste the snippet into the code editor that appears, make the data-src substitution, and bring the finished component onto the canvas from the assets panel, positioning it where the testimonials belong. The right-hand preview should show the testimonials once the component is placed; publishing the page is the separate final step that makes them visible to visitors.
What the embed snippet actually controls
The code component is compact, and every attribute in it does one specific thing. Knowing which values you are meant to edit — and which you should leave untouched — prevents most of the blank-preview problems people hit on the first attempt. The table below maps each part of the supplied snippet to its role and to the change, if any, that belongs there.
Method 2: Use the marketplace plugin
The plugin route is for people who would rather position the wall by dragging than maintain a code component. It still needs a published wall, and the account link is finished on the testimonial service's own authorization screen rather than inside Framer. Follow the sequence below in order, matching the interface labels as they appear in your version; if a label differs, use the closest matching control and check the plugin's own documentation before going further. Nothing here depends on a particular plan tier or on any promise about cost, support or trial length — those terms belong to the respective providers and should be confirmed on their own pages before you commit a project to this workflow. The sequence assumes one Framer project and one testimonial wall; with several, repeat the selection step per page and note which wall was published for which page so the panel choice stays unambiguous. Before starting, confirm the wall is already published, since the panel only offers walls that have been through that step, and confirm you are signed in to the project you actually want to edit rather than a duplicate or staging copy. On a shared team project, check with the account owner that connecting an external service is permitted, because authorization grants the plugin access on behalf of the account rather than the individual editor. The ordered steps are: 1. Open the plugin's marketplace listing and click Open Plugin in the top right corner. 2. When prompted, select the Framer project where the testimonials should appear. 3. Inside the Framer editor, click the Connect button to link the testimonial service. 4. Complete the authorization on the service's own screen, approving access for your account. 5. In the popup at the top right, pick the specific wall whose widget you created and published, then click Add to page. 6. Drag and drop the testimonial widget box to the spot on the page where the testimonials should sit. 7. In the width settings, choose Fill so the widget spans the full width of the Framer page. 8. Check the preview, then publish the page to make the result live. The preview is the quickest way to catch a wrong wall or a width that does not span the page. If something looks off after publishing, check three things in this order: a wall that was edited but not re-published, a widget sitting inside a container that constrains its width, and a page published before the widget was added. Avoid re-running the authorization step unless the panel genuinely shows no walls, since repeating it rarely fixes a layout problem and can muddy which connection is active.
Which method fits your project
Use the embed when you want the wall loaded by a script you control and you are fine editing a code component. Use the plugin when you want the widget placed visually and do not want to touch code. Both need the wall published first, and both end with a page publish. If you are handing the site to a non-technical editor later, the plugin leaves them a draggable element; the embed leaves them a component they can move but not easily re-point without editing the data-src value.
When the wall does not show up
Three failures look alike but need different fixes. If the preview shows nothing and the dashboard offers no embed option, the wall was never published — publish it, then reopen Get Embed Code. If the preview is blank or shows the wrong content, the data-src attribute still holds the placeholder value or points at a different wall URL than the one you published; correct it to your published wall address. If the plugin panel lists no walls, either the account authorization did not complete or the wall you want was not published before you opened the panel; finish the authorization or publish the wall, then reopen the panel.
Worked example of the substitution
Say your published wall lives at a URL ending in your-wall-slug. The snippet arrives with a placeholder value in the data-src attribute. After the edit, that attribute holds your real wall address in place of the placeholder, so the component loads your testimonials rather than the demo. Leave data-format at grid unless you want a different layout, and keep the script source and the width style exactly as supplied. Then drag the component onto the canvas and check the right-hand preview before publishing the page.
| Part of snippet | What it does | What to change |
|---|---|---|
| data-src | Points the embed at a specific testimonial wall | Replace the placeholder with your published wall URL |
| data-format | Sets the display layout | Change only if you want a layout other than the default grid |
| style width | Controls the embed width | Keep 100% unless your layout needs otherwise |
| script src | Loads the embed script | Leave as supplied |
| script defer | Defers script execution | Leave as supplied |
Field names and values are taken from the supplied snippet; no additional options are implied.
| Step | Code-component embed | Marketplace plugin |
|---|---|---|
| Prerequisite | Published wall with embed code copied | Published wall selected in the plugin panel |
| Framer entry point | Code → Create Code Component | Open Plugin from the marketplace listing |
| Account link | Not required beyond the wall URL | Connect button plus account authorization |
| Placement | Drag the code component onto the canvas | Drag the widget box and set width to Fill |
| Verification | Right-hand preview shows testimonials | Preview shows the widget before publish |
Comparison reflects the two documented workflows only; it does not rank them.
Frequently asked questions
Do I need to publish the testimonial wall before adding it to Framer?
Yes. The Get Embed Code option appears after the wall is published, and the plugin panel asks you to select a wall whose widget was published. Publishing the wall is separate from publishing the Framer page.
Can I add testimonials to Framer without writing code?
The plugin route avoids editing code: you open the plugin, authorize the account, select the wall, and drag the widget onto the page. The code-component route requires pasting a supplied snippet and changing one attribute value.
What URL goes into data-src?
The URL of the testimonial wall you published. The snippet ships with a placeholder value, and the wall will not render correctly until that placeholder is replaced with your wall address.
How wide should the widget be in Framer?
The plugin workflow recommends setting the widget width to Fill so it occupies the full width of the page. The embed snippet uses a 100% width style by default.