Start with the image’s job in the article. Keep a screenshot if it helps explain a feature or task; give it alt text for the information it adds. If a cover only repeats the visible title, treat it as decorative and use an empty alt attribute. Name the files clearly, place useful images beside the explanation they support, then check the public page—not just the draft—to see what readers and search engines can access.
Choose images that help answer the question
Before adding an image, ask what a reader would miss if it disappeared. A screenshot can show where a control sits or what a result looks like. A diagram can make a sequence easier to follow. If neither adds anything beyond the prose, the image may still suit the design, but it does not need the same text treatment as an informative image. W3C distinguishes images that convey information from images included for visual appeal or whose information is already in adjacent text.
For a SaaS walkthrough, crop a screenshot around the control and result the paragraph discusses. If a reader needs a detailed explanation of several tiny interface elements, put that explanation in the article rather than expecting one short alt attribute to carry the whole walkthrough. Keep any labels needed to follow the step legible at mobile width.
Give each file and text alternative a clear purpose
Use a short filename that identifies the image, such as onboarding-overdue-task-filter.png, rather than final-v3.png. The filename helps your team recognize the asset; it is not a substitute for explaining the image on the page. Write alt text in the context of the article: W3C advises that an informative image’s alternative convey the meaning it adds, not merely list everything visible in the picture.
Here is a fictional example: an article explains how to find overdue tasks in an onboarding dashboard. Its screenshot shows the Overdue filter selected and the resulting task list. The branded cover displays only the article title and decoration, while that title already appears as text above it. The choices below depend on those roles, not on whether an image is called a “cover” or “screenshot.”
For the title-only cover in this example, use alt="" if it is rendered as an HTML image. W3C recommends an empty alt attribute for an image that adds no information beyond nearby text; omitting the attribute is different, because some screen readers may announce the filename. If your cover instead contains a distinct message that the article does not state, describe that message rather than automatically making its alt empty.
| Image and job | Filename | Alt attribute | Nearby article text |
|---|---|---|---|
| Screenshot: show the selected filter and result | onboarding-overdue-task-filter.png | alt="Overdue filter selected in the onboarding dashboard, showing tasks that still need attention" | Explain when to select Overdue and what to do with the resulting tasks. |
| Cover: repeat the visible title as artwork | onboarding-tasks-cover.png | alt="" | Keep the article title in readable page text. |
Publish, then inspect the live article
Before release, check that the chosen files, filenames, alt values and accompanying explanation are present in your draft or site build. Then publish the article and its image assets together. A preview can show your editorial intent, but the public URL is where you can confirm what actually shipped.
Open the published article on desktop and mobile. Check that each image loads, that screenshot labels remain readable, and that the screenshot sits near the paragraph explaining the filter. Google notes that the content of a page containing an image can affect how that image appears in search, so give the screenshot meaningful surrounding text rather than leaving readers to infer its purpose from the file alone.
Finally, inspect the live image elements, not just their appearance. Confirm the screenshot has the intended alt value and a working image URL; confirm the decorative cover has alt="" rather than a missing alt attribute. If you want an image to be discoverable through Google Images, ask your developer to check that the published image is supplied through an HTML img element with a src URL. Google says it can find images in img elements, including those within picture, but does not index CSS background images.
Keep on-page images separate from social previews
Ranks offers branded article covers and says you can review and edit articles before publishing on your own blog. That makes the cover worth checking as part of the article, but it does not establish the filename, alt attribute or image markup on your published page. Make the alt-text decision from what the cover contributes there, then verify the live result.
The image visible inside an article is also a different question from the image shown when someone shares its link. If the sharing image is wrong, use the separate social-preview image guide. Changing an on-page image’s alt text is not a substitute for checking social-preview metadata.



