Ecommerce photography should answer the questions a buyer cannot resolve from a product name: what is included, how the item differs and which details matter. Plan those questions before taking photographs, then check the delivered crops and page markup. A useful image set combines accurate product evidence with accessible descriptions and responsive files that remain clear on smaller screens.
Begin with the product itself and the information the page needs to communicate. A consistent background can make a catalogue easier to browse, but visual consistency should preserve the distinctions that matter to a purchase. A close detail, an included accessory and a different variant each have a separate job. Give every proposed frame a question to answer.
The original shot-to-page worksheet below uses a hypothetical shoulder bag. The technical guidance comes from Google Search Central and the W3C Web Accessibility Initiative, read on 24 October 2026. For the broader store presentation, see online stores and web development.
Which buyer questions belong on the shot list?
For the sample bag, a buyer might need to see the opening, the fastening, the internal compartments and the parts included with the product. Write those questions in the first column of the shot list. In the second, describe the frame that would answer each question. This makes the brief assessable: the photographer and catalogue owner can agree whether the resulting picture supplies the intended evidence.
Identify the exact sample and variant before capture. Keep a simple private record connecting the sample identifier, image files and product record. When the catalogue owner approves the set, ask them to check that the visible item corresponds to the listing. This is a proposed editorial practice for accuracy, rather than a technical feature supplied by the sources.
Use props thoughtfully. If an object is present only to suggest scale or demonstrate use, make its role clear in the surrounding copy where needed. The image set and product description should agree on what the purchase includes. Avoid allowing an attractive arrangement to create an expectation the actual product information cannot support.
| Buyer question | Proposed frame for the sample bag | Delivery check |
|---|---|---|
| What is the overall shape? | Clear front view | Full outline remains visible in the card crop |
| How does it open? | Opening and fastening detail | Important edges remain readable on mobile |
| What is inside? | Interior view with compartments visible | Lighting reveals the relevant space |
| Which variant is this? | Consistent view of the selected variant | File is mapped to the intended product option |
| What is included? | Agreed arrangement of supplied parts | Description and photograph identify the same contents |
| How is the image used? | Product evidence or linked card | Text alternative matches the image’s purpose |
Treat this as a working brief. Adapt the questions to the product instead of assuming every catalogue needs the same number of photographs or an identical sequence.
How should photographs reach search crawlers?
Google can discover images through the src attribute of an HTML img element. Google does not index CSS background images. Its image SEO guidance therefore makes the delivery method part of the image review. Inspect how the primary product image appears in the page source, alongside how it looks in the browser.
Google recommends a fallback src URL when responsive-image attributes are used. Google describes srcset as a way to provide versions for different screen sizes. Keep the approved master separate from the files intended for page delivery, then have the implementer show how the page selects among the derivatives. Review the actual downloaded file in the intended viewport rather than judging performance from a filename.
Google Search supports JPEG, PNG, WebP and AVIF among its image formats. Format support is one part of the decision; the subject, transparency needs and visible quality still matter. Compare a proposed derivative with the approved master at the size in which it will be used. Set a delivery requirement from that comparison and the measured page, rather than inventing a universal file-size limit.
Google recommends placing images near relevant text. A detail photograph should therefore sit where the relevant feature is explained, or be clearly reachable from the image set. Help the reader connect the picture to the question it answers. This also gives the catalogue reviewer a practical way to identify a missing caption or a misleading image association.
What should the text alternative communicate?
W3C recommends a short description of the essential information for informative images. Its images tutorial bases the text alternative on purpose and context. For a sample interior photograph, identify the visible arrangement that matters to the page rather than repeating the product name without adding information.
W3C recommends an empty alt attribute for purely decorative images. Decide whether the image genuinely adds no information before applying that treatment. A background flourish and a photograph showing the fastening have different roles even if both improve the appearance of the page. Keep the decision with the content owner who understands what the picture is intended to communicate.
W3C says a linked or button image’s alternative should describe its function. A product card that opens a product page needs that purpose to remain understandable. Inspect the combined link text and image alternative in context, particularly where the same card contains both a photograph and a visible product title. Aim for a clear destination rather than needless repetition.
Google advises against keyword stuffing in image alt attributes. Write for the person who needs the image’s information. Include the relevant feature or function honestly and leave unsupported characteristics out. The text should describe what the page can substantiate, not add sales claims that are absent from the photograph and product record.
How should a crop review be organised?
Review the catalogue card, product gallery and any approved sharing image separately. A crop that works for a close-up gallery slide can remove the outline needed in a small catalogue tile. Begin with the buyer question assigned to the frame, then ask whether the crop still answers it at the intended size.
For the sample bag, inspect the opening and fastening in the narrow mobile view. If a crop removes the clasp, choose another derivative or a different framing decision. Record the approved crop against its intended use. Keep the original photograph available so a future layout change does not require reconstructing detail that has already been discarded.
Use a real device or an appropriate browser viewport to inspect the result. Record the viewport, delivered file dimensions and measured transfer size in the delivery sheet. These are useful observations once the test is run; the worksheet itself does not supply them. Let the observed clarity and performance guide the next adjustment.
Original shot-to-page acceptance worksheet
For each approved frame, retain the buyer question, sample identifier, master filename, product mapping, intended crop, text alternative and delivered derivative. Add an approval owner and an observed-result field. This creates a chain from the original brief to the image the customer actually receives.
Walk through one complete product before applying the method to the wider catalogue. Ask the product owner to confirm factual accuracy, the content reviewer to check the question and description, and the implementer to inspect markup and delivery. Record unresolved points with their owner so that the next person knows whether the issue concerns the sample, the crop or the page implementation.
Use the worksheet to commission or assess imagery with a concrete purpose. For discoverability beyond the image itself, see SEO. To discuss the product questions and delivery requirements, get started with a representative product and the proposed shot list.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.