17.07.2026
Trust-building website sections: what to show customers
The phrase “you can trust us” does not answer the customer's questions. They want to see whether you have delivered similar projects, what the price includes, and how the work will proceed. Trust-building sections should provide these answers, not simply fill the page with badges and testimonials.
Start with four things: real work, clear terms, the collaboration process, and contact details. Below, we explain exactly what to show and how to check the finished page. Industry examples are illustrative: they are recommendations, not descriptions of our clients’ results.
1. Portfolio: show the task, not just the picture
Add a short explanation to each project: what the client commissioned, which part your team completed, what constraints existed, and what can be verified now. If you only did the design or a specific integration, say so. Do not take credit for the entire project.
For a construction company
Next to project photos, specify the type of work, materials, completion stage, and your scope of responsibility. Work-in-progress photos can help explain concealed work. Publish only materials you have the right to show; do not disclose the exact address of a private home without permission.
For a Restaurant or Cafe
Show an up-to-date menu with prices, your own photos of the dining area and dishes, opening hours, and reservation terms. If a table request still needs staff confirmation, the button and post-submission message must not promise an already-confirmed reservation.
For a website developer or service provider
Show the workflow relevant to the customer: product search, checkout, booking, or handling an inquiry. A link to real Web Alchemy projects provide context for the work completed. Interactive example helps test a specific feature, but demo data is not a client's result or proof of return on investment.
2. Price: explain the scope of work and the offer’s limits
A “from” label is not enough. Next to the price, list what is included in the base scope, what is charged separately, and what information is needed for a final estimate. For a website, this may include the number of page types, catalog population, payments, shipping, and CRM integration.
Separate one-time development costs from recurring expenses: hosting, the domain, licenses, and support. If the timeline depends on materials or client approval, state that condition. Our indicative pricing helps choose a format but does not replace an estimate for the specific task.
A guarantee should also be specific: what will be fixed, within what period, and what is excluded from support. Do not promise terms on behalf of a business that are not in the actual offer or contract.
3. Reviews and figures: keep only what can be verified
Publish a review with the author's consent, without changing its meaning. Add the service context and a link to the source if available. Do not rewrite a neutral comment as an enthusiastic review or use a fictional name or photo.
A business metric needs a time period, a source and a definition alongside it. A “lead”, a “qualified inquiry” and a “paid sale” are not the same thing. If there is no verified data on the website's impact on sales, describe the functionality delivered: for example, sending form submissions to a CRM. This is more honest than an unverified growth percentage.
Should you add star ratings to JSON-LD?
Do not add a rating just to get stars in search. According to Google's review guidelines, reviews of your own organization on its website do not qualify for review snippets for Organization or LocalBusiness. This also applies to third-party widgets displaying such reviews. Separate requirements apply to products.
General structured data guidelines require markup to match visible content. Even valid markup does not guarantee a rich result or a high ranking. Genuine reviews can be shown to people without promising Google stars.
4. Team and Contacts: Explain Who Is Responsible
Show real people only with their permission. If there are no photos yet, it is better to name the person responsible for communication and describe their duties than to invent a team. Customers need to know who agrees on scope, handles revisions, and helps after launch.
State next to the form what happens after submission and when a reply can be expected. Do not write “around the clock” if the team only works on weekdays. Check the phone number, email, successful submission message and receipt of the inquiry by the manager. Detailed steps are in the contact page checklist.
Where to place evidence on the page
- Next to a Specific Service: an example of relevant work, not the entire portfolio archive.
- Beside the price: scope, exclusions, and estimate conditions.
- Before an inquiry: the next step, response hours, and the responsible person's contact details.
- On the product page: the actual interface, compatibility, limitations, and a tested demo, if available.
On mobile, important labels must not be hidden behind floating buttons. Photos should open, links should be visible, and buttons should work with a keyboard. Do not hide essential terms only in a tooltip that appears on mouse hover.
Pre-publication check: six questions
- Is it clear to an outsider what you specifically did, rather than other project participants?
- Do you have permission to use the photo, name, logo and review text?
- Can you explain the source of every figure, its time period and how it was calculated?
- Can the customer see the price breakdown and next step without exchanging messages?
- Do the examples open, the contact methods work, and the test inquiry arrive?
- Does the visible information match the title, page description, and structured data?
Start with one verified example and clear terms. Add new work and reviews when they genuinely become available. If you need help with the structure, website development or sending inquiries to a CRM, contact Web Alchemy and specify which question the customer cannot resolve on the current page.