Loading...
Loading...
One review at a time, advancing on its own. The layout for a homepage section where a grid would take over the page.
Live slider preview — this is the actual widget, not a screenshot
Sample reviews. Connect your own business in the configurator to preview with your real ones.
That trade is the whole decision. A carousel occupies the height of one review card no matter how many reviews you have, which is why it fits into a homepage between two other sections without pushing everything down the page.
The cost is that a visitor sees one review unless they wait or click. Most do neither. So a carousel shows your best review to everyone and your other reviews to almost nobody, which is fine if the first one is strong and a waste if your case rests on volume.
The version people get wrong is setting the auto-advance too fast. If it moves before an average reader finishes the card, it is decoration rather than social proof.
The most common and the most defensible. It gives a visitor proof early without spending the whole fold on it.
Catches people who scrolled the whole page and are deciding whether to call.
A carousel handles a 300px column better than a grid, which collapses to one column anyway and then just becomes a long list.
A continuously moving band. Ambient proof, not something people read closely.
Several reviews visible at once. The safe default and usually the right one.
A vertical stack, full width each. Best for long reviews and narrow columns.
Variable-height cards packed together. For reviews of very different lengths.
A compact rating badge. Goes on every page; opens the full reviews on click.
Nothing. They are two words for the same layout and both are searched roughly as often. The configurator calls it Slider.
Slow enough to finish reading the card, which for a typical review is around seven seconds. The default is set there. Faster looks lively and communicates nothing.
The reviews in a BlooTrue widget load in the iframe with an indexifembedded directive, so the visible slide is not a ranking problem in the way a hidden-content carousel would be. If you want the text itself on your page for crawlers, inline the content endpoint server-side instead.
Yes. Touch dragging works and the pagination dots stay tappable.
Use the grid layout with one row instead. That gives you several cards visible with the same horizontal paging behaviour.