Prepare project photographs for image SEO by deciding what each image needs to explain, then coordinating the crop, web dimensions, filename, alternative text and surrounding page content. A photograph should help a prospective customer understand the work, your contribution and its relevance to their own needs. A striking image with no useful context can leave those questions unanswered.
A project folder may contain twenty attractive photographs of almost the same scene. Publishing all of them is rarely the most helpful choice. A smaller selection showing the overall result, an important detail and the work in use can tell a clearer story. This guide offers a practical workflow for agencies, design studios, manufacturers and service businesses. Dimensions, file sizes and project scenarios below are illustrative examples, not search engine requirements or reported client results.
Start the shot list with customer questions
A list of wide shots, close-ups and process photographs is a useful production starting point. Add a question to every planned image: what does the visitor need to understand from this view? They might be evaluating a material, trying to judge scale or checking how a finished item works. An additional wide-angle photograph will not answer a question that requires a clear view of a connection or component.
Consider a hypothetical packaging project. A closed box shows the overall appearance, an open view explains the arrangement inside, and a close-up reveals a finish or printed detail. None of these photographs, by itself, demonstrates that the packaging passed a shipping test. A durability claim requires separate, verified evidence. The guide to unboxing experience and shipping protection helps distinguish presentation decisions from protection requirements.
A useful initial selection might include:
- One image that makes the whole project easy to understand.
- Two or three details that matter to a customer's decision.
- A contextual view that explains scale or use.
- A genuine process photograph, where the process needs explanation.
- An alternative composition that remains useful in a mobile crop.
These are roles to consider, not a minimum image quota. A simple project may need only two photographs. A more complex installation may require several views with different explanations. When discussing photo and video production, share the intended page layout and the questions the images must answer. That gives the production team a clearer brief than a request for a large collection of impressive pictures.
Keep a project record alongside the image collection
Create a short record with the project name, date, agreed scope, information approved for publication and a note explaining each selected image. The person publishing the page may not have attended the shoot. Folder names such as “final selection” or “latest version” become ambiguous as soon as another revision arrives.
Be precise about your contribution when several businesses worked on the same project. Designing the packaging is different from manufacturing the product. Photographing a completed interior does not mean your business designed the architecture. The page description should establish the actual scope rather than allowing the image to imply broader responsibility.
Record publication conditions before the release. A photograph can contain faces, registration plates, screens, private documents or products that have not been announced. Ask the responsible person to confirm what may appear and remove unnecessary sensitive details from the composition where possible. This is a general editorial check, not a legal determination of usage rights; specific rights questions may need professional advice.
Make the handover understandable to someone outside the original team. A simple list linking an image identifier to its subject, intended placement and approval status can prevent a future editor from publishing the wrong version. Keep the original source separate from the versions prepared for the website so that later crops do not repeatedly degrade an already compressed file.
Select for useful evidence before editing for appearance
Remove blurred, poorly focused and repetitive images first. Also remove technically polished photographs that hide the detail the customer needs to see. The selection should be reviewed by someone who understands the product or project, as well as someone assessing visual quality. Those are different responsibilities, even when one person performs both.
Colour correction should make the photograph useful without misrepresenting the material. Fabric texture, packaging colour and surface finish can affect a buying decision. Strong contrast or sharpening may look attractive in a thumbnail but produce artificial edges at a larger size. Check the result in the intended page context, not only in the editing application's workspace.
Perspective correction and considered cropping can improve clarity. Adding an installation that was never completed, concealing a defect while presenting the image as proof of successful delivery, or using a stock photograph as a real project record changes the meaning. Label visualisations and illustrative mockups clearly. Visitors should be able to distinguish a photographed result from a proposed design.
Treat pixel dimensions and transfer size as different decisions
Pixel dimensions describe width and height. File weight describes how much data must be transferred. Two photographs with the same dimensions can have very different file sizes because their detail, format and compression differ. Reducing an image to a particular width does not, by itself, establish that it is suitable for the page.
As an illustrative example, an image displayed at 800 pixels wide on a desktop layout might also need an appropriate version for a higher-density screen. That does not mean every phone should receive the same large file. The web.dev explanation of responsive image sizing describes how browsers can choose between supplied image widths. The website template must support that behaviour as well as the production process.
Judge the combined gallery load, not just each individual asset. Eight photographs at 250 KB each add up to roughly 2 MB before other page resources. This calculation is a planning example rather than a universal performance target. It helps expose the cumulative effect of a gallery whose individual files appear modest.
Compare JPEG, WebP or AVIF versions at the size customers will actually see. The best choice depends on the image, the export tools and what the website can deliver reliably. Examine small lettering, product edges and smooth colour transitions. A smaller file that removes a meaningful product detail is not a better editorial result. A heavy PNG for a photograph that does not need transparency also deserves review.
Avoid setting one export rule for every placement. A small project card and a large detail view serve different purposes. Agree on a few supported uses with the design and development team, then prepare the necessary versions consistently. This keeps editors from improvising a new size for every upload and helps make future replacements predictable.
Give filenames, alternative text and captions distinct roles
A filename is a concise identifier for the asset. Alternative text explains the image's information or function in its particular context. A visible caption supplies project context for readers. Copying the same keyword list into all three fields does not make the page clearer. Decide what each field contributes before writing it.
For a hypothetical ceramic mug package, a filename could be “ceramic-mug-box-internal-support.webp”. Suitable alternative text might be “Cardboard insert holding a ceramic mug inside its box”. A visible caption could explain the design decision behind the arrangement, provided that explanation is accurate. Do not add an untested protection claim simply because the photograph looks convincing.
Google recommends descriptive filenames and relevant alternative text, with surrounding content helping explain the subject. Repeated keyword lists are not the purpose of those fields. Consult the Google image SEO guidance when reviewing implementation. Renaming files alone does not provide a ranking guarantee.
Informative and decorative images also need different treatment. W3C recommends an empty text alternative for purely decorative images, while an image acting as a link or button needs text that conveys its function. The W3C images tutorial explains these distinctions. Choose according to the image's role on the page, rather than applying the same description to every occurrence.
A useful editorial question is: what would a reader miss if this photograph were unavailable? Write that information naturally, then read it aloud. If the sentence becomes a sequence of brand names, locations and service terms, it probably needs another edit. Preserve the important detail without attempting to catalogue every object in the frame.
Place photographs where their explanation belongs
A gallery does not have to carry the entire project story. Give the page a short explanation of the need, the scope of work and the decisions that matter. Place the relevant photographs near those explanations. A close-up of a construction detail buried inside a general company introduction may look attractive while providing little useful evidence.
Arrange the sequence around understanding: establish the overall result, show the important detail, then add use or process context where needed. Keep an extra angle only if it supplies information the reader would otherwise lack. Most projects do not need a separate thin page for every photograph. A coherent project page is usually easier to maintain and review.
If the portfolio connects with a product catalogue, distinguish their roles. The project explains how a particular need was addressed; the product page supports selecting a specific item. The guide to category, product and filter pages helps place images within the appropriate customer journey. Link related information where it assists a decision rather than creating another gallery solely to target a keyword.
Check delivery behaviour with the development team
Compressing a file cannot fully compensate for an unsuitable loading sequence. The main image visible on arrival and a photograph near the bottom of a long gallery do not need identical priority. Largest Contentful Paint, or LCP, measures when the largest eligible visible content element is rendered. The LCP optimisation guide explains why delaying a main image through lazy loading can be counterproductive.
Images further down the page may benefit from deferred loading. Separately, the layout needs to reserve the appropriate image space so that text and controls do not move unexpectedly when a file appears. Ask the developer to review both issues. The image performance guidance describes loading behaviour and layout stability in more detail.
An editor can still conduct a useful acceptance check without changing code. Open the page on a phone, read the initial explanation, move through the gallery and return to the main content. Can you understand the project before every image has loaded? If an enlarged view opens, is the way back obvious? Evaluate those tasks alongside technical measurements.
Do not assume that a setting named “optimisation” implements the right behaviour everywhere. Ask for a demonstration using the actual project template and representative photographs. The outcome should be an understandable acceptance result: the important image appears promptly, its detail remains usable and the layout remains stable while the rest of the content loads.
Maintain consistent facts across languages
Turkish and English project pages should describe the same work. Wording can change to suit the reader, but the materials, dates, contribution and scope should remain consistent. Adding an unverified overseas office or delivery capability to an English version is not localisation.
Write alternative text in the language of the page. Use natural product terminology rather than translating word by word when that produces an awkward description. Before creating duplicate image files for each language, establish how the site's image management works. Do not break existing image addresses simply to introduce a preferred naming convention.
Ask someone reviewing the language version to check the photograph and caption together. A translated sentence can be grammatically correct while referring to a different component or implying a different project stage. Shared visual evidence makes these inconsistencies easier to catch before publication.
Follow one image through the entire publishing process
Before checking a large collection superficially, follow one representative image from the project record to the live page. Confirm that it belongs to the right project, that the crop preserves its meaning and that its explanation is correct. Then apply the same checks to the remaining selection. This reveals mistakes introduced between a well-organised folder and the website.
A practical handover includes:
- The location of source assets and the approved web versions.
- The intended page and role of each selected image.
- Approved filenames, language-specific alternative text and necessary captions.
- The person responsible for colour, cropping and factual checks.
- Any unresolved mobile, loading or navigation issues.
Include those deliverables in the scope for a corporate website and online store. Producing a photograph, writing its context and placing it correctly in the system are separate tasks. “Images to follow” is not an adequate owner or acceptance condition for any of them.
Improve an existing gallery in a manageable sequence
Choose an existing project page where a visitor's decision is difficult, ideally supported by relevant traffic or search impressions. If the sequence is confusing, improve the selection. If a necessary detail is missing, locate an appropriate source image. If the page is heavy, inspect the actual versions being delivered. Changing every filename, layout and paragraph simultaneously can make the result harder to interpret.
Record the problem, the change and the observed outcome separately. “The mobile crop hid the internal support; an alternative crop was supplied and checked” is a useful maintenance note. “SEO completed” does not tell the next editor what happened. Assign unresolved template behaviour to the appropriate technical owner rather than marking it complete because the content editing is finished.
Measure relevant visibility without overstating the result
Record the page's search queries, impressions and clicks before the change. If you examine image search, state the search type explicitly rather than combining it with the Web report as though both measured the same activity. Where the title, copy and internal links changed at the same time, do not attribute every movement to the photographs.
A few clicks over a week rarely justify a confident conclusion. Compare suitable complete periods and examine whether the queries relate to the services you actually provide. Review useful onward journeys and verified enquiries where measurement allows. An event that has not been tested does not establish that the business received no customer interest.
An image sitemap can help with discovery, but it does not guarantee indexing. If the implementation uses one, check it against Google's image sitemap documentation. A sitemap does not repair an inaccessible file or supply the missing explanation on a project page.
When discussing SEO and organic visibility with WeAreMedia, bring a representative project page, photographs approved for publication and the questions prospective customers need answered. A useful review should identify which images to retain, which explanations are missing and which delivery behaviours need testing. That creates an actionable next step rather than stopping at a list of renamed files.