Image SEO means preparing and presenting website images so they support the page, remain understandable to people who cannot see them, and load without unnecessary weight. File names, alternative text and compression all contribute, but they solve different problems. A descriptive filename identifies a file, alt text communicates an image’s meaning in context, and compression reduces the data needed to display it.
For a small-business owner, the most useful starting point is a repeatable publishing routine. Choose an image that helps the reader, prepare it for the space where it will appear, write the appropriate text alternative, and check the finished page. This guide takes you through that process, including a hypothetical business example and the decisions that are often missed when people focus only on an SEO plugin score.
Start with what the image contributes
Before editing a filename, ask why the image belongs on the page. Does it show a product detail, demonstrate a step, explain a comparison, introduce a real person, or provide evidence of completed work? An image with a clear purpose is easier to select, crop and describe. A decorative photograph chosen only to fill space may add loading weight without helping someone understand the subject.
Imagine a furniture repair business explaining how it assesses a damaged chair. A close photograph of a loose joint can support the explanation better than a generic picture of a furnished room. The relevant photograph lets a potential customer recognize the kind of issue being discussed. It does not need dramatic styling or a collection of keywords to become useful.
Keep the reader’s task in view when choosing between several images. A beautiful wide shot may work as a portfolio introduction, while a tightly framed detail may be better inside a tutorial. There is no requirement to use the same type of visual everywhere. Its placement and purpose should guide the choice.
Understand what each image field actually does
A file name belongs to the uploaded asset and usually forms part of its URL. Alt text belongs to an image’s use within a page. A caption is visible text that adds context for everyone. The media title inside your content management system may primarily help you identify the asset, depending on how the theme uses it.
Confusing these fields creates unnecessary work. Writing a good media-library title does not guarantee that the image has useful alt text where it appears. Similarly, a caption explaining who photographed a scene may be valuable, but it does not necessarily communicate the visual information a reader needs.
Treat each field as a separate decision. Record the source and usage rights in your asset notes, give the file an understandable name, and decide whether the page needs a caption. Then write the text alternative based on the role the image plays in that particular location.
Choose simple, descriptive file names before uploading
A filename such as “chair-leg-joint-before-repair.webp” is easier to understand and manage than “IMG_4827-final-final.webp.” Use a short description of the actual subject and a consistent naming convention. Hyphens between ordinary words make names easy to read without adding spaces or complicated characters.
Do not turn filenames into promotional sentences. Adding every service, nearby city and keyword variation creates clutter. If the image shows a chair joint, its name should not claim to show furniture repairs in ten different cities. Accuracy is more useful than trying to make one asset represent everything the business offers.
Google describes filenames as a light clue about an image’s subject in its image SEO guidance. That is a reason to name new uploads sensibly, not a reason to rename thousands of established image URLs without assessing the consequences. The page and image still need to be useful together.
Decide whether the image needs descriptive alt text
The right alternative depends on the image’s purpose. An informative photo needs a concise explanation of the information it contributes. A purely decorative image may appropriately use an empty alt attribute. An image that functions as a link or button needs an accessible name that communicates the action or destination.
The W3C alt decision tree provides a useful way to distinguish these cases. Start with the function of the image rather than a target keyword. A decorative flourish and a photograph demonstrating damage should not receive the same treatment just because they appear on the same service page.
For the chair example, “Loose wooden joint where the front chair leg meets the seat frame” communicates the detail being discussed. “Best furniture repair near me affordable chair repair” does not. The second phrase advertises a service while failing to describe the useful information in the photograph.
Write alt text for the context, not an imagined keyword target
Describe the important information clearly, using ordinary language. You generally do not need to begin every description with “image of” when the element is already identified as an image. Include relevant details that help the reader understand the point, and leave out incidental objects that do not matter to the explanation.
The same photo can have different appropriate alternatives in different contexts. A team photograph on an About page may need to identify the people if that is the purpose of the image. The same photo used as a decorative background behind text may not need a repeated description of every person.
Do not invent details that are not visible or supported. A photo does not establish that a business is the best in its city, that a repair lasted ten years, or that a product is suitable for a particular medical condition. Alt text should communicate information, not add unverified sales claims.
Make charts and screenshots usable beyond a short label
Some visuals carry too much information for one short alternative. A chart may need a concise description plus a nearby explanation of the pattern and the underlying values. A screenshot of instructions may need those instructions repeated as ordinary text so readers can follow them without relying on the image.
The W3C guidance for complex images discusses providing fuller text equivalents for detailed visuals. In practical terms, do not hide the only useful answer inside a graphic. If the image contains a comparison, make the comparison understandable in the surrounding article too.
For example, a before-and-after compression comparison should explain what changed and what the reader should inspect. A caption could point out blurred lettering or lost texture. That explanation turns a visual into a teaching aid rather than expecting everyone to notice the same detail unaided.
Resize images for their intended use
Pixel dimensions and file weight are different. Dimensions describe the image’s width and height, while file weight describes how much data it contains. A photograph can be visually reduced by the page layout while the browser still downloads an unnecessarily large original.
Begin with the space the image must fill. A small author portrait and a wide project photograph need different preparation. Preserve enough detail for the intended display, but do not assume that every upload needs to retain the camera’s full resolution. Keep the original separately so you can produce another version later.
Check the crop as well as the size. A square thumbnail can accidentally remove the very detail that makes a picture relevant. Preview featured images in the archive, the single post and mobile layouts because the same file may be cropped differently in each location.
Compress without destroying the useful detail
Compression reduces file weight, but aggressive settings can damage the image. Look closely at faces, fine edges, gradients, small labels and textures after exporting. The right balance is the version that preserves the information readers need while avoiding unnecessary data.
For ordinary production images on this website, WebP is the established format. The important lesson for your own workflow is to use a format and export process your website supports, then inspect the actual result. Changing a file extension alone does not convert an image; the file must be encoded in the chosen format.
Keep an original master and create a web version from it. Repeatedly opening and recompressing an already degraded file can make quality worse. A consistent export routine is easier to maintain than applying random settings to each upload. The web.dev guide to automated image processing explains how resizing and encoding can become part of a repeatable workflow.
A worked example for a small-business article
Suppose a furniture repair business is preparing an article about assessing a loose chair leg. It has an original photo, a close-up of the joint and a decorative room shot. The editorial decision is to use the joint photograph beside the assessment explanation because it helps readers understand the problem.
The business keeps its original image, creates a web-sized crop that preserves the joint, exports a compressed version, and inspects it at its actual display size. It then gives the asset a descriptive filename and writes alternative text about the visible issue. The example below illustrates decisions, not measured performance results.
After uploading, the editor previews the article on a phone-sized screen. If the joint is too small to see, the solution may be a better crop or a different image rather than a larger download. This is why image selection, design and technical preparation should be reviewed together.
| Element | Choice | Reason |
|---|---|---|
| Image | Close-up of a loose chair joint | Shows the issue discussed in the article |
| Filename | chair-leg-joint-before-repair.webp | Identifies the actual subject |
| Alternative text | Loose wooden joint where the front chair leg meets the seat frame | Communicates the useful visible detail |
| Caption | Example of the joint area to photograph before requesting an assessment | Adds practical context |
| Quality review | Inspect the joint after resizing and export | Preserves the detail the reader needs |
Check what WordPress actually displays
In WordPress, add an Image block for an image inside the article and use the featured-image setting for the post’s main preview image. These are different placements. Adding one does not always populate the other, and your theme may treat their sizes and captions differently.
Review the alternative text in the relevant image settings. Do not assume that changing a media-library field updates every previously inserted instance in every context. Check the actual block or rendered page, especially when a file is reused in several posts.
Also distinguish the media attachment page from the article. Your intended destination should remain the useful article or service page. If clicking an image unexpectedly opens an empty attachment page or an oversized file, review the link setting and choose the behavior that serves the reader.
Review image loading as part of the whole page
An image can look sharp and still cause a poor experience if it appears late or makes surrounding text jump. Preview the page from a fresh load and observe what happens before everything settles. A gallery, hero image and sidebar portrait may need different treatment.
If a performance report identifies images as a problem, inspect the actual finding. An oversized download, missing dimensions and delayed loading are different issues. Do not apply one blanket setting to every image merely because a tool suggests an image-related improvement.
For a business owner working with a developer, ask for a concrete explanation: which image is affected, what the proposed change does, and how the result will be checked. This turns an abstract request to “optimize images” into work that can be reviewed.
Improve an existing image library in a sensible order
Start with important pages and obvious issues. A broken image on your main service page deserves attention before an obscure old file with an untidy name. Next, address images whose meaning is inaccessible, whose crops hide useful details, or whose downloads are unnecessarily heavy.
Avoid deleting or renaming assets just because they look duplicated in the media library. They may be used in old articles, templates, social previews or external links. Identify where a file is used before replacing it, and preserve working references when making changes.
A simple asset record can include the page, image purpose, current problem, intended correction and completion date. This is enough to make a small cleanup project manageable. You do not need an elaborate spreadsheet before fixing a few clear issues.
Common questions about image SEO
Should every image contain my main keyword in its alt text? No. Use the phrase only when it naturally describes the image’s relevant information. Repeating the same keyword across unrelated images reduces the usefulness of the alternatives. Describe a staff photo, product detail and instructional screenshot according to their different roles.
Is there one ideal image file size? No single weight suits every use. A detailed diagram and a small decorative icon have different requirements. Compare the image’s purpose, dimensions and quality, then test the page. A strict arbitrary limit can produce a small file that no longer communicates what the reader needs.
Can I use AI to generate alt text? You can use a suggested description as a starting point, but review it against the image and its page context. Automated tools may misidentify objects, overlook the important detail or add unsupported assumptions. The person publishing remains responsible for the final alternative.
Will fixing images solve low traffic? It may resolve a specific usability or image-discovery issue, but it does not establish the cause of low traffic. Review the broader page purpose and evidence. The guide on why content is not getting traffic helps you investigate beyond individual image fields.
Build a routine you can repeat
Before publishing, confirm that each important image has a purpose, an appropriate crop, a sensible web export and the right text alternative. Preview the page in its actual template, including a narrow screen. Save the original separately and record any remaining problem that needs design or development support.
This routine makes future articles easier to maintain because the decisions happen before the media library becomes difficult to manage. If you want to practice on your own website, one-on-one SEO coaching with Marium can help you assess real images, explain the choices and build a workflow you understand.
