Asset Audit
Analyze assets on a Webflow site for SEO optimization.
Important Note
ALWAYS use Webflow MCP tools for all operations:
- Use Webflow MCP's
data_assets_tool for fetching and updating assets
- Use Webflow MCP's
get_asset_preview (with the asset's asset_id) for analyzing image content
- Use Webflow MCP's
data_sites_tool with action list_sites for listing available sites
- Use Webflow MCP's
webflow_guide_tool to get best practices before starting
- DO NOT use any other tools or methods for Webflow operations
- All tool calls must include the required
context parameter (15-25 words, third-person perspective)
Instructions
Phase 1: Site Selection & Asset Discovery
- Get site: Identify the target site. If user does not provide site ID, ask for it.
- Fetch all assets: Use Webflow MCP's
data_assets_tool to get all assets from the site (each asset record includes its asset_id, needed for previews)
- For sites with 50+ assets, process in batches of 20
- Show progress: "Processing assets 1-20 of 150..."
- Detect patterns: Analyze asset naming for common patterns:
- Camera uploads (IMG_, DSC_, etc.)
- Screenshots (screenshot, Screen Shot, etc.)
- Generic names (untitled, image-1, etc.)
- Date-based names (2024-01-10, etc.)
Phase 2: Issue Analysis & Pattern Recognition
- Identify issues: List all assets which:
- Do not have alt text set (null or empty string)
- Have existing alt text but it's poor quality (too short, redundant phrases, etc.)
- Do not have SEO-friendly asset names
- Are duplicates or very similar
- Pattern detection report: Show detected patterns:
- Ask user preference: Ask if they want to generate:
- Alt text only
- SEO-friendly names only
- Both
- Apply naming pattern/template
Phase 3: Analysis & Suggestion Generation
- Analyze assets: Use Webflow MCP's
get_asset_preview tool, passing each asset's asset_id (from Phase 1), to analyze the assets that need updates
- Error handling: If Webflow MCP's
get_asset_preview fails, use fallback:
- Extract description from existing filename
- Use generic placeholder with warning
- Continue with other assets
- Process in batches to avoid timeout
- Generate suggestions with validation:
- Alt text validation:
- Max 125 characters (warn if longer)
- No redundant phrases ("image of", "picture of", "photo of")
- Must end with punctuation
- Flag generic descriptions (confidence < 50%)
- SEO name validation:
- Only lowercase a-z, 0-9, hyphens
- No double extensions (.webp.webp) - strip existing extension first
- Max 100 characters
- Replace spaces/underscores with hyphens
- No special characters
- Folder organization suggestions: If patterns detected, suggest folder structure:
Phase 4: Granular Approval & Application
- Present suggestions with granular approval:
- Show numbered list with checkboxes
- Allow individual toggle: "Enter numbers to skip (e.g., '2,4')"
- Options: "all", "none", or specific numbers
- Show validation warnings for each suggestion
- Offer naming template (if many similar assets):
- Store rollback data: Before applying changes, store:
- Original asset names
- Original alt text
- Timestamp
- Assets modified
- Apply updates: Use Webflow MCP's
data_assets_tool to update approved assets only
- Show progress for batch updates
- Handle partial failures gracefully
- Report successes and failures separately
- Offer rollback option: After changes applied:
Examples
User prompt:
Step 1: Initial Audit Report
Example with Validation Warnings:
Step 2: After user selects option 3 and images are analyzed
Step 3: After user confirms with "all"
Alternative Step 3: User selects specific assets (e.g., "1,3")
Guidelines
Phase 1: Critical Validations (Must Follow)
File Extension Handling:
- ALWAYS strip existing extension before adding new one
- Bad:
image.webp → new-name.webp.webp
- Good:
image.webp → new-name.webp
- Implementation: Use filename without extension + new extension
Alt Text Quality Rules:
- Max length: 125 characters (accessibility best practice)
- Must end with punctuation (period, exclamation, question mark)
- Remove redundant phrases:
- ❌ "Image of a person" → ✅ "Person working at desk"
- ❌ "Picture of logo" → ✅ "Company logo on blue background"
- ❌ "Photo showing" → ✅ Direct description
- Flag if too short (< 10 chars): ⚠️ "Too generic - needs more detail"
- Flag if too long (> 125 chars): ⚠️ "Consider shortening for screen readers"
SEO Filename Rules:
- Only allow: lowercase a-z, numbers 0-9, hyphens
- Max length: 100 characters (before extension)
- Convert spaces to hyphens:
team photo → team-photo
- Convert underscores to hyphens:
team_photo → team-photo
- Remove special characters:
photo!@#$ → photo
- Convert to lowercase:
TeamPhoto → team-photo
- Remove consecutive hyphens:
team--photo → team-photo
- Trim leading/trailing hyphens:
-photo- → photo
Phase 2: Batch Processing & Performance
Large Site Handling:
- Sites with 50+ assets: Process in batches of 20
- Show progress: "Processing batch 1 of 5 (assets 1-20)..."
- Allow user to process specific batches
- Timeout protection: If Webflow MCP's
get_asset_preview takes > 30s, skip to next batch
Pattern Detection:
Detect and report these patterns:
- Camera uploads:
IMG_, DSC_, DCIM_, P_
- Screenshots:
screenshot, Screen Shot, Capture
- Generic names:
untitled, image-1, photo, asset
- Date formats:
2024-01-10, 20240110, 01-10-2024
- Suggest bulk rename when 3+ assets match a pattern
Error Handling:
- If Webflow MCP's
get_asset_preview fails:
- Log the error (don't show to user)
- Use fallback: Extract description from filename
- Mark with ⚠️ warning: "Generated from filename (image preview failed)"
- Continue with other assets
- Partial success handling:
- Report successes separately from failures
- Show: "✅ 15 updated, ❌ 2 failed, ⏭️ 3 skipped"
- Offer to retry failed assets
Phase 3: Advanced Features
Granular Approval System:
- Number each suggestion:
[1], [2], [3], etc.
- Show checkmark status:
✓ or ✗
- Accept multiple formats:
- "all" - approve all
- "none" - cancel operation
- "1,3,5" - skip items 1, 3, and 5
- "2-5" - skip items 2 through 5
- Always show validation status per item
Naming Templates:
Offer templates when 5+ similar assets detected:
[category]-[description]-[modifier]
- Example:
product-laptop-front-view.jpg
[description]-[location]-[year]
- Example:
team-photo-office-2024.jpg
[type]-[name]-[variant]
- Example:
icon-arrow-blue.svg
Folder Organization:
Suggest folders when detecting:
- 5+ images with "team", "staff", "employee" →
team-photos folder
- 5+ images with "product", "item" →
product-images folder
- 5+ images with "logo", "brand" →
branding folder
- 5+ images with "screenshot", "capture" →
screenshots folder
Rollback System:
Before any update, store in memory:
- Offer undo for 5 minutes after changes
- Clear rollback data after next audit starts
- Show rollback option in final summary
Duplicate Detection:
- Compare asset sizes (exact match = likely duplicate)
- Compare filenames (similar names = potential duplicate)
- Report: "⚠️ Potential duplicates: asset1.jpg (2.4MB) and asset1-copy.jpg (2.4MB)"
- Don't auto-delete - let user decide
General Best Practices
- Always use Webflow MCP's
get_asset_preview (with asset_id, not a URL) to understand image content
- Generate specific, descriptive suggestions (not generic)
- Validate all suggestions before presenting to user
- Handle partial operations gracefully
- Provide clear progress indicators for long operations
- Group similar issues together in reports
- Use visual indicators: ✅ ⚠️ ❌ 🔍 💡 📋 🎉
- Be conversational but concise
- Always offer rollback after changes