Where should trust signals actually sit on the page?

Above the fold, adjacent to every primary CTA and repeated through mid-page proof bands between major content sections. The footer is fine for the full certifications grid but it's the wrong place for the signals that close deals. We typically place four to six client logos or one to two hero certifications under the hero, a short proof statement next to every CTA ("Trusted by 12 of the FTSE 100" or "ISO 27001 certified since 2018") and quantified case study highlights mid-scroll. Buyers don't read pages linearly. They scan and decide at conversion moments.

Are stock photos of the team a real conversion problem?

Yes. IT directors notice when a "team" photo is clearly a model and they discount everything else on the page. The same applies to "happy customer" stock images and creative-agency-at-work shots. Three replacements that consistently work better. A genuine professionally shot team photograph. A real photograph of a client environment with permission. A clean illustration that communicates the service model. The credibility cost of fake imagery on a B2B tech site is higher than the budget cost of a half-day photo shoot.

Designing trust signals that convert IT directors

IT directors do not buy on a whim. They buy after due diligence, vendor research and at least one internal conversation about whether anyone has heard of you. By the time they reach your website, they are looking for reasons to believe (or reasons to disqualify). Most B2B tech sites we audit have plenty of trust signals, but they are buried, generic or misaligned with what the buyer actually trusts. The result is a site that has done the hard work of building credibility offline and squandered it online.

We have rebuilt sites for managed service providers ranging from regional firms like Acronyms IT Support to enterprise providers like Littlefish, and the trust signal patterns that move IT directors are remarkably consistent. Here is what works, why and where to put it.

What an IT director is actually checking

Before getting into specifics, it helps to understand what the buyer is checking when they land on your site. From the user research we have run with IT decision-makers, the questions are roughly:

Can I trust this vendor with our data and infrastructure?
Have they worked with businesses like ours, at our scale?
Are their certifications real, current and relevant?
Will I be able to defend this choice to my board, my CISO and my finance director?
If something goes wrong, who do I escalate to?

Notice what is not on the list. “Are their offices nice?” “Do they have a strong brand?” “Do their case studies have great photography?” Trust signals that do not answer one of the questions above are decoration.

The hierarchy of trust signals

Not all trust signals are equal. The hierarchy we work to:

Third-party verifiable certifications (ISO 27001, Cyber Essentials Plus, SOC 2, Microsoft Solutions Partner)
Named, recognisable client logos with consent
Quantified case studies with named individuals at named companies
Independent review platforms (G2, Gartner Peer Insights, Trustpilot, Glassdoor)
Industry analyst recognition (Gartner Magic Quadrant, Forrester Wave)
Specific operational metrics (uptime, response times, ticket SLA performance)
Press coverage in recognised publications
Generic awards (least valuable, particularly pay-to-enter awards)

Most B2B tech sites lead with the bottom of the list and bury the top. The fix is to invert this and make the strongest signals most prominent.

Placement matters more than design

Trust signals work positionally. A logo of a major client is worth nothing in a footer carousel that nobody scrolls to. The same logo above the fold, under the hero, anchors the entire page.

Our usual placement pattern for trust signals on B2B tech sites:

Above the fold: 4 to 6 client logos or 1 to 2 hero certifications, no more
Adjacent to every primary call to action: a short proof statement (“Trusted by 12 of the FTSE 100” or “ISO 27001 certified since 2018”)
Mid-page proof bands: between major content sections, breaking up the visual rhythm
Footer: full certifications grid, regulatory information, registered company details

The logic is that visitors do not read pages linearly. They scan, jump, skim. Trust signals at every conversion moment catch the buyer at the moment they are deciding whether to commit. We covered the broader product page architecture in designing product pages that close enterprise deals, the conversion structure in why MSP websites fail to convert and the specific hero pattern in what to put in an MSP homepage hero.

Specific signals that move IT directors

Cyber and infosec certifications

For UK-focused MSPs and IT services, Cyber Essentials Plus is table stakes. Without it you are disqualified by most public sector and enterprise procurement. ISO 27001 is the next tier and is increasingly expected. SOC 2 Type II matters for any business with US enterprise customers.

Display these as proper certification logos linked to the certifying body or your evidence page. Do not display the standard logo without context. “ISO 27001 certified since March 2019” is more credible than a logo on its own.

Microsoft, Cisco and other vendor partnerships

For MSPs and IT services, vendor partnerships are credentials. Microsoft Solutions Partner designations (with the specific solution areas), Cisco Premier or Gold, AWS Partner Network tier, Google Cloud Partner status. Display the current tier with the current logo (these change frequently and outdated logos hurt credibility).

Client logos with proof

A grid of logos is a starting point. A grid of logos with sector context (“Working with finance, healthcare, education and manufacturing”) is better. A grid with a click-through to a relevant case study is better still. Always check you have written consent to display each logo.

For enterprise buyers, sector relevance often beats brand recognition. An MSP showing logos from three Big Four accountancies will resonate more with a finance prospect than one showing logos of consumer brands the buyer has heard of but does not relate to.

Case studies with named people and quantified outcomes

A “satisfied customer” testimonial from “John, IT Manager” is worse than no testimonial. A named individual at a named company with a specific outcome is what carries weight. “James Kelly, Head of IT at [client], on reducing major incidents by 78 per cent in the first year” is the level of specificity that closes enterprise deals.

We have written separately about case studies that close, but the headline rule is: name names, share numbers and link to a full case study so the buyer can read more.

Operational proof

For service-led businesses (MSPs, IT support, managed services), operational metrics are powerful trust signals.

“98.6 per cent first-time fix rate”
“Average response under 11 minutes for P1 incidents”
“99.99 per cent uptime across managed cloud customers in 2025”

These are credible because they are specific. They invite the procurement question “how do you measure that and can we see the methodology”, which is a question you should be ready to answer.

Independent review presence

A G2 profile, a Trustpilot rating, a Glassdoor employer rating, a Gartner Peer Insights presence. These are external, harder to fake and signal that you operate in the open. A small linked badge to your G2 profile with the rating is more powerful than a 50-pixel star you designed yourself.

Trust signals for AI search and zero-click

In 2026, a meaningful share of buyer research starts in ChatGPT, Claude or Copilot, not Google. The trust signals that influence which vendors get cited by AI assistants are different from the ones that influence Google rankings. They include:

Mentions in third-party industry publications
Press coverage and analyst reports
Wikipedia presence (where editorially appropriate)
Independent review platform presence
Strong, structured About and Team pages with named individuals

We unpack this in auditing visibility in Copilot and ChatGPT, brand mentions versus backlinks for AI and E-E-A-T for tech companies. The implication is that offline credibility now feeds AI visibility, so PR and analyst relations pay back through both organic search and LLM citations.

Common trust signal mistakes

A few patterns we see repeatedly that undermine credibility.

Over-claimed credentials

“Award-winning” with no named award. “Industry-leading” with no benchmark. “Trusted by hundreds” without naming any of them. Vague claims trigger scepticism. Specific claims (with proof) build trust.

Mismatched logos

A homepage with logos of Fortune 500 brands and case studies featuring 50-person businesses. The mismatch is obvious and reads as either logo-padding or unfocused positioning.

Stale evidence

A homepage testimonial from 2018 dated by reference to the writer’s job title since changed. Five-year-old case studies linked from “recent work”. Awards from defunct programmes. Trust signals expire and the maintenance cadence matters.

Stock photography pretending to be staff

The team page with “creative agency at work” stock photography. The “happy customer” image that is clearly a model. IT directors notice this and discount everything else on the page.

Defensive language

“We pride ourselves on” and “We strive to deliver” are filler, not trust signals. Replace with specific, externally validated claims.

Building a trust signal asset library

A practical exercise we run with marketing teams is to audit and structure trust assets as a library, owned by marketing and refreshed quarterly:

Current certification logos with expiry dates
Approved client logos with consent records
Quotable testimonials with permissions
Quantified case study highlights
Operational performance numbers, sourced and dated

This becomes the source of truth for the website, sales decks, proposals and bid responses. It also surfaces gaps so you can plan ahead.

Where it fits

Trust signals are part of a wider conversion strategy. They have to be supported by a fast and accessible site, strong content marketing and a coherent positioning. They will not save a site that loads in seven seconds or pages that fail WCAG basics, as we covered in the page speed checklist.

If you are rebuilding key pages and want a second view on the trust architecture, start a conversation with us. Our 30-minute calls usually surface a couple of placement changes worth testing immediately.