Advanced Scenarios

Real-world examples of complex tasks you can accomplish with BlokMCP.

Scenario 1: Content Audit and Cleanup

Goal: Audit blog content and clean up outdated posts.

Step 1: Analyze content
- Show me all blog posts from 2022 and earlier
- Count how many are published vs draft
- List which ones have broken images (404 assets)
- Identify posts with missing required fields

Step 2: Categorize
- Tag posts from 2020-2021 as "legacy-content"
- Tag posts with broken images as "needs-asset-update"
- Tag incomplete posts as "needs-completion"

Step 3: Action plan
- Move legacy content to /blog/archive/
- For posts with broken images, find replacement assets
- For incomplete posts, either complete or delete

Step 4: Cleanup
- Unpublish archived posts
- Update posts with fixed assets
- Delete truly obsolete content

Scenario 2: Multilingual Product Launch

Goal: Launch 50 products in 3 languages simultaneously.

Step 1: Create English versions
- Create product stories from CSV data
- Upload product images to /products/2024-launch/
- Add products to "New Arrivals" datasource

Step 2: Translation setup
- Duplicate all English products to /es/ and /de/ folders
- Tag Spanish versions "needs-translation-es"
- Tag German versions "needs-translation-de"

Step 3: AI-assisted translation
- For Spanish versions, translate:
  * Product name
  * Description
  * Features list
- Keep SKUs, prices, and technical specs in English

Step 4: Review and launch
- Workflow: Draft → Translation Review → Approved
- Request approvals from language leads
- Schedule all for launch day at 9 AM local time

Scenario 3: Component Migration

Goal: Migrate 200 stories from old component to new version.

Step 1: Preparation
- Export current "hero_v1" component schema
- Create "hero_v2" with improved structure
- Document field mapping (title → headline, etc.)

Step 2: Test migration
- Duplicate one high-traffic story
- Manually convert hero_v1 to hero_v2
- Verify frontend renders correctly
- Confirm no data loss

Step 3: Gradual rollout
- Migrate 10 stories manually (high priority pages)
- Verify for 24 hours
- If good, migrate next 50 stories
- Continue in batches

Step 4: Final migration
- Get all remaining stories using hero_v1
- For each story:
  * Extract hero_v1 data
  * Map to hero_v2 fields
  * Replace component
  * Verify save successful

Step 5: Cleanup
- Verify zero stories still use hero_v1
- Move hero_v1 to "Archived Components" group
- Update documentation
- Delete hero_v1 after 30 days

Scenario 4: Automated Content Pipeline

Goal: Set up automated blog publishing pipeline.

Step 1: Workflow setup
- Create workflow: Draft → Editor Review → SEO Check → Scheduled → Published
- Configure stage permissions
- Set up auto-transitions

Step 2: Automation tasks
- Task 1: Auto-tag new posts with creation date
- Task 2: Generate SEO title suggestions
- Task 3: Calculate reading time
- Task 4: Webhook to Slack on status changes

Step 3: Approval routing
- Content in "Editor Review" → Email assigned editor
- In review > 3 days → Escalation email
- Approved posts → Auto-move to "Scheduled"

Step 4: Publishing
- Posts in "Scheduled" → Publish on specified date/time
- On publish → Trigger search index update
- On publish → Post to social media via webhook
- On publish → Email notification to author

Scenario 5: Asset Library Organization

Goal: Reorganize 5,000+ unorganized assets.

Step 1: Analysis
- Count assets by upload date
- Identify assets without folders
- Find assets with generic names (IMG_, Screenshot)
- List assets without metadata (alt, copyright)

Step 2: Automated organization
- Create folder structure:
  * /products/ (by category)
  * /blog/ (by year/month)
  * /marketing/ (by campaign)
  * /brand-assets/
  * /archive/

Step 3: Smart sorting
- Assets with "product-" → /products/
- Assets with "blog-" → /blog/YYYY/MM/
- Assets with "logo" → /brand-assets/
- Unclassified → /unsorted/ for manual review

Step 4: Metadata enrichment
- For all products/, add tag "product-photo"
- For all blog/, add tag with post slug
- Generate alt text from filename
- Add copyright notice to all

Step 5: Cleanup
- Find unused assets in /unsorted/
- Move to /archive/ if older than 1 year
- Delete duplicates
- Rename files to follow conventions

Scenario 6: SEO Optimization Audit

Goal: Audit and optimize 500 pages for SEO.

Step 1: Audit content
- Find pages without meta descriptions
- Find pages with titles > 60 characters
- Identify missing H1 tags
- Check for broken internal links
- Find images without alt text

Step 2: Prioritize fixes
- High traffic pages first (from analytics)
- Homepage and key landing pages
- Product pages
- Blog posts
- Other pages

Step 3: Optimize metadata
- Generate meta descriptions (150-160 chars)
- Optimize titles for keywords
- Add H1 tags where missing
- Ensure one H1 per page

Step 4: Content improvements
- Add alt text to all images
- Fix broken internal links
- Add schema.org markup
- Ensure mobile responsiveness

Step 5: Verify and monitor
- Re-check all pages
- Export sitemap
- Submit to Google Search Console
- Monitor rankings weekly

Scenario 7: Emergency Content Rollback

Goal: Quickly revert bad content deployment.

Step 1: Identify affected content
- List all stories published in last 2 hours
- Show what changed (use version history)
- Identify stories with issues

Step 2: Immediate mitigation
- Unpublish affected stories immediately
- Replace with previous versions if available
- Put up temporary "Under maintenance" message

Step 3: Root cause
- Review what went wrong
- Check if component change caused issue
- Verify data integrity

Step 4: Fix and republish
- Restore content from backups
- Test thoroughly before republishing
- Republish in small batches
- Monitor for issues

Step 5: Prevention
- Document what happened
- Add safeguards to prevent recurrence
- Update deployment checklist
- Train team on new procedures

Need help with complex scenarios? Describe your situation to Claude and ask for a step-by-step plan!