The Pipeline, Not the Magic Trick
Most people use AI for blogging the wrong way. They type "write me a blog post about productivity" and paste whatever comes out. The result is generic, forgettable, and ranks nowhere. The fix isn't a better one-shot prompt. It's a pipeline: a sequence of small steps where you stay in control and AI does the heavy lifting in between.
Here's the pipeline you'll run every time:
- Angle — what specifically are you saying, and to whom?
- Outline — the skeleton, approved by you before any prose exists.
- Draft — section by section, not all at once.
- Cut — edit it down to something you'd actually publish.
- SEO pass — title, headings, and meta that match how people search.
Treat these as separate jobs. The biggest quality jump comes from refusing to let AI do steps 1 and 2 for you. Those are your decisions. AI is a faster typist, not a smarter thinker.
Lock the Angle Before You Write Anything
A blog post about "remote work" is dead on arrival. A post about "the three Slack habits that quietly wreck remote teams" has a fighting chance. Specificity is the whole game.
Use AI to pressure-test your angle, not generate it:
I want to write a post for college students about using
AI to study for exams. Give me 8 specific, contrarian
angles — not generic "tips" listicles. For each, name
the exact reader pain it solves in one sentence.
Pick one. Maybe steal half of another. Then write a single sentence you'll be held to: "By the end, the reader can build a spaced-repetition deck from their lecture notes in 20 minutes." That sentence is your filter for everything that follows. Anything that doesn't serve it gets cut.
If you're worried about whether your claims will hold up under scrutiny, AI Literacy: Spotting Misinformation is worth a look — your readers can smell a hollow post, and so can search engines.
Outline First, Always
Never ask AI for a full draft cold. Ask for the skeleton, react to it, then write. The outline is where you catch a bad structure in 30 seconds instead of rewriting 1,200 words later.
Outline a 1,000-word post with this promise:
"[your one sentence]."
Audience: time-pressed students, skeptical of hype.
Give me:
- 3 hook options (each under 25 words)
- 4-5 H2 sections with a one-line purpose each
- one concrete example or mini-case per section
Don't write the body yet.
Read the outline like an editor. Is section three actually different from section two? Does the order build, or does it wander? Reorder, delete, merge. When the skeleton is right, the draft almost writes itself.
Hooks That Earn the Second Sentence
The first two sentences decide whether anyone keeps reading. AI defaults to throat-clearing — "In today's fast-paced world..." Kill those on sight. The hooks that work open with a specific tension, a surprising number, or a flat contrarian claim. From your three generated options, pick the one that would make you stop scrolling, then sharpen it yourself.
Draft Section by Section
Feeding the whole outline in one go produces an even, lifeless slab of text. Draft one section at a time so you can steer voice and depth as you go.
Write the section "[H2 title]" from our outline.
~180 words. Second person, direct, no filler.
Use the example we agreed on. No summary sentence
at the end — just make the point and stop.
Keep your voice rules from earlier chapters loaded in the conversation so the model stays consistent. After each section, do a quick gut check: would you say this out loud to a friend? If not, regenerate with a sharper instruction, or just rewrite the weak line yourself. You're the editor now.
For newsletters, the pipeline is identical but the geometry changes: shorter sections, one clear idea, and a single call to action. Inboxes are less forgiving than search results. If your first line doesn't deliver, the whole thing gets archived unread.
Cut It Down Until It Hurts
AI overwrites. Every draft you get back is 20-30% too long. That padding is exactly what makes content "sound like AI." The edit is where you win.
Cut this draft by 25% without losing any real point.
Remove hedging, repeated ideas, and any sentence that
restates the heading. Flag 3 spots where a claim needs
a real example or a source.
Then go through by hand. Delete adverbs. Break up sentences longer than two lines. If a paragraph could be a single sentence, make it one. Read it aloud — anywhere you stumble, the reader will too. A tight 800-word post beats a bloated 1,500-word one every time.
A Practical SEO Pass
You don't need to be an SEO expert. You need to match the words people actually type and make the post easy to scan. That's most of the win.
- Title: put the main search term near the front, keep it under ~60 characters, and make it a promise, not a description.
- Headings: your H2s should read like a table of contents someone could skim and still get value.
- Meta description: ~155 characters, written for a human deciding whether to click — not stuffed with keywords.
Here's my draft. Suggest:
- 5 title options with the primary keyword "[term]"
- an H2 structure optimized for skimming
- a 155-char meta description that reads like a human
wrote it, not a robot
Don't keyword-stuff. Natural phrasing only.
One rule that overrides all of this: never publish a fact you haven't verified. AI invents statistics and sources with total confidence. Pull the three flagged claims from your edit pass and check each one against a real, current source before it goes live. A single fabricated stat torches your credibility — and Google increasingly notices too.
Run this pipeline three times and it becomes muscle memory. Idea to published post in an afternoon, in your voice, with nothing in it you'd be embarrassed to defend.