Skip to main content

The handoff message for whoever edits your site

Ask Your Developer to Add Testimonials

You picked the testimonials and built the widget. Now someone else has to put it on the site, and the first reply is usually a question: which page, where on it, and is there anything else to install? Fill in the builder below and send one message that answers all of it, with the code already inside, so the job takes your developer ten minutes rather than three emails.

  • The embed code written into the message for you
  • Page, position and done criteria in plain words
  • Versions for in-house, freelance and multi-page jobs
Use the free toolStart free (opens in a new tab)
New message

SubjectTestimonial widget on https://example.com/pricing by Thursday

Hi Sam,

Could you add our testimonial widget to https://example.com/pricing, directly under the plan comparison table, above the FAQ?

It is two lines of HTML, nothing to install:

<div data-storyproof-widget="your-widget-id"></div>

<script src="https://app.storyproof.io/embed.js" async></script>

4 ready-to-send versions

Free tool, no sign-upTry it below

Message builder

Write the request your developer can act on

Copy the widget id from StoryProof, fill in the page and the spot, then copy the message.

Who is doing the work
  1. Quick ticket for a colleague

    Subject: Testimonial widget on [https://example.com/pricing] by [Thursday]

    Hi [Sam],

Could you add our testimonial widget to [https://example.com/pricing], [directly under the plan comparison table, above the FAQ]?

It is two lines of HTML, nothing to install:

<div data-storyproof-widget="[your-widget-id]"></div>
<script src="https://app.storyproof.io/embed.js" async></script>

The div goes where the testimonials should appear. The script can sit once in the shared footer instead of next to the div, if that is how we load other scripts.

Done means: the widget shows on the live page on desktop and mobile, and nothing else on the page moves or breaks.

Thanks,
[Priya]
  2. Follow-up when it is live

    Send after you have checked the page yourself.

    Thanks [Sam], it is showing on [https://example.com/pricing]. If you ever rebuild that template, the div with id [your-widget-id] needs to come across with it, or the section will go blank.

[Priya]

What you type stays in this browser tab. Nothing is sent or stored.

The problem, solved

Why testimonial handoffs bounce back, and what to put in the message

  • Problem 1

    They asked what to install first

    Developers expect a plugin, package or API key and lose time looking for one.

  • Problem 2

    The script ended up on the page twice

    Each widget was pasted with its own script, so pages with two widgets load the same file twice.

  • Problem 3

    They asked us to send the quotes

    Some developers assume they must type the testimonials into the page, which turns a quick paste into a content job.

  • Problem 4

    It landed in the wrong spot

    "On the pricing page" leaves a developer to guess between the top, the sidebar and the footer.

  • Problem 5

    The client noticed a badge we did not mention

    An agency installs the widget for a client who then asks about a small credit line under it.

A filled-in brief

Illustrative sample, not a real customer

Hi Sam, could you add our testimonial widget to the pricing page, directly under the plan comparison table and above the FAQ, by Thursday?

Nothing to install: one div and one script line, both below. Our footer already loads the script for the homepage widget, so only the div is needed here.

Done means it shows on the live page on desktop and mobile with nothing else moving.

Page
Pricing
Position
Under the comparison table, above the FAQ
Script
Already in the footer

In StoryProof

Before you press send

Step 1 of 4

Finish the selection first

Choose the approved testimonials for the widget before the developer starts, so the first look on the live page is the real one.

Before you start

What the message cannot do for you

  • It does not cover every builder

    Some website builders strip scripts or put custom code in a frame. Your developer knows your platform; the message leaves the method to them.

  • It does not test the result

    A clear brief reduces mistakes but someone still has to look at the live page. If the widget stays blank, the troubleshooting page is the next stop.

  • It assumes one widget id

    A different selection on another page means another widget and another id. Send one message per widget to keep them apart.

  • It does not cover consent tools

    If your site runs a consent manager, ask the developer how it treats new scripts before the widget goes live.

FAQ

Questions people ask

Short answers to what usually comes up next.

Does my developer need a StoryProof account?

No. They need only the two lines of code in the message. You keep the account and the testimonial selection.

Can the developer put the script in the site header instead?

The script is async, and it needs to load once on any page that has a widget div. A shared footer is the usual place; the header works too if that is how your site loads scripts.

What if the developer wants to restyle the widget with our CSS?

Start by choosing a layout in StoryProof that fits the page. Ask the developer to tell you before overriding any styles, so later changes on your side do not clash with theirs.

How do I add the same widget to more pages later?

Send the "Several pages" version. Once the footer loads the script, each new page needs only the div.

Still have a question? Ask the StoryProof team or book a demo.

Build the widget, then hand it over

Choose your testimonials and layout in StoryProof, and send your developer two lines of code.

Start free (opens in a new tab)

Last updated 2026-11-13.