seo-images
Skill0 starsChanged 3 months agoMITView on GitHub
Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, CLS prevention, image SERP rankings (via DataForSEO), and image file optimization (WebP/AVIF conversion, IPTC/XMP metadata injection). Use when user says "image optimization", "alt text", "image SEO", "image size", "image audit", "optimize images", "image metadata", "image SERP", "convert to webp", or "image file optimize".
- Installs packages
32 other projects use a version of this, 27 of them edited.
Adopted by
Most recently taken up by
- gaznil/seo-skills-by-gaznilword for word, first seen Nov 16, 2026
- martinbattaglia-commits/Claude-skillsedited, first seen Nov 16, 2026
- yotamwiesel/claude-skillsedited, first seen Nov 16, 2026
- joaoguirunas/team-osedited, first seen Nov 15, 2026
- YerayRodri/claude-skillsedited, first seen Nov 13, 2026
- seranking/seo-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use seo-agentic, seo-sxo and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AgriciDanielSkillseo-agentic
Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).
Also in 5 projects that use this
timruebenachSkillseo-sxo
Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".
Also in 18 projects that use this
timruebenachSkillseo-image-gen
AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".
Also in 16 projects that use this
mangollcSkillseo-local
Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.
Also in 20 projects that use this
- +3 more from timruebenach
Other versions32 projects use a version of this.
Word for word · 1
- gaznil/seo-skills-by-gaznil★ 0100% same
Edited · 27
- AgriciDaniel/claude-seo★ 30k83% same
- zhtyyx/codex-seo★ 15293% same
- coopersimson96/ai-content-system★ 1788% same
- joaoguirunas/team-os★ 694% same
- 01clauding/claude-seo-skill★ 488% same
- avalonreset/legends-seo-dungeon★ 499% same
- megastep/codex-skills★ 488% same
- realwigu/claude-skills★ 488% same
- alpit-patel/seo-aeo-geo-kit★ 292% same
- agrivisionai/claude-skills★ 192% same
17 more not listed
Wrote their own version · 4
- seranking/seo-skills★ 201same name
- oegeyilmaz9/seo-aeo-geo-ultimate★ 6same name
- amirjahfar1/automate-seo-with-claude★ 2same name
- david-corroy/skills-seo-geo★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms-full.txtllms.txt
- llms.txtllms.txt
- ab-testingSkill
- accessibilitySkill
- ai-seoSkill
- analyticsSkill
- attributionSkill
- blog-analyzeSkill
- blog-audioSkill
- blog-auditSkill
- blog-brandSkill
- blog-briefSkill
- blog-calendarSkill
- blog-cannibalizationSkill
- blog-chartSkill
- blog-clusterSkill
- blog-discourseSkill
- blog-factcheckSkill
- blog-flowSkill
- blog-geoSkill
- blog-googleSkill
- blog-imageSkill
- blog-locale-auditSkill
- blog-localizeSkill
- blog-multilingualSkill
- blog-notebooklmSkill
- blog-outlineSkill
- blog-personaSkill
- blog-repurposeSkill
- blog-rewriteSkill
- blog-schemaSkill
- blog-seo-checkSkill
- blogSkill
- blog-strategySkill
- blog-taxonomySkill
- blog-translateSkill
- blog-writeSkill
- canonical-tagSkill
- competitorsSkill
- content-optimizationSkill
- content-strategySkill
- copywritingSkill
- core-web-vitalsSkill
- croSkill
- directory-submissionsSkill
- eeat-signalsSkill
- entity-seoSkill
- featured-snippetSkill
- google-search-consoleSkill
- heading-structureSkill
- indexingSkill
- indexnowSkill
- internal-linksSkill
- keyword-researchSkill
- local-seoSkill
- meta-descriptionSkill
- mobile-friendlySkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 7 are common, 2 are distinctive, and 6 are very specific to this project.
7
Common
Most of the 30 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 64
Use progressive enhancement with the most efficient format first:
- Common: line 96
Do NOT lazy-load above-fold/hero images (hurts LCP)
- Common: line 97
Check for native vs JavaScript-based lazy loading
- Very specific: line 120
When auditing image SEO, report lazy_method alongside loading so users know whether their site is using a JS-driven lazy-loader (in which …
- Very specific: line 126
Add fetchpriority="high" to your hero/LCP image to prioritize its download in the browser's network queue:
- Very specific: line 132
Critical: Do NOT lazy-load above-the-fold/LCP images.
- Very specific: line 136
Add decoding="async" to non-LCP images to prevent image decoding from blocking the main thread:
- Common: line 164
Check if images served from CDN (different domain, CDN headers)
- Common: line 166
Check for edge caching headers
- Common: line 191
Add alt text to X images
- Common: line 192
Add dimensions to X images
- Distinctive: line 200
When DataForSEO MCP is available, enhance the image audit with competitive data.
- Distinctive: line 223
If DataForSEO MCP is not available, inform user and suggest installing the extension.
- Very specific: line 242
Before running: Check which tools are available with which exiftool cwebp convert ffmpeg.
- Very specific: line 382
When /seo images optimize is run on AI-generated assets, prompt the user to confirm the source type and inject the matching IPTC value …
“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Image Optimization Analysis
Checks
Alt Text
- Present on all
<img>elements (except decorative:role="presentation") - Descriptive: describes the image content, not "image.jpg" or "photo"
- Includes relevant keywords where natural, not keyword-stuffed
- Length: 10-125 characters
Good examples:
- "Professional plumber repairing kitchen sink faucet"
- "Red 2024 Toyota Camry sedan front view"
- "Team meeting in modern office conference room"
Bad examples:
- "image.jpg" (filename, not description)
- "plumber plumbing plumber services" (keyword stuffing)
- "Click here" (not descriptive)
File Size
Tiered thresholds by image category:
| Image Category | Target | Warning | Critical |
| Thumbnails | < 50KB | > 100KB | > 200KB |
| Content images | < 100KB | > 200KB | > 500KB |
| Hero/banner images | < 200KB | > 300KB | > 700KB |
Recommend compression to target thresholds where possible without quality loss.
Format
| Format | Browser Support | Use Case |
| WebP | 97%+ | Default recommendation |
| AVIF | 92%+ | Best compression, newer |
| JPEG | 100% | Fallback for photos |
| PNG | 100% | Graphics with transparency |
| SVG | 100% | Icons, logos, illustrations |
Recommend WebP/AVIF over JPEG/PNG. Check for <picture> element with format fallbacks.
Recommended <picture> Element Pattern
Use progressive enhancement with the most efficient format first:
<picture>
<source srcset="image.avif" type="image/avif">
<source srcset="image.webp" type="image/webp">
<img src="image.jpg" alt="Descriptive alt text" width="800" height="600" loading="lazy" decoding="async">
</picture>The browser will use the first supported format. Current browser support: AVIF 93.8%, WebP 95.3%.
JPEG XL: Emerging Format
Third-party reporting and Wikipedia describe a Rust-based JPEG XL decoder as shipped in Chrome 145 stable (2026-02-10) behind the chrome://flags/#enable-jxl-image-format flag, not enabled by default; no Google-owned confirmation was retrieved in the fact pack. Because default support is not confirmed, it is not yet practical for production web delivery. Keep serving AVIF/WebP with JPEG fallback and monitor.
Responsive Images
srcsetattribute for multiple sizessizesattribute matching layout breakpoints- Appropriate resolution for device pixel ratios
<img
src="image-800.jpg"
srcset="image-400.jpg 400w, image-800.jpg 800w, image-1200.jpg 1200w"
sizes="(max-width: 600px) 400px, (max-width: 1200px) 800px, 1200px"
alt="Description"
>Lazy Loading
loading="lazy"on below-fold images- Do NOT lazy-load above-fold/hero images (hurts LCP)
- Check for native vs JavaScript-based lazy loading
<!-- Below fold - lazy load -->
<img src="photo.jpg" loading="lazy" alt="Description">
<!-- Above fold - eager load (default) -->
<img src="hero.jpg" alt="Hero image">Detected lazy-loader methods (lazy_method field)
claude-seo run parse_html.py classifies each image's lazy-loading mechanism via the
lazy_method field on every image entry. Five values:
lazy_method | Signal detected | Common stack |
native | loading="lazy" HTML attribute | Modern browsers, plain HTML |
perfmatters | data-perfmatters-src/-srcset OR class perfmatters-lazy | WordPress + Perfmatters plugin |
ewww | data-ewww-src / data-eio OR class lazyload-eio | WordPress + EWWW Image Optimizer |
js-generic | data-src / data-lazy-src / data-original / data-srcset OR class lazyload/lazyloaded/lazy | Lazysizes, vanilla-lazyload, jQuery plugins |
none | Neither attribute nor class signal | Page is not lazy-loading this image |
When auditing image SEO, report lazy_method alongside loading so users know
whether their site is using a JS-driven lazy-loader (in which case the native
loading="lazy" attribute is intentionally absent, that is not a regression).
fetchpriority="high" for LCP Images
Add fetchpriority="high" to your hero/LCP image to prioritize its download in the browser's network queue:
<img src="hero.webp" fetchpriority="high" alt="Hero image description" width="1200" height="630">Critical: Do NOT lazy-load above-the-fold/LCP images. Using loading="lazy" on LCP images directly harms LCP scores. Reserve loading="lazy" for below-the-fold images only.
decoding="async" for Non-LCP Images
Add decoding="async" to non-LCP images to prevent image decoding from blocking the main thread:
<img src="photo.webp" alt="Description" width="600" height="400" loading="lazy" decoding="async">CLS Prevention
widthandheightattributes set on all<img>elementsaspect-ratioCSS as alternative- Flag images without dimensions
<!-- Good - dimensions set -->
<img src="photo.jpg" width="800" height="600" alt="Description">
<!-- Good - CSS aspect ratio -->
<img src="photo.jpg" style="aspect-ratio: 4/3" alt="Description">
<!-- Bad - no dimensions -->
<img src="photo.jpg" alt="Description">File Names
- Descriptive:
blue-running-shoes.webpnotIMG_1234.jpg - Hyphenated, lowercase, no special characters
- Include relevant keywords
CDN Usage
- Check if images served from CDN (different domain, CDN headers)
- Recommend CDN for image-heavy sites
- Check for edge caching headers
Output
Image Audit Summary
| Metric | Status | Count |
| Total Images | - | XX |
| Missing Alt Text | ❌ | XX |
| Oversized (>200KB) | ⚠️ | XX |
| Wrong Format | ⚠️ | XX |
| No Dimensions | ⚠️ | XX |
| Not Lazy Loaded | ⚠️ | XX |
Prioritized Optimization List
Sorted by file size impact (largest savings first):
| Image | Current Size | Format | Issues | Est. Savings |
| ... | ... | ... | ... | ... |
Recommendations
- Convert X images to WebP format (est. XX KB savings)
- Add alt text to X images
- Add dimensions to X images
- Enable lazy loading on X below-fold images
- Compress X oversized images
Image SERP Analysis
When DataForSEO MCP is available, enhance the image audit with competitive data.
/seo images serp <keyword>
Cross-reference on-page images with Google Images SERP rankings.
Workflow:
- Fetch Google Images results via
serp_google_images_live_advanced(depth=100) - Extract: top domains, image types, alt text patterns
- Output competitor image SERP landscape
Output:
| Rank | Domain | Title/Alt | Image URL | Page URL |
| 1 | example.com | "Blue running shoes..." | .../shoes.webp | /products/... |
Analysis includes:
- Domain dominance: which sites own the most image positions (top 10 by count)
- Alt text patterns: common title/alt patterns in top-ranking images
- Format distribution: WebP vs JPEG vs PNG in top results
- Opportunity score: keywords where you have page rankings but no image presence
If DataForSEO MCP is not available, inform user and suggest installing the extension.
Image File Optimization
Optimize image files for SEO: format conversion, metadata injection, compression.
/seo images optimize <path>
Optimize image file(s) for web and SEO. Converts to WebP/AVIF, injects IPTC metadata, compresses, and generates responsive variants.
Tools used (in order of preference):
exiftool-- EXIF/IPTC/XMP read/write (install:sudo apt install libimage-exiftool-perl)cwebp-- WebP conversion (install:sudo apt install webp)- ImageMagick
convert-- Format conversion, resizing (pre-installed on most systems) - FFmpeg -- Fallback for format conversion (pre-installed)
Before running: Check which tools are available with which exiftool cwebp convert ffmpeg.
Format Conversion
Convert images to modern formats with metadata preservation:
# WebP (recommended default) - with metadata preserved
cwebp -q 82 -metadata all input.jpg -o output.webp
# WebP via ImageMagick (fallback if cwebp not installed)
convert input.jpg -quality 82 output.webp
# AVIF via FFmpeg (slower encode, best compression)
ffmpeg -i input.jpg -c:v libaom-av1 -crf 30 -still-picture 1 output.avif
# Responsive variants (400w, 800w, 1200w)
convert input.jpg -resize 400x -quality 82 image-400.webp
convert input.jpg -resize 800x -quality 82 image-800.webp
convert input.jpg -resize 1200x -quality 82 image-1200.webpMetadata Injection (IPTC for Google Images Display)
Google Images displays IPTC Creator, Credit Line, and Copyright in search results. This is NOT a ranking factor but can improve Google Images display and brand attribution.
With exiftool (preferred):
# Read all metadata
exiftool image.jpg
# Inject IPTC + XMP metadata for Google Images rich results
exiftool \
-IPTC:ObjectName="Product Photo Description" \
-IPTC:Caption-Abstract="Detailed image description" \
-IPTC:By-line="Brand Name Photography" \
-IPTC:Credit="Brand Name" \
-IPTC:CopyrightNotice="Copyright 2026 Brand Name" \
-IPTC:Source="brandname.com" \
-XMP:Title="Product Photo Description" \
-XMP:Description="Detailed image description" \
-XMP:Creator="Brand Name Photography" \
-XMP:Rights="Copyright 2026 Brand Name" \
image.jpg
# Batch inject to all images in directory
exiftool -overwrite_original \
-IPTC:By-line="Brand Name" \
-IPTC:CopyrightNotice="Copyright 2026 Brand Name" \
*.jpg *.webp *.pngWith ImageMagick (fallback):
identify -verbose image.jpg | head -50
convert input.jpg \
-set comment "Product Photo Description" \
-set IPTC:2:80 "Brand Name Photography" \
-set IPTC:2:116 "Copyright 2026 Brand Name" \
output.jpgNote: WebP supports EXIF and XMP but not IPTC natively. For WebP files, use XMP fields instead of IPTC. exiftool handles this conversion automatically.
AI-Generated Images: DigitalSourceType (Merchant Center requirement)
For product images produced by generative AI, Google Merchant Center requires
IPTC DigitalSourceType: TrainedAlgorithmicMedia metadata. This is an
operational policy requirement, not a ranking factor: feeds missing this label
on AI-generated imagery can be disapproved.
Primary source (Merchant Center AI-generated content policy): https://support.google.com/merchants/answer/14743464 (the ai-optimization-guide does not document DigitalSourceType/IPTC/Merchant labeling.)
Audit command:
# Audit a directory for the IPTC label (counts: missing, ai, captured, etc.)
claude-seo run iptc_ai_label.py audit ./images/ --json
# Audit a single image
claude-seo run iptc_ai_label.py audit ./hero.webp --json
# Inject the AI label into an image
claude-seo run iptc_ai_label.py inject ./ai-hero.webp \
--source-type trainedAlgorithmicMedia
# Other vocabulary values:
# compositeSynthetic (mix of captured + AI elements)
# algorithmicMedia (created purely by algorithm, NOT from sampled training data)
# compositeWithTrainedAlgorithmicMedia (e.g. AI inpainting/outpainting over real media)
# digitalCapture (fully captured photograph)Raw exiftool equivalents (for ad-hoc usage):
# Inject manually
exiftool \
-XMP-iptcExt:DigitalSourceType="https://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia" \
ai-generated-product.jpg
# Audit: find images missing the label across a directory
exiftool -if 'not $XMP-iptcExt:DigitalSourceType' \
-filename -DigitalSourceType *.jpg *.webp *.pngGoogle extracts these IPTC DigitalSourceType values:
trainedAlgorithmicMedia: fully AI-generated (use this for diffusion-model product imagery)compositeSynthetic: mixes captured + AI-generated elementsalgorithmicMedia: created purely by an algorithm, not from sampled training datacompositeWithTrainedAlgorithmicMedia: composite of trained algorithmic media + other media (e.g. AI inpainting/outpainting over a real photo)digitalCapture: fully captured photograph (note:digitalCaptureis not on Google's extracted-values list, but is a valid IPTC value)
Provenance signals (consumer-facing): SynthID watermarks and C2PA Content Credentials are emerging signals for AI media identification. Treat product-surface coverage as subject to change unless verified from a current Google-owned source. This is detection/transparency, not an extra required Merchant feed field beyond IPTC DigitalSourceType.
Licensable images: to earn the Licensable badge, supply EITHER structured data (
ImageObjectwith thelicenseproperty +acquireLicensePagefor the "Get this image" link) OR embedded IPTC photo metadata (Licensor URL / Web Statement of Rights). Cross-linkseo-schemafor the ImageObject markup.
Discovery note: image discovery now includes visual search fan-out across Lens / AI Mode / Circle to Search (Gemini multimodal scene/object understanding), so images surface via scene, objects, and materials, not alt text alone. No new published image-SEO lever yet; keep descriptive alt text + clean structured data.
When /seo images optimize is run on AI-generated assets, prompt the user to
confirm the source type and inject the matching IPTC value automatically.
For AI-generated product titles and descriptions, Google Merchant Center
also requires the AI-generated text to be separately specified and labeled in
the feed. This is enforced at the feed layer, not the page layer, flag this
in cross-reference with seo-ecommerce.
Metadata Audit
# Quick audit with exiftool
exiftool -IPTC:all -XMP:all -EXIF:ImageDescription image.jpg
# Batch audit - find images missing IPTC Creator
exiftool -if 'not $IPTC:By-line' -filename *.jpg *.webp *.pngFull Optimization Pipeline
For maximum image SEO, run this pipeline on each image:
- Audit existing metadata:
exiftool -IPTC:all -XMP:all image.jpg - Inject IPTC/XMP metadata: Creator, Copyright, Description
- Convert to WebP:
cwebp -q 82 -metadata all image.jpg -o image.webp - Generate responsive variants: 400w, 800w, 1200w
- Verify metadata preserved:
exiftool image.webp - Generate
<picture>HTML: AVIF > WebP > JPEG fallback chain
What Matters vs What Doesn't for Google Images
| Factor | Impact | Where to Set |
| Alt text | CRITICAL (ranking) | HTML <img alt=""> |
| Filename | HIGH (ranking) | File system (descriptive, hyphenated) |
| Page context | HIGH (ranking) | Surrounding HTML content |
| File size/speed | MEDIUM (indirect via CWV) | Compression + format conversion |
| IPTC Creator/Copyright | LOW (display only) | Image file metadata |
| EXIF camera data | NONE | Irrelevant for SEO |
| IPTC Keywords | NONE | Google ignores these |
Error Handling
| Scenario | Action |
| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if site requires authentication. |
| No images found on page | Report that no <img> elements were detected. Suggest checking if images are loaded via JavaScript or CSS background-image. |
| Images behind CDN or authentication | Note that image files could not be directly accessed for size analysis. Report available metadata (alt text, dimensions, format from markup) and flag inaccessible resources. |
| exiftool not installed | Fall back to ImageMagick for metadata. Recommend: sudo apt install libimage-exiftool-perl |
| cwebp not installed | Fall back to ImageMagick or FFmpeg for WebP conversion. Recommend: sudo apt install webp |
| DataForSEO MCP not available | Skip Image SERP Analysis section. Note extension is not installed. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

