Practical guides on websites, online stores, and getting found on Google — written for business owners, not developers.
Tell us about your business today — get a free quote within 24 hours. No pressure, no confusing tech talk.
Tell us about your business today — get a free quote within 24 hours. No pressure, no confusing tech talk.
Trust advice was written for checkouts. What actually builds trust when your site takes enquiries, not payments.
Almost every guide to building trust on a website was written about a checkout. Add an SSL badge, show the payment logos, put a security seal next to the card fields.
Now look at your own site. If you sell services, there is no card field. Nobody is deciding whether to hand over a Visa number. They're deciding something much harder to reassure them about: whether you exist, whether you can actually do the work, and what happens to their money if you can't.
Trust badges answer none of that.
What does answer it is evidence. That there are real people here. That they've done this specific thing before. That somebody else paid you and was glad about it afterwards. And that the arrangement doesn't leave the client carrying all of the risk.
Eight things below, roughly in order of how much they matter for a business that quotes rather than sells from a cart. Two of them are things to take off your site rather than add to it.
Almost all the useful research on website trust comes from ecommerce checkouts, and it's genuinely good research. Baymard surveyed more than 4,000 US adults about why they abandoned a purchase, and close to one in five said they didn't trust the site with their credit card details. Around 18% actively look for a security indicator before typing a card number in.
So badges do work in that context, placed next to payment fields, when the visitor recognises them.
This may surprise you: they work in reverse too. One documented case ran 17 different badges and converted at 2.1%. Removing 11 of them and keeping 6 in deliberate positions took it to 3.4%, a 62% improvement from taking things away. Baymard found the same pattern in user testing. Past about six seals, people start wondering why a site needs quite that much convincing. And a padlock icon with "Secure Checkout" written beside it, issued by nobody in particular, doesn't register as a signal at all. It's decoration.
Recognition is the variable that matters, not quantity. It's also why most large retailers display no badges whatsoever. They aren't borrowing anyone else's credibility.
Now the part that applies to you. Every figure above was measured at a checkout, at the moment somebody types in a card number. Your site has no such moment. Your visitor's anxiety turns up earlier than that and it's about different things: whether the business is real, whether it can do this particular job, and whether their deposit is safe once it's sent.
One finding does carry across. Baymard observed that a visitor's sense of whether a site is secure comes mostly from gut feeling, formed by how the site looks rather than anything technical underneath it. That holds whether or not you take payments. The judgement is the same. The evidence people use to reach it isn't.
Before anyone works out whether you're any good, they check whether you're there at all. It happens fast, mostly below conscious thought, and on a lot of small business sites it quietly fails.
The signals are unglamorous. A street address rather than a city name or a PO box. A company registration number, if your country issues them. Named people with photographs of their actual faces. A phone number that somebody answers.
Most About pages don't do any of this. They open with a mission statement and a paragraph about passion, which tells a visitor nothing about whether there's a building somewhere with people in it. Put the facts first and the philosophy after, if the philosophy earns the space at all.
The photographs matter here too, though that's covered in the wider design mistakes. The short version is that stock people undo everything this section is trying to do.
If you work remotely, or from another country, say so plainly. This is where businesses tend to make things worse for themselves. A vague "global team" with no address, or a virtual office in a city where nobody actually sits, reads as concealment, and concealment is exactly what your visitor is scanning for. A line like "We're a two-person studio in Dhaka working with clients in Singapore and the UK" answers the question outright. It's also checkable, which is the entire point.
Distance was never the problem. Ambiguity is.
A logo wall says "trusted by" and then doesn't finish the sentence. Trusted to do what? For how long? Was that a two-year retainer or one small job in 2019 for somebody's cousin?
Visitors know logos are cheap to add and close to impossible to verify, so a grid of twelve does less work than you'd hope. For a small business it can push in the wrong direction entirely. Either the names sit oddly against the rest of the site and look borrowed, or they land perfectly well and the visitor quietly concludes you're out of their price range.
One case study does more than the whole grid. It doesn't need to be long either. What the situation was, what you did about it, what changed, and what didn't. That last part is the one everyone skips, and it's the one that makes the rest believable, because a case study where everything went perfectly reads like marketing. Nothing goes perfectly.
Numbers help, but they don't have to be dramatic. "Bookings went from three a week to nine" is more convincing than "200% growth", because the small number tells the reader what size of business this was and whether it resembles theirs.
If you can't name the client, describe them precisely instead. "A marine calibration company in Singapore" carries most of the weight a company name would, and you can publish it today. Either way, get permission in writing before you publish anything about somebody else's business.
A testimonial is worth roughly as much as the reader's ability to check it. That's the whole mechanism. "Amazing service! – Sarah M." can't be checked, so it carries nothing, and a page full of them carries slightly less than nothing, because it suggests you had the option of naming somebody and chose not to.
Checkable means a full name, the company, their role, and ideally a link to somewhere they exist, their site, their LinkedIn. A date helps too. A testimonial with no date could be from last month or from 2017.
Then there's the legal side, which most small businesses assume doesn't apply to them. It does. The FTC's Rule on the Use of Consumer Reviews and Testimonials (16 CFR Part 465) took effect on 21 October 2024, and it covers six things:
Fake or false reviews and testimonials, including AI-generated ones and any from people who never used the service
Buying positive or negative reviews, or making an incentive conditional on the review being positive
Insider reviews from officers, managers, employees or immediate relatives, without a clear disclosure of the relationship
Company-controlled review sites that present themselves as independent
Review suppression, including groundless legal threats to get a bad review taken down
Buying fake followers or engagement
Penalties run to over $50,000 per violation and adjust annually. There's no small business exemption, and state attorneys general can bring actions as well.
Two of those catch small firms constantly. Insider reviews: if your co-founder, your cousin or your employee writes one, the relationship has to be disclosed. And the incentive rule: offering a discount in exchange for a review is fine, offering one in exchange for a positive review is not.
The grey area is worth knowing about too. Asking only your happy customers isn't banned by the Rule itself, and the FTC's own Q&A says as much, but it can still run into the FTC Act's endorsement guidance. Asking everyone the same way is the safer habit, and it's less work than maintaining a list of who you're allowed to ask.
Everything on your website was written by you. Your visitor knows that. So the fastest way to check whether any of it is true is to leave your site and look somewhere you couldn't have edited.
Most people do this without thinking about it. They search your company name. They look for you on LinkedIn. They check whether the person in the About photo has a history that matches the one on the page.
The usual advice at this point is to set up a Google Business Profile, which is good advice if you have a service area and customers who might drive to you. If you work remotely, or your clients are in another country, there's no local pack for you to appear in and the standard playbook runs out.
What works instead:
LinkedIn profiles for the actual people, not only a company page. A company page is another thing you wrote. A person with a ten-year history is not.
A review platform you don't own. Clutch, G2, Trustpilot, an industry-specific directory — whichever one your buyers already use. The point isn't the star rating, it's that you can't edit it.
Platform or marketplace profiles, if you work in an ecosystem that has them. A Shopify partner listing or a Webflow profile is verification you didn't write.
Evidence on the client's side. A footer credit, a case study they published, a mention in their newsletter. That's the strongest version, because it costs somebody else something.
The principle underneath all of it is that trust comes from evidence you can't edit. A Google Business Profile is one instance of that rather than the whole idea.
Nothing else on this list gets undone as quickly as a page that won't say what anything costs.
The reason isn't only that people can't work out whether they can afford you, though that's real enough and it's covered in [seven reasons people don't get in touch][PLANNED LINK: /why-visitors-dont-contact-you/]. It's what the silence implies. If the number is only available privately, the reader's next thought is that the number depends on who's asking. That isn't a pricing problem, it's a trust one.
Plenty of work genuinely can't be priced on a page, and nobody expects a fixed figure for a custom build. But there's a wide gap between publishing a fixed price and saying nothing at all:
A starting figure. "Projects start around $X."
A range, with what moves it. "$X to $Y depending on page count and whether you need ecommerce."
A worked example. "Here's a project we did, here's what was in it, here's what it cost."
Any of the three takes the suspicion away, and none of them ties you to a number you'd have to honour.
The same goes for everything else the client eventually has to pay for: hosting, maintenance, third-party licences, changes after sign-off. Finding those out later feels like finding them out deliberately, which is the opposite of what the previous four sections were building.
There's more on where transparency helps and where it doesn't in should you show pricing on your website.
Every instinct says to keep the door open. List every service, turn nobody away, describe yourself in terms broad enough to cover whatever walks in.
Pause for a second on how that reads from the other side. A business that does everything for everyone reads as a business that hasn't specialised in anything, which is fine for a hardware shop and slightly worrying in a supplier you're about to hand a project to.
There's a sharper reason underneath it, though. A page that never says no has nothing to spend when it says yes. If you take on every kind of work, your claim to be good at this particular kind carries no weight, because you'd have made the same claim either way.
Turning work down is a costly signal, and costly signals are the ones people believe. Anyone can say they're experienced. Only somebody with enough work to be selective can afford to decline any of it, and readers understand that without being told.
In practice it's three sentences rather than a manifesto:
What you don't do. "We don't build mobile apps." One line, no apology.
Who you're probably wrong for. "If your budget is under $X, or you need it live in two weeks, we're not the right fit."
Where else to go. Naming somebody who does the thing you don't is the strongest version, because it costs you a lead and the reader can see that it did.
The side effect is that your enquiries improve. People who read the exclusions and write in anyway have already decided.
One caution: specific, not superior. "We only work with serious businesses" says nothing and sounds unpleasant. "We don't take projects under $2,000, because we can't do them properly at that price" says something, and sounds like a person said it. We cover here how to optimize your contact.
Here's the fear nobody puts on their website. It isn't that a card number will get stolen. It's I pay these people and nothing arrives, or the slightly worse version, I pay these people and what arrives is worse than what I had.
That's the actual risk in buying a service, and almost every site answers it with a security badge, which addresses a completely different anxiety.
What answers it is structure. Four things, in rough order of how much they help:
Split the payment so the client is never far ahead of the work. A deposit and a balance, or monthly milestones. The point isn't the cash flow, it's that the client's exposure stays small enough to survive being wrong about you.
Write down what "done" means. A scope the client can hold you to is also a scope you can hold them to, and both of you benefit from that being on paper before anyone starts.
Say what happens when it goes wrong. How many rounds of revisions are included. What counts as a change rather than a fix. How either side gets out.
Offer an NDA before they ask. People about to describe their business to a stranger often want one and feel awkward raising it.
We ran the first engagement with our marine calibration client on a deposit model: half before the on-page SEO work started, half once it was finished. Now that the relationship has a history behind it, the ongoing off-page work and maintenance runs monthly, on milestones. The structure changed because the risk did.
Most businesses get the timing wrong on this. All of it sits in the proposal, which the client only reads after making contact, and the doubt they needed answering happened well before that.
This is the second of the two things to take off rather than add, and it's the easier one.
Go and count what's on your site right now. Most badge collections weren't decided, they accumulated. One came from the hosting company, one arrived with a plugin, one is from a directory somebody signed up to in 2021.
Then sort them into three piles.
Generic and self-issued goes first. A padlock graphic, "100% Secure", "Satisfaction Guaranteed" in a starburst, anything you could have made in Canva in four minutes. None of it is verifiable, so none of it is evidence, and past a certain number these raise the very question they were meant to settle.
Recognised third-party stays, if it's relevant to what you actually sell. On a service site that usually means payment logos, and only if you take payment on the page, which most service businesses don't.
Credentials are the pile that matters and the one service businesses consistently under-use. A Shopify or Webflow partner listing, a trade association membership, an ISO certification, professional indemnity insurance, a named qualification. They're checkable, they're specific to the work, and they answer the question a security seal never could. Not is this page encrypted, but do these people know what they're doing.
Two rules for whatever survives the sort. Put it where the anxiety actually is, which for a service business means beside the enquiry form or the pricing rather than in a footer strip repeated on every page. And check the dates on anything with an expiry. An expired certification is worse than no certification, because now the visitor knows you didn't notice.
The order is roughly the order above, because the early items are cheap and the later ones need decisions.
We start with existence, since it's the fastest to fix and the most commonly missing. Address, real names, real faces, a location stated plainly rather than implied. Then we look at what proof already exists but isn't on the site, which is usually more than the owner thinks — a client who said something useful in an email two years ago, a project with numbers nobody wrote down.
After that come the decisions, and these aren't design work. What you'll publish about price. Who you'll say you're not for. How the payment is structured so a first-time client isn't carrying all of the risk. Those conversations take longer than the build.
Then the subtraction: the logo wall, the badges, anything that's decorative rather than checkable.
If your site looks fine and the enquiries still aren't arriving, this list is usually where the problem has been hiding.
Do trust badges actually work?
At an ecommerce checkout, next to payment fields, when the visitor recognises the issuer — yes. On a service website with no checkout, mostly no. Recognition is what makes a badge work, and a seal nobody recognises does nothing at best. Credentials specific to your trade are a different thing and worth displaying.
How many testimonials do I need?
Three verifiable ones beat twenty anonymous ones. Verifiable means a full name, a company, and ideally somewhere the reader can confirm that person exists.
I'm a one-person business. Doesn't that look less trustworthy?
Less than a large agency, sometimes. Less than a business that won't say how big it is, never. Ambiguity is the thing that costs you, not size. Say what you are and let people decide.
Should I show my address if I work from home?
If you're comfortable with it, yes, and a city with a registered business address is usually enough. What damages you isn't a modest address, it's the absence of one, or a virtual office in a city where nobody actually sits.
Is it risky to publish prices?
You'll get fewer enquiries and better ones. If publishing a fixed price genuinely doesn't fit the work, publish a starting figure or a worked example instead. Saying nothing at all is the option that costs you.
Editorial Team
The AppDeel Editorial Team creates practical guides on website design, development, SEO, eCommerce and digital growth, combining our team's hands-on experience building and improving websites for businesses.
Read more posts by AppDeel Editorial Team →Technically reviewed by Azizul Hakim — CEO
Your site gets visitors but the form stays empty. These 7 reasons explain why people who could contact you don't and exactly what to change.
How to work out how long your site has actually been compromised, and why that answer decides everything else.
Google described our client's homepage as "Slide 1." Here is how design decisions quietly break SEO, and why website architecture should be planned first.
A breakdown of the fake Cloudflare verification scam hitting WordPress sites — how it hides from site owners, why security scanners miss it, and how we remove it.
Tell us about your business today — get a free quote within 24 hours. No pressure, no confusing tech talk.
