I automated the boring half of my blogging workflow
Description and use
Automating WordPress posting: AI generation, optional translation, humanizer rewrite, one‑click publish, saving time and cost.
Problem
Writing posts was fine, but moving them into WordPress was a 15‑minute repetitive process that had to be repeated for each language.
Outcome
The tool cuts the manual posting workflow to a single preview/edit step, saves a few cents per article, and eliminates vendor lock‑in by using the user’s own API key.
Workflow
- Write topic
- AI generates article (30s–2min, SSE)
- Humanizer rewrites style
- Optional bidirectional translation (Chinese↔English)
- Publish to WordPress (draft or direct)
Evidence
I run a small bilingual tech blog on WordPress. For the longest time, every single post cost me the same annoying 15 minutes: write in a doc, fix the formatting, log into wp-admin, paste, clean up the mess, preview, publish.
Five steps, but only one of them is me.
Generation takes 30s–2min depending on the model. It streams (SSE), so I'm not staring at a spinner wondering if it hung.
Translation is bidirectional — Chinese ↔ English. Code blocks and technical terms survive the trip, which was the dealbreaker in every other tool I tested.
Publish is one click after a one-time WordPress connection. Draft if I want to review, direct publish if I don't.
A "Humanizer" pass strips the tells — you know the ones: "firstly, secondly, finally", "it's worth noting that", the five-paragraph essay structure that no human chooses on purpose.
No vendor lock-in. It supports 20+ providers — Qwen, DeepSeek, Zhipu GLM, Doubao, OpenAI, Anthropic, Gemini, Kimi, Mistral, Groq, and a bunch of others.
The API calls go directly from my machine. The key sits in a local config file and never passes through someone's server.
A full article typically costs me somewhere between a few cents and a couple of毛 through my own API account. Compare that with a $20–40/mo writing subscription that generates the same kind of text.
First run takes 10–15 minutes and involves: 1) Creating a WordPress Application Password 2) Getting an API key 3) Checking that your security plugin hasn't disabled the REST API 4) Optionally a Tavily key if you want live web search while writing.
- Record date: 2026-10-15T07:56:00.773Z