Automatically generate content with AI

🏗️ Architecture of an AI content pipeline

Overview of the flow

A mature AI content pipeline follows these steps:

Brief → Writing → SEO → Translation → Image → Review → Publication

Each step can be automated, but with different confidence levels:

The fundamental principle: the right models in the right places

The most common mistake is using the same model (often the most expensive) for all steps. In reality, each task has different requirements:

• Long-form writing → premium model (Claude Opus, GPT-4) for writing quality
• SEO / metadata → economical model (Gemini Flash, Haiku) for structured tasks
• Translation → mid-range model (Claude Sonnet) for the quality/cost balance
• Ideation / brainstorm → fast model (Flash) to iterate quickly

This strategy can divide your costs by 3 to 5 with no perceptible loss of quality.

📝 Step 1: From brief to writing

Structuring the brief

A good brief is the foundation of everything. AI needs clear guidelines to produce relevant content:

## Brief article

- **Title** : How to get started with AI agents
- **Audience** : Beginner AI developers
- **Tone** : Accessible, educational, with concrete examples
- **Length** : 2500-3000 words
- **Structure** : Introduction, 4-5 H2 sections with emojis, conclusion
- **SEO keywords** : AI agent, automation, LLM, tutorial
- **Required elements** : comparative tables, code blocks, internal links
- **To avoid** : excessive jargon, unsourced claims

Auto-fill: generate briefs automatically

The auto_fill pattern involves letting the AI generate briefs itself based on a defined content strategy. Specifically, you provide it with a target category and the list of your existing articles. The model then identifies missing topics to fill gaps in your editorial coverage, targets a high-potential SEO keyword, and ensures that the new topic integrates naturally with your already published content. All of this is returned in a structured format ready to be inserted into a database.

This system can run as a scheduled task (cron) to automatically feed an article queue. For example, a job configured to run every Sunday at 10 PM analyzes your database, identifies missing topics, creates the corresponding briefs, and inserts them into the database with a draft status.

The actual writing

This is the step that requires the most powerful model. The writing prompt must enforce impeccable French with a professional but accessible tone. It must request the use of emojis in H2 titles (one per title), the inclusion of at least one comparative table and code blocks if relevant. Each H2 section should be between 300 and 500 words, for a total of 2500 to 4000 words. The model must also respect the exact structure of the brief provided as input, without literal translation and avoiding any excessive jargon or unsourced claims.

🔍 Step 2: Automatic SEO Optimization

Essential metadata

Once the article is written, the AI can automatically generate:

• SEO Title (50-60 characters)
• Meta description (150-160 characters)
• Targeted keywords
• Estimated reading time
• Optimized URL slug

The process is simple: the AI analyzes the article's content (focusing on the first 3000 characters to remain cost-effective) and extracts the SEO metadata in a structured format. It generates an optimized title with the main keyword at the beginning of the sentence, a compelling 150 to 160-character meta description, a list of 5 to 8 relevant keywords, and calculates the estimated reading time. A fast and cost-effective model like Gemini Flash is more than sufficient for this structured task.

Content SEO audit

Beyond metadata, the AI can audit the content itself:

🌍 Step 3: Automatic Translation

Why translate?

An article translated into English potentially multiplies your audience by 10. With modern LLMs, translation quality is excellent, especially for technical content.

Translation strategy

Do not translate word for word. Ask for an adaptation. The rules to provide the model are clear: adapt idiomatic expressions without literal translation, maintain the tone and style of the original, adapt cultural examples if necessary, keep code blocks unchanged, translate H2 titles while keeping emojis, and maintain the exact markdown structure. The goal is for the result to seem natively written in English.

Recommended model for translation

Claude Sonnet offers the best quality/cost ratio for translation. It produces natural results without the cost of Opus. You can set up a scheduled task that runs every night at 3 AM to find the next article without an English translation, translate it according to these guidelines, and automatically update the database. To dive deeper into automating this type of process, you can check out our guide on how to translate your content automatically with AI.

🎨 Step 4: Image Generation

The header image

Every article needs an attractive header image. AI image generators (DALL-E, Midjourney, Stable Diffusion, Flux) can produce professional visuals from a prompt.

Image generation pipeline

The pipeline follows three steps. First, the AI analyzes the title and the beginning of the article's content to generate a suitable image prompt. This prompt must describe an abstract or conceptual visual scene, use a modern and bright style, be written in English (for image APIs), be a maximum of one to two sentences, and avoid including text in the image. Next, the prompt is sent to the image generation API. Finally, the generated image is saved and associated with the article in the database. A fast model like Flash is sufficient to generate the prompt.

Image cost optimization

🌙 The Night Worker pattern

The Night Worker is an automation pattern where heavy tasks (writing, translation, image generation) are executed at night, when:

• APIs are less busy (better availability)
• Costs are sometimes reduced (certain providers)
• You are sleeping and won't be disturbed by notifications
• The content is ready for your review in the morning

To go further on nighttime automation, check out our guide Cron + AI: automating smart tasks 24/7.

Implementation with OpenClaw

The implementation is broken down into five successive scheduled tasks:

• 10 PM — Brief Generator (Flash): analyzes existing articles, identifies missing topics in the content strategy, generates the corresponding briefs, and inserts them into the database with draft status.
• 11 PM — Night Writer (Opus): takes the next draft article, writes the full content according to the brief, generates SEO metadata, and changes the article status to need_review_human.
• 1 AM — Night Translator (Sonnet): translates the next approved article that doesn't have a translation yet into English, applying cultural adaptation rules.
• 2 AM — Night Illustrator (Flash + API image): generates header images for articles that don't have one yet, first creating a prompt suited to the topic and then launching the generation via the API.
• 7:30 AM — Morning Report (Flash): summarizes the night's work (articles written, translated, illustrated), lists what is awaiting human review, and sends a notification on Telegram.

Night Worker diagram

⚖️ Quality vs Quantity: finding the right balance

The trap of mass production

It is tempting to generate 10 articles per night. But mediocre content harms your SEO and your credibility. Here are the risks:

Human review: essential

No automated pipeline should publish without human validation. The need_review_human status is your safety net.

What the human checks:

1. Factual accuracy — AI can hallucinate figures, dates, features
2. Relevance — Does the content truly answer the search intent?
3. Tone and voice — Does the style match the brand?
4. Links and references — Are the links valid and relevant?
5. Added value — Does the article bring something new?

What the human can delegate:

• Spelling corrections → AI
• Markdown formatting → AI
• SEO metadata → AI
• Translation → AI (with proofreading)
• Image generation → AI

Efficient review workflow

The workflow begins when the article is generated with the need_review_human status. A notification is sent on Telegram in the morning. During the human review (15 to 20 minutes per article), three outcomes are possible: the article is approved and moves to the published status, it requires corrections and receives notes with the need_review_ia status so the AI automatically applies the changes, or it is rejected and reverts to the draft status for a new brief.

🆓 Free models for simple tasks

Optimizing costs with free models

Not all pipeline steps require a premium model. Here is how to use free or very affordable models via OpenRouter:

Recommended mixed architecture

By using this approach, only writing (the most important step) uses a premium model. Everything else can run on affordable models without any significant loss of quality.

🔄 Full automation with OpenClaw

Integrated configuration example

To bring everything together in OpenClaw, configuring the cron module simply requires enabling scheduled tasks and limiting concurrent execution to a single job at a time. This prevents database access conflicts when a writing task and a translation task overlap.

Pipeline cron jobs

The complete pipeline relies on five scheduled jobs, which take up and extend the Night Worker logic:

• Sunday 9 PM — Content Strategy (Flash): analyzes the article database, identifies 3 to 5 missing topics for the coming week, and creates briefs in the database using existing categories.
• Every day 11 PM — Night Writer (Opus): takes the next article in draft, writes it entirely according to the brief, applies style rules, generates SEO metadata, and sets the article status to need_review_human.
• Every day 1 AM — SEO Optimizer (Flash): for each article awaiting human review that does not yet have complete SEO, generates or optimizes the SEO title, meta description, keywords, and reading time.
• Every day 2 AM — Translator (Sonnet): translates the next published article without an English translation, favoring cultural adaptation over literal translation.
• Every day 3 AM — Image Generator (Flash): generates missing header images by first creating a prompt tailored to the topic, then launching the generation and associating the image with the article.

📊 Measuring and iterating

KPIs to track

Continuous improvement

The pipeline is never "finished". Iterate on:

1. Prompts: refine based on recurring corrections
2. Models: test newer models that are more performant or cheaper
3. The workflow: adjust schedules and frequency according to your needs
4. Quality criteria: gradually raise the bar
5. Content strategy: adapt topics to SEO trends

🎯 Conclusion

AI-automated content generation is not a magic wand — it's a productivity tool that, when properly configured, can transform your content strategy. The key to success lies in three pillars:

1. A structured pipeline with the right models in the right places
2. Systematic human review to guarantee quality
3. Continuous improvement based on metrics

Start small: one automatically generated article per week, reviewed in the morning with your coffee. Then gradually increase the pace when you are confident in the pipeline's quality.

The future of content is not "AI vs human" — it's AI + human, each doing what they do best.

📋 The essentials

• An AI content pipeline breaks down production into steps (brief, writing, SEO, translation, image, review), each associated with the most suitable model.
• Using a premium model for writing and cost-effective models (Flash, Haiku) for structured tasks makes it possible to divide costs by 3 to 5 without any loss of quality.
• The Night Worker pattern executes heavy tasks at night so you can wake up to content ready for review in the morning.
• Human review remains essential: it ensures factual accuracy, relevance, and tone, and prevents the publication of hallucinations.
• Based on 2025 field feedback, a well-configured pipeline maintains a pace of 3 to 5 articles per week at a cost of less than €1 per article.

🛠️ Recommended tools

To optimize data collection upstream of your briefs, smart AI scraping or the combined use of Hunter, Phantombuster, and AI allow you to automatically enrich your article topics.

❌ Common mistakes

• Using the same model for everything : Using GPT-4 or Claude Opus to generate a slug or extract keywords is a waste. Save premium models for writing.
• Publishing without human review : Even the best model hallucinates. An article with wrong figures or broken links destroys your credibility.
• Translating word for word : A literal translation produces artificial text. Systematically ask the model for cultural adaptation.
• Generating too much volume too fast : Churning out 10 articles a night without iterating on the prompts leads to generic content that hurts your SEO.
• Ignoring SEO metadata : An excellent article without an SEO title or meta description will never rank well, no matter how good it is.

❓ FAQ

How much does an AI pipeline-generated article cost?
With a mixed architecture (Flash for structured tasks, Opus only for writing), the cost generally sits between €0.30 and €0.80 per article in 2025, excluding image generation.

Can you really publish without touching the article?
No. Human review is a mandatory safety net. AI can hallucinate sources, figures, or features. However, with a good pipeline and iterated prompts, the review is reduced to 15-20 minutes per article.

What production pace should be recommended?
Start with 1 to 2 articles per week. Gradually increase to 3 to 5 articles per week only when your human validation rate exceeds 80% and the average review time remains under 20 minutes.

Should you systematically translate into English?
Yes, if your target audience is international. An article translated into English can potentially multiply your audience by 10. With Claude Sonnet, the translation quality is native-like for a moderate cost.

How can you avoid repetitions between generated articles?
Two levers: include the list of existing articles in the brief prompt so the AI can identify uncovered angles, and add a cross-audit step in the human review.