A good-looking gallery can still leave customers unsure
You have photos of finished work: a renovated bathroom, a newly landscaped yard, a logo on a storefront, or a completed repair. They look polished, so you add them to your website. Yet prospective customers still ask whether you handle projects like theirs, what was included, or whether you work in their area. Some leave without getting in touch at all.
The problem is not necessarily the quality of the photography. A gallery of unexplained images asks visitors to draw their own conclusions. A potential customer is trying to reduce risk before they contact you. They want to know whether you are a plausible fit for their situation, not simply whether you have completed attractive work before.
A useful project gallery is evidence, not decoration. Each entry should answer at least one real question: Do you provide this service? Have you worked on a similar type of property, business or brief? Can you handle a relevant constraint? What did you actually do? If an image cannot help answer one of those questions, it may still be suitable for social media or a private consultation, but it may not earn its place on a website.
This is narrower than adding general trust signals. A gallery should help someone compare their need with your demonstrated work, then take a sensible next step. For broader guidance, see How to Build Trust Online: 7 Website Elements That Turn Visitors into Customers.
Give every project one clear job
Start by reviewing individual projects rather than judging the gallery as a whole. A project can prove relevant capability, experience with a particular customer type, care with a visible finish, or a thoughtful response to a constraint. It does not need to prove everything at once.
For example, a hypothetical fence company could show one project to demonstrate cedar replacement work, another to show a gate configuration for a sloped yard, and a third to explain how it matched an existing fence. A caption saying only “Recent project” gives a visitor very little. “Replaced damaged cedar panels and adjusted the gate layout for a sloped backyard in southwest Edmonton” gives useful, restrained context.
Use only details you can state accurately. Avoid claims such as “the best result,” “guaranteed transformation,” or “increased value” unless you can substantiate them and they are appropriate to the project. Describe the scope, material, decision or visible outcome instead. This is more credible and more useful to a customer deciding whether to enquire.
A small gallery of three to six well-explained examples is often more useful than dozens of images with no context. It is also easier to keep current. If your work is visual, consistent presentation matters: image cropping, headings, captions and page hierarchy should support the business’s identity rather than compete with it. Thoughtful graphic design can help make those choices consistent across the website and other customer materials.
Do not make the image carry all the meaning
Important information should not exist only in a photograph. Someone may be using a screen reader, have a slow connection, be viewing a small screen, or simply not understand what a close-up image shows. Put the key context in visible text: the service, relevant scope and any decision that makes the project useful as evidence.
Alternative text, often called alt text, is a short description available to assistive technology when an image is informative. It should convey the image’s purpose in context, rather than mechanically list every visible object. For example, “Completed cedar gate matching the existing fence” may be more useful than “brown wooden gate beside a house.” If the image is purely decorative and the caption already provides the meaningful information, it should not create extra noise for screen-reader users.
This is not a request to turn every gallery item into a lengthy case study. A concise structure is enough: a clear project title, one or two sentences of context, and a next step for a similar customer. If a visitor needs more detail before making contact, link to a fuller project page or explain what happens when they request a consultation.
When planning a new gallery or improving an existing one, page structure matters as much as image selection. A custom website design process can help place project proof beside the relevant services and contact paths, rather than leaving it as an isolated photo page.
[Draft] Image Alternative Text - Easy Checks | Web Accessibility Initiative (WAI) | W3C
Treat permission and privacy as part of the process
A completed project can reveal more than intended. Before publishing, check for identifiable people, house numbers, street signs, vehicle plates, documents, computer screens, medical or other sensitive outcomes, and details a customer reasonably expected to remain private. A general area may be enough; a full address rarely helps a prospective customer choose a provider.
Canadian privacy guidance says meaningful consent is generally required for the collection, use and disclosure of personal information in commercial activities covered by PIPEDA. In practice, do not assume that permission to do the work also means permission to use images in marketing. Explain the intended use clearly, such as a public website portfolio and social media, and keep a record of what was agreed. Requirements can vary by province and circumstance, so seek qualified privacy or legal advice for uncertain or sensitive situations.
The safest option is not always to avoid showing work. It is to make a deliberate decision for each project. You might crop identifying details, use a general location, obtain clear permission, show the project only during a private consultation, or choose not to publish it. Be especially careful where an image could reveal a client’s identity, location, health information, security arrangements or personal circumstances.
This approach also protects the relationship behind the work. A customer who feels respected is more valuable than an extra gallery image.
PIPEDA Fair Information Principle 3 – Consent - Office of the Privacy Commissioner of Canada
PIPEDA requirements in brief - Office of the Privacy Commissioner of Canada
Run a 20-minute review before you publish
Choose three projects currently on your website, or three you intend to add. For each one, answer these questions: Is the service immediately obvious? Is this relevant to the customers we want to attract? Does the caption explain the starting point, scope or meaningful decision? Can a visitor understand the important point without seeing the image? Is every claim accurate? Do we have appropriate permission for this public use? Is there an honest next step for someone with a similar need?
Sort the result into four groups: keep and explain; keep but obtain clearer permission or remove identifying details; use privately in a consultation rather than publicly; or do not publish. This gives you a manageable improvement plan without requiring a complete website rewrite.
For future projects, keep a simple record with the customer’s problem or starting point, work completed, a relevant constraint, an accurate outcome, location at an appropriate level of detail, permission status and the next step for a similar customer. You will have better material when it is time to update your website, and less pressure to reconstruct details later.
If you have strong work but are unsure how to turn it into clear customer evidence, help with a project-gallery or case-study section can be worthwhile. The aim is not to make every project look dramatic. It is to make it easier for the right customer to recognize that your business may be a fit.