Most bloggers don’t have a writing process. They sit down, stare at a blank screen, write something, fight with it for two hours, give up, come back the next day, force it out, hit publish, and never want to do it again. This isn’t talent; it’s the absence of process. A repeatable process turns blog writing from an emotional ordeal into ordinary work.

What follows is that process, laid out in seven steps you can run on nearly any post, whether you’re publishing on Aurora or any other WordPress setup.

Seven-step blog writing process from topic selection through publishing

Step 1: Pick the topic, narrow the angle

Don’t sit down to “write a blog post.” Sit down to write a specific post on a specific angle. The narrower, the easier.

Two questions before starting:

  • What’s the one question this post answers?
  • Who is this post for?

If you can’t answer both in a sentence, the topic is too broad. Narrow it. If you’re staring at a blank list with no topic at all, that’s a different problem, and how to come up with blog post ideas when you’re stuck is worth reading before you try to force this step.

Time: 10 minutes.

Step 2: Outline before drafting

An outline is the cheapest place to fix structural problems. A bad outline takes 15 minutes to fix. A bad draft takes 2 hours.

The outline should include:

  • The promise of the post in one sentence, similar to what you’d want a strong blog post intro to deliver.
  • The H2 sections in order.
  • For each section, 1 to 2 bullet points of what it covers.
  • The conclusion or final point.

Review the outline. Does each section earn its place? Cut weak ones now, not after writing them. This is also the point to sanity-check scope; if you’re unsure how much a topic needs, how long a blog post should actually be is worth a quick look before you commit to a structure.

A quick tip for the outline stage: write your H2s as questions a reader would actually type into Google, not as vague topic labels. “How long should a blog post be” outlines better than “Post length considerations,” and it makes the eventual keyphrase and headings line up almost automatically.

Time: 20 to 40 minutes.

Step 3: Draft fast and ugly

The most important rule of drafting: do not edit while drafting. The two activities use different mental modes, and switching between them kills momentum. This isn’t just a personal preference either; writing research going back to the Flower and Hayes cognitive process model has long treated planning, translating ideas into words, and revising as genuinely separate cognitive activities, which is part of why forcing them together makes drafting feel so much harder than it needs to be.

Write the whole draft. Don’t go back. Don’t reword. Don’t polish. If you get stuck on a sentence, write a placeholder (“something something about hosting”) and keep moving.

Goal: a complete bad draft. A bad draft is a required step here, not a failure, because a bad draft that actually exists is far easier to fix than a perfect paragraph that never gets written.

The reason: editing a bad complete draft is far easier than editing a perfectionist half-draft. The hard part is having something to work with.

Time: 60 to 120 minutes for a 1500-word post.

Step 4: Walk away

This step does more for quality than any other. After drafting, close the doc. Don’t open it for at least an hour. Ideally overnight.

You come back as a slightly different reader. Things you couldn’t see during drafting, like rambling, redundancy, or mismatched tone, are obvious now. The draft you couldn’t have edited five minutes after writing it edits itself when you read it 12 hours later.

Bloggers who skip this step produce worse writing for the same effort.

A writer's desk showing a draft set aside before editing the next day

Step 5: Structural edit

First editing pass. Read the whole draft. Ignore individual sentences. Focus on:

  • Does each section deliver what its heading promised?
  • Is the order right? Are sections in the order a reader would want them?
  • Are any sections missing?
  • Are any sections doing the same job? Merge them.
  • Does the intro promise the right things?
  • Does the conclusion follow from the body? A weak ending is its own separate problem, and how to write a blog post conclusion worth reading covers it in more depth if this pass keeps stalling on the last section.

Cut. Move. Restructure. Don’t worry about prose yet, since the prose only matters once the structure is right.

Time: 30 minutes.

Step 6: Sentence edit

Second editing pass. Now sentence-level. Read each section. Ask:

  • Is this sentence necessary? Cut if not.
  • Is this the shortest version of this sentence?
  • Are there hedges or filler? (“It’s important to note,” “essentially,” “really.”) Cut.
  • Are sentences varied in length? Mix it up.
  • Are adjectives doing work or just padding?
  • Read it out loud. Where you stumble, fix.

Hemingway-style minimalism, of the kind tools like Hemingway Editor nudge you toward, isn’t the goal here. The goal is intentional sentences. Every sentence should be there on purpose. For a deeper pass on this, editing your own writing: the passes that actually matter goes further into what each editing round should actually be looking for.

Time: 30 to 45 minutes.

Step 7: Publish prep

The non-writing tasks that need to happen before you hit publish:

This checklist takes 15 minutes. Skipping it means publishing posts that don’t fully work, and if you’re running Aurora, part of this list gets shorter automatically since the theme’s clean, semantic HTML output already gives search engines the structural signals a lot of other themes need a plugin to add.

Total time

For a 1500-word post:

  • Topic narrowing: 10 min
  • Outline: 30 min
  • Drafting: 90 min
  • Walk away: overnight
  • Structural edit: 30 min
  • Sentence edit: 40 min
  • Publish prep: 15 min

Total active time: about 3.5 hours. Spread over two days with the overnight gap.

This is slower than “sit down and force out a post.” It produces better writing for less emotional cost.

What this process avoids

Specific traps the process prevents:

Editing while drafting

This is the most common reason a post that should take three hours ends up taking eight, because constantly switching between generating and evaluating forces your brain to restart each time.

Polishing the first paragraph forever

You can’t see if the intro works until you’ve written the body. Don’t polish before drafting is done.

Publishing without an outline

The post ends up structurally wrong. The reader notices even if they can’t name why.

Skipping the walk-away

You edit while still attached to the writing. Quality suffers.

Forgetting the publish checklist

Featured image missing, no meta description, no internal links. The post is technically published but underperforming from day one.

For longer posts

For 3000+ word posts, the process scales up but stays the same:

  • Outline takes longer, 60+ minutes.
  • Drafting can be broken into 2 to 3 sessions.
  • Walk away should be at least 24 hours, ideally a few days.
  • Edit in two separate passes with breaks between.

Bigger posts benefit even more from process. They’re where ad-hoc writing breaks down hardest.

The “I don’t have time” objection

Bloggers who think they don’t have 3.5 hours often spend 6+ hours per post chaotically. Process saves time in aggregate. It also makes the time less emotionally draining, which is why some bloggers keep going for years and others quit in month 3. If speed genuinely is the bottleneck rather than structure, how to write blog posts faster without cutting quality tackles that problem directly instead.

What it comes down to

Topic, outline, fast ugly draft, walk away, structural edit, sentence edit, publish prep. Seven steps. Separate generating from editing. Set time per step. Never edit while drafting. The walk-away is the highest-leverage step. Most stuck posts get stuck because the writer is trying to do everything at once.