How do you build trust on a website?

Build trust on a website by putting proof on every page instead of on one testimonials page. Name real clients, date the work, and place verifiable specifics next to each point where the page asks a visitor to act, so the evidence sits inside the decision rather than one or two clicks away from it.

By Joshua Jackai, senior web designer and AI marketing creative strategist at Demand Designer. The worked example below is W Communications, LLC, a client project of that studio, built between May 2025 and June 2026.

Trust is a condition of every page, not a section of the site

Trust on a website is usually treated as a place: a testimonials page, an About page, a row of client logos in the footer. I think that is the wrong shape for it. Trust is the condition every other page is already running on, and in my view the pages doing the asking need it most.

Two terms first, because the rest of this piece leans on them. A call to action is the single thing a page asks a visitor to do: book a call, send a form, order a book. A conversion path is the route from landing on a page to completing that one action. My rule is one call to action per page, because in my view a second ask makes a visitor choose between the two before choosing the one you wanted.

In my view, every conversion path has a point where a visitor has to believe something. If the proof for that belief is two clicks away, the evidence is furthest from the ask at the point that carries the most weight. Proof belongs beside the ask. Not near it. Beside it.

Why a testimonials page is the wrong home for proof

A testimonials page can only be read by someone who clicked through to it, so it reaches people already interested enough to go looking. My argument against it as the main home for proof is plain: it puts the evidence behind a door that the least convinced reader has the least reason to open. I have no data on how testimonials pages perform and I am not claiming any. That is a design position, not a finding.

My argument is that placement matters more than volume. Gathering more quotes, more logos and more case studies leaves all of it in one room. The same material, distributed across the pages that do the asking, is present in every path instead of parked in one.

Illustration with example copy: proof placed beside the call to action.

What the W Communications rebuild did with its proof

W Communications, LLC is a strategic communications consultancy in Seattle, four decades old, founded by Wanda J. Herndon, who previously led global communications at Starbucks and was raised working class in Flint, Michigan. The live site is wcommgroup.com. Demand Designer rebuilt it as a client project, and the engagement ran from May 2025 to June 2026.

The build, briefly: eight pages of hand-coded HTML moved into WordPress on Bricks Builder, a visual page builder that lets a non-technical team edit a page without touching code, ten service disciplines organized, three conversion paths, one call to action per page, and a two-phase delivery that shipped a single landing page, one standalone page, for the London book launch event ahead of the full rebuild because the event date could not move. I have written up that side of the work separately, on how an executive website gets built and handed over to a non-technical team.

The part of that rebuild this article is about is where the proof went. Case studies, testimonials and endorsements were carried across every page rather than parked on a single testimonials page. That was the core design decision of the rebuild.

The live W Communications homepage, wcommgroup.com, as rebuilt.

Wanda J. Herndon wrote a book, Working Class to Breaking Glass: One Woman's Fight to Belong and to Lead, published by Ingenium Books. It is endorsed by Howard Schultz, founder and CEO of Starbucks, who called it "a quintessentially American story", by Christine Day, former CEO of Lululemon Athletica, and by Carolyn House Stewart, Esq., 28th international president of Alpha Kappa Alpha Sorority. Those three endorsed the book, not the website, and the site carries the endorsements as what they are. Stretching a book endorsement into a website endorsement would have been an easy sentence to write, and in my view a bad trade.

This piece reports what was built and the reasoning behind it, not what it produced.

Illustrative photo.

How do you measure whether a website is building trust?

Measuring whether a website is building trust starts with accepting that you cannot measure belief directly. You can measure the action that follows it, and the useful move is to measure each ask on its own rather than reporting one combined number for the site.

Attribution is the practice of working out which link, page or campaign a visit or a click came from. A UTM parameter is a tag added to the end of a link so an analytics tool can report that source. On the W Communications books page, two Amazon buy buttons sit on one page, and in my experience two buttons on one page can report as one line in analytics unless each button carries its own tag. Per-button tagging was added so that each button reports separately.

One catch matters before any of that gets built. Amazon strips UTM parameters on its own servers, so a tag on an outbound link to Amazon does not survive the trip. Attribution for an outbound click has to be captured on your own site, at the moment of the click, before the visitor leaves. A measurement plan that depends on the destination honoring your tags is not a plan.

The tagging exists so the question can be asked later with real numbers. This piece does not report those numbers.

What makes a website look untrustworthy?

A few things reliably damage a site's credibility with me as a reader. These are my judgments, not measured effects.

• Stacked badges. Five security seals and four award logos in a row read to me as anxiety rather than credibility. One mark a reader can verify is worth more than nine that decorate.

• Undated work. A post with no date, an award with no year, a case study with no timeframe. My read is that undated work asks the reader to guess, and I would not count on a generous guess. That is why the example above carries its dates.

• Claims with no named source. "Studies show" is not a source. The institution, the date and the sample size are.

• Self-contradicting urgency. A countdown timer that resets when the page is reloaded is not a deadline. Anyone who reloads can see that, and I would not put one on a client's site.

• Links that go to the wrong thing. A buy button pointing at the wrong edition of a product, a contact form that sends nowhere, a case study link that leads to a missing page. Faults like these are easy to miss in a desktop review and they surface at the moment someone is trying to act.

  

How do AI answer engines decide a website is credible?

An answer engine answers questions instead of listing links. A website is now read twice. Once by a person on the page, and once by a model deciding whether to cite the page inside ChatGPT, Claude, Perplexity or a Google AI Overview.

The Pew Research Center published a July 2026 snapshot titled "How Much of the Internet Is Written With AI?", based on 490,000 English-language pages drawn from Common Crawl, a public archive of crawled web pages. Pew found that 35 percent of pages published since the release of ChatGPT show signs of AI authorship, against 10 percent across the whole web. The .com domain dominates that crawl, so the all-web figure and the .com figure converge near 10 percent. The contrast that carries meaning is .com near 10 percent against .edu and .gov near 1 percent.

My reading of the Pew finding is that fluent, reassuring copy is now close to free, so fluency has stopped being evidence of anything. What is left is whatever can be checked against something outside the page. A named person in a role that can be verified. A named client with a live URL. A dated engagement. A claim that agrees with what other sources say about the same organization.

Entity consistency is the working term for that last one. An entity is the thing a page is about: a person, a company, a product. Consistency means the name, the role, the location and the claims agree across your own pages, your profiles elsewhere, and third-party mentions of you. I work on the assumption that a site contradicting its own founder's public profile gives a model a reason to pick a different source.

How do you build trust on a new website with no reviews or case studies yet?

A new website has no client roster and no review count, so specificity has to do the work that volume normally does.

Name your process step by step, including the parts you refuse to do. Be explicit about what drives the size of a piece of work: how many pages, how many service areas need organizing, whether an existing site is being moved onto a new system, whether an outside date that cannot move forces a phased delivery. In my view, a reader who can see what changes the shape of the work can also see that you have done it before.

Put a real name and face on the page, in a role that can be checked against a profile elsewhere. Date everything. Describe one piece of work in enough operational detail that nobody could have written it without having done it, and name the constraint you worked inside rather than the outcome you wish you could claim. Then answer, in your own words, the objection you are most afraid of.

Start with the page you would least want a stranger to land on

Open your site in a private browser window, on a phone, and go to the page a stranger is most likely to reach from a search result. In my experience it is rarely the homepage. Find the one action that page asks for, then look at what proof is visible on the screen at the moment it asks. Not elsewhere on the site. On the screen.

If nothing is there, move one piece of proof onto that page this week: a named client, a dated piece of work, a quote with a full name and title attached. One page, one path, one piece of proof, then the next page, until every route a buyer can take has evidence inside it.

The testimonials page can stay. It just stops being the plan.

Frequently asked questions

Should testimonials go on their own page?

A testimonials page can exist, but it should not be the plan. Reaching it requires a visitor who already went looking, so put case studies, testimonials and endorsements beside the call to action on every page instead.

How do you measure whether a website is building trust?

Measure each ask separately rather than reporting one combined number, so every conversion path has its own tag. Capture outbound clicks on your own site, because Amazon strips UTM parameters on its servers before the click is reported.

How do AI answer engines decide a website is credible?

Answer engines, which answer questions instead of listing links, can check specifics against sources outside the page: a named person in a verifiable role, a named client with a live URL, a dated engagement, and claims that agree with third-party mentions. Pew Research Center, in a July 2026 study of 490,000 English-language pages, found 35 percent of pages published since ChatGPT's release show signs of AI authorship, which is why, in my view, fluent copy alone proves nothing.

How do you build trust on a new website with no reviews or case studies yet?

Specificity replaces volume. Name your process including what you refuse to do, be explicit about what drives the size of a piece of work, put a real name and face in a checkable role, date everything, and describe one job in detail only someone who did it could write.

Want proof sitting next to every ask on your site?

Demand Designer rebuilds B2B and executive sites so the evidence lives inside the conversion path instead of behind a testimonials link. If you want a read on where your own site asks without proving, book a call and I will walk your pages with you.

Book a strategy call