Skip to main content

Organising your library

Tag your testimonials so the right story turns up when you need it

A library of eighty testimonials is only useful if someone can find the one about switching from a competitor, from a finance lead, in under a minute. List what you sell, who buys and what they worry about, and get a tag scheme your whole team can follow.

  • A tag scheme generated from your own products and buyers
  • Naming rules that stop duplicate tags
  • A routine for tagging each new testimonial
Use the free toolSet up my library (opens in a new tab)
Your tag scheme

PRODUCT (one tag each)

Starter plan, Onboarding package

AUDIENCE (one tag each)

4 versions to copy

Free tool, no sign-upTry it below

The problem, solved

Why a testimonial library stops being searchable, and how StoryProof fixes it

  • We keep reusing the same three quotes

    Without labels, the team reaches for the testimonials it remembers, so one founder quote turns up on the homepage, the pricing page and every deck.

  • Tagging waits for a quiet afternoon

    A backlog of eighty untagged testimonials never shrinks, because the quiet afternoon never arrives.

  • Our best reviews live on G2, not here

    Praise on review sites stays outside the scheme, so the page that needs a switching story never gets the one a reviewer wrote last year.

  • Finding the story is only half the job

    Locating the right finance-lead quote helps little if putting it on the pricing page means a ticket to the web team.

Flip the switch to see how StoryProof handles each one.

Generator

Generate your tag scheme

Type each list separated by commas. Choose the library size and the scheme adjusts to it.

Library size
  1. Your tag scheme

    Three families are enough at this size. Add more only when you feel the gap.

    PRODUCT (one tag each)
[Starter plan, Onboarding package]

AUDIENCE (one tag each)
[founders, finance leads, agencies]

OBJECTION IT ANSWERS (one tag each)
[price, switching, support]

USE ON
[pricing page]
  2. Naming rules
    One word or a short phrase, lower case, hyphens between words.
Singular, not plural: "agency", not "agencies".
The buyer’s word, not your internal name.
Before creating a tag, check whether a close one exists.
One person reviews the tag list each quarter and merges duplicates.
  3. Tagging routine for each new testimonial
    When you approve a testimonial, add:
1. One product tag from: [Starter plan, Onboarding package]
2. One audience tag from: [founders, finance leads, agencies]
3. Every objection it answers from: [price, switching, support]
4. Its format
5. A use tag if it belongs on the [pricing page]

If none of the objection tags fit, note what it does answer. That is how new tags should be born.

The scheme is generated in your browser. Nothing is saved.

A scheme in use

Illustrative scenario, not a StoryProof customer

A payroll software company has testimonials from founders, finance leads and accountants, about two products. Its pricing page loses buyers who fear a painful migration from their old provider.

With objection tags in place, the marketer looks up everything tagged with the finance-lead audience and the switching objection, finds four answers, and picks the one that names the old provider’s export.

The sales team uses the same tags to find a story for a prospect who raised the same worry on a call.

Product
payroll, expenses
Audience
founder, finance-lead, accountant
Objection
price, switching, compliance
Use
pricing-page, sales-deck

In StoryProof

Apply it in StoryProof

  • You will need
  • Your generated scheme
  • A StoryProof workspace
  1. 1

    Create the tags from your scheme

    Tags are on every plan. Set up the families from the generator before the next batch of testimonials arrives.

  2. 2

    Tag while you approve

    Every submission waits in your queue for approval, which is the natural moment to tag it, while you have just read it.

  3. 3

    Back-tag your best twenty first

    Do not try to tag the whole archive at once. Start with the testimonials already on your site and in your sales materials.

  4. 4

    Build widgets from tagged stories

    When a page needs proof for one objection, find the matching tags and add those testimonials to the page’s widget.

What happens next: Every new testimonial now joins the library already labelled for the pages and conversations that need it.

Before you start

Keep it workable

  • Fewer tags beat more

    A scheme nobody remembers is not used. Start with the three families and grow from real gaps.

  • Tags need an owner

    Without one person reviewing the list, near-duplicates creep in within months.

  • Tags do not replace reading

    They narrow the search. Someone still has to read the shortlist and choose.

  • Use tags follow permission

    A use tag such as ads only helps if the customer agreed to that use. Check what they allowed before tagging a testimonial for a placement.

FAQ

Questions people ask

Short answers to what usually comes up next.

How many tags should a testimonial have?

Usually three to five: a product, an audience, the objections it answers, and its format. More than that and tagging becomes a chore people skip.

Should I tag by star rating?

Not as a tag. Rating is already part of the testimonial. Tag by what the story is about and who it will persuade.

What about testimonials that fit nowhere?

Note what they do answer. If several land there, that is a new objection tag worth adding.

What if two teammates tag the same testimonial differently?

Settle which tag fits and add that testimonial to your naming rules as an example. A disagreement usually shows a tag that needs a clearer definition.

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

Start a library you can actually search

Collect testimonials, tag them on approval and pull the right one into any page.

Set up my library (opens in a new tab)Book a demo (opens in a new tab)

Last updated 2026-11-04.