SEO Image Gen: AI Image Generation for SEO Assets (Extension)
Shared Data Cache
Step 0 -- Check shared data cache:
Before gathering, check .seo-cache/ for reusable context from related SEO skills.
Reference: ../seo/references/shared-data-cache.md for schemas and dependency map.
Check these cache files when present:
.seo-cache/site-meta.json for domain, business type, industry, and crawl context
.seo-cache/audit-scores.json for prior full-audit priorities
.seo-cache/pages/{url-slug}/page-analysis.json for page-level context when a URL is provided
If found: parse and use clearly valid fields (note "Using cached [X] from [date]")
If missing, corrupt, or irrelevant: continue with fresh evidence
If the user says "refresh" or "re-run": ignore cache reads and overwrite on write
Generate production-ready images for SEO use cases using Gemini's image generation
via the banana Creative Director pipeline. Maps SEO needs to optimized domain modes,
aspect ratios, and resolution defaults.
Architecture Note
This extension is built on the Banana image-generation pipeline
for SEO-specific image workflows in Codex.
This skill has two components with distinct roles:
Agent (agents/seo-image-gen.toml): Audit-only analyst spawned during /seo audit to assess existing OG/social images and produce a generation plan (never auto-generates)
Prerequisites
This skill requires the banana extension to be installed:
./extensions/banana/install.sh
Check availability: Before using any image generation tool, verify the MCP server
is connected by checking if gemini_generate_image or set_aspect_ratio tools are
available. If tools are not available, inform the user the extension is not installed
and provide install instructions.
Quick Reference
Command
What it does
/seo image-gen og <description>
Generate OG/social preview image (1200x630 feel)
/seo image-gen hero <description>
Blog hero image (widescreen, dramatic)
/seo image-gen product <description>
Product photography (clean, white BG)
/seo image-gen infographic <description>
Infographic visual (vertical, data-heavy)
/seo image-gen custom <description>
Custom image with full Creative Director pipeline
/seo image-gen batch <description> [N]
Generate N variations (default: 3)
SEO Image Use Cases
Each use case maps to pre-configured banana parameters:
Use Case
Aspect Ratio
Resolution
Domain Mode
Notes
OG/Social Preview
16:9
1K
Product or UI/Web
Clean, professional, text-friendly
Blog Hero
16:9
2K
Cinema or Editorial
Dramatic, atmospheric, editorial quality
Schema Image
4:3
1K
Product
Clean, descriptive, schema ImageObject
Social Square
1:1
1K
UI/Web
Platform-optimized square
Product Photo
4:3
2K
Product
White background, studio lighting
Infographic
2:3
4K
Infographic
Data-heavy, vertical layout
Favicon/Icon
1:1
512
Logo
Minimal, scalable, recognizable
Pinterest Pin
2:3
2K
Editorial
Tall vertical card
Generation Pipeline
For every generation request:
Identify use case from command or context (og, hero, product, etc.)
Apply SEO defaults from the use cases table above
Set aspect ratio via set_aspect_ratio MCP tool
Construct Reasoning Brief using the banana Creative Director pipeline:
Load references/prompt-engineering.md for the 6-component system
Be SPECIFIC and VISCERAL: describe what the camera sees
Generate via gemini_generate_image MCP tool
Post-generation SEO checklist (see below)
Check for Presets
If the user mentions a brand or has SEO presets configured:
python3 scripts/presets.py list
Load matching preset and apply as defaults. Also check references/seo-image-presets.md
for SEO-specific preset templates.
Post-Generation SEO Checklist
After every successful generation, guide the user on:
Alt text:Write descriptive, keyword-rich alt text for the generated image
File naming:Rename to SEO-friendly format: keyword-description-widthxheight.webp
WebP conversion:Convert to WebP for optimal page speed:
magick output.png -quality 85 output.webp
File size:Target under 200KB for hero images, under 100KB for thumbnails
Schema markup:Suggest ImageObject schema for the generated image:
{"@type":"ImageObject","url":"https://example.com/images/keyword-description.webp","width":1200,"height":630,"caption":"Descriptive caption with target keyword"}
OG meta tags:For social preview images, remind about:
<metaproperty="og:image"content="https://example.com/images/og-image.webp" /><metaproperty="og:image:width"content="1200" /><metaproperty="og:image:height"content="630" /><metaproperty="og:image:alt"content="Descriptive alt text" />
Cost Awareness
Image generation costs money. Be transparent:
Show estimated cost before generating (especially for batch)
Log every generation: python3 scripts/cost_tracker.py log --model MODEL --resolution RES --prompt "brief"
Run cost_tracker.py summary if user asks about usage
Approximate costs (gemini-3.1-flash):
512: ~$0.02/image
1K resolution: ~$0.04/image
2K resolution: ~$0.08/image
4K resolution: ~$0.16/image
Model Routing
Scenario
Model
Why
OG images, social previews
gemini-3.1-flash-image-preview @ 1K
Fast, cost-effective
Hero images, product photos
gemini-3.1-flash-image-preview @ 2K
Quality + detail
Infographics with text
gemini-3.1-flash-image-preview @ 2K, thinking: high
Rephrase prompt - see references/prompt-engineering.md Safety section
MCP unavailable
Fall back: python3 scripts/generate.py --prompt "..." --aspect-ratio "16:9"
Extension not installed
Show install instructions: ./extensions/banana/install.sh
Cross-Skill Integration
seo-images (analysis) feeds into seo-image-gen (generation): audit results from /seo images identify missing or low-quality images; use those findings to drive /seo image-gen commands
seo-audit spawns the seo-image-gen agent (not this skill) to analyze OG/social images across the site and produce a prioritized generation plan
seo-schema can consume generated images: after generation, suggest ImageObject schema markup pointing to the new assets
Crafted prompt:show what was sent to the API (educational)
Settings:model, aspect ratio, resolution
SEO checklist:alt text suggestion, file naming, WebP conversion
Schema snippet:ImageObject or og:image markup if applicable
Write to shared data cache
After completing all work, write a concise JSON summary to .seo-cache/ when the workflow produced durable findings.
Use the schemas and naming rules in ../seo/references/shared-data-cache.md; include at least cache_type, analyzed_at, source URL/domain, key findings, issues, recommendations, and tool limitations. Add .seo-cache/ to .gitignore if it is missing.
