Skip to content

On Page SEO

How to Optimize Blog Images for SEO

Takes about a minute. You hear back from me personally.

Prefer Saad Raza SEO on Google Add this site as a preferred source to see more of my SEO and AI search guides in Google Top Stories.

Add saadrazaseo.com as a preferred source on Google

Short answer: To optimise blog images for SEO, use original images that support the text, give each file a short descriptive name, write alt text that says what the image shows, resize it to the width your theme displays and compress it (WebP is a safe default). Always set width and height, lazy load only images below the fold, and place each image next to the paragraph it explains.

68%of mobile pages have an image as their Largest Contentful Paint elementWeb Almanac, 2024
45%of img elements have no alt text at allWeb Almanac, 2024
32%of mobile img elements set both width and heightWeb Almanac, 2024
7 formatsGoogle Search indexes: BMP, GIF, JPEG, PNG, WebP, SVG and AVIFGoogle Search Central

This guide is for bloggers, content writers and site owners who publish articles with screenshots, photos, charts or featured images and want those images to help rather than slow the page down. It follows the order I use when I fix images on a client blog: what to choose, how to prepare the file, what to write in the HTML, and how to check it worked. Use the checklist below on your next post, then work back through your older ones.

Blog image SEO checklist (one post at a time)

  • Pick an image that earns its place: it explains, proves or shows something the text cannot do as well.
  • Prefer original images: your own screenshots, photos, charts and diagrams over generic stock.
  • Rename the file before upload: short, lowercase, hyphenated and descriptive, such as gsc-page-indexing-report.png.
  • Resize to the display width: no 4000 px camera originals in a 760 px content column.
  • Compress and choose the format: WebP for most photos and screenshots, SVG for logos and simple icons.
  • Write alt text: describe what the image shows and why it is there; leave it empty only for purely decorative images.
  • Set width and height: so the browser reserves space and the text does not jump while the image loads.
  • Do not lazy load the first image: lazy load only images below the fold.
  • Serve responsive sizes: srcset and sizes, with a normal src as the fallback.
  • Place it beside the related text: and add a caption when the image needs explaining.
  • Set a strong featured image: large, relevant and at least 1200 px wide for Discover and social previews.
  • Check discovery: images in your sitemap or image sitemap, and not blocked in robots.txt.
  • Test the page: run PageSpeed Insights and look at the LCP element and any layout shift.

Ticks are saved in your browser, so you can work through a post and come back later. Each item is explained below.

How images help (and hurt) a blog post in search

Images affect a blog post in three separate ways, and it helps to keep them apart because the fixes are different.

  • Google Images and visual search. A well-labelled original image can be found on its own through Google Images and Lens, and send visitors to the post. Google’s image SEO best practices say it uses alt text, file names, page content near the image and structured data to understand what an image shows. I cover the wider picture in my guide to visual search optimisation.
  • Page speed and Core Web Vitals. On most blogs the featured image or first in-content image is the Largest Contentful Paint element. The HTTP Archive Web Almanac 2024 found that 68% of mobile pages have an image as their LCP element. A heavy, lazy-loaded hero image is one of the most common reasons I see a poor LCP score, which is part of Core Web Vitals.
  • Understanding and usefulness of the article. A screenshot of the exact setting, or a chart of real data, makes the post more helpful for readers. That is the part that supports rankings for the text itself.

Image SEO is a smaller topic within image SEO optimisation for the whole site. This post focuses on what a writer or editor controls when publishing a single article.

Step 1: Choose images that add information

Before any technical work, ask whether the image tells the reader something. When I audit blogs, the weakest images are generic stock photos of laptops and handshakes placed under every H2. They add page weight, they are the same images that appear on thousands of other sites, and they do nothing for the reader.

Better choices for a blog post:

  • Annotated screenshots of the exact screen the reader needs, with arrows or boxes on the setting being discussed.
  • Charts made from your own data, with the numbers also written in the text or a table.
  • Photos you took: your product, your work, your office, a finished job.
  • Simple diagrams that explain a process in one view.

If you use AI-generated images, treat them like stock: use them only where they genuinely illustrate the point, and do not present them as real photos of a real place or result.

Rather have an expert do this for you?

Hand it over and get back to running your business.

Hand it over to me

Step 2: Prepare the file: name, size, format and compression

File names

Google recommends short, descriptive file names, because names like IMG_4821.jpg or image1.png say nothing. Rename the file on your computer before uploading, since WordPress uses the uploaded name in the URL. Use lowercase words separated by hyphens and describe the image, not the keyword you wish to rank for: search-console-page-indexing-report.png rather than seo-seo-tips-best-seo-2026.png.

Dimensions

Check the width of your theme’s content column (often between 700 and 900 px) and resize images to that width, or twice that for sharp display on high-density screens if your theme serves responsive sizes. The free image resizer does this in the browser.

Format and compression

Image typeFormat I useWhy
Photos and featured imagesWebP (AVIF if your stack supports it)Much smaller than JPEG at similar quality; both are supported by Google Search
Screenshots with textWebP or PNGKeeps text sharp; WebP is usually smaller
Logos, icons, simple diagramsSVGScales to any size with a tiny file
Short animationsMP4 or WebM video instead of GIFAnimated GIFs are often several megabytes
Images people may download or printJPEG or PNGWidest compatibility outside the browser

Compress every image before or during upload. Run files through my image compressor and WebP converter, or use an optimisation plugin that converts on upload. Check the result by eye: screenshots with small text can blur if you push the quality too low. Make sure the file extension matches the real file type, as Google’s guidance asks.

Step 3: Write alt text that describes the image

Alt text is read aloud by screen readers, shown when an image fails to load, and used by Google as the most important text attribute for an image. Write it for a person who cannot see the image: what does it show, and why is it there? A keyword fits naturally when the image really is about that topic; repeating keywords is against Google’s guidance and does nothing useful. My guide to alt text in SEO goes deeper; the short version is in the table.

ImageWeak alt textBetter alt text
Screenshot of a reportseo imageSearch Console Page indexing report showing 312 pages not indexed
ChartchartLine chart of organic clicks falling after the March core update
Photo of foodbiryani biryani recipe best biryani KarachiPlate of Sindhi biryani with potatoes and fried onions
Decorative dividerdecorative lineEmpty alt (alt=””) so screen readers skip it
Logo used as a home linklogoThe destination, for example “Home”

The W3C alt decision tree is the reference I use for edge cases: purely decorative images get an empty alt, an image that is a link should describe the destination, and text inside an image belongs in the alt unless it is repeated in the text nearby. For dense charts, keep the alt short and put the actual numbers in the article or a table.

Step 4: Add it to the page correctly

Placement and captions

Put each image directly next to the paragraph it supports. Google uses the surrounding text to understand an image, so a screenshot of a robots.txt file belongs in the robots.txt section, not in a gallery at the end. Add a caption when the reader needs to know what to look at; people scanning a post often read captions even when they skip whole paragraphs.

Width, height and lazy loading

Always output width and height attributes. Google’s web.dev guidance on lazy loading recommends adding them to all img tags so the browser reserves space, which prevents the text jumping around as images arrive. If you already have this problem, my guide to fixing cumulative layout shift walks through it.

Use loading="lazy" only for images below the fold. The same web.dev article warns against lazy loading images that are likely to be in the viewport on load, especially the LCP image. This is the single most common image mistake I find on WordPress blogs: a theme or plugin lazy loads everything, including the featured image, and LCP gets worse.

Responsive images

WordPress adds srcset and sizes to content images automatically, so the browser picks a smaller file on phones. On a custom build, add them yourself and keep a normal src, which Google says is the fallback for browsers and crawlers that do not understand srcset or the picture element.

Worked example: the HTML I want to see for a blog image
<figure>
  <img src="/images/gsc-page-indexing-800.webp"
       srcset="/images/gsc-page-indexing-400.webp 400w,
               /images/gsc-page-indexing-800.webp 800w,
               /images/gsc-page-indexing-1600.webp 1600w"
       sizes="(max-width: 820px) 100vw, 800px"
       width="800" height="450"
       loading="lazy" decoding="async"
       alt="Search Console Page indexing report showing 312 pages not indexed">
  <figcaption>The Why pages aren't indexed table is where most fixes start.</figcaption>
</figure>

For the first image in the post, remove loading="lazy" and consider fetchpriority="high" so the browser fetches it early.

Your featured image does double duty: it is often the LCP element on the post and it is the image used in social shares and in Google Discover. Use a relevant, high-quality image at least 1200 px wide, avoid text-heavy graphics or your logo as the only image, and make sure your SEO plugin outputs it as the og:image. My guide on how to optimise for Google Discover covers the large image setting.

Step 6: Help Google find and understand the images

  • Use real img elements. Images added only as CSS backgrounds are not indexed as images.
  • Do not block image folders in robots.txt if you want them in Google Images.
  • Sitemaps: most WordPress SEO plugins list images inside the normal XML sitemap. If images sit on a CDN or are loaded by JavaScript, an image sitemap helps Google discover them, and Google allows image URLs from other domains in it.
  • Structured data: Article or BlogPosting schema markup with an image property tells Google which image represents the post. For recipes and products, the image property is required for rich results.

Mistakes I see most often on blog images

  • Uploading phone or camera originals of several megabytes and relying on the browser to shrink them.
  • Lazy loading the featured image, which delays the LCP element.
  • Keyword-stuffed alt text copied from the post title onto every image.
  • Text baked into images (tables, steps, quotes) with no text version, so neither readers using screen readers nor Google can read it.
  • Stock photos under every heading purely to break up text.
  • Changing image URLs during a redesign without redirects, which loses any Google Images traffic they had.

After fixing a post, run it through the PageSpeed and Core Web Vitals checker, look at which element is the LCP, and check that no image is flagged as oversized or missing dimensions. Then apply the same routine to the next post; if you are rewriting the whole article, my guide to writing SEO-friendly blog posts covers the text side.

Frequently asked questions

What is the best image size for a blog post?

Match the width of your content column, usually 700 to 900 px, and supply a double-width version for high-density screens through srcset. Featured images should be at least 1200 px wide for Discover and social previews. Keep file size as low as the image allows; most compressed blog images can sit well under 200 KB.

Is WebP better than JPEG for SEO?

Google indexes both, so the format itself is not a ranking factor. WebP usually produces a smaller file at similar quality, which helps page speed, so it is my default for photos and screenshots. Keep JPEG or PNG for files people will download.

Should every image have alt text?

Every informative image should. Purely decorative images, such as dividers or background flourishes, should have an empty alt attribute (alt=””) so screen readers skip them. A missing alt attribute is different from an empty one and should be avoided.

Do image file names still matter for SEO?

Yes, a little. Google lists the file name as one of the signals it uses to understand an image. It is a small effort to rename files before uploading, and descriptive names also make your media library easier to manage.

Should I lazy load all images on my blog?

No. Lazy load images below the fold only. The first image a visitor sees, usually the featured image, should load normally, because lazy loading it delays your Largest Contentful Paint.

Sources

  • Google Search Central, “Google image SEO best practices” (accessed 2026).
  • HTTP Archive, “Web Almanac 2024: Media chapter” (2024).
  • web.dev, “Browser-level image lazy loading for the web” (accessed 2026).
  • W3C Web Accessibility Initiative, “An alt Decision Tree” (accessed 2026).

If your blog has hundreds of posts with heavy images and you would rather fix it at the template level than one post at a time, my website speed optimisation service covers image delivery, lazy loading and LCP across the whole site.

Rather have an expert do this for you?

Tell me about your website and goals, and I will reply with a free first review.

Your details are only used to reply to your request. No spam.

Grow my trafficCall