Good photography can slow a website down or earn visits from Google Images. What Google's own documentation says about alt text, file names, formats, sizes and image sitemaps, where the folklore goes further, and the checklist we use.
On this page
We often see good photography uploaded as IMG_4471.jpg, at full camera resolution, with no description, in a slider that loads before anything else. The page is slower than it needs to be, and Google has little to go on.
Google Images, and the image results in ordinary search, can only use a photograph Google can find, fetch and understand. Here is what Google's documentation says about each step, where common advice goes further, and our checklist. None of it guarantees rankings or traffic.
What Google actually uses
Google's image SEO best practices name the signals:
- The page around the image. Google "extracts information about the subject matter of the image from the content of the page, including captions and image titles", and asks for images near relevant text, on pages about the same subject.
- Alt text, used "along with computer vision algorithms and the contents of the page". For a linked image, it is also the anchor text.
- The file name, which "can give Google very light clues".
- Structured data, which can make images eligible for certain rich results and a badge in Google Images.
- A preferred image. Choosing a result's thumbnail is "completely automated", but you can suggest one with schema.org primaryImageOfPage or an og:image tag, ideally not a logo or an image of text.
The guide does not say how much captions, titles or the title attribute weigh, so we treat a title attribute as optional, never a substitute for alt text. It does not mention EXIF data, the camera settings, date and GPS position written into the file, and Google's Martin Splitt was reported in September 2024 as saying that Search does not use EXIF for ranking (Search Engine Roundtable). On that evidence, we treat geotagging photos for SEO as folklore.
Alt text is for people first
Alt text is what a screen reader announces in place of the image. Write it for that listener and it usually serves search too. Google warns that filling alt attributes with keywords "results in a negative user experience and may cause your site to be seen as spam".
The W3C's alt decision tree works through five questions. In practice:
- A product shot. Bad: "perfume dubai best oud perfume buy online". Good: "100 ml amber glass oud perfume bottle with a brushed brass cap".
- A team photo. Bad: "team" or "IMG_4471". Good: "The four-person service team at the reception desk of the Business Bay showroom". If a caption already names everyone, the alt text need not repeat it.
- A decorative image, such as a background texture or a divider: an empty alt attribute, alt="", so screen readers skip it. Leaving the attribute out is different, because some screen readers then announce the file name.
- An image that is a link: describe where the link goes.
On the Arabic version of a page, the alt text is in Arabic.
File names, decided before upload
Google asks for file names that are "short, but descriptive", prefers my-new-black-kitten.jpg to IMG00023.JPG, and suggests translating the file names of localised images too. Separate words with hyphens, which Google recommends over underscores; non-Latin characters such as Arabic are percent-encoded in the URL.
Name files before upload. John Mueller of Google said in 2019 that renamed images are "seen as new images" and that, because images rarely change, Google does not crawl them as frequently (Search Engine Journal), and Google's site move guide says image URLs need to be moved like all other content. So a better name is rarely worth changing an indexed image's URL; if a rebuild changes it anyway, redirect the old one. Google also asks you to "consistently reference the image with the same URL" across pages.

Formats: what Google reads and what we use
Google Search supports BMP, GIF, JPEG, PNG, WebP, SVG and AVIF images referenced from the src attribute of an img element. Our defaults:
- Photographs: AVIF or WebP, with a JPEG fallback. MDN's image format guide recommends both for better compression. As of October 2026 it lists AVIF support in Chrome, Edge (from version 121), Firefox, Opera and Safari (from 16.1), WebP in all of them, and still advises a fallback.
- Screenshots and line art: PNG, which is lossless. PNG, WebP and AVIF all handle transparency.
- Logos, icons and diagrams: SVG, which stays accurate at any size.
Sizes and delivery, without the code
The metrics are in Core Web Vitals are a business metric. For images, five habits from web.dev do most of the work.
- Serve the size that is displayed. An image shown at 500 by 500 pixels is optimally 500 by 500; a 1,000-pixel file is "twice as large as needed" (web.dev, Image performance).
- Let the browser choose. Responsive images give the browser several widths of the same photograph and a note of how wide it will appear (the srcset and sizes attributes), and the browser picks the best one for the device. The picture element can also offer AVIF first with JPEG behind it, or a different crop for phones. Google asks for a plain src fallback, as some crawlers understand neither.
- Compress, then look. web.dev: "there isn't a universal setting suitable for all cases". Compare exports at their displayed size. If you strip metadata to save bytes, Google recommends you "retain critical metadata related to image rights information and identification".
- Lazy-load everything except the first screen. The browser's built-in loading="lazy" defers an image until it nears the viewport. For the Largest Contentful Paint image, often the hero photograph, web.dev is blunt: "Never lazy-load your LCP image". Give it fetchpriority="high" instead, and no more than one or two images (Optimize LCP).
- Give every image a width and a height. Browsers use them to reserve space before the file arrives, so the text does not jump, which is what Cumulative Layout Shift measures (web.dev, Optimize CLS).
Make sure Google can reach the images
- Use a real img element. "Google doesn't index CSS images", so a product photo set as a CSS background will not appear in Google Images.
- Do not block the image folder. robots.txt can keep images out of Google's results, so check that no rule covers your uploads directory or image CDN. More in Technical SEO before a site launches.
- Lazy-load without hiding images. Google asks that lazy-loaded content loads whenever it is visible in the viewport, without relying on scrolling or clicking. The browser's built-in method does.
- Add an image sitemap where it helps. An image sitemap lists images Google might not otherwise find, such as those loaded by JavaScript, up to 1,000 per page, including images on a CDN if both domains are verified in Search Console. Only image:image and image:loc remain: caption, title, geo_location and license were deprecated in May 2022 and have had no effect since 6 August 2022.
Original photography versus stock
Google publishes no penalty for stock photography. Its image guide says "high-quality photos appeal to users more than blurry, unclear images". John Mueller has said stock imagery "doesn't matter for web-search directly", but that in image search, "if it's the same image as used in many places, it'll be harder" (Search Engine Journal, 2020). Your showroom, team and product exist only on your site.
Original photographs can also carry your name. With IPTC metadata in the file or structured data on the page, Google Images can show the creator and credit, and a Licensable badge linking to your licence terms; the badge needs the IPTC Web Statement of Rights field or, in structured data, the license property (Image metadata in Google Images). Google does not guarantee the badge.
The checklist
- Each image sits near relevant text on a relevant page, with a caption where it helps.
- Alt text says what the image shows; decorative images have alt="".
- File names are short, descriptive and hyphenated before upload; indexed image URLs stay put or are redirected.
- Photographs are AVIF or WebP with a JPEG fallback; logos and icons are SVG.
- Images are exported at their displayed sizes, with responsive variants and compression judged by eye.
- The LCP image is not lazy-loaded; images further down are.
- Every image has a width and a height.
- Content images are img elements that robots.txt does not block.
- Original photographs carry IPTC creator, credit and rights fields.
Photographs are often a business website's most expensive asset and its heaviest; these checks decide whether they earn their keep. Because we photograph as well as build, we plan a shoot around the pages its images will sit on.
Sources
- Google Search Central, Google image SEO best practices: signals, alt text, file names, formats.
- Google Search Central, Image sitemaps: tags and limits.
- Google Search Central Blog, Spring cleaning: some sitemap extension tags are going away: deprecated image tags.
- Google Search Central, Image metadata in Google Images: IPTC and licensing.
- Google Search Central, Fix lazy-loaded content: lazy-loading.
- Google Search Central, Introduction to robots.txt: robots.txt and images.
- Google Search Central, URL structure best practices: hyphens, percent-encoding.
- Google Search Central, Site moves with URL changes: moving image URLs.
- web.dev, Optimize Largest Contentful Paint: the LCP image.
- web.dev, Optimize Cumulative Layout Shift: width and height.
- web.dev, Image performance: sizing, srcset, compression.
- MDN, Image file type and format guide: formats and browser support.
- W3C WAI, An alt decision tree and Decorative images: alt text.
- Search Engine Journal, 2019 and 2020: Google on renamed images and stock.
- Search Engine Roundtable, September 2024: Google on EXIF data.
- image SEO
- alt text
- Google Images
- page speed
- photography



