A technician photograph helps a visitor understand who will arrive at their home. A tiny diagram with twelve unreadable labels gives that visitor little help. Both may have an image file, an alt attribute, and a place in your content calendar. Only the first has passed a useful editorial check.
Review images as part of the page's explanation. Ask what the visitor learns from the image, whether the image shows what the copy claims, and how someone who cannot see it receives that information.
Write alt text after looking at the image
Google recommends relevant placement, descriptive file names, and useful alt text, and warns against keyword stuffing. Its image guidance connects the image with surrounding content. Describe the actual visual in that context.
| Visible image | Useful alt text | What to avoid |
|---|---|---|
| A technician checking the filter in an indoor air unit. | Technician checking the filter in an indoor air-conditioning unit. | Claiming a repair, location, certification, or named person that the image does not establish. |
| A flow diagram showing a website inquiry entering a CRM review queue. | Website inquiry flows into a CRM review queue before a team member assigns it. | Repeating a list of SEO and CRM keywords. |
| A cropped screenshot with an error blocking a submitted booking. | Booking form shows an error after submission and leaves the request incomplete. | Calling it a successful booking because that would support the article's story. |
These examples describe hypothetical images. Replace the wording after inspecting your final asset. If the photographer captures a different action, change the description to match.
Some visuals serve decoration rather than information. W3C advises an empty alt attribute for decorative images in the appropriate context; see its decorative-image guidance. Treat a background texture differently from a diagram that carries the article's instructions.
Keep evidence readable without the picture
Suppose an article includes a chart comparing two reporting periods. Put the measured values, dates, metric definition, and decision in the page text or an accessible table. The reader should not have to zoom a picture to discover what the claim means.
For a screenshot, include a caption that identifies the relevant observation. Crop unrelated navigation and remove private information before publication. Do not replace a screenshot with a generated dashboard and present it as analytics evidence. An illustrative dashboard can support an example if you label the numbers and purpose as hypothetical.
A team photograph has a different acceptance test. Confirm that the people shown actually represent the team, that the crop works in the published layout, and that your organization has permission to use the image. A caption can identify the team without putting an employee biography into the alt text.
Run an image acceptance pass
- Purpose: Write one sentence explaining what the reader gains from this visual.
- Truth: Compare the visual, alt text, caption, and nearby claim. Resolve contradictions.
- Readability: Check the article at phone width. Rebuild diagrams whose useful labels disappear.
- Delivery: Confirm the file loads on the public page and ask the developer to serve dimensions appropriate to the layout.
- Fallback: Make the important information available in the page text if the image fails to load.
- Provenance: Keep the source file, usage permission, and any evidence period with the content package.
Use a descriptive filename that you can recognize during a content update. The repair photograph might become air-conditioner-filter-check.webp. Do not add a string of city names to the filename or alt text just because the service covers those cities.
Choose the smallest visual that explains the point
A short process often needs three or four labels. A comparison can use two clearly titled panels. If the article's useful object is a detailed checklist, keep the checklist in HTML and use the image to show its structure. That gives phone readers something they can read and copy.
For wider page checks, use the technical SEO checklist. The Ops Guide's SEO services can help review the content and website details customers encounter before they inquire.

