Blank space where the proof should be
Testimonial Widget Not Showing Troubleshooting
You pasted the embed code, published the page and got an empty gap. Almost every blank widget comes down to one of five things: half the code never reached the page, the script was stopped from running, the id points at the wrong widget, the widget has nothing approved in it, or the page itself is hiding the box. The checklist below walks through them in the order that finds the cause fastest, on any website builder.
- Works on any builder or hand coded site
- Ordered from the quickest check to the slowest
- Each tick rules out one cause
The problem, solved
Six reasons a StoryProof widget stays blank, and the fix for each
Start with the one that matches what you see. The checklist further down covers them in order if you are not sure.
Situation 1 of 6
There is a gap but nothing loads
Some editors keep the div and quietly drop the script tag, or turn the whole snippet into escaped text when it lands in a normal text block.
How StoryProof solves it
The embed is two parts only: a div carrying your widget id and the async embed.js script from app.storyproof.io. Open the published page source and confirm both arrived exactly as copied.
Situation 2 of 6
It works on one page, not another
The script was pasted into one page, or into a template that only some pages use, so the other pages get the div with nothing to fill it.
How StoryProof solves it
Load embed.js once per page from somewhere every page shares, such as the site footer. One copy fills every StoryProof div on that page, so each page then needs only its div.
Situation 3 of 6
The widget loads but shows nothing
The frame or heading appears and the testimonials do not. Usually the widget simply has no approved testimonials picked for it yet.
How StoryProof solves it
Nothing goes public until you approve it, and each widget shows only the approved testimonials you chose for it. Approve at least one and add it to this widget.
Situation 4 of 6
My colleague sees it, I do not
A content blocker in one browser, or a strict company network, can stop third party scripts for one person while everyone else sees the widget.
How StoryProof solves it
Because the script comes from app.storyproof.io, test in a private window with extensions off and on a phone using mobile data. If it appears there, the page is fine and the block is local.
Situation 5 of 6
Our security headers block the script
A Content Security Policy that lists allowed script hosts will refuse any host not on the list, and the browser console says so in red.
How StoryProof solves it
Add https://app.storyproof.io to script-src and connect-src. If the console then names another blocked StoryProof request, allow that host in the matching directive too.
Situation 6 of 6
We pasted the wrong widget id
The id was copied from an old test widget, or two snippets were mixed up, so the page shows a different set of quotes or none.
How StoryProof solves it
The id inside the div decides which widget appears, and each widget carries its own choice of testimonials. Copy the snippet again from the widget you meant and compare the id character by character.
Diagnosis checklist
Find out why your testimonial widget is blank
Open the published page, not the editor preview, in a desktop browser. Work down the list and stop at the first item you cannot tick: that is almost always the cause.
Your ticks stay in this browser tab and are not sent anywhere.
What you see, and where to look first
In StoryProof
Get the widget showing again
- 1
Copy a fresh snippet
Take the embed code again from the widget you intend to show. Pasting a fresh copy rules out a mangled quote mark or a truncated id in one go.
- 2
Put each part where it belongs
Place the div in an HTML or code block exactly where the testimonials should appear. Put embed.js once in a place every page loads, such as the footer code area.
- 3
Give the widget something to show
Approve the testimonials you want public and choose them for this widget. A widget with no approved selection has nothing to display.
- 4
Publish, clear caches, test clean
Publish the site, purge any cache your host or CDN keeps, then load the page in a private window and on a phone before you decide it is still broken.
What happens next: If one page is fixed, check every other page that should carry a widget. The same missing footer script or stale cache usually affects them all.
Before you start
What this checklist cannot do
It cannot see your site
We have no view of your page source, headers or console. The checklist narrows the cause down; the fix still happens in your builder or server settings.
Visitors’ blockers are out of your hands
If a visitor’s extension blocks third party scripts, the widget will not show for them whatever you change. A plain text link to your Wall of Love still works for those visitors.
No script means no widget
The div is filled by embed.js in the visitor’s browser. A browser with JavaScript turned off sees only the empty div.
Security headers may need your developer
Content Security Policy is often set by a host, a plugin or a server config you cannot edit from the page builder. Send the exact console error to whoever manages it.
Builder rules come first
Some website builders limit where scripts may run or reserve custom code for certain plans. Check your platform’s own help pages if the code will not save at all.
FAQ
Questions people ask
Short answers to what usually comes up next.
Why does the widget show in the editor but not on the live page?
Editors often render a preview differently from the published site. Either the change has not been published, a cache is still serving the old page, or the live template does not load embed.js. Check the published page source, not the editor.
Can I paste the script once for several widgets on the same page?
Yes. One copy of embed.js fills every StoryProof widget div on that page, so a page with three widgets needs three divs and a single script.
Does an ad blocker stop the widget for my visitors?
It can, for visitors whose blocker treats third party scripts as unwanted. You cannot switch that off for them. Test in a clean private window to confirm the page itself works.
What should I send to support if nothing on the list helps?
The page URL, which checklist items you could not tick, and a copy of any red console error. That is usually enough to find the cause without a call.
The widget shows old testimonials. Is that the same problem?
No, that is a selection or caching question rather than a blank widget. Check which approved testimonials are chosen for the widget, then clear any page cache your site keeps.
Still have a question? Ask the StoryProof team or book a demo.
Two lines of code and nothing hidden
StoryProof widgets are a div and one async script, so there are only a few places a problem can hide.