If you are buying a website for a local business, the photo decision begins before the designer opens a layout file. A visitor may be deciding whether you serve their kind of job, whether the team looks familiar, or whether a location is accessible. A generic hero image can fill space without answering any of those questions. The goal is a small set of accurate images, each attached to a buyer decision and a page that can be maintained.
This guide is an acceptance tool for your own photo collection or a quoted photography task. It does not claim Zendory photographed a customer business or tested one site's conversion. The worked example below is hypothetical, and the demand for this exact query is a research hypothesis rather than measured search volume.
Start with the question each page must answer
Write the page's customer question in one sentence. A homepage may need to show what the business actually offers and who it serves. A service page might need to show the work area, a completed deliverable, or the person who visits a customer. A location page may need the real entrance or parking approach. A booking page may benefit from a clear explanation of the next step more than another decorative portrait. If the image cannot help a visitor understand that page, it has no guaranteed place simply because it looks polished.
Separate evidence from atmosphere. An actual team photo can identify people; a properly licensed stock image might set a mood but cannot prove who will arrive. A project photo can show the kind of work done only if its subject, date, rights, and context are known. A dramatic “after” image can imply a typical result that the business may not be able to support. Keep the service description and contact path in text so the page still works when an image is slow or unavailable.
The broader website content brief helps decide which page facts to collect. This guide handles the separate task of choosing and accepting visual evidence for those facts.
Use a six-field photo acceptance matrix
Make one row per candidate image. A shared spreadsheet is enough. Mark any unknown field “hold” and ask for evidence before the asset reaches the live site.
| Field | Record | Acceptance question |
|---|---|---|
| Original and date | File name, source, capture or receipt date, and unedited original | Can the business find the source again? |
| Subject and claim | Who or what appears, where, and which service fact the photo supports | Would a visitor infer something true today? |
| Rights and privacy | Photographer license, subject or property permission where needed, and allowed uses | May this exact image appear on this public page? |
| Page purpose | Target page, buyer question, nearby text, and desired next action | Does the image clarify that decision? |
| Crop and text | Important subject boundaries, phone crop, intended alternative text, and any text inside the image | Does meaning survive mobile, zoom, and image failure? |
| Owner and review | Approver, accepted version, review date, and replacement contact | Who corrects it when staff, premises, or service changes? |
Do not infer permission from a photo being public on a social account. Check who made it, who or what it depicts, and the intended website use. Where a customer, employee, child, private property, or sensitive job is involved, use the business's consent and legal process. A designer can flag missing permission but should not invent it. Keep the approval record with the site's handoff so a later owner can replace an image without losing its context.
Work through a hypothetical service-page choice
Imagine a local appliance-repair company buying a new service page. It has three candidate images: a real technician checking a dishwasher in a customer's kitchen with documented permission, a polished stock photo of a large workshop the company does not own, and a blurry phone photo of a finished installation. These are invented candidates for the method, not Zendory customer assets or measured performance results.
The real technician image can answer “what will a visit look like?” if the depicted service and uniform still match the current business. The workshop image should not be presented as the company's facility; even if licensed, it could create a false impression. The blurry installation photo may not show enough detail to explain the work. The owner could approve the first image for the service page, omit the other two, and ask for a new photo of a completed repair if that proof is important. The acceptance record should say why, not merely mark a favorite.
Now test the approved image in the proposed layout. At phone width, does the crop cut off the technician's hands or the appliance, leaving an unhelpful portrait? Does an overlaid headline cover the only useful part? The designer can change layout and crop, but cannot make a low-resolution original reveal detail that was never captured. If the photo fails in context, the right action may be to request a different source rather than apply more editing.
Check discovery and accessibility without inventing SEO value
Google Search Central's image guidance explains that image discovery depends on accessible image URLs and the landing page context, among other technical requirements. Descriptive surrounding copy and appropriate image markup help explain what a real image shows. None of that makes a stock photo into first-party evidence, and no file name or alt-text formula guarantees image-search traffic.
W3C's alt decision tree asks what function the image performs. If the photo conveys information not already in nearby text, write a concise text alternative that communicates that information. If it is purely decorative, an empty alternative can be appropriate. If text embedded in the image carries necessary meaning, the same information must be available to people who cannot see it. Review the actual page; “photo of business” repeated on every image helps nobody.
Ask the provider to show the final page with images loaded, delayed, and unavailable. The heading, service scope, location, and contact action should remain understandable. On a phone, verify that the important subject is visible without horizontal scrolling, that text has readable contrast, and that tapping the action does not depend on the image itself. These checks prove usability of the finished page, not an SEO ranking gain.
Accept the site against the photo record
- Open each original and the proposed live crop side by side. Confirm the subject, current service, location, and any visible name or logo.
- Check the rights record and the approved use. Hold any image with uncertain permission or an implied claim the business cannot support.
- Read the nearby heading, caption, service details, and alternative text together. They should describe the same real thing without adding a guarantee the image cannot prove.
- Load the page on a phone and desktop, then with images unavailable. The buyer question and next action should remain clear.
- Save the accepted image version, approver, and review date. Assign a person to replace images when staff, premises, equipment, or service terms change.
If the business lacks a suitable image for a high-value decision, launch with clear text and a truthful placeholder treatment while planning an approved shoot. Do not imply a stock subject is the real team or publish an invented result to fill the grid. The website launch checklist covers the wider release, including working links and handoff. Compare Zendory's website-build options with the photo matrix so the scope includes the real sourcing, permission, crop, and review work your pages require.