# From 500-Article Backlog to Automated Pipeline

> A 500-article SEO mandate, two AI providers, three-tier PDF extraction, and a Word-doc formatter that almost no one will ever see. This is how a content backlog became a content engine — and turned me from a content grunt into a content engineer.

Canonical URL: https://francisj2nd.cv/cs/500-article-machine/
Category: Engineering / AI
Date: April 22, 2026
Read time: 15 min read

## TL;DR

Faced with 500+ pre-approved article topics for SonaCorp's pre-launch SEO, I built a multi-project Python pipeline using DeepSeek + OpenAI: brand-aware GEO/AEO prompts, two-step cover-image chain, three-tier PDF rewrite mode, rich .docx formatting, and OneDrive sync. Throughput went from ~8/hr manual to 150–200/hr hands-off.

Key metrics:
- Topics Queued: 500+
- Throughput Lift: 25×
- Hours Reclaimed: 100+

---

Let me tell you about the time I had a 500-article backlog hanging over my head like an unpaid rent notice. It was the kind of workload that made me question my career choices — or at least my time management. But instead of panicking (okay, after panicking), I built a solution that turned what should've taken 100+ hours into a mostly hands-off, AI-powered machine.

This wasn't some "growth hack." It was a legitimate software build, solving a real bottleneck in our content marketing pipeline for an upcoming e-commerce platform under SonaCorp. We needed visibility, traffic, backlinks — the full SEO buffet — and the strategy was to publish hundreds of optimized thought-leadership articles targeting every relevant keyword from here to next quarter. The only catch? I didn't write a single one. AI did. But not without some engineering on my part.

## The Challenge

We had a list of over 500 pre-approved article topics. Each one needed to:

- Be substantial (over 1,000 words)
- Use a consistent brand tone per project
- Be formatted cleanly in Word (.docx), ready for upload
- Include GEO + AEO optimization — structured for AI search engines like Google SGE, Perplexity, and Copilot, not just traditional SEO
- Include 3–5 image placeholders with keyword-rich titles and SEO alt text, in a precise machine-readable format
- Include an FAQ section, a meta description under 160 characters, and a keyword list
- Have a real AI-generated cover image embedded directly in each document

Initially, I tried generating the content manually. Copy a topic, paste into an AI tool, wait, format the output into a Word document, save, rename, update the tracker. After maybe 40 articles, I realized I had accidentally reinvented hell.

> After 40 articles, I'd accidentally reinvented hell.

## Architecting the Solution

I stepped back and treated this like what it really was: a pipeline problem with multiple distinct stages. The system I built has two text generation APIs working in tandem:

**Provider 01: DeepSeek**
- Long-form article writing
- PDF rewrite pipeline
- Image-prompt crafting

**Provider 02: OpenAI**
- Cover render (gpt-image-1)
- Vision OCR fallback (gpt-4o-mini)
- Scanned-PDF page extraction

Everything is configured through a single `config.json` file — API keys, model names, timing delays, image settings, and OneDrive sync paths.

## The Multi-Project Architecture

One of the first design decisions was supporting multiple clients and brands from a single codebase. I didn't want to hardcode anything. The solution: a `projects/` folder where each subfolder is a self-contained project.

```
projects/
├── SonaCorp/
│   ├── brand_profile.txt        ← injected into every prompt
│   ├── topics.txt               ← one topic per line
│   ├── completed_topics.txt     ← auto-updated log
│   ├── completed_rewrites.txt   ← tracks rewritten PDFs
│   ├── articles/                ← output .docx files
│   ├── Rewrite/                 ← input PDFs for rewrite
│   └── cover_images/            ← generated PNG covers
└── ClientB/     ...same shape, fully isolated
```

On startup, the script scans `projects/`, lists all available clients, and asks you to pick one. No hardcoded paths. Switch projects in seconds.

The `brand_profile.txt` is the secret sauce — it contains the client's tone, product details, and guidelines, and gets injected wholesale into every article prompt. That's what keeps 500 articles sounding like they came from the same brand, not 500 different ghost writers.

## The Flow

Here's the pipeline end-to-end, for a single article:

1. Load `config.json` and initialize both API clients
2. User selects a project from the `projects/` folder
3. Script loads `brand_profile.txt` and `topics.txt`, checks `completed_topics.txt` to skip already-done topics
4. User toggles cover image generation on/off, and chooses a batch size
5. **Rewrite mode runs first** — scans `Rewrite/` for PDFs, extracts their text, and rewrites them in GEO+AEO format
6. **Topic generation runs** — for each pending topic, construct a brand-aware GEO+AEO prompt, call DeepSeek with exponential backoff, optionally chain into an image render, assemble the .docx, log completion, sync to OneDrive, brief delay, repeat

Every block here was once a manual task. Now it's just another function.

### The Pipeline Steps

**01 — Plan:** Pick project · load brand profile · diff against completed log

**02 — Generate:** DeepSeek writes · OpenAI renders cover · backoff on 429s

**03 — Ship:** Format .docx · log completion · OneDrive sync

## The Prompt Engineering

The most important part of this project wasn't the code — it was the prompt engineering. You can't just throw "write me a blog post" at an LLM and expect gold.

The system targets **GEO (Generative Engine Optimization)** and **AEO (Answer Engine Optimization)** — the new SEO. That means structuring articles so AI search engines like Google's SGE, ChatGPT Browse, Perplexity, and Copilot can extract direct answers from them. Here's what every prompt enforces:

- **Conversational H2/H3 subheadings** phrased as user questions
- **Immediate value in the first paragraph** — no intro fluff, just a direct answer to the main query
- **E-A-T signals**: expert language, specific data references, authoritative framing
- **Image placeholders** in an exact machine-readable format
- **FAQ section** (3–5 questions) compatible with FAQ schema
- **SEO Keywords** (5+ intent-based long-tail queries)
- **Meta description** under 160 characters
- **"Last Updated" timestamp** for freshness signals

## The API Layer

The call to DeepSeek is robust with exponential backoff. Failures don't stop the flow; the topic gets skipped and logged, and the next one picks up immediately.

## The Cover Image Pipeline

This was a two-step AI chain:

1. **DeepSeek** reads the first 2,000 characters of the generated article and produces a cinematic, photorealistic image prompt.
2. **OpenAI `gpt-image-1`** renders that prompt as a 1536×1024 PNG (16:9 landscape, ideal for article headers).

The image is saved to `cover_images/` and embedded directly at the top of the Word document. If the image already exists from a previous partial run, it's reused — no redundant API calls.

## The Rewrite Mode

The rewrite pipeline handles existing PDFs automatically with a three-tier extraction fallback:

1. **pypdf** — fast, for text-based PDFs
2. **pdfplumber** — handles complex layouts
3. **GPT-4o-mini Vision OCR** — page-by-page rendering for scanned/image-based PDFs

The Vision OCR fallback renders each PDF page as a PNG at 2× resolution, sends it to GPT-4o-mini, and stitches the extracted text back together. Output is saved as a formatted .docx and logged to `completed_rewrites.txt`.

## The Word Document Formatter

The .docx output is not just a text dump. The `save_to_word_formatted` function does real rich formatting:

- Cover image centered at the top (6.5" wide)
- Title as `Heading 0` (document title style)
- H1/H2/H3/H4 Markdown headings mapped to proper Word heading levels
- Bullet and numbered lists with correct Word styles
- Inline `**bold**` text parsed and applied as actual bold font runs
- Image placeholders rendered as centered, italic, grey 10pt text
- All body paragraphs justified at 11pt

Filenames are sanitized to strip Windows-forbidden characters and capped at 80 characters.

## OneDrive Sync

Once a file is saved, it's automatically copied to a project-specific OneDrive folder if one is configured in `config.json`. Finished articles land in the shared drive without anyone lifting a finger.

## The Result

**Manual:** ~8/hr  
**Pipeline:** 175/hr

Start the script. Choose a project. Hit Enter. Go make coffee. Come back to a folder full of branded, GEO+AEO-optimized, image-headed Word documents, already synced to OneDrive.

It didn't just save time — it made our pre-launch SEO strategy viable in a way that manual production never could have been.

> It flipped the table from content grunt to content engineer.

## What I'd Add With More Time

- **Multi-threading** for parallel topic processing across CPU cores
- **A lightweight web interface** so non-technical teammates can queue batches without touching a terminal
- **CMS API integration** to push finished articles directly into WordPress or Webflow as drafts
- **Quality scoring** — running a second LLM pass to rate each article before saving, and flagging low-confidence outputs for human review

## Final Thoughts

This project wasn't about AI for AI's sake. It was about solving a human problem — one that was boring, repetitive, and dangerously time-consuming.

The engineering here spans two AI providers, a multi-project file system, three-tier PDF extraction, a two-step image generation chain, rich document formatting, and automatic cloud sync. None of it is over-engineered. Every piece exists because a real workflow demanded it.

Writing code that writes content isn't a shortcut — it's a force multiplier. When you're staring down 500 deliverables and you're the only one in the room, it's easy to freeze. But the moment you ask, "How can I engineer my way out of this?", you flip the table. You go from content grunt to content engineer.

## Skills Demonstrated

Python, OpenAI API (gpt-image-1, gpt-4o-mini), DeepSeek API, python-docx, PDF parsing (pypdf/pdfplumber/pytesseract), OneDrive Graph API, prompt engineering, GEO/AEO content strategy, exponential backoff, multi-project architecture

## Author

Francis Jeremiah Sharon  
https://francisj2nd.cv  
me@francisj2nd.cv  
https://www.linkedin.com/in/francisj2nd/