AIO Copilot

Image SEO Checker

Paste a page's HTML to list every image with its alt text, size attributes, lazy loading and format, with the gaps flagged. It reads the markup only, so it cannot see file sizes.

How to use the image checker

Four steps, and how to read the flags.

  1. Copy the page source

    Right-click the page, choose View Page Source and copy all of it. Images that JavaScript adds after the page loads will not be in it.

  2. Run the check

    The tool pulls out every img tag and reads its src, alt, width, height and loading attributes. Nothing is uploaded and no image is downloaded.

  3. Read the summary

    The score starts at 100 and loses points by the share of images with each issue, weighted most heavily for missing alt text (30 points) and missing dimensions (20).

  4. Fix with judgement

    Missing alt text and missing dimensions are real problems. Empty alt is reported as decorative, so confirm each one really is decoration, and the first image is exempt from the lazy loading check because it is often the main image on screen.

How do I check my images for SEO?

Check four things on each image: that it is a real HTML img element, that its alt text describes it, that it has width and height so the page does not jump while it loads, and that the file is no heavier than it needs to be. Google's image SEO best practices cover the first two: standard HTML image elements help crawlers find and process images, and Google doesn't index CSS images. Google's web.dev guides cover the other two. The checker above runs the first pass on one page's HTML.

How does Google use alt text?

As one of several clues. Google says it uses alt text along with computer vision algorithms and the contents of the page to understand the subject matter of an image. Its example of good alt text is "Dalmatian puppy playing fetch", and it warns against filling alt attributes with keywords, which it says results in a negative user experience. Google sets no length limit; the 125 character warning in this checker is a common rule of thumb, not a Google rule. When an image is a link, the alt text does extra work: Google uses it as the anchor text, so a linked logo with no alt tells Google nothing about where the link goes.

When should alt text be empty?

When the image is decoration. The W3C's accessibility tutorial says decorative images should carry a null alt attribute, alt="", so screen readers skip them, and that leaving the attribute out is not an option because some screen readers then announce the file name instead. So the checker treats the two cases differently: a missing alt attribute is an error that costs points, and an empty one is reported as decorative, with no deduction. It is still worth confirming that each of those images really is decoration.

Why do images need width and height attributes?

So the browser can reserve the space before the file arrives. web.dev's CLS guide lists images without dimensions among the most common causes of poor Cumulative Layout Shift, one of Google's Core Web Vitals, and explains that browsers calculate an aspect ratio from the width and height attributes before the image loads. Setting height: auto in CSS keeps the image responsive while the ratio holds. Once the attributes are in, the Core Web Vitals calculator shows where your CLS field value sits against Google's 0.1 threshold.

Should every image be lazy-loaded?

No. web.dev's lazy loading guide says not to lazy-load images that are likely to be in the viewport when the page loads, especially the Largest Contentful Paint image, and its LCP guide says never to lazy-load the LCP image because that always adds delay. The checker follows that advice for the first img tag in the source: it never asks you to lazy-load it, and it warns if that image carries loading="lazy". Every later image without the attribute is flagged, so if the second or third image also sits in the first screen, leave its flag alone.

Do WebP, AVIF and filenames help rankings?

Not directly. Google indexes BMP, GIF, JPEG, PNG, WebP, SVG and AVIF images and states no preference among them in its image guidelines. Format matters for weight: Google's WebP page says lossy WebP files are 25 to 34% smaller than comparable JPEGs at equivalent quality, and lossless WebP files 26% smaller than PNGs. Images are often the heaviest part of a page: the median mobile home page carried 900 KB of images, against 558 KB of JavaScript, in the HTTP Archive's 2024 Web Almanac. The checker lists JPEG, PNG and GIF files for information and takes no points off for them.

Filenames matter even less. Google says a filename can give it very light clues about an image's subject and suggests short, descriptive names: my-new-black-kitten.jpg rather than IMG00023.JPG. Use descriptive names for new uploads; renaming a published image changes its URL, which is rarely worth it for clues that light. The checker notes names that are hashes, UUIDs or long strings of digits, but takes no points off for them.

What can't the checker see?

It never downloads an image, so it cannot see file sizes, pixel dimensions or whether an image is far larger than the space it fills. It reads only img tags: CSS backgrounds are ignored (Google does not index those either), and inside a picture element only the fallback img is read, so a WebP source with a JPEG fallback is noted as a JPEG. Images added by JavaScript after load are not in the page source at all. To see whether Google Images sends you visitors, filter Search Console's Performance report to the image search type. Images come up twice in our technical SEO audit checklist: as a cause of slow, shifting pages and as content the mobile version must carry.

Image SEO questions.

Alt text, formats, lazy loading and filenames.

How long should alt text be?

Google sets no limit. Its image guidelines ask for useful, information-rich alt text that uses keywords appropriately, and warn against filling alt attributes with keywords. This checker flags anything over 125 characters as a rule of thumb; a short phrase that says what the image shows is usually enough.

Should decorative images have alt text?

They should have an empty alt attribute, alt="", which tells screen readers to skip them, according to the W3C's accessibility tutorial. Leaving the attribute out entirely is worse, because some screen readers then read out the file name. The checker reports empty alt as decorative and takes no points off for it.

Does Google index CSS background images?

No. Google's image SEO guidelines say Google doesn't index CSS images and that standard HTML image elements help crawlers find and process images. Any image you want in Google Images should be an img element, with a src fallback if you also use srcset or the picture element.

Is WebP better than JPEG for SEO?

Not for ranking. Google lists WebP alongside BMP, GIF, JPEG, PNG, SVG and AVIF as supported formats and states no preference among them. The gain is weight: Google says lossy WebP files are 25 to 34% smaller than comparable JPEGs at equivalent quality, and lossless WebP files 26% smaller than PNGs, which helps pages load faster.

Should I lazy-load my hero image?

No. Google's web.dev guidance says never to lazy-load the Largest Contentful Paint image, because doing so always delays it. The checker treats the first img tag in the source as the likely hero: it takes no points off when that image lacks loading="lazy" and warns when it has it. Lazy-load the images further down the page instead.

Do image filenames affect SEO?

Very slightly. Google says a filename can give it very light clues about an image's subject and recommends short, descriptive names, such as my-new-black-kitten.jpg rather than IMG00023.JPG. That is worth doing for new uploads, but rarely worth renaming published images for, since a new name means a new image URL.

Added image dimensions? See where your CLS lands.

Enter the LCP, INP and CLS figures from your field data and the free Core Web Vitals Calculator shows where each one falls against Google's published thresholds.

Check your Core Web Vitals

What to do next.