Using testimonials on your site
Builds guide sites for a livingPublished July 22, 2026Last updated July 26, 202613 min read
- Review markup for a local business is documented as only for sites capturing reviews about others.
- Place one quote at each doubt on the page rather than stacking them on a page of their own.
- Keep the specific detail and cut the compliments, which is the opposite of the usual instinct.
- Ask what attribution each client is comfortable with, and never pair a photo with another's words.
- Link to platform reviews rather than reproducing a favourable selection without their context.
The first thing to know about testimonials on your own site is what they cannot do. Google's structured data documentation permits review markup for a local business only on sites that capture reviews about other local businesses, and points to its guidelines on self-serving reviews. Which means quotes on your own pages will never produce stars in a search result, however they are marked up. Their entire job happens on the page, in front of somebody already reading it. That reframes the work completely: this is not a search problem, it is a placement problem, and the testimonial that works is the one sitting next to the doubt it answers. Everything around it sits under the getting-booked hub.
Where a quote goes, and what it has to answer
| Page position | The reader's doubt | The quote must say |
|---|---|---|
| Beside the price | Is it worth it | What they got for it |
| Beside the beginner trip | Will I embarrass myself | That somebody else did not |
| Beside the weather policy | Will I lose my money | What happened when it blew |
| Beside the booking button | Is this person real | Something only a real client knows |
Why will testimonials never get you stars?
Because the eligibility list excludes your own site.
The documentation describes a review snippet as a short excerpt of a review or a rating from a review website, usually an average of combined rating scores from many reviewers.
It lists the features you can supply ratings for, and against two of them it attaches a condition.
Local business is marked as available only for sites that capture reviews about other local businesses, with a pointer to the guidelines on self-serving reviews.
Organisation carries the same restriction, only for sites that capture reviews about other organisations.
So a guiding operation marking up its own testimonials is outside the intended use, and the stars people imagine will not appear.
That is not a loss. It clarifies what the quotes are for, which is persuading a person already on the page rather than attracting one who is not.
The documentation is published by Google Search Central.
So what is the quote actually doing?
Answering the objection at that exact scroll position.
A page is a sequence of small doubts, and a reader abandons at whichever one goes unanswered.
Beside a price the doubt is value. Beside a beginner trip it is embarrassment. Beside the weather policy it is losing money. Beside the booking button it is whether you are a real person.
A quote placed at the doubt it answers does work that no amount of general praise does.
Which means the useful sorting question is not which testimonial is best, it is which doubt each one addresses.
Go through what clients have actually said and label each line with the doubt it answers, then place it there.
Most operations find they have six quotes answering the same doubt and none answering the expensive ones.
Where to find better material is covered in the review request piece.
What makes a quote believable?
Specificity that could only come from a real day.
Generic praise is discounted instantly, because everybody knows it is trivial to write.
What survives that scepticism is detail: a month, a species, a mistake somebody made, a moment that would not occur to an inventor.
A quote saying the guide was patient is worth nothing. A quote saying he re-tied a leader four times without commenting is worth a great deal.
So when you collect, ask for the specific rather than the general, and when you edit, keep the specific parts and cut the compliments.
That is the opposite of what most operations do, which is to cut the detail and keep the praise.
The same instinct governs the filmed version, covered in the video testimonials piece.
How many quotes a page can carry. Count the doubts on the page rather than the quotes in your folder. A typical trip page has four: cost, difficulty, weather and trust. One quote each is a full set, and a fifth added anywhere is decoration. Now count what you have: most operations hold two dozen quotes that all answer the trust doubt and nothing that answers the money one. The gap is the work. Neither count is measured here; both come from reading your own page and your own folder, and no claim is made about what any number of testimonials achieves.
How should a quote be written?
In the client's words, in plain ones.
The federal plain language guidance exists because clarity is a public obligation rather than a style preference, and its framing is useful even where nothing binds you.
It defines plain writing as writing that is clear, concise, well-organised, and follows other best practices appropriate to the subject or field and intended audience.
That last clause is the operative one for a testimonial: appropriate to the intended audience, which for a guiding page is somebody who does not know the jargon.
A quote full of terms only anglers use will read as insider talk to exactly the beginner it was meant to reassure.
So where a client uses a term the reader will not know, either cut the sentence or let the surrounding page explain it first.
And never rewrite the quote into cleaner prose, since the roughness is the evidence.
The guidance is published as a set of guides on Digital.gov, covering principles, writing, design and testing for understanding.
Where does that plain language obligation come from?
An Act of 2010, and its purpose is worth borrowing.
The statute states its purpose as improving the effectiveness and accountability of federal agencies to the public by promoting clear government communication that the public can understand and use.
It defines plain writing in the terms quoted above, and applies it to documents necessary for obtaining a benefit or service, documents providing information about one, and documents explaining how to comply with a requirement.
None of that governs a fishing guide, and the framing transfers cleanly: communication the reader can understand and use.
A testimonial that a reader cannot understand and use is decoration, however flattering it is.
Use is the interesting word there, since a quote is used when it removes a specific hesitation and lets somebody act.
Judge your quotes by that rather than by how nice they are.
The Act was enacted on 13 October 2010 and is published at GovInfo.
Should you use names and photographs?
As much as the client agreed to, and no more.
A first name and a town is more credible than initials, and a photograph more credible still, because both are harder to invent.
They are also personal information about somebody who agreed to a quote rather than to a portrait, so ask specifically.
Offer the options plainly: name and town, first name only, or initials, and let them choose.
Where somebody chooses initials, do not compensate by adding a stock photograph, which is worse than nothing and reads as invented.
Never use a client's photograph beside somebody else's words, even by accident, since that is a fabricated pairing.
Keep a note of what each person agreed to, because in two years you will not remember.
The permission conversation is set out in the photo permission piece.
How many is too many?
A wall of them reads as compensating.
Thirty quotes stacked on a page tell a reader that somebody was worried about credibility, which is the opposite of the intended effect.
Four well-placed quotes on the pages where decisions happen outperform a page containing everything.
The failure is easy to spot: if a reader would have to scroll past testimonials to find information, there are too many.
Keep the archive by all means, and publish from it selectively.
Rotate them seasonally rather than adding indefinitely, which keeps the page fresh without growing it.
And retire anything describing something that has changed, because an out-of-date quote quietly misleads.
How to keep the whole page honest is covered in the website mistakes piece.
What about reviews from platforms?
Link to them rather than reproducing them wholesale.
Reviews left on a platform belong in that platform's context, where a reader can see the count, the distribution and the unflattering ones.
Lifting a favourable selection onto your own page removes exactly the context that made it credible.
A short quotation with a link to the source is honest and stronger, because the reader can check it.
Reproducing platform reviews may also engage that platform's own terms, which is worth reading before building a page on it.
What works better is pointing plainly at where the reviews live and letting somebody go and read them.
A guide confident enough to send people to an unfiltered page is making a claim no quote can make.
Where those reviews come from is covered in the getting reviews piece.
Can you test whether they work?
Crudely, and crude is enough.
The plain language material includes testing for understanding as one of its four parts, which is a discipline worth borrowing from an agency rather than a marketer.
The cheap version for a guide is to hand your trip page to somebody who does not fish and ask what they still do not know.
Whatever they name is a doubt, and the quote answering it belongs there.
Do that with three people and you will have a better page than any split test would give you at this traffic level.
Repeat it once a year, since your page drifts and your clients change.
What you must not do is judge testimonials by whether they feel good to read, because you are not the audience.
The wider measurement question is handled in the piece on measuring without obsessing.
What should you do with a lukewarm one?
Publish it, if it answers a doubt.
Operations instinctively publish only the most enthusiastic quotes, which is why testimonial sections all read the same and none of them is believed.
A quote saying the fishing was slow and the day was still worth it is more persuasive than five saying it was incredible, because it concedes something.
It also answers the doubt a reader actually has, which is what happens when the fishing does not cooperate.
The same goes for a quote mentioning a genuine limitation: the early start, the run, the lack of a toilet, the cost.
Publishing one of those signals that you are not curating, which makes the enthusiastic ones credible again.
The line is honesty rather than self-harm: publish a real reservation, not a complaint you have since fixed without saying so.
Where you have fixed something a client mentioned, say so beside the quote, which turns a criticism into evidence of listening.
How to handle the genuinely negative version is covered in the negative reviews piece.
How do you collect against a gap?
Ask a question shaped like the doubt.
If the missing quote is about value, the question is what made the day worth the money, not whether it was worth it.
If the missing quote is about weather, ask what happened when the forecast turned, which only somebody who lived it can answer.
If it is about beginners, ask what they were worried about beforehand and what actually happened.
Each of those produces usable material because the question already contains the shape of the answer.
Send the question to the specific client whose trip fits, rather than to everybody, since a general request produces general praise.
Two targeted asks a season fills the gaps within a year, which is faster than it sounds and slower than anybody wants.
Keep a note of which doubt each new quote fills, so the next ask targets the next gap.
The timing of those requests is set out in the welcome sequence piece.
Do testimonials belong in email and social too?
Sparingly, and never as the whole message.
A quote inside an email works when it illustrates something the email is already saying, and fails when it is the point of the message.
Nobody opens an email to read praise of the sender, and a message consisting of testimonials reads as an advertisement even to people who like you.
On social the same holds with a sharper edge, since a quote graphic is instantly recognisable as marketing.
What works better in both places is the specific story the quote came from, told plainly, with the client's line at the end.
That way the quote is evidence for something rather than the entire content.
And it gives you something to say, which is the harder problem in both channels.
Reuse the same quote across surfaces rather than collecting separately for each, since a good one works everywhere.
Ideas for what those messages carry are in the newsletter ideas piece.
What if you are just starting out?
Use what you have, and say what it is.
An operation in its first season has few clients and no archive, and the temptation is to pad with something invented, which is the one unrecoverable mistake here.
The honest alternatives are better than they look. A single specific quote from your third-ever client, presented as exactly that, is more disarming than a wall of anonymous praise.
A line from somebody you took out before you were charging is legitimate if you say so.
So is describing the trip plainly and letting the absence of testimonials stand, since a new operation being new is not a defect anybody minds.
What people do mind is discovering that a business overstated itself before they even booked.
Collect properly from the first paying client and you will have a full set by the end of a second season.
Until then, put the effort into the pages themselves, which do more work than any quote at that stage.
What those pages need is set out in the website examples piece.
Which habits weaken a testimonial page?
Seven, and the first is herding them onto one page.
Building a testimonials page nobody navigates to, instead of placing quotes where decisions happen.
Keeping the praise and cutting the detail, which removes the only credible part.
Marking up your own testimonials expecting stars that the documentation excludes.
Adding a stock photograph beside an anonymous quote.
Stacking thirty quotes, which reads as anxiety.
Reproducing platform reviews without their context or a link.
And leaving up a quote about a boat, a price or a service that no longer exists.
What the rest of the page should contain is covered in the on-page basics piece.
What surprises operators here?
That the stars were never available.
The documentation limits local business review markup to sites capturing reviews about other local businesses, which excludes almost every operation that wants it.
The second surprise is that placement matters more than selection, and that most folders contain quotes answering only one doubt.
The third is that specificity beats praise so decisively that cutting the compliments improves a quote.
The fourth is that a federal definition of plain writing describes the standard better than any marketing framework.
The fifth is that sending a reader to an unfiltered review page is a stronger move than any curated wall.
Taken together, this is an editing and placement job rather than a collection job.
Where the collection itself happens is covered in the segmenting piece.
The page, in order
Find the doubts, then place a quote at each.
List the doubts a reader has on each page, in the order they arrive.
Label every quote you hold with the doubt it answers, and notice which doubts have nothing.
Collect specifically against the gaps rather than asking for general praise.
Place one quote at each doubt and no more, and delete the testimonials page.
Keep the client's own words, cut the compliments, and keep the detail.
Ask each person what attribution they are comfortable with, and record the answer.
Link to platform reviews rather than reproducing a favourable selection.
And hand the page to three people who do not fish, once a year, and fix whatever they still do not know.
No conversion figure appears on this page, for a quote, a placement or a page. The published numbers about testimonials come from ecommerce experiments run at traffic volumes no guiding operation reaches, and applying them here would be borrowing a stranger's measurement. The arithmetic panel counts doubts and quotes, both of which you read off your own page, and asserts nothing about what either produces. Nor does this page supply wording for a quote, since a fabricated testimonial is the one unrecoverable mistake in this subject. Sources checked 26 July 2026. Structured data eligibility and platform terms both change, so read the current pages before building anything on them.
How this was checked. The structured data material is quoted from Review snippet structured data, in Google Search Central documentation at developers.google.com, read on 26 July 2026. Taken from it: that a review snippet is a short excerpt of a review or a rating from a review website, usually an average of the combined rating scores from many reviewers; that when Google finds valid reviews or ratings markup it may show a rich snippet including stars and other summary information; that review snippets may appear in rich results or Google Knowledge Panels; that ratings may be supplied for book, course list, event, local business, movie, product, recipe and software app features, with local business marked as only for sites that capture reviews about other local businesses and a pointer to the guidelines about self-serving reviews; that reviews are also supported for a list of schema.org types including Organization, again only for sites that capture reviews about other organizations; and that the documented process is to add the required properties, follow the guidelines, validate with the Rich Results Test, deploy pages and test with the URL Inspection tool, ensuring the page is not blocked by robots.txt, a noindex tag or login requirements. The plain language material is taken from the plain language guide series published on Digital.gov, read the same day, which states that plain language is content that is clear and easy to understand, that the guides cover principles of plain language, writing for understanding, design for understanding and testing for understanding, and that the Plain Writing Act of 2010 established the requirement that content for the public is written for its specific audience. The statute itself, Public Law 111-274, enacted 13 October 2010, is published at govinfo.gov and was read the same day: its stated purpose is to improve the effectiveness and accountability of Federal agencies to the public by promoting clear Government communication that the public can understand and use; it defines plain writing as writing that is clear, concise, well-organized, and follows other best practices appropriate to the subject or field and intended audience; and it defines a covered document as one necessary for obtaining any Federal Government benefit or service or filing taxes, or providing information about any Federal Government benefit or service, or explaining to the public how to comply with a requirement the Federal Government administers or enforces, including a letter, publication, form, notice or instruction in paper or electronic form, and excluding a regulation. Nothing in that Act applies to a private business; it is quoted here for its definition and framing only. No conversion figure and no sample testimonial wording appears anywhere on this page.
If your booking calendar has more open weeks than you’d like, I’ll build you a free preview of your booking site before you pay a cent.
Get a free website previewUsing testimonials, the questions that matter first
Will testimonials on my site get me stars in search?
No, and the documentation says why. Google's review snippet structured data page lists the features you can supply ratings for, and marks local business as available only for sites that capture reviews about other local businesses, pointing to its guidelines on self-serving reviews. Organization carries the same restriction. So a guiding operation marking up its own testimonials sits outside the intended use, and the stars people imagine will not appear. That is not a loss: it clarifies that the quotes exist to persuade somebody already on the page rather than to attract somebody who is not.
So what is a testimonial for?
Answering the objection at that exact scroll position. A page is a sequence of small doubts and a reader abandons at whichever one goes unanswered. Beside a price the doubt is value; beside a beginner trip it is embarrassment; beside the weather policy it is losing money; beside the booking button it is whether you are a real person. A quote placed at the doubt it answers does work no amount of general praise does. So the sorting question is not which testimonial is best, it is which doubt each one addresses. Most operations find six quotes answering one doubt and nothing answering the expensive ones.
What makes a quote believable?
Specificity that could only come from a real day. Generic praise is discounted instantly because everybody knows it is trivial to write. What survives scepticism is detail: a month, a species, a mistake somebody made, a moment that would not occur to an inventor. A quote saying the guide was patient is worth nothing; a quote saying he re-tied a leader four times without commenting is worth a great deal. So collect for the specific rather than the general, and when editing, keep the specific parts and cut the compliments. That is the opposite of what most operations do.
How should the quote be written?
In the client's words, in plain ones. The federal plain language guidance defines plain writing as writing that is clear, concise, well-organized, and follows other best practices appropriate to the subject or field and intended audience. That last clause is the operative one: appropriate to the intended audience, which on a guiding page means somebody who does not know the jargon. A quote full of terms only anglers use reads as insider talk to exactly the beginner it was meant to reassure. Where a client uses a term the reader will not know, cut the sentence or let the page explain it first, and never rewrite the quote into cleaner prose.
Should I use names and photographs?
As much as the client agreed to, and no more. A first name and a town is more credible than initials, and a photograph more credible still, because both are harder to invent. They are also personal information about somebody who agreed to a quote rather than to a portrait, so ask specifically and offer the options plainly: name and town, first name only, or initials. Where somebody chooses initials, do not compensate with a stock photograph, which is worse than nothing and reads as invented. Never place a client's photograph beside somebody else's words, and record what each person agreed to.
How many should a page carry?
Fewer than you think. Thirty quotes stacked on a page tell a reader that somebody was worried about credibility, which is the opposite of the intended effect. Four well-placed quotes on the pages where decisions happen outperform a page containing everything. The failure is easy to spot: if a reader has to scroll past testimonials to find information, there are too many. Keep the archive and publish from it selectively, rotating seasonally rather than adding indefinitely. And retire anything describing a boat, a price or a service that has changed, because an out-of-date quote quietly misleads.
What about reviews left on platforms?
Link to them rather than reproducing them wholesale. Reviews left on a platform belong in that platform's context, where a reader can see the count, the distribution and the unflattering ones, and lifting a favourable selection onto your own page removes exactly the context that made it credible. A short quotation with a link to the source is honest and stronger, because the reader can check it. Reproducing platform reviews may also engage that platform's terms. A guide confident enough to send people to an unfiltered page is making a claim no curated quote can make.
Sources & methods
- Review snippet (Review, AggregateRating) structured data, Google Search Central
- Plain language guide series (Digital.gov)
- Plain Writing Act of 2010, Public Law 111-274 (GovInfo)
Every figure here is traced to a named public source and checked against it. Licensing, tax, and fee rules change. Verify your state’s current rules with the agency directly before you count on any number here.
Evan Knox
I build booking websites and run the ads and search for owner-run fishing guides, one operation per stretch of water. My first guide client, Bowman Fly Fishing, grew its revenue 4x in a year from that work. Field Notes is where I put the straight numbers on the business of guiding.
More field notes
Quotes where the doubt is. A page that closes it.
I'm Evan, and the guide whose best client line sits exactly where a reader hesitates is the one who fills a calendar. I build booking sites and run the search and local SEO for owner-run guide operations, one operation per stretch of water. Text me at (470) 777-9686 and I'll build you a free preview of your site before you pay a thing.