Plan website photos around the questions they answer

List the pages being built and the question an image could answer on each. A team photo shows who customers may meet. A process photo explains how work happens. A finished project shows an actual result. An exterior image can help visitors recognize a real customer-facing location.

For an illustrative repair business, the service page might need a clear view of the equipment and technician's work, while the contact page needs a recognizable entrance. Those are different assignments. A dramatic wide shot cannot always replace a practical detail image, and a stock image should not imply a completed customer project.

Describe the subject, intended page, orientation and any space needed for surrounding copy. Capture alternatives so the layout does not depend on one exact crop. Ask the photographer to preserve original files and deliver web-ready versions under an agreed usage arrangement.

Include the normal customer experience, not only polished portraits. Preparation, tools, materials and the handoff can reveal useful details. Keep confidential information, customer documents, screens, vehicle plates or addresses out of the frame when they are not approved for publication.

• People: the actual owner and team, with permission.
• Process: a truthful view of one important service step.
• Work: approved finished examples and relevant close details.
• Place: only locations the business can accurately represent.
• Flexible crops: horizontal and vertical options for important subjects.

Before the shoot, decide which customers, staff and locations can appear publicly. A picture existing on someone's phone does not establish the business's right to use it in advertising. Record the agreed usage and publication approval in the project assets.

Keep captions with the approved selections. They should explain what is visible without exaggerating scope or results. If an image demonstrates a process rather than documenting client work, describe it that way. If a detail matters to a buyer, put that information in the page text too instead of relying on the picture alone.

Check the crop on desktop and mobile before approving the page. Faces, tools or important work details should not disappear behind headings or buttons. Reduce unnecessary file weight while preserving enough detail for the image's job.

W3C explains that alternative text depends on an image's function: informative images need the meaningful information conveyed, while purely decorative images can have an empty alternative. Give the builder context so these choices are accurate. Do not fill alternatives with city names or unrelated sales keywords.

Keep an asset index with file names, approval and intended usage. When a service or team changes, that index makes it easier to identify the images that need updating.