How many widgets to build
One Testimonial Widget or Several
The first widget is easy: pick some testimonials, pick a layout, paste the code. The second question arrives a week later, when the pricing page wants different quotes from the homepage. Build one widget and reuse it everywhere, and every page says the same thing. Build one per page, and you have twenty selections to keep current and may run past your plan’s allowance. Five questions below point you to a structure that fits your site, then the rest of the page shows how to run it.
- Four widget structures, from one to many
- Weighs your pages, products and upkeep time
- Respects the widget allowance on your plan
Decision helper
How many testimonial widgets does your site need?
Answer for the whole site, not one page.
Your answers stay in this browser tab and are not sent anywhere.
The problem, solved
Widget sprawl and widget sameness, and how to avoid both
- Problem 1
We hit our widget limit
A widget was made for every landing page and campaign, and now a new page has no slot left.
How StoryProof solves it
Widgets are counted per workspace: Widgets per workspace: Free 1, Starter 5, Pro unlimited. A small "Powered by StoryProof" badge shows until Pro. Reuse one widget on every page of the same type instead of building one per page.
- Problem 2
Every page shows the same three quotes
One widget everywhere means a visitor reads identical proof on the homepage, the pricing page and the contact form.
How StoryProof solves it
Each widget carries its own choice of approved testimonials, so a pricing widget and a homepage widget can show different quotes from the same library.
- Problem 3
Updating ten widgets takes all afternoon
Each new testimonial has to be added to several selections by hand, so in practice it goes nowhere.
How StoryProof solves it
Fewer widgets, reused, cut the work. The same div pasted on five pages shows one widget, so one change to its selection reaches all five.
- Problem 4
Picking quotes for each product is slow
Scrolling the full library to find the five quotes about one product is why segment widgets go stale.
How StoryProof solves it
Tag testimonials by product or industry as they arrive. Tags are on every plan, so filling a segment widget becomes picking from a short list.
- Problem 5
Two widgets on one page look heavy
A wall at the top and a carousel at the bottom of the same page doubles the script and crowds the layout.
How StoryProof solves it
A single embed.js fills every StoryProof widget on the page, and the layouts range from walls down to compact badges, so a second widget can be small and cost no extra script.
The four structures side by side
In StoryProof
Set up the structure you chose
- 1
Group the pages
Write each page next to the widget it will use. Pages that answer the same doubt share a widget.
- 2
Check the allowance
Count the widgets your grouping needs and compare it with your plan’s widget allowance before building anything.
- 3
Tag, then select
Tag testimonials by the page type or segment they support, then choose the matching approved testimonials for each widget.
- 4
Embed once per page, reuse across pages
Paste each widget’s div on every page in its group, and load embed.js once per page in a shared footer.
- 5
Name widgets after their job
Call them “Pricing proof” or “Healthcare segment”, not “Widget 3”. Whoever adds the next testimonial needs to know where it goes.
What happens next: Each time a testimonial is approved, decide which widget it belongs in. That single habit keeps any structure from going stale.
Before you start
Things to weigh before you decide
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
The allowance is per workspace
Widgets counted against your plan include test and forgotten ones. Free up slots before planning a structure that needs more.
- 02
Selections are kept by hand
You choose the testimonials for each widget. More widgets means more selections to revisit as new testimonials arrive.
- 03
This helper does not see your traffic
It weighs structure and effort. Whether a dedicated pricing widget persuades more than a shared one is something only a test on your pages can show.
- 04
A shared widget is the same everywhere
Reusing one widget means one layout and one selection on every page it sits on. If a page needs a different look, it needs its own widget.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can I put the same widget on more than one page?
Yes. The embed is a div with the widget id plus the embed.js script, so pasting that div on several pages shows the same widget on each.
Do two widgets on one page need two scripts?
No. Load embed.js once on the page and it fills every StoryProof widget div there.
How many widgets does my plan include?
Widgets per workspace: Free 1, Starter 5, Pro unlimited. A small "Powered by StoryProof" badge shows until Pro. The pricing page has the current numbers.
Should every landing page get its own widget?
Only when the landing page speaks to a different buyer. Campaign pages for the same offer can share one widget, which saves slots and upkeep.
Still have a question? Ask the StoryProof team or book a demo.
Build the widgets your site needs
Start with one, add more as your pages ask for different proof.
Last updated 2026-11-12.