← All field notes

A WordPress image SEO workflow for a real publishing team

Image SEO often gets reduced to renaming a file and filling every field in the media library. That misses the editorial question: what is this image helping the reader understand?

Start there. A product detail photograph, a screenshot of a setting and a decorative shape do different jobs. Their descriptions and placement should reflect those jobs rather than repeat the page’s target keyword.

Choose the image before optimizing the fields

Use a visual that explains something the surrounding text does not explain as well. For a tutorial, that might be the exact screen where a reader has to make a choice. For a service page, a genuine product screenshot is more informative than a generic office photograph.

Check that you have permission to publish it. If the image shows a real account, remove credentials and private customer details before it enters the media library. Keep an unedited original in the team’s approved asset storage when required, not in a public uploads folder by default.

Write alternative text for this context

Describe the information a reader would miss if they could not see the image. A screenshot might need the selected option or the error being discussed, not a list of every item in the interface. Do not use the alt field as a second meta description.

Google’s image guidance recommends useful contextual information and descriptive alt text while warning against keyword stuffing. It also discusses discoverable image markup and delivery. Follow those principles without assuming that filling a plugin checklist guarantees an image ranking.

For an image that is purely decorative in its placement, an empty alt attribute may be appropriate. The W3C alt decision tree helps distinguish decorative, informative and functional images. If the image is a link, consider the destination or action the link needs to communicate.

Make the upload usable on the page

Choose dimensions appropriate to the display area and inspect the compressed result. Small text in a screenshot can become unreadable even when the file size looks excellent. Check the mobile version before accepting the asset.

Use the image features available in the theme and WordPress editor rather than inserting a huge background image merely because it is easy to position. Review the generated page in a browser: the intended image should load, reserve sensible space and remain readable at the sizes visitors use.

  • Keep filenames understandable without stuffing multiple search phrases into them.
  • Use a caption when it adds context or identifies a detail the text refers to.
  • Check the crop so the important part survives narrow layouts.
  • Confirm that a performance setting has not delayed the main above-the-fold image unnecessarily.

Give one person the final visual check

A writer can supply the intended meaning and an editor can verify the actual placement. Make that handoff explicit. Otherwise the correct alt text may be attached to an image that was later replaced, or a caption may describe a screen from an older product version.

Record when a screenshot needs review, especially in a software tutorial. An accurate article can become confusing when its interface image no longer matches the instructions.

After publication, inspect the page and use search performance data to decide what deserves improvement. Do not replace useful images just to make a scoring indicator turn green. For the wider publishing routine, keep image checks alongside the site maintenance checklist. A reader should be able to identify the setting in your screenshot on a phone. If they cannot, fix the image or crop before spending more time on its filename.


Have a correction or a workflow we should cover? Tell the IrmaWP team.