Skip to main content

A brief pack for whoever builds the new site

Export Testimonials for a New Website

Your testimonials already live in StoryProof. The new website is being built by an agency, a freelancer or a teammate on a different platform, and they need to know what proof exists, where it showed before and how it gets onto the new pages. Hand them a pack: the CSV for copy decisions, a map of widgets to pages, and the embed codes, so testimonials are part of the build instead of an afterthought.

  • The CSV as the content inventory
  • Every widget mapped to its old and new page
  • Embed codes collected in one document

The problem, solved

What a website builder needs from you, and where each piece comes from

  • The agency asks what testimonials we have

    Without a list, designers guess at quote lengths and leave lorem ipsum where proof should go.

  • They plan to paste quotes into templates

    Hard-coded quotes are exactly the mess that makes the next redesign painful.

  • The new theme has a global footer

    Builders worry about loading a script on every page that carries a widget.

  • Which widgets deserve a slot?

    Carrying every widget across copies dead weight into a fresh design.

  • We want a testimonials page on the new site

    A hosted wall link sends visitors away from the new site you are paying for.

Flip the switch to see how StoryProof handles each one.

Brief pack checklist

Assemble the testimonial pack for your builder

Build the pack before design starts. A designer who sees real quotes sizes the layout to fit them.

Inventory
Widget map
Code and access

Nothing here is stored. Ticks reset when the page reloads.

How each testimonial use reaches the new site

Use on the new siteBest routeWhy
Proof beside a product or pricing blockA widget slotYou choose its testimonials in StoryProof, not in the template
A full testimonials pageWall of Love embedOne code shows every approved testimonial
A short line in a hero headlineText copied from the exportFine for one line, but it will not change unless someone edits the page
A PDF or print piece linked from the siteText copied from the exportEmbeds do not work in files

In StoryProof

From export to launch

  1. 1

    Export and review

    Download the CSV for each space and read it with the new sitemap in hand.

  2. 2

    Map widgets to pages

    Use the views ranking to decide which widgets move, which retire and which pages need new ones.

  3. 3

    Set each widget’s selection

    Choose the approved testimonials each new page’s widget should show.

  4. 4

    Hand over code, not quotes

    Give the builder the embed snippets and the wall embed code, plus the footer script note.

  5. 5

    Check on staging and at launch

    Open every page with a slot and confirm each widget shows, on a phone too.

What happens next: After launch, watch the views ranking for a few weeks to see whether the new placements are seen.

Before you start

Before you send the pack

What this does not cover, and what to check on your side. Better to know now than after launch.

  1. 01

    The CSV is for planning

    The export informs copy decisions. On the site itself, prefer widgets and the wall embed; a pasted quote is fixed text that only a page edit can change.

  2. 02

    Platform rules vary

    The embed needs a page that accepts HTML and scripts. Ask your builder whether the new platform allows that everywhere you plan a slot.

  3. 03

    Wall layout is not described here

    This page makes no claim about how the embedded wall looks or resizes. Preview it on staging.

  4. 04

    Old URLs need redirects

    If the old testimonials page ranked in search, ask the builder to redirect it to the new one.

FAQ

Questions people ask

Short answers to what usually comes up next.

Do I need to export at all if widgets just move?

The embed codes are what move. The export is for the people writing and designing the new pages, who need to see the real quotes and their lengths.

Will the widgets work on a different platform?

Any page that accepts HTML and a script tag can carry them. Check with your builder for the platform you chose.

Should the new site have a testimonials page?

If you want one, the Wall of Love embed gives you a page of approved testimonials without anyone copying text into it.

What about testimonials hard-coded on the old site?

Find and gather those first. The redesign page covers recovering quotes that never reached the library.

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

Give your new site proof from launch day

Keep the library in StoryProof, export it for the brief, and embed it on whatever platform you build.

Sources

  1. Manage testimonials FAQ: exporting, StoryProof. Checked 2026-11-19.

Last updated 2026-11-19.