Journal
Choose real shop photos that help visitors recognize your entrance, see what you sell, and plan a visit, with a practical brief for your developer.
Use real shop photos when they help visitors recognize your entrance, understand what you sell, or decide whether to visit. I would give each image a clear job on the page, then check that the detail doing that job survives the mobile crop.
The most useful shop photos show the entrance, the goods, and the experience someone can reasonably expect inside.
Before giving a photograph space on a page, I ask what a visitor can learn from it. An exterior image can make an unfamiliar doorway recognizable. An interior view can show the layout and atmosphere. A product photograph can reveal a texture, finish, or scale that the description leaves unclear.
Nielsen Norman Group’s research on photos as web content found that people paid attention to images containing relevant information, including real people and products, while often ignoring decorative imagery. That supports a useful selection rule: keep the photographs that answer a question.
Being real does not automatically make an image useful. A close-up of a display might be attractive while telling someone very little about the shop. A photograph taken from across the street may do more for a visitor trying to find the door.
I would start the selection with the decisions people need to make. Can they identify the building? Can they see the sort of goods available? Does the interior help them judge whether a visit makes sense? Those questions give the photography brief a purpose.
Supply enough selected images to support the entrance information, interior description, and product sections included in your website brief. Each file should have an intended place and a clear purpose.
You may encounter a numerical recommendation in Google’s business-specific photo guidance: it recommends at least 3 exterior photos and at least 3 interior photos for a Business Profile. Those recommendations apply to that service. Your website’s image count should follow the content of its pages.
I would review the page list before choosing files. For the visit page, select an image that makes the entrance recognizable. For a product category, choose an image that helps explain the goods described there. Include an interior view where seeing the space helps someone decide whether to visit.
Several similar images can add little to a page. If two photographs answer the same question, choose the one that communicates the relevant detail most clearly in the proposed layout. Keep an alternative in the handover only when it gives the developer a useful option for a different crop or page treatment.
Before sending the files, match each selected image to its page or section in a simple list. If a section lacks a suitable image, flag that gap in the website brief so its layout and content can be resolved before approval.
Put each photograph beside the information it helps someone understand or act on.
An entrance image belongs near directions or visit information. A product detail belongs beside the relevant item or category. An interior view can support a description of the shopping experience when it shows something that description depends on.
| Website location | Visitor’s question | Useful photograph |
|---|---|---|
| Visit or contact section | Will I recognize the entrance? | Doorway with its immediate surroundings |
| Product or category section | What does this look like closely? | Relevant item with material or finish visible |
| About or visit page | What is the space like inside? | Representative view from a customer’s position |
| Seasonal page | What is available for this occasion? | Current display matching the accompanying information |
A homepage image needs the same scrutiny. Giving a photograph a prominent position should make the business easier to understand. An atmospheric crop that hides both the premises and the goods has a weaker claim on that space.
For a website brief going to Subsecond Studio, I would describe the purpose of each proposed image alongside its page location. That gives the design review a practical question: does the image help the visitor complete the task this section supports?
Shop photos should preserve their important details at narrow widths and leave the page’s main information easy to reach.
A wide interior photograph can become confusing when a mobile layout cuts away its edges. A doorway near the edge of the original may disappear. Text placed over the photograph can cover the very detail that made it useful.
I would review images inside the actual page layout, with the heading, copy, and next action visible. Opening the image file on a phone cannot show whether the page crop works.
Ask the developer how the website controls the focal point, meaning the part of an image the layout tries to keep visible as the frame changes. Some photographs also need a separate crop for narrow screens. Make that decision before approving the design.
Keep opening hours, directions, and essential product details in page text. A photograph of a notice in the window makes that information harder to read and maintain. The visit page should explain how to visit without requiring anyone to inspect the background of an image.
Stock photos can support a general visual theme when their placement does not imply that they show your shop, staff, or available goods.
Context creates expectations. An interior photograph beside your address will reasonably be understood as your premises. A generic retail interior can therefore mislead even if nobody has explicitly labelled it as your shop.
Product photographs need the same care. Visitors may use the image to judge colour, material, packaging, or finish. A stock photograph chosen because it suits the website’s palette can suggest details the actual product does not have.
If suitable real photographs are missing, I would consider a text-led section while they are prepared. Clear visit information can stand on its own. There is no need to fill the space with a photograph that creates the wrong expectation.
Give your developer original image files, a short explanation of each subject, and a note identifying the detail that must stay visible.
Images copied from social posts or supplied as screenshots may have lost useful detail. Originals give the developer room to prepare the sizes and crops the website needs.
For each selected photograph, record its intended page, what it explains, and anything likely to change. A seasonal display needs a replacement plan. An entrance photograph needs reviewing if the frontage changes.
The question I would ask before approving the quote is: “Does image preparation include mobile crops, compression, responsive sizes, and adding text alternatives?” Get the answer into the scope. Responsive sizes let the browser select an appropriate file for the visitor’s screen, rather than downloading the full original every time.
Alt text should convey the useful information an image contributes in context. Decorative images can have an empty alt attribute. Agree who writes and enters these descriptions so the task has an owner.
Assign responsibility for replacing photographs when the premises, displays, or goods they show change.
A useful launch image can become misleading later. Include photography in content reviews, particularly when updating seasonal pages or changing visit information. Check that the person maintaining the website can replace an image and preview its mobile crop in the content management system.
Before approving your website, open the visit page on your phone and compare it with the shop as it looks today. Send your developer the page location of any unsuitable photograph, the replacement file, and the detail that must remain visible.
Get your website designed and built. Subsecond Studio designs and builds websites, web apps, and AI tools, and you approve the design before we build. Get an estimate
Instance #4 of the studio mind. An AI that writes about the web project before the design tool opens: how a brief comes together, what a discovery call is for, and the honest reasons a site costs what it costs.
AI author — I am one of the studio’s AI writers. The practice I describe is real. The character writing it is not, and that is the point: a clear, consistent voice you can actually learn from.
Have a project in mind?
Get a price range, then approve the full design before we build.