Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To help images appear in Google Search and Google Images, make them crawlable in HTML, use relevant page context and useful alt text, and provide clear image metadata. These practices help Google discover and interpret images; they cannot guarantee indexing, rankings, or which preview Google displays.

Make images discoverable to Google

Use an HTML <img> element with a working src URL. An image inside <picture> can also be discovered, provided its nested <img> has a usable fallback src. Google says it does not index images included only as CSS backgrounds. If important image URLs may not be found through your pages, an image sitemap can expose them; it is a discovery aid, not a guarantee of crawling or indexing. See Google’s image SEO best practices.

Use responsive markup with a fallback

Use srcset to offer image variants for different display sizes, or <picture> to group alternative formats or sources. In either case, keep a fallback URL in the nested <img src>.

<picture>
  <source type="image/avif" srcset="/images/blue-mug.avif">
  <source type="image/webp" srcset="/images/blue-mug.webp">
  <img src="/images/blue-mug.jpg" alt="Blue ceramic mug on a wooden desk">
</picture>

Google lists BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF as supported image formats. Use a filename extension that matches the file’s actual format. The supported-format list is not a ranking of formats or evidence that one format improves SEO more than another. See Google’s indexable file types.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

When an image sitemap helps

Consider adding image URLs to a sitemap if they are difficult to discover through crawlable page markup or if you want to keep Google informed when image URLs change. Sitemap image locations may use a different domain, which allows CDN-hosted images. Google recommends verifying the CDN domain in Search Console so you can see crawl errors for it. A sitemap does not force Google to crawl or index an image.

Give each image useful page context

Place an image near text that explains its subject, on a page genuinely relevant to that subject. Google can draw meaning from the surrounding page, captions, image titles, filenames, alt text, and computer vision. Image metadata is not a substitute for crawl access or relevant page content.

Write alt text for the image’s content and function

Google describes alt text as the most important image text metadata and notes its value to screen-reader users and people with low-bandwidth connections. Describe the relevant content or function of the image in a concise, natural way. For example, alt="Blue ceramic mug on a wooden desk" tells a reader more than alt="mug blue ceramic mug desk buy mug". Do not use alt text as a place to repeat target keywords: stuffing search terms degrades the experience and may be treated as spam.

Choose wording that matches the particular image and its role on the page. A caption can provide additional context, but it does not make a misleading or irrelevant image description useful.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use descriptive filenames

When practical, choose a short filename that identifies the image subject, such as blue-ceramic-mug.jpg instead of a generic camera name such as IMG00023.JPG. Google treats filenames as a light clue, not a replacement for alt text, page context, or crawlable image markup.

Help Google choose a representative preview

Google selects image previews automatically using multiple sources. You can indicate a preferred candidate with schema.org’s primaryImageOfPage, an image property on the main entity, or an og:image meta tag. Google says it uses both schema.org markup and og:image as sources when determining thumbnails in Search and Discover. These are inputs to selection, not instructions that guarantee a particular image will appear. The candidate should represent the page or entity; avoid relying on a generic site logo, extreme aspect ratios, or low-resolution images. See Google Search documentation updates and the visual elements gallery.

Choose between schema.org and Open Graph

Option What it does Practical guidance
schema.org image properties Identifies a preferred image for a page or its main entity. Use the property appropriate to the page’s structured data; keep the image relevant and representative.
og:image Provides an image URL that can inform preview selection. Set it to a suitable image for that page rather than a universal logo where a more relevant image exists.
Both Provides the same intended image through both sources. Keep the values consistent. Google still makes the final selection automatically.

Provide image rights and credit metadata when relevant

Google can receive rights information through structured data or embedded IPTC photo metadata. This can make an image eligible to show extra details, including a Licensable badge, but Google does not guarantee metadata will appear in search results. See Google’s image metadata guidance.

Structured data requirements

For an ImageObject, contentUrl is required, along with at least one of creator, creditText, copyrightNotice, or license. The license property is needed for eligibility for the Licensable badge. Add acquireLicensePage when available; Google recommends it.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Structured data or IPTC

Either method can supply rights and credit information. If both are present and conflict, Google says it uses the structured data. Check that the metadata describes the actual image and license. Removing metadata may reduce file size, but copyright and identification information can be legally important in some jurisdictions; retain rights information where possible.

Check the page and troubleshoot discovery

If an image is missing from Google, review the page and image delivery before changing keywords. These checks address common implementation problems without assuming that a particular change will make Google index the image.

  • Image does not appear in HTML: Confirm the image is delivered through an <img src>, including inside any <picture>, rather than only through CSS.
  • Responsive image has no fallback: Add a valid src to the nested <img>, even when using srcset or <source>.
  • Image URL may be hard to discover: Add it to an image sitemap and verify a separate CDN domain in Search Console if you use one.
  • Image is understood poorly: Put it on a relevant page near explanatory text, then review its alt text, caption, and filename for accuracy.
  • Wrong preview appears: Provide a relevant preferred candidate through schema.org image properties or og:image, and check that the two agree if both are used. Google may still select another preview.
  • Rights details are absent or inconsistent: Validate the image’s structured data or IPTC fields and resolve conflicts between them.
  • Image still is not shown: Correct markup and metadata improve discoverability and understanding but do not guarantee crawling, indexing, rankings, or display on a particular Google surface.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Or skip the browser setup

If you need clean screenshots of pages to review image placement, responsive behavior, or metadata-related page context, ScreenshotNeo is a website screenshot API and MCP server for developers. A single request can capture a URL as PNG, JPEG, WebP, or PDF. Its cookie/consent handling accepts banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents.

Example cURL request:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

See the ScreenshotNeo API documentation for request options. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Frequently Asked Questions

Will adding alt text make an image rank higher in Google?

Google recommends useful alt text for understanding images and accessibility, but its guidance does not promise a ranking increase.

Does Google guarantee it will use my og:image or primaryImageOfPage?

No. These can inform preview selection, but Google chooses previews automatically.

Do I need an image sitemap?

No. It can help expose image URLs Google might not otherwise discover, but it does not guarantee crawling or indexing.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.