← The Marketing Station ~ dish 05 of 10 · the marketing station

SEO-Grounded Blog Drafting

Search volume is dropping. Answer engines are rising. A blog post now has to be SEO-sharp and useful to the reader and grounded in your actual point of view. All three. The station's job is the structure. Your job is the specificity.

The job

You want to rank on “how to choose a contractor” or “when to replace your HVAC system” or whatever your market is actually searching for. The keyword is clear. The need is clear. The internet is full of consensus answers. What’s missing is your answer. Not how to structure an answer. Your answer. Your data. Your specific point of view.

The station can handle the structure. Research the keyword. Build the outline. Draft the sections. But by section three, you need to step in. You’re the one who knows which thing the consensus gets wrong. You’re the one with client data. You’re the one who can say “I’ve seen this fail in these specific ways.” That’s where the ranking power lives.

The leverage is Output Over Process. Describe the destination, not the steps. “A 2400-word blog on the financial math of insourcing versus outsourcing your dispatch operation, grounded in three years of client data showing where most operators leave money on the table.” Not “outline four sections, draft an introduction, add tables, link internally, optimize for keywords.” The destination matters. The route doesn’t.

The recipe

All seven ingredients still apply. The leverage on this dish is Output Over Process (Ingredient #5). You describe the final plate. The station handles the plating.

Context comes second. The keyword research. Search intent. What the competition is ranking for. What angle is open. Examples come third. One blog post of yours that ranked. Not because it was perfect. Because it said something specific the competition didn’t. Training comes fourth. House style on blog writing. How technical. How narrative. How specific. Guardrails come fifth. Things you never do on a blog. You never claim something without a source. You never solve a problem you haven’t actually seen. You never pretend a tool solves a problem it doesn’t.

How to build it

  1. Pick the keyword. The one you want to rank on. Run keyword research. Search volume. Intent. Competition level. Document the two competitors who are currently ranking.
  2. Write the destination. Not outline format. Plain English. “A 2200-word blog on the financial math of replacing versus repairing a commercial HVAC system, grounded in install data showing where most owners leave money on the table. Customer story embedded. Calculator linked.”
  3. Note your angle. What are the top three ranking posts missing? What do you know that the competition doesn’t. Write it down.
  4. Gather context. The keyword research. The competitor analysis. Your angle statement.
  5. Pull one blog post you wrote that you’re proud of. Recent. On a different topic. Show the station your structure, your depth, your specificity.
  6. Define guardrails. “Never claim something without data.” “Never solve a problem we haven’t actually seen.” “Always include customer context.” 4-5 rules.
  7. Feed the destination, context, example, and guardrails to the station. Ask for a draft.
  8. Review the draft for structure. Outline. Subheading hierarchy. Where the station put your angle. If structure is 80% there, you now do your work. Step in. Add specificity. Add data. Add customer examples. Add the thing only you can add.
  9. Once you’ve added your specificity layer, the station can tighten prose if needed. But the blog is mostly done because your specificity is the ranking power.

What breaks it

  • Destination is vague. “A blog on HVAC replacement” gives the station no guardrails. It drafts generic because you didn’t describe specific. Better destination: “1800-word blog comparing cost per BTU of three replacement options for commercial systems over 15 years, with a table showing payback scenarios.”
  • Output Over Process collapses into Process description. You say “outline the post, research the keyword, draft three paragraphs, add a table, insert a customer story.” The station has no destination. It has steps. It will optimize for steps, not output. The blog stays generic.
  • Specificity is optional. You review the draft. It’s 2200 words, well-structured, keyword-optimized. But it says nothing you couldn’t read on fifteen other blogs. You didn’t step in to add data or customer context. The blog doesn’t rank because it has nothing to rank on.
  • Measurement death. The blog publishes. Nobody tracks clicks or rankings or engagement. By month three, the station is still drafting blogs with no feedback on what works.

When it’s working

By month two, you have the rhythm. The station drafts the structure. You spend 90 minutes adding specificity, data, customer context. The Chef + station work is tight. By month four, you’re not rewriting. You’re adding. By month six, you have four blogs ranking on keywords that matter because they say something the competition doesn’t. The station built the house. You built the reason someone lives in it.

The signal that the recipe is sharp: you rank on a keyword where the top three results are generic consensus. Your blog ranks because you said something specific.

Monday Move

Pick one keyword you want to rank on. Run the research. Write the destination in plain English. Not outline format. Destination. Then pull a past blog of yours that ranked. Show that to the station as an example. Ask it to draft the new blog using the destination, the keyword context, and the example. Review the draft for structure. If the outline is right, add your specificity layer. Data. Customer story. The angle nobody else has. That’s the blog. By week two, you have a drafted blog ready for publication.

Dish 5 of 10 on the Marketing Station. Build-note leverage: Output Over Process (Ingredient #5).