Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsUse a short, accurate filename in a simple URL path: for example, /images/black-kitten-playing.jpg rather than /images/IMG00023.JPG. Separate words with hyphens, use the language your audience reads, and keep the image URL stable when you reuse the image. A descriptive filename is only a light clue to Google—not a guarantee of indexing or better rankings—so make the image discoverable in your page’s HTML and give it useful surrounding context and alt text.
Choose a filename that describes the image
Name the file for what it actually shows, using a few specific words a reader would understand. For a photograph of a black kitten playing, black-kitten-playing.jpg is clearer than IMG00023.JPG or a string of unrelated search terms.
As an Amazon Associate I earn from qualifying purchases.
Google Search Central says, “Likewise, the filename can give Google very light clues about the subject matter of the image.” That is a modest signal, not a promise of a ranking change. The page’s relevance, image context, and whether Google can find and crawl the image matter too. See Google’s Image SEO Best Practices.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Be accurate: do not name an image for a subject it does not depict.
- Be concise: use the identifying details that distinguish the image, not a keyword list.
- Use the same language your intended readers use. If your site serves audiences in multiple languages, choose a consistent naming convention for each version.
Make the URL readable and consistent
Use a straightforward path and separate words with hyphens, such as /images/black-kitten-playing.jpg. Avoid joined-together words, underscores, and unnecessary query parameters when those parameters do not change which image is served. Google recommends a simple URL structure where practical; its guidance is at URL Structure Best Practices for Google Search.
#1 Best Overall
Choose one consistent casing convention—commonly lowercase—and stick with it. Google treats URLs as case-sensitive, so Black-Kitten.jpg and black-kitten.jpg can be different URLs. A server may handle case variants alike, but do not assume that it does.
Keep the same image at the same URL when it appears on multiple pages. A stable URL lets Google cache and reuse the resource. If you are changing URLs on an established site, do not rename files casually: update every reference and discovery path, and plan the migration. Google’s documentation does not prescribe one universal redirect rule for image renames. Its SEO Starter Guide also notes that Google may already understand an existing site’s URL structure.
Rank #2
Make images discoverable to Google
Expose the image through HTML
Make the image available in a standard HTML <img> element with a valid src URL. Responsive markup such as srcset or <picture> can help browsers select an appropriate version, but include a fallback src. Google says it does not index CSS images in the same way as images exposed through standard HTML image elements. See Google’s crawlable URL requirements.
Consider an image sitemap for harder-to-find images
An image sitemap can help Google discover images it might not otherwise find through page markup. For images hosted on a CDN, Google permits image sitemap entries that use external-domain image URLs. Google also encourages verifying ownership of the CDN domain in Search Console so you can see crawl errors for that domain. A sitemap can aid discovery; it does not guarantee indexing.
Use alt text and page context for their own purposes
Write alt text that communicates the image’s useful meaning in context, including for people who cannot see it. Do not turn it into a list of keywords or duplicate the filename mechanically. The text around the image should also make sense for the page. A descriptive URL cannot compensate for missing context, blocked crawling, or an image Google cannot discover.
Match the extension to the actual image format
Use an extension that reflects the file’s real format; do not rename a file to a different extension without converting it. For images referenced through an img src, Google documents support for BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF. The filename’s extension helps identify the resource, but changing the extension alone does not convert the image.
A practical naming workflow
- Describe the image. Write a concise, factual filename in the audience’s language, such as
black-kitten-playing.jpg. - Apply a consistent convention. Use lowercase and hyphens between words; avoid unnecessary query parameters if they do not alter the image.
- Put it in a simple path. Use a clear directory such as
/images/rather than adding needless path complexity. - Keep the URL stable. Reuse the same image URL across pages. For an existing site, assess references and migration impact before renaming files.
- Check discovery and context. Confirm the page exposes the image through an HTML
imgelement, has useful contextual text and alt text, and is not preventing crawling. Consider an image sitemap if discovery is otherwise difficult.
Common mistakes and fixes
- Keeping camera-generated names: replace names such as
IMG00023.JPGwith an accurate, readable description when practical. - Stuffing keywords into filenames or alt text: describe the image naturally and accurately instead.
- Using inconsistent case: settle on one casing convention and make references match the actual URL.
- Changing an established image URL without updating references: update page markup and discovery paths, and plan the migration rather than assuming the old and new URLs are interchangeable.
- Using only a CSS background for an important image: expose it with an HTML
imgelement when it should be discoverable as image content. - Assuming a descriptive URL guarantees visibility in search: check crawlability, page context, and discovery; naming alone cannot overcome those problems.
Or skip the browser setup
ScreenshotNeo is a website screenshot API, not an image-URL naming tool. It can capture a page for a visual check of how its images and surrounding content render; it does not optimize filenames or guarantee indexing. Its capture process removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are not billed; an MCP server lets AI agents take screenshots; and 1,000 screenshots a month are free with no card, with paid plans starting at $5 for 3,000. See ScreenshotNeo and the API documentation.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Sign up for 1,000 free screenshots a month, with no card required.
Quick Recap
Best Value
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.
