top of page

Image SEO Best Practices: A Practical Guide for UK Business Websites

Nov 9
6 min read

If your website relies on product photos, team headshots, before-and-after shots or infographics to tell your story, how you handle those images affects far more than how fast your pages load. Following the right image SEO best practices helps Google understand what each picture actually shows, index it correctly, and in some cases, surface it directly in Google Images. For UK and London businesses competing for attention in crowded local search results, image SEO is one of the more overlooked parts of on-page optimisation. This guide pulls together what Google's own documentation says about image SEO best practices, covering file formats, file names, alt text, structured data, responsive images and lazy loading, so you can work through your own site with a clear checklist.


Why image SEO best practices matter for UK business websites

Google is explicit about how it discovers images: it finds them through the src attribute of an <img> element, including images nested inside a <picture> element, and it does not index images that are only applied as CSS background images. That single rule changes how a lot of sites should be built. A hero photo set purely as a CSS background on a homepage, for instance, is effectively invisible to Google's image indexing, no matter how relevant or high-quality it is.

  • Discovery and indexing – images referenced correctly in HTML can be crawled, indexed and shown in Google Images, which is a genuine source of organic traffic in its own right.

  • Page speed – images are usually the single largest contributor to a page's weight, which directly affects Core Web Vitals and user experience.

  • Accessibility – descriptive alt text helps people relying on screen readers understand what an image shows, not only search engines.

  • Context for search – clear file names, alt text and structured data all help Google understand what a page and its images are actually about.


Image file formats and compression that search engines prefer

Google Search supports images referenced in an <img> src attribute in BMP, GIF, JPEG, PNG, WebP, SVG and AVIF formats, and recommends matching your file extension to the actual file type rather than, say, saving a PNG with a .jpg extension. For most UK business websites, that translates into a few practical habits.

  • Use WebP or AVIF for photographic images where possible, since both typically produce smaller files than JPEG at a similar visual quality.

  • Use SVG for logos, icons and simple graphics, since it scales cleanly and usually produces tiny file sizes.

  • Compress every image before upload rather than relying on your CMS to do it automatically, and test the result with a tool like PageSpeed Insights.

  • Be cautious with inline data URIs: Google notes that while they can reduce the number of requests a browser makes, they can also considerably increase the size of the page itself.

This is also where our technical SEO audit checklist comes in, since unoptimised images are one of the most common causes of slow page speed we see on UK business websites.


Image SEO best practices for website photography: a digital camera on a wooden shelf

File names: an easy win for image SEO best practices

One of the simplest image SEO best practices to apply is also one of the most commonly ignored: giving images a descriptive, readable file name before you upload them. Google's own example contrasts my-new-black-kitten.jpg with IMG00023.JPG – the first tells Google, and you, what the file actually shows, the second tells it nothing. For a UK business, that might mean renaming a file to something like bathroom-renovation-before-after-london.jpg rather than keeping whatever your camera or phone generated. If your site serves more than one language, Google also recommends translating file names for each version and URL-encoding any non-Latin characters, rather than reusing the same English file name everywhere.


Alt text: the most important image SEO best practices rule

Google describes alt text as the single most important piece of metadata you can add to an image, because it serves two audiences at once: people using screen readers, and search engines trying to understand what the image shows. Good alt text is descriptive and matches the surrounding content – “a plumber fitting a new boiler in a London flat” tells a much clearer story than “plumber”, or worse, “plumber, boiler repair, boiler installation, emergency plumber London”. Google is direct about that second approach: keyword stuffing in alt text is treated as a form of spam, not an SEO shortcut.

Two details are easy to miss. First, if you're using inline SVG rather than an <img> tag, the accessible label should go in the SVG's <title> element instead of a separate alt attribute. Second, when an image doubles as a link – a thumbnail that takes visitors through to a product page, for example – its alt text effectively becomes the link's anchor text, so the same anchor text best practices that apply to ordinary text links apply here too.


Structured data and choosing a preferred image for the page

If you want an image to be eligible for a rich result or the badge that appears on some images in Google Images, Google's documentation is clear that the image property is a required field in the relevant structured data markup, alongside the general structured data guidelines and any rules specific to the schema type you're using. Separately, you can help Google pick which image best represents a page using schema.org's primaryImageOfPage property, a mainEntityOfPage or mainEntity reference with an image property, or a simple og:image meta tag. Google's advice here is to choose an image that's genuinely relevant and high-resolution, and to avoid logos, images that are mostly text, or unusual aspect ratios when selecting this preferred image.


Responsive images and lazy loading without hurting speed

Most modern websites serve different image sizes to different devices using the srcset attribute or the <picture> element. Google's guidance, and the HTML Standard itself, is to always include a fallback src attribute alongside these, because some browsers and crawlers don't support srcset or <picture> at all. If you're using <picture>, it should end with an <img> element that has a working src, not just a list of source options.

Lazy loading is where we see UK business sites most often get things backwards. The native loading="lazy" attribute is supported in all major browsers, so there's rarely a need for a JavaScript library to achieve it. But Google's own performance guidance is specific about where it should, and shouldn't, be used.

  • Only add loading="lazy" to images positioned outside the initial viewport, and remember that the viewport varies by device, so an image visible on a small phone screen might sit comfortably above the fold on a laptop.

  • Never add it to hero images or anything likely to be your Largest Contentful Paint (LCP) candidate: Google's own guidance says to “definitely omit” lazy loading here, since it can delay the very image Core Web Vitals is measuring.

  • Remember that the loading attribute only affects timing, not network priority, and doesn't replace the wider performance work most sites still need.


Image sitemaps: helping Google find images it would otherwise miss

An image sitemap is a dedicated or extended XML sitemap that lists image URLs so Google can discover images it might not find through normal crawling. Unlike a standard sitemap, Google specifically allows you to include image URLs from other domains in the <image:loc> element, which is useful if your images are served from a CDN rather than your own domain. If you do this, verifying the CDN domain in Google Search Console lets you see crawl errors for those images specifically. It's also worth keeping a single, consistent URL for each image and reusing it across pages, rather than duplicating the same photo at several different addresses: Google notes this lets it cache the image once rather than re-requesting it repeatedly.


An image SEO best practices checklist for your next review

  • Every meaningful image sits in an <img> or <picture> element with a real src attribute, not only as a CSS background.

  • File names are short and descriptive, written in the page's own language.

  • Alt text describes the image naturally, without keyword stuffing, and inline SVG uses <title> instead.

  • Images use a supported format (WebP, AVIF, JPEG, PNG or SVG) with sensible compression.

  • Responsive markup, srcset or <picture>, always includes a working src fallback.

  • loading="lazy" is used only below the fold, never on hero or likely LCP images.

  • An image sitemap is submitted, with any CDN domains verified in Search Console.

  • Key pages mark a preferred image using primaryImageOfPage, mainEntityOfPage or mainEntity, or a simple og:image tag.


None of this needs fixing all at once, and most sites improve steadily by tackling the worst offenders first, usually oversized hero images and missing alt text. If you'd like a second pair of eyes on your own image SEO best practices alongside the rest of your technical setup, our team can take a look.


Comments


bottom of page