Catalog/Image filename is generic/auto-generated (missed image-search signal)
SEO issue

Generic image filenames like IMG_1234: fix for image search

Filenames like IMG_0023.jpg or photo1.png waste an image-search ranking signal — Google reads the filename to understand the image. Find generic filenames and rename them.

2902
audited sites affected

What it means

One or more <img src> filenames match a generic auto-generated pattern — IMG_1234, DSC0019, photo1, image2, screenshot, pic3, untitled, or a bare UUID. These filenames carry no descriptive information about the image content.

Why it matters

Google uses the image filename as one signal of what an image depicts, alongside alt text and surrounding context. Its image guidance contrasts descriptive filenames (puppy.jpg) with generic ones (IMG00023.jpg) as better for image-search ranking. The filename is set precisely at upload time with no rendering dependency, making it a low-effort, persistent asset — and generic filenames often correlate with a careless image workflow overall.

How to fix it

  1. Before uploading, rename the file to describe its subject in plain language, using hyphens as separators.
  2. Keep filenames concise — two to four descriptive words.
  3. Use lowercase and hyphens only; avoid underscores, spaces and special characters.
  4. If renaming already-published images, update all src references and add 301 redirects from the old URLs.

Example

Before — HTML
<img src="/uploads/IMG_4821.jpg" alt="Handmade oak dining table">
After — HTML
<img src="/uploads/handmade-oak-dining-table.jpg" alt="Handmade oak dining table">

Rename the file to hyphen-separated descriptive words before upload. Google reads the filename as a signal of image content for Google Images ranking.

When it's not a problem

Decorative images (spacers, icons, textures) rarely need descriptive filenames and should carry alt="" instead. If a CDN transforms every filename into a hash or UUID you cannot control, this may fire for all images — consider whether a readable path prefix is possible, or suppress the rule where the CMS prevents filename control.

How Crawlinx detects it

We inspect each <img> src basename against generic patterns (IMG_1234, photo1, DSC00001, screenshot-…, and bare UUIDs). Matches are counted and flagged, because an auto-generated filename wastes an image-search signal.

How common is it?

2902 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.

FAQ

Do image filenames actually affect SEO?
For Google Images, yes — Google's own guidance says the filename gives it clues about the image's subject. It's a minor signal, but free to get right and it compounds across a large media library.
What makes a good image filename?
Short, descriptive, hyphen-separated words that match the image content: golden-retriever-puppy.jpg, not IMG_0231.jpg. Use hyphens, not underscores, as word separators.
Does renaming existing images help?
It can, but changing URLs means updating references and ideally 301-redirecting old paths. It's highest-value to fix the upload pipeline so new images get good names going forward.
Breakdowns

CMS

View breakdown →

Category

View breakdown →

Related
Catalog Image alt text is keyword-stuffed (repetition / low variety) Image alt text is very long (possible keyword stuffing) Broken image (src returns 4xx/5xx) Category CMS Likely hero image lacks fetchpriority=high Images missing alt text Images without width/height (layout shift / CLS) Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →