Image SEO for large sites (2026)

Image SEO makes your images discoverable, understandable and useful in search. On a large site, start with crawlable image URLs, accurate alt text, responsive files and landing pages that explain what each image shows. Fix shared templates before editing individual uploads. An image sitemap helps Google discover files, but it cannot repair blocked delivery or a product gallery that only loads after a click.

I'm Brenden House, founder of Searchmaxxed. We do technical SEO, content and AI search optimisation, including the implementation that turns an audit into changes on your website.

In summary

• Make important images available through ordinary HTML image elements and stable public URLs.
• Write alt text for the image's purpose on that page, not for a keyword quota.
• Keep product details and diagram labels readable when compressing files for mobile screens.
• Check the CDN, rendered page and image sitemap together before releasing a template change.
• Measure image-search traffic separately, then check whether the landing pages help people enquire, book a demo or find the information they need.

What does image SEO involve on a large website?

Image SEO covers the image file, its delivery, its description and the page that gives it meaning. Large sites need consistent rules across those parts.

Consider a manufacturer with product photographs, installation diagrams and downloadable specification sheets. This is a worked example, not a client result. A product photograph should help someone recognise the equipment; a diagram should explain a connection or clearance that affects whether the equipment will fit.

Different jobs need different treatment.

Searchmaxxed's technical SEO work covers crawling, indexing, mobile rendering, XML sitemaps and schema. Those checks belong alongside the content work, because fixing either side alone can leave the image unusable.

How does Google find and understand images?

Google discovers images through HTML image elements and image sitemaps, then uses the image and surrounding page to understand its subject. Access comes first.

Google's image SEO guidance states: “Google doesn't index CSS images”.

A meaningful product photograph therefore belongs in an <img> element, even when the surrounding layout uses CSS.

Keep a real src URL. Google recommends that fallback even when your site uses srcset or a <picture> element to offer different image versions for different devices.

Check the page around it. A photograph labelled “front view” on a generic gallery page gives less useful context than the same photograph beside the product name and specifications.

Searchmaxxed handles page copy, internal links and technical fixes together. For the manufacturer's catalogue, that means connecting the photograph to the correct product page rather than treating the media library as a separate SEO project.

How should you name image files and write alt text?

Use short, descriptive filenames and alt text that communicates the image's purpose in context. Neither field should become a list of search terms.

Alt text is an image’s text alternative. It helps people who cannot see the photograph, diagram or icon understand the information or function it provides on the page.

Google describes filenames as “very light clues” about subject matter. That's a useful correction to advice that makes renaming an entire media library sound like the main job.

For new uploads, use descriptive names. For existing files, weigh the naming improvement against changing URLs already referenced across your website, sitemaps and external pages.

Don't infer a certification from appearance. If a photo shows a stainless-steel housing, its alt text should not invent a food-safety rating or claim suitability for hazardous environments.

The W3C images tutorial makes the important distinctions:

• Informative images need a useful text alternative.
• Decorative images use alt="".
• Image-only links and buttons need text describing their function or destination.
• Complex charts and diagrams need a complete text equivalent of their information.

A caption isn't automatically an alt-text replacement. Nor is a tooltip.

Can one image have different alt text on different pages?

Yes. The description should fit the image's role on each page.

Keep the shared asset URL stable, but allow the CMS to store alt text against each placement. A catalogue overview and a maintenance guide may use the same photograph to explain different things.

That distinction matters at scale. Searchmaxxed's reusable page work needs both consistent technical behaviour and copy that answers the question on the individual page.

Which image formats and sizes should you use?

Choose formats by visual content, then compare the downloaded file and rendered result. Google supports JPEG, PNG, WebP, AVIF, SVG, GIF and BMP images, so format selection can follow the content rather than an imagined ranking preference.

There isn't one useful file-size target for every image. A product zoom and a small interface icon serve different purposes, so compressing both to an arbitrary limit can destroy useful detail.

Treat these as starting points.

Responsive images let browsers select an appropriate file for the available space, avoiding the need to send a large photograph to every device. Use srcset, sizes and a fallback src.

Set image dimensions so the browser can reserve space. Then check the layout on mobile rather than assuming that a smaller download means the page now works.

Performance needs its own measurement. Our Core Web Vitals guide covers that work in detail; this article focuses on preserving image discovery and meaning while improving delivery.

Can lazy loading stop images appearing in Google?

Lazy loading can hide images when the implementation depends on interaction or never exposes the real image URL to Google. Test the rendered page.

Lazy loading delays non-critical image downloads until they are needed. Google's lazy-loading guidance recommends viewport-based loading and warns that Google Search does not interact with your page.

Check click-only galleries carefully. Their images should remain discoverable in the rendered page without asking a crawler to open a lightbox or operate the gallery controls.

Use the following as an illustrative pattern for a below-the-fold diagram:

<img
  src="/images/pump-installation-diagram.webp"
  alt="Pump installation diagram with inlet and outlet connections"
  loading="lazy"
  width="1200"
  height="800">

Those dimensions are example values. Use the actual dimensions and aspect ratio of your file, with responsive styling that fits the page.

Keep the main loading image eager. Google's Largest Contentful Paint guidance says not to lazy-load the LCP image, because doing so delays its request.

For Searchmaxxed's mobile-rendering work, the useful check is whether the released page exposes the right image, not whether the CMS has a lazy-loading checkbox.

Do large sites need an image sitemap?

An image sitemap helps Google discover important images, including files that might be difficult to find through the page alone. It complements crawlable HTML.

Google accepts a separate image sitemap or image entries within an existing XML sitemap. Neither format gets preference in its image sitemap documentation.

This simplified example associates a public image with its product page:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
  <url>
    <loc>https://example.com/products/centrifugal-pump</loc>
    <image:image>
      <image:loc>https://images.example.com/pump-side.webp</image:loc>
    </image:image>
  </url>
</urlset>

The tags have different jobs. <loc> identifies the landing page, while <image:loc> identifies the image file associated with that page.

Google permits up to 1,000 images per page entry, according to that documentation. That's a limit, not a target.

Keep the generator current. Google has deprecated image:caption, image:geo_location, image:title and image:license in image sitemaps; those fields are not required additions to your XML.

Searchmaxxed's sitemap work should be checked against the released pages and files. A valid XML document still isn't useful if it lists deleted images or points to the wrong product photograph.

What can go wrong when images use a CDN?

A content delivery network can serve images efficiently, but its access rules and generated URLs must still allow crawling. Test the image host itself.

A CDN delivers files from distributed servers. Google permits cross-domain image URLs in image sitemaps and tells owners to verify the relevant domains in Search Console.

Check what you control with engineering. A provider's shared domain may need a different setup from a dedicated image subdomain that your organisation owns.

For a large catalogue, use this diagnostic list:

Don't disable security across the CDN when correcting a public-image delivery rule, because the same service may also handle confidential documents and private files.

Google recommends reusing the same URL across a larger website so it can cache the image rather than request the same file repeatedly.

This is where technical implementation matters. Searchmaxxed's managed work includes redirects, crawl fixes and deployment, so these issues can be addressed alongside the page rather than left as audit notes.

How should you prepare product images and diagrams for Google Lens and AI answers?

Use clear, accurate images with useful surrounding text, and keep important information available outside the image. Visual search does not remove the need for readable pages.

Google says Lens results can include similar images, websites showing them and AI Overviews. That supports publishing useful visuals, not a claim that adding alt text earns an AI citation.

For the manufacturer, show the equipment clearly. Put the model identifier and verified specifications on the page, with captions explaining the details someone might use to distinguish similar products.

For a SaaS company, use the current interface rather than a decorative dashboard mock-up. Explain the workflow beside the screenshot so the feature remains understandable without seeing it.

Diagrams need another check. Repeat the information in accessible text, including labels, relationships and any values needed to understand the diagram.

Google's AI-feature guidance says there are no extra technical requirements for AI Overviews or AI Mode. It recommends supporting text with useful visuals.

Searchmaxxed's AI search work includes plain facts and matching structured data, so the visual, description and product information should all tell the same story.

Does image schema help?

Relevant structured data connects the image to the page, describing whether it belongs to an article, a product or another type of content. Choose markup that matches the page.

Product pages should describe the actual product. Article images should belong to the article, and any licensing information must reflect rights you hold.

Google also accepts preferred-image signals through primaryImageOfPage, an entity's image property or og:image. Its selection remains automated.

Choose the preview deliberately. Google's image guidance advises against generic logos or text-heavy images as the preferred preview, even when a labelled diagram belongs inside the article.

A video thumbnail has a different job. Use our B2B video SEO guide for the requirements around video pages rather than treating a thumbnail as the whole implementation.

How do you turn image SEO into an engineering brief?

Write acceptance checks for each system that handles the image, with a named owner who can fix a failure and verify the released result. Missing-alt reports only cover one part.

Apply the matrix to the manufacturer's catalogue. It connects Searchmaxxed's technical SEO, page implementation and live verification work to specific checks, giving your engineering and content teams a shared brief.

Start with a representative product page. Check its mobile rendering, the direct image request and the sitemap entry before applying the template change across the catalogue.

Then test the exceptions: a gallery, a diagram, a translated page and a discontinued product. Each exercises a different part of the publishing system.

Searchmaxxed's managed plans use a 90-day plan broken into weekly releases, with the site, repository, content and data owned by the client. That makes the template fix part of ongoing website work rather than a separate spreadsheet your team has to interpret.

How do you measure whether image SEO is working?

Measure image visibility, landing-page behaviour and completed actions separately. More image impressions do not tell you whether the right people reached the right pages.

In Search Console, use the Image search type for Google Images traffic. Google's Performance report documentation distinguishes that from Web: multimodal traffic, which includes searches originating through Lens.

Keep those sources separate. Then compare changed page families over matched periods, checking country and device so a shift in audience doesn't disguise the result.

For Australia and the US, report each market separately. The implementation can be shared while the searches, landing-page language and commercial value differ.

Searchmaxxed includes Search Console and GA4 setup checks, plus monthly measurement against competitors. The report should explain which pages changed and what happened afterwards, without labelling every increase an image-only result.

Is Searchmaxxed right for your image SEO work?

Searchmaxxed fits teams that need technical fixes implemented alongside product pages, content and AI search optimisation. We handle the website changes as part of managed search work.

Growth System includes technical, schema and internal-link work without reducing its page-release commitment. Agentic Search Engineering adds comparison, industry and integration page families, while Custom & Enterprise can include dedicated engineering and multiple markets.

You work directly with the people doing the work, without an account-manager relay. The website and data stay yours.

For a large catalogue with broken delivery and inconsistent templates, the implementation scope matters far more than the number of warnings in an audit.

Frequently asked questions