Squarespace Testimonial Slider: Testimonial Carousel and Slider Plugin Options for 7.1 and 7.0

This is the fact the whole category is built on and almost nobody states plainly. Squarespace's own guide to auto layouts describes three options for a list section: a simple list, a banner slideshow, and a carousel. The carousel entry reads "displays items and their elements in a row from left to right in a rotating carousel." Rotating there describes the shape, not the behavior. There is no autoplay control, no interval setting and no auto scroll toggle documented for any of the three layouts.

So when somebody searches for a Squarespace testimonial slider, what they usually mean is a block of quotes that advances on its own, and that is not a setting anywhere in Squarespace. The tutorials that deliver it all work the same way underneath: a script runs on a timer and programmatically clicks the carousel's own navigation arrow. That is why those tutorials tell you to turn the arrows on first and leave them on. The arrows are the mechanism, not decoration.

One detail from the same Squarespace guide that catches designers out: "if you disable the navigation arrows, visitors on a computer will click and drag to scroll through items, but the arrows will always display on mobile devices." You cannot hide the arrows on phones. If your auto scroll script depends on them, that is convenient. If your design does not want them, that is a constraint you find out about after the build. Auto layouts are a 7.1 feature; the Squarespace guide states plainly that it is for version 7.1, and 7.0 sites are told to build rows and columns with blocks instead.

Two honest notes before the rest of the page. If you have four testimonials that will never change and you are happy for a visitor to click through them, the native carousel is free, it is already in your account, and you should not pay anybody anything. And $25 once for a plugin that rotates is genuinely good value against a subscription if display is the only problem you have. The rest of this page is about the problems that survive both of those answers.

Most write ups of this get the Squarespace plan requirement slightly wrong, usually by copying an older article. The current position from Squarespace's own code block documentation is more specific and more useful, because it splits the feature in half.

Squarespace states: "On all plans, code blocks support plain text, HTML, Markdown, and CSS code surrounded by style tags." Then, separately: "Adding JavaScript or iframes to code blocks is available in the Core, Plus, Advanced, and some legacy billing plans." Legacy Business, Commerce Basic and Commerce Advanced plans sit in that second group.

Read those two sentences against the routes above and the picture is clean. A static block of quotes you style with CSS runs on any Squarespace plan, including the cheapest. Anything that moves, loads, or talks to another service is JavaScript, and JavaScript is gated. That covers the auto scroll script, the summary block trick, most bought plugins, and any third party embed including ours. There is no route to a self advancing Squarespace testimonial slider on a plan below Core.

The last row matters if you were planning to proxy a review API yourself from inside Squarespace. You cannot. That has to live somewhere else, which is one of the reasons the widget market for this platform exists at all. The same constraint shapes what is possible on the wider Squarespace testimonials page.

The first row of this table is responsible for more support tickets in this category than everything below it combined, and it is not a bug. It is documented Squarespace behavior that reads exactly like a broken widget.

The pattern is worth naming, because it decides which route you should pick. Three of those six rows are not faults in the slider at all. They are Squarespace behaving as documented in a way that looks like a fault. The two that are real faults, class names changing after a release and scripts colliding, both belong to the free copy and paste route, and both come back. A self contained embed does not target Squarespace's internal class names, so a Squarespace update does not break it.

The Squarespace plugin market is unusual and mostly admirable. These are small independent developers selling a file and a snippet for a one time fee, and the prices are honest. Ghost Plugins lists the Bebe Testimonial Slider at $25.00 with a Multi-Site License, stating it "works with Squarespace 7.0 (Brine) and 7.1" and "requires Core/Business Plan or Higher." That is a fair deal for a designer who builds several client sites a year.

There is a risk in the model that nobody selling into it will write about, and it is easy to demonstrate rather than assert. On September 6, 2026 the SQSPThemes product page for their Testimonial Slider plugin returns HTTP 404, while third party roundups published this year still list it by name and quote its price. The plugins index on the same domain loads normally, so the site is fine. The product is simply not there any more.

Nothing dramatic follows from that on day one. Code you already installed keeps running. What you lose is the update path: when Squarespace changes a class name or ships a layout revision, there is no longer a developer shipping a fix, and the snippet in your code injection is now yours to maintain. For a designer with fifteen client sites carrying the same discontinued plugin, that is fifteen sites to revisit at once, on a schedule Squarespace chooses.

The free tutorial route has the same exposure in a sharper form, because there was never a support relationship to begin with. The summary block method popularized by Will Myers is genuinely clever and it is free, and it requires jQuery to be installed separately, which is one more moving part that has to keep being present. The author is candid about the underlying gap: "Squarespace does have a testimonials block, they don't have a testimonials slider block."

None of that makes a $25 plugin a bad purchase. It makes it a display purchase with a maintenance tail, which is the right way to think about it when you compare it against a subscription that also does the collecting.

Everything above is about display. The reason a Squarespace site still has the same three testimonials it launched with is the other half of the job, and no slider on any route touches it.

Start with duplication. A quote typed into a 7.1 list section belongs to that section. Put the same testimonial on the home page, the services page and a sales page and you have typed it three times into three independent places. Fix a typo and that is three edits. Swap in a better testimonial and that is three edits. Nothing in Squarespace tells you where else that quote is used, because as far as Squarespace is concerned it is three unrelated pieces of page copy.

Then removal, which nobody plans for. A client can ask you to stop using their testimonial. People change jobs, sell the business, or simply change their mind, and an endorsement you no longer have permission to run needs to come down in one move rather than from memory across a site you built two years ago. If the quote also went into a bought slider on a client's site, it is in a fourth place.

There is a quieter one underneath the retyping. You have the client email open and a slide to fill. The quote runs long for the card, so you trim it. A qualifying clause muddies the point, so it goes. Two good sentences from different paragraphs read better joined, so you join them. Then you put quotation marks around the result, because that is what a testimonial looks like. The Federal Trade Commission Endorsement Guides at 16 CFR 255.1(b) say an endorsement may not be presented out of context or reworded so as to distort in any way the endorser's opinion or experience, and that an advertisement need not use the endorser's exact words unless the advertisement represents that it is presenting the endorser's exact words, such as through the use of quotation marks. The quotation marks raise the standard you are held to, and once you have retyped the quote there is no record anywhere of what the client originally wrote.

Keeping the original submission with a timestamp and the consent attached is not a legal service and it guarantees nothing. It means taking a testimonial down is one action instead of an archaeology exercise across your Squarespace pages. Which edits are safe is worked through in the testimonial release form guide, and the federal rules generally are in FTC testimonial rules.

A slider is a space saving device. It trades visibility for vertical space, and that trade is good in some places on a Squarespace site and bad in others.

It is good in a tight homepage strip, where you have one band of vertical space and a lot of quotes, and the point being made is that many people are happy rather than any particular person's story. It is good in a footer band. It is good on a services page where the testimonial is a reassurance rather than the argument.

It is bad on a pricing or booking page. Somebody on that page is actively hesitating, and a rotating carousel hides most of your proof behind a control that almost nobody clicks. Squarespace's own guidance makes it worse on desktop: with arrows disabled, visitors on a computer click and drag to scroll, which is a gesture a hesitating buyer will not discover. On the page where the decision happens, a full wall of testimonials does more work, because the quantity is itself the argument.

Length is the other lever. A card in a carousel holds roughly twenty five to forty words before it starts scrolling inside itself on a phone, which is why the best slider testimonials are edited down to one specific claim rather than a paragraph. What to cut and what to keep is covered in how long a testimonial should be, and where each format belongs across a site is in how to display testimonials on your website.

If Squarespace is one of several platforms you build on, the same embed renders inside a Divi code module, an Elementor HTML widget, a Webflow embed and a Wix HTML element, which means one library of approved testimonials across every client site instead of a separate copy retyped into each builder. The platform specific versions are on Divi testimonial slider, Elementor testimonial widget, Webflow testimonials and Wix testimonials. The collection half, which is the part none of the slider routes solve, is on automated testimonial collection.