Where should testimonials go so people actually read them?
Next to the claim each one proves, not in a section of their own. A quote sitting beside the sentence it supports gets read because it is part of the argument. The same quote in a carousel two thirds down the page is decoration, and decoration is the category of thing people have trained themselves to skip.
This is the most common structural mistake I see on B2B sites, and it survives because it looks organised. Someone collects five good quotes, builds a tidy section called What Our Clients Say, and considers proof handled. The page now contains proof and communicates none.
I have shipped websites for 25 or more clients across six years, and the testimonial section is the block I most often argue about and most often win by taking apart.
Why does the dedicated testimonials section get skipped?
Because it looks like an ad, and people have learned not to look at ads. Nielsen Norman Group's eyetracking work on banner blindness reported that users almost never look at anything that looks like an advertisement, whether or not it is actually an ad, and that users do not fixate within design elements that resemble ads even if they are not ads.
That research is old, published in 2007, and I want to be straightforward about that rather than dressing it up as new. But the mechanism it describes is about learned visual pattern recognition, and the pattern in question has only become more entrenched since. A row of smiling faces in circular crops with a five star flourish is, visually, an advertisement.
The irony is that the more polished you make that section, the more it reads as marketing rather than evidence. A quote that looks designed looks bought. A quote that looks like it was pasted in next to a specific claim looks like it was pasted in because it was true.
What does adjacency actually mean on a page?
It means the proof appears within a screen of the assertion it supports, with no section break between them. If you claim you deliver on a fixed fee without surprise invoices, the quote from a client saying exactly that belongs directly under that sentence, not in a collection with four unrelated quotes.
The test I use is whether the quote would still make sense if you deleted the surrounding copy. If it would, it is generic and it is doing nothing. If it would read as a fragment without the claim above it, you have placed it correctly, because it is now part of a single argument rather than a standalone endorsement.
This also fixes the selection problem. When proof has to sit next to a specific claim, you stop choosing quotes by how flattering they are and start choosing by what they establish. Those are very different criteria, and only one of them persuades.
Which claim deserves proof, and which does not?
Proof belongs on the claims a sceptical buyer would doubt, not on the ones they would accept. Nobody needs a testimonial confirming that you build websites. They need one confirming the thing they are privately worried about, which is usually timelines, communication, or what happens when something goes wrong.
So the useful exercise is to write down the three objections you actually hear on calls, then find or request a quote for each. If you cannot find one, that is information. Either the objection is not as common as you think, or you have never asked a happy client the right question.
Ask better questions when you request testimonials and this stops being hard. A client asked what it was like to work with you produces a pleasantry. A client asked what worried them before starting and whether it happened produces evidence, and that answer will land next to the exact claim it addresses.
How many testimonials belong on one page?
Fewer than you have, and at most one per claim. Three specific quotes placed against three real objections outperform twelve general ones stacked together, because twelve reads as a volume play and volume reads as compensation.
Quantity also creates a reading problem. Nobody reads the fourth testimonial in a row. By the third the reader has classified the block and moved on, which means quotes four through twelve are occupying page height, adding load, and persuading nobody. They are a cost with no matching benefit.
If you have more good quotes than places to put them, that is a fine problem, and the right home for the surplus is a dedicated case study or a clients page where someone deliberately went looking for depth. I have written about what makes a testimonial believable in the first place, and believability and placement are separate problems that compound. A vague quote placed perfectly is still a vague quote.
Should testimonials go above the fold?
Usually not a quote, sometimes a name. Above the fold your job is to say what you do and for whom, and a testimonial competes with that rather than supporting it. The reader does not yet have a claim in mind to be persuaded of.
What can work high on the page is a single line of attribution rather than a full quote. Naming the kind of client you work with, or a recognisable name if you genuinely have one, establishes category membership in a few words without asking for reading time you have not earned yet.
The same restraint applies to the logo strip that usually lives up there, which is a related pattern with the same failure mode. I have written about showing integrations without defaulting to a logo wall, and the underlying principle is identical: a grid of marks is a visual cliche that gets scanned past, while one named example inside a sentence gets read.
What about the right rail and the sidebar?
Avoid it. Nielsen Norman Group's finding was explicit that people have learned not to look at the right rail, and a sidebar testimonial is the clearest possible case of putting evidence exactly where attention is not.
On a modern responsive layout there is a second problem underneath the first. A right rail collapses on mobile, usually to the bottom of the content, which means your proof ends up after everything for most of your traffic. You have designed a placement that is ignored on desktop and buried on phones.
If content is important enough to include, it is important enough to sit in the main column. If it is not important enough for the main column, the honest move is to cut it rather than to find it a quiet corner.
How does this change on a pricing page versus a services page?
On a services page the objections are about capability and process, so proof sits next to method claims. On a pricing page the objections are about value and surprise, so proof sits next to the number, and it should speak to whether the price turned out to be the price.
That is a genuinely different quote, and most sites use the same one in both places. A client saying the work was excellent does nothing beside a price. A client saying the final invoice matched the quote does a great deal, and it addresses the specific fear a person reading a pricing page is holding.
The same logic extends to an about page, where the doubt is about who you are rather than what you charge. That page carries trust differently, and I have written about how an about page earns trust rather than asserting it.
What should you do next?
Open your highest intent page and find every testimonial on it. For each one, write down which sentence on that page it proves. Any quote that does not have an answer gets cut or moved next to a claim it genuinely supports, and any claim that a buyer would doubt and that has no proof beside it becomes a request you send to a past client this week.
Then delete the section header. If your quotes are placed correctly you no longer need a block called testimonials, and removing the label is what stops the content reading as an advertisement in the first place.
If you would like someone to go through a page and tell you which proof is working and which is furniture, reach out. It is a quick review and the changes are usually small.
Get found, cited and the back office automated
Let's make your site the source AI engines quote and wire up the systems behind it.
Read more blogs
Let's get your website found and cited by AI
Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.