Image SEO is easiest to manage when it is part of your publishing workflow rather than a last-minute technical task. This guide gives bloggers a repeatable checklist for choosing file formats, writing useful alt text, compressing images, checking page performance, and maintaining a clean media library over time.
Overview
Images support a blog post in several ways: they can explain a process, break up dense text, demonstrate a result, or provide context that words alone cannot. They can also create avoidable problems when files are oversized, filenames are vague, alternative text is missing, or old screenshots remain embedded in otherwise updated articles.
For independent publishers, image SEO should serve three connected goals:
- Help people understand the page: Images should add information, orientation, or useful visual structure.
- Support accessibility: Readers who use assistive technology should receive the relevant meaning of an image, or be told when an image is purely decorative.
- Protect page performance: Images should be no larger or more complex than the page requires.
Search visibility is a result of good publishing decisions, not a reason to add keywords everywhere. A descriptive filename, accurate alt text, a relevant caption, and an appropriately sized file are more useful than repeating a target phrase in every image field.
Use the checklist below before publication, then return to the maintenance section during a monthly or quarterly review. Your exact schedule can depend on how often you publish and how frequently your subject matter changes.
What to track
1. File names and image context
Rename an image before uploading it when the original filename is unclear. A name such as IMG_4821.jpg tells neither a reader nor a content system what the file contains. Prefer a short, descriptive filename that reflects the image and, where useful, its relationship to the article.
For example:
- Weak:
IMG_4821.jpg - Better:
blog-image-seo-checklist.jpg - For a specific screenshot:
cms-image-alt-text-field.png
Use lowercase words separated by hyphens. Avoid stuffing several variations of a keyword into the filename. The filename should remain accurate if the image is reused in a newsletter, social post, or another article.
2. Dimensions and compression
Start with the size at which the image will actually appear. Uploading a very large original for a small content column creates unnecessary work for the browser and the reader. Keep an original backup separately if you may need to crop or reuse it later.
Compression reduces file weight by removing or simplifying data. The right setting depends on the image: photographs often tolerate more compression than screenshots, diagrams, or text-heavy graphics. Inspect the compressed result at the size readers will see it. A smaller file is not an improvement if labels become difficult to read or edges look visibly damaged.
| Image type | Useful starting choice | Check before publishing |
|---|---|---|
| Photograph or complex scene | A modern web image format or a well-compressed JPEG-style format | Fine detail, color changes, and visible compression artifacts |
| Screenshot with text | A format that preserves sharp text and interface edges | Legibility at the displayed size; crop unnecessary browser chrome |
| Simple illustration or logo | A format suited to flat colors or transparency | Transparent areas, crisp edges, and color consistency |
| Small icon or decorative shape | The smallest practical format for the design | Whether the image should be an image at all, rather than CSS or inline content |
Format support and compression features can change as tools and browsers evolve. Treat the table as a decision aid, not a permanent rule. Test the formats your publishing stack serves and verify that important images remain usable when delivered to readers.
3. Alt text
Alt text should communicate the purpose or meaningful content of an image. It is not a caption, a file description, or a place to repeat the article's keyword. Write it as if you were explaining the image to someone who cannot see it but still needs to understand the page.
Use this decision guide:
- Informative image: Describe the relevant subject, action, or result. Include details that support the surrounding text.
- Functional image: Describe what happens when someone selects it, such as “Search the site” for a search icon used as a control.
- Decorative image: Use empty alt text when the image adds visual style but no information. Do not add a made-up description simply to fill the field.
- Text in an image: Include the text when it is necessary to understand the content, while also considering whether the information should appear as real HTML text.
Before-and-after examples:
- Weak:
alt="SEO image" - Better:
alt="Prepublication checklist showing filename, dimensions, alt text, and compression checks" - Weak:
alt="dashboard screenshot" - Better:
alt="Media library filtered to show oversized images awaiting compression"
Keep alt text focused. If an image requires a long explanation, provide that explanation in the article and use concise alt text to identify the image and its role.
4. Captions, placement, and links
A caption can explain why an image matters, identify a source, or clarify what readers should notice. It should add information rather than restate the alt text. Place images near the paragraph they support, and avoid inserting decorative images between closely related steps in a process.
If an image links to another page, the surrounding link text or the image's accessible label should make the destination clear. Do not rely on a generic image or thumbnail to communicate where the link leads.
5. Media-library health
Track more than the images in your newest article. During a media audit, look for oversized files, duplicate uploads, missing alt text, obsolete screenshots, broken image URLs, and images that no longer match the article's current advice. Record the page URL, image URL, issue, owner, and planned action in a simple spreadsheet if your CMS does not provide a useful report.
Cadence and checkpoints
A lightweight schedule keeps image maintenance from becoming a large technical project.
Before every publication
- Confirm that each image has a clear purpose.
- Rename the file if its current name is meaningless.
- Resize and compress it for its intended display area.
- Choose the format that preserves the required quality.
- Write accurate alt text or mark the image as decorative when appropriate.
- Check captions, credits, links, and placement.
- Preview the article on a narrow screen and a larger screen.
Monthly spot check
Review the newest articles and inspect images that appear slow, blurry, stretched, or unexpectedly cropped. Check the browser preview and your performance tools if available, but treat a single score as a diagnostic signal rather than the entire definition of quality. Confirm that important images load correctly when lazy loading, responsive sizing, or a content delivery layer is involved.
Quarterly media audit
Review a representative group of older posts, plus any articles that have been updated recently. Search for missing alt text, duplicate files, oversized originals, outdated product interfaces, broken paths, and images that no longer support the article's intent. Prioritize pages that receive meaningful traffic, support important topic clusters, or are used in newsletters and campaigns.
Every six months or after a platform change
Recheck the image formats, compression settings, CMS behavior, and browser rendering used by your site. Tools may add new export options, and a theme or plugin change may alter how images are resized or delivered. Update this workflow when your publishing stack changes rather than assuming old settings still apply.
How to interpret changes
When an image-related performance issue appears, identify the cause before changing every image on the site. A slow page may involve several assets, scripts, fonts, hosting conditions, or layout behavior. If only one article is affected, inspect its largest images first. If many pages changed at once, look for a CMS, theme, plugin, or delivery change.
Use these signals to choose an action:
- Large file with acceptable visual quality: Resize it to the displayed dimensions and compress it again.
- Blurry image: Check whether the source is too small, the display dimensions are too large, or an aggressive compression setting was used.
- Readable image but poor accessibility: Rewrite the alt text around the image's purpose, not its filename or target keyword.
- Traffic falls after a visual update: Check whether the image is broken, blocked, replaced with an irrelevant crop, or surrounded by changed content before drawing an SEO conclusion.
- Repeated duplicate files: Establish a naming convention and reuse approved assets instead of uploading another copy for every article.
Keep a simple change log for important updates. Note the date, page, image, issue, action, and any observable result. This prevents repeated experiments and makes quarterly reviews more useful.
When to revisit
Return to this article and your image checklist before each new post, during a monthly spot check, and during a fuller quarterly media audit. Revisit sooner when you redesign the site, change your CMS or image delivery setup, replace a major screenshot, publish a new content series, or notice a cluster of broken or slow-loading images.
For a practical next step, create four columns in your editorial system: image URL, issue, next action, and review date. Add every image issue you find, then fix the highest-impact items first. Connect this process to your content calendar so image checks happen alongside scheduled updates, and use your content audit to identify old articles whose screenshots or illustrations need replacement.
Image SEO works best as a small, repeatable part of a broader post-launch SEO workflow. Make the checks routine, record what changes, and update the process when your site or tools change. That approach improves accessibility, usability, and publishing consistency without turning every article into a technical project.