On this page
Write alt text that describes the image
Alt text is the written description of an image. It serves people using screen readers first, and it gives Google context about what the image shows. Describe what is actually there, in a short natural phrase, and use the page’s topic where it fits. Do not stuff keywords or start with “image of”.
Examples. A product photo: “Navy wool crew-neck sweater laid flat on a wooden table”. A chart: “Bar chart of monthly organic sessions rising from 2,100 to 4,800 over six months”. A team photo on an about page: “Three plumbers in grey uniforms standing beside a service van”. A purely decorative image should have empty alt text so screen readers skip it. If the image is a link, the alt text should describe where the link goes.
Do not use alt text for things the page text already says in full. If an image is a decorative divider or repeats the caption beneath it, leave the alt empty or keep it short. Over-describing slows down screen reader users and adds nothing for search engines.
Name files and place images near relevant text
Use a short descriptive file name: navy-wool-sweater.webp beats IMG_4032.jpg. Separate words with hyphens. Google also uses the surrounding text, the caption, and the page title to understand an image, so place images next to the paragraph they illustrate and add a caption when it helps a reader.
Put images in the page with a standard img element and a real source address. Images loaded only as CSS backgrounds or after a script runs may not be picked up for image search. Where it makes sense, use unique images rather than stock photos, since the same file on a thousand sites adds little.
Consider the page the image sits on as the real unit. A relevant photo on a strong page is more likely to appear in image results than the same photo on a thin page. Add a caption only where it helps a reader, and make sure the image is a fair illustration of what the text says.
Want the articles written for you?
Researches keywords and what competitors rank for. Publishes to WordPress, Webflow, Shopify or Framer once you approve.
Compress, convert, and size correctly
Large images are the most common cause of a slow Largest Contentful Paint. Export at the largest size the layout actually displays, not the camera original. Use modern formats: WebP is widely supported, and AVIF compresses further where the tooling allows it. Keep JPEG or PNG as a fallback only if you need one.
Serve responsive versions with srcset so phones download smaller files than desktops. Set width and height attributes so the browser reserves space and the layout does not shift. The effect on speed and stability is covered in Core Web Vitals.
A quick way to choose quality: export at several compression levels and compare at the displayed size. Most photos look identical at a much smaller file than the default export, and the savings are often large across a page with ten images.
Lazy-load the rest, not the hero
Native lazy loading, the loading attribute set to lazy, delays images below the fold until the visitor scrolls near them. It saves bandwidth and speeds the first render. Do not apply it to the main image visible on load, because that delays the largest paint and hurts the metric you are trying to improve. Consider preloading that image instead.
Google can handle native lazy loading, but images that only load on a scroll event or click may never be seen by the crawler. Check with the URL Inspection tool that the rendered page includes your images.
Image mistakes that cost rankings and speed
The usual problems are quick to spot. Hero images uploaded at four thousand pixels wide and shown at one thousand. Text baked into an image, which search engines and screen readers cannot read, so the words should be real text on the page. File names left as camera defaults. Missing dimensions that make the page jump as images load.
Another is using the same alt text on every image on a page, or stuffing a keyword into all of them. Alt text should differ because the images differ. A third is relying on images loaded by a script that crawlers cannot run, such as a carousel that only loads on interaction.
Audit with a crawler: export all images with their size, dimensions, and alt text, and sort by file size to find the biggest wins. Fix the top twenty and the template-level images first, since a header image appears on every page.
Help Google find and show them
If images are important to your business, such as a shop or a portfolio, list them in an image sitemap or add image entries to your existing sitemap. Add product schema so product images can be eligible for richer results. Keep the image address stable, since changing it forces Google to start over.
Image search is a real traffic source for visual topics, but the same principles apply as to web pages: relevance, quality, and a good page around the image. Add images to the technical SEO checklist and the product-page work in product page SEO.
Questions
How long should alt text be?
Keep it to a short phrase or one sentence, a rule of thumb being under about 125 characters. Say what the image shows and why it is on the page. Longer descriptions belong in the surrounding text.
Does alt text help SEO?
Yes. Google uses alt text, along with the page text and file name, to understand an image, and it is how images can rank in image search. It is also required for accessibility, which is the main reason to write it well.
What image format is best for SEO?
WebP is a safe default today, and AVIF can be smaller still. The best format is the one that gives the smallest file at acceptable quality and that your platform serves reliably.
Should I add keywords to image file names?
Use descriptive words that match the image, which often includes the topic. Do not repeat keywords or string many together. A clear file name is a small signal, not a lever.
Do I need an image sitemap?
Usually not, if images appear normally in the page HTML. It helps when images are loaded by script or sit on pages that are hard to crawl, or when image search matters to your business.