This video was generated from the original Tygart Media article using NotebookLM’s audio-to-video pipeline. The article that describes how we automate image production became the script for an AI-produced video about that automation — a recursive demonstration of the system it documents.
Watch: Build an Automated Image Pipeline That Writes Its Own Metadata
What This Video Covers
Every article needs a featured image. Every featured image needs metadata — IPTC tags, XMP data, alt text, captions, keywords. When you’re publishing 15–20 articles per week across 19 WordPress sites, manual image handling isn’t just tedious; it’s a bottleneck that guarantees inconsistency. This video walks through the exact automated pipeline we built to eliminate that bottleneck entirely.
The video breaks down every stage of the pipeline:
- Stage 1: AI Image Generation — Calling Vertex AI Imagen with prompts derived from the article title, SEO keywords, and target intent. No stock photography. Every image is custom-generated to match the content it represents, with style guidance baked into the prompt templates.
- Stage 2: IPTC/XMP Metadata Injection — Using exiftool to inject structured metadata into every image: title, description, keywords, copyright, creator attribution, and caption. XMP data includes structured fields about image intent — whether it’s a featured image, thumbnail, or social asset. This is what makes images visible to Google Images, Perplexity, and every AI crawler reading IPTC data.
- Stage 3: WebP Conversion & Optimization — Converting to WebP format (40–50% smaller than JPG), optimizing to target sizes: featured images under 200KB, thumbnails under 80KB. This runs in a Cloud Run function that scales automatically.
- Stage 4: WordPress Upload & Association — Hitting the WordPress REST API to upload the image, assign metadata in post meta fields, and attach it as the featured image. The post ID flows through the entire pipeline end-to-end.
Why IPTC Metadata Matters Now
This isn’t about SEO best practices from 2019. Google Images, Perplexity, ChatGPT’s browsing mode, and every major AI crawler now read IPTC metadata to understand image context. If your images don’t carry structured metadata, they’re invisible to answer engines. The pipeline solves this at the point of creation — metadata isn’t an afterthought applied later, it’s injected the moment the image is generated.
The results speak for themselves: within weeks of deploying the pipeline, we started ranking for image keywords we never explicitly optimized for. Google Images was picking up our IPTC-tagged images and surfacing them in searches related to the article content.
The Economics
The infrastructure cost is almost irrelevant: Vertex AI Imagen runs about $0.10 per image, Cloud Run stays within free tier for our volume, and storage is minimal. At 15–20 images per week, the total cost is roughly $8/month. The labor savings — eliminating manual image sourcing, editing, metadata tagging, and uploading — represent hours per week that now go to strategy and client delivery instead.
How This Video Was Made
The original article describing this pipeline was fed into Google NotebookLM, which analyzed the full text and generated an audio deep-dive covering the technical architecture, the metadata injection process, and the business rationale. That audio was converted to this video — making it a recursive demonstration: an AI system producing content about an AI system that produces content.
Read the Full Article
The video covers the architecture and results. The full article goes deeper into the technical implementation — the exact Vertex AI API calls, exiftool commands, WebP conversion parameters, and WordPress REST API patterns. If you’re building your own pipeline, start there.
Related from Tygart Media
- The $0 Marketing Stack: Open Source AI, Free APIs, and Cloud Credits — The broader stack that this image pipeline fits into.
- Watch: The $0 Automated Marketing Stack — Video companion to the $0 stack article.
- How We Built a Free AI Agent Army With Ollama and Claude — The AI agent layer that orchestrates pipelines like this one.
- I Used a Monte Carlo Simulation to Decide Which AI Tasks to Automate First — How we prioritize which automation to build next.
Leave a Reply