SEO & Content LLM Prompts Intermediate

Image Seo Optimizer

Optimize images with alt text, compression, and metadata to improve search rankings and accessibility.

Best Model
ChatGPT GPT-5.5 + Perplexity Sonar for current researchResearch-grounded SEO
Brevity Mode
Concise
Difficulty
Intermediate
Automation
Needs user context

Use This When

Articles, service pages, AEO/GEO content, interlinking, SERP-informed briefs.

Inputs Needed

URL, target keyword, audience, competitors, location, search intent, internal links, products/services.

Expected Output

SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions.

The Workflow Prompt

Copy-paste ready. Replace [bracketed placeholders] with your specifics.
You are a technical SEO strategist and editorial content lead.

Objective:
Image Seo Optimizer

Context:
Optimize images with alt text, compression, and metadata to improve search rankings and accessibility.

Original task:
You are a world-renowned image SEO expert who has optimized 50,000+ images, generating millions of clicks from Google Images and increasing overall organic traffic by 30%+ through image optimization alone. Your expertise includes image format optimization, alt text strategy, image title optimization, structured data for images, visual search optimization, and image search ranking factors.Create a comprehensive image SEO strategy for [YOUR_DOMAIN]. Provide:1. **Current Image Audit**: Analyze all images on your site; assess alt text quality, file names, sizes, and optimization level2. **Image Format Optimization**: Recommend format conversions (WebP, AVIF, modern formats) for faster loading and better quality3. **File Size & Compression**: Analyze image file sizes; recommend compression ratios and tools maintaining visual quality4. **Responsive Images**: Recommend srcset implementation for different device sizes and resolutions5. **Alt Text Strategy**: Provide alt text writing guidelines; write optimized alt text for 50+ priority images balancing accessibility and SEO6. **File Naming Optimization**: Recommend semantic file naming conventions; provide new names for priority images7. **Image Context & Placement**: Analyze image placement within content; recommend repositioning for better relevance signals8. **Image Title & Caption Optimization**: Recommend optimized image titles and captions incorporating keywords naturally9. **Image Schema Markup**: Recommend schema implementation (ImageObject, schema:image properties) for image SEO10. **Image Linking Strategy**: Recommend anchor text optimization for links from images11. **Google Images Ranking**: Analyze images ranking in Google Images; recommend optimization for image search visibility12. **Visual Search Optimization**: Recommend optimization for visual search (Pinterest Lens, Google Lens, Amazon Visual Search)13. **Image Sitemap**: Create or optimize image sitemap submission

Inputs I may provide:
URL, target keyword, audience, competitors, location, search intent, internal links, products/services.

Operating instructions:
- First, restate the objective in one clear sentence.
- If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them.
- Use a Concise response style.
- Be specific to the business, audience, channel, and constraints provided.
- Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use.
- When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources.
- Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead.
- End with a short QA checklist that helps me verify the output.

Required output:
SEO brief or content draft with search intent, outline, on-page elements, internal links, FAQ, schema suggestions.

Caution:
Use live web research or source documents before finalizing claims.

QA Follow-Up Checklist

After the AI returns its output, verify against:

  1. Output is specific to the provided business/context.
  2. Assumptions are clearly labeled.
  3. No unsupported claims without source checks.
  4. Next actions are clear and usable.
  5. Search intent, internal links, FAQ, and on-page elements are included.

Follow-Up Prompt

Run this next to refine the first output into a client-ready version.
Now turn the result for 'Image Seo Optimizer' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.

Avoid / Cautions

Use live web research or source documents before finalizing claims.

How Different Verticals Use This Workflow

Restaurant & Hospitality

A 25-table farm-to-table restaurant whose menu PDFs rank but image-light menu page doesn't runs the prompt against their dish photos. Output: rename 40 dish photos with semantic file names ('grilled-octopus-charred-lemon.webp'), add structured alt text mentioning the dish + location, and implement Recipe schema. Google Images traffic to the menu page goes from 8/mo to 340/mo in 90 days.

Retail & E-commerce

An online furniture retailer with 2,000 PDPs and slow LCP on listings runs the prompt against their image pipeline. Output: convert hero images to AVIF, lazy-load below-fold, add srcset, write alt text with product + use-case ('walnut bookshelf in modern home office'). LCP drops from 4.2s to 1.8s, mobile conversion lifts 12% in 60 days.

Professional Services & B2B

A consulting firm with 30 case study pages and stock photos throughout runs the prompt. Output: replace stock with branded screenshots of dashboards/deliverables, alt text describes the artifact + outcome ('client SaaS dashboard showing 3x lift in trial conversion'). Case studies start ranking for 'B2B SaaS conversion case study' queries that drive 4 inbound leads/month.

Beauty & Personal Care

A skincare brand with before/after photos that bounce off Google but not Pinterest runs the prompt. Output: ImageObject schema with creator + license, alt text describing skin condition + outcome, structured comparison images. Pinterest reverse-traffic 5x'd as Google Lens started serving their before/afters in visual search results.

Local & Trade Services

A landscaping company with 200 portfolio photos and zero image traffic runs the prompt. Output: rename files by project type + neighbourhood ('paver-patio-leaside-toronto.webp'), alt text mentions service + location, LocalBusiness + ImageObject schema. Google Images becomes their #2 traffic source within 4 months, driving 18 quote requests/month.

Frequently Asked

Does image SEO actually drive real traffic in 2026 or is it a vanity exercise?

It drives traffic in three cases: visual-heavy verticals (recipes, fashion, home design, travel) where Google Images is a discovery surface, product pages where image carousels in SERPs steal clicks, and any page where Core Web Vitals are blocking rank. Outside those, it's hygiene — won't hurt, won't move the needle. Don't run a 50-image alt text rewrite if your real bottleneck is thin content.

What's the right way to write alt text that's useful for SEO and not creepy keyword-stuffed?

Describe the image as you'd describe it to a blind friend, then add one natural keyword phrase if it fits. 'Woman in red coat standing in Toronto's distillery district at dusk' beats 'red wool coat winter outerwear Toronto fashion 2026.' Screen readers and Google both reward clarity over density. The alt-text-as-keyword-dumping-ground tactic was killed around 2018; it now reads as spam to both systems.

Should I rename every existing image file or is that a waste of time?

Rename only the priority images on money pages (product hero shots, recipe step images, location photos for local SEO). The lift per file is small and renaming breaks any existing image links if you don't 301 the old URLs. Set the naming convention going forward, rename the top 50-100 images, and stop. Renaming 8,000 archive blog images yields nothing measurable and consumes a week.

WebP, AVIF, or just stick with JPEG — what's the actual call in 2026?

AVIF for hero images and above-the-fold (best compression, all modern browsers support it now). WebP for everything else with JPEG fallback only if you have measurable IE/Safari-old traffic, which you almost certainly don't. Run Squoosh or Cloudinary's auto-format and stop debating. The 12 months of arguing about formats cost more in dev time than any compression saved.

Related Workflows

Copied to clipboard