Publishing customer words without creating a problem

It has to be real

Written by an actual customer about an actual job. Not composed by you in a customer's voice, not bought, not generated.

This sounds obvious and fabricated reviews remain among the most common enforcement subjects, usually at businesses that told themselves it was only placeholder text.

Placeholder testimonials have a way of going live. If you have none yet, publish none and say you are new.

The placeholder problem is worth taking seriously because it is how honest businesses end up with invented reviews. Filler written during a build has a way of surviving to launch.

Permission, in writing

A review left on a public platform is public, and republishing it on your own site with a name and a photo is a further step. Ask.

A short message saying may I use this on my website, with their reply, is enough. Keep it with the testimonial.

Agree how they are named. First name and suburb suits most people. Full names and photographs need a clearer yes.

• Ask before publishing, not after
• Say where it will appear — website, social, print
• Agree how they are named: first name, suburb, full name
• Ask separately about a photograph
• Keep the reply with the testimonial
• Note the date, so you know how old the quote is

Attribution that means something

Anonymous praise reads as invented, because plenty of it is. A first name, a town and the job done is far more persuasive.

Where the customer is a business, name it only with their agreement. Some clients will not want their supplier relationships public.

Do not tidy the words. Light punctuation fixes are fine. Rewriting the sentiment makes it your writing, not theirs.

The typical results question

If a testimonial describes an unusually good outcome, presenting it as what customers get is misleading even though the quote is genuine.

The safer approach is to choose ordinary happy customers rather than the single spectacular one, or to say plainly what a normal result looks like.

One outstanding case surrounded by five ordinary ones tells a truer story and is more believable anyway.

The safer selection is deliberately unglamorous: ordinary satisfied customers rather than the single spectacular case, which is also more believable to anybody reading carefully.

Incentives have to be disclosed

If you gave a discount, a gift card or anything else in exchange for a review, that connection must be clear to a reader.

The disclosure belongs with the review, not in a policy page. A short line saying this customer received a discount for sharing their experience does it.

Asking for honest feedback with no reward attached avoids the question entirely, and produces reviews people trust more.

The disclosure belongs with the review itself, not on a policy page, for the same reason set out in disclosing affiliate links and sponsorship.

Filtering and the gating problem

Asking only satisfied customers for reviews, or suppressing poor ones, produces a page that misrepresents your average.

Platforms take a dim view of it and so do regulators. The reputational risk is worse: a wall of perfect scores reads as managed.

A few middling reviews answered well is the most convincing thing a business can publish.

How they sit on the page

Near the decision, not in a carousel nobody waits for. A moving slider hides most of your testimonials and is awkward to operate by keyboard.

Write them as real text rather than screenshots, so they can be read aloud, enlarged and found by search.

Every page written by Website Builder Studio passes a check that runs before anything publishes, and no rating markup is emitted for reviews that do not exist.

Publish them as real text rather than screenshots, so they can be read aloud, enlarged, and found. A wall of images of reviews is invisible to everything except a sighted reader.