Write a Blog Post and Publish It

You describe the topic, goal, and audience to your agent, it writes the first draft, and after one or two feedback rounds the finished article sits in your CMS as a draft. The final click, publishing, you do yourself.

Writing a blog post rarely fails at the writing and often at the starting: blank page, no hook, and no appetite for the CMS on top of it. Your agent takes that first bit of resistance off your hands. It delivers the opening serve, you make it good with targeted feedback, and in the end a draft sits exactly where it belongs: in your WordPress or Strapi, ready for approval. One thing up front: the agent writes fast, but it doesn't think for you. The quality comes out of the feedback round, and the responsibility for every statement stays with you.

What you need

• Required: a connected CMS with write access. Either WordPress or Strapi, one is enough. To connect it in the portal, see Connect Marketing Accounts to Your Agent (for ChatGPT there's the ChatGPT counterpart). Make sure the source is set up with write access: connected read-only, the agent can't create a draft.
• Optional, WordPress only, for step 4 only: the Honeyfield connector plugin. It lets the agent set the SEO title and meta description. Without it, skip step 4 and set the two fields by hand in the CMS.

This tutorial uses WordPress as the main example. With Strapi it works the same way; at the one point where something differs, there's a note.

1. Give the topic, goal, and audience

An agent that only hears "write something about Google Ads" delivers something arbitrary. Give it three things instead: about what, for what, for whom. The more concrete your brief, the more usable the first draft. Replace [workspace] with the name of your account from the portal.

Write me a blog post draft for [workspace].
Topic: [what it's about, e.g. "5 Google Ads mistakes on a small budget"]
Goal of the article: [what it should achieve, e.g. build trust and lead to a consultation]
Audience: [who reads it, e.g. self-employed people who run their own ads]
Length: around 700 words, with subheadings, second-person address, no jargon without explanation.

Write the draft into the chat first, nothing to the CMS yet.

What you get back:

Draft "5 Google Ads Mistakes That Burn Small Budgets" (in the chat):
Intro plus 5 sections with subheadings, around 720 words, second-person address.
Outline: 1) Keywords too broad 2) No negative list 3) Only one ad per group
4) Conversion tracking missing 5) "Set it and forget it." Want me to adjust anything?

✓ Checkpoint: You have a complete draft in the chat, with subheadings and in the right address. Nothing is in the CMS yet.

Doesn't work? If you only get a rough outline instead of running text, the brief was too thin. Give the topic, goal, and audience more concretely and name the length you want.

2. Sharpen the draft with feedback

This is the step that counts. The agent writes the first serve, but the quality comes from your feedback: facts, tone, examples. Don't accept everything, say concretely what should get better. One or two rounds are usually enough.

Good start. Now let's sharpen it:
- The intro is too general, make it more concrete with a real example.
- Please explain "CPA" in one sentence, readers don't know the term.
- Work in this example: [your number / your fact].
- Tone a bit more matter-of-fact, less ad-speak.
Show me the revised version.

What you get back:

Revised: the intro now starts with the €12.50 click example, "CPA" explained in one
sentence (the cost per conversion), your number example worked into section 4,
tone more matter-of-fact. The rest is unchanged. Does it work like this?

✓ Checkpoint: The new version contains your corrections, not just cosmetic rewording.

Doesn't work? If the agent changes too much at once, give feedback in smaller rounds: the intro first, then the examples, then the tone. That way you keep control over every building block.

3. Drop it into the CMS as a draft

Only when the text is right does it move to the CMS, and as a draft. Nothing goes live in the process. The agent shows you what it wants to create first and only creates it after your yes (in Claude by default, in ChatGPT depending on the plugin's permission setting).

Works. Now create the article as a draft in WordPress, for [workspace].
Don't publish yet: I want to read over it myself first.

What you get back:

Suggestion: create new post "5 Google Ads Mistakes That Burn Small Budgets"
as a draft in WordPress ([workspace]). Create it?
→ Draft created · Status: draft (not public) · ID 128
Open it in your WordPress backend under Posts → Drafts.

✓ Checkpoint: A new post with status "draft" sits in your CMS. It's not publicly visible yet.

Doesn't work? If the agent reports it isn't allowed to write, the CMS source in the workspace is connected read-only. Check in the portal whether WordPress or Strapi is set up with write access.

Using Strapi? The prompt is the same, just "in Strapi" instead of "in WordPress." There too the entry is created as a draft and goes live only through a separate, deliberate step.

4. Review in the CMS and publish it yourself

Now comes the part that stays with the agent, and the part that stays with you. Optionally, before publishing, you have it set the SEO title and meta description, the texts that appear in the Google results list (with Strapi you set both directly in the entry, this prompt step is WordPress-specific). Then you open the draft yourself in the CMS, read over it, and put it live.

Before I publish: set an SEO title (max 60 characters) and a meta
description (max 155 characters) for this draft, matching the
search term [main search term].

What you get back:

SEO set for the draft:
Title: 5 Google Ads Mistakes on a Small Budget (39 characters)
Meta description: Small budgets don't forgive wasted spend. The 5 most common
Google Ads mistakes and how to avoid them. (102 characters)

Then the last step, and you do it by hand: open the draft in your CMS, read it one last time, fix whatever still snags, and click Publish. No article appears without you triggering it.

✓ Checkpoint: The article is public under its URL because you clicked Publish in the CMS, not the agent.

Doesn't work? If the SEO title stays empty, the WordPress site is missing the Honeyfield connector plugin (it writes the Yoast or Rank Math fields). Without the plugin, just set the title and meta description by hand in the CMS.

Variations

• A new angle from an existing article: "Take my article [title or URL] as a base and write a draft for the audience [other group]."
• Plan a small series right away: "Suggest 5 article topics for [workspace] that fit [broader topic], and write the first one as a draft."
• Keep working on an existing draft: "Read the draft [title] from the CMS and cut it to 500 words without losing the five key points."

Honest limit

The agent doesn't fact-check. It phrases fluently, but it supplies no evidence and no sources. For client, number, or legal topics you check every statement yourself. You're liable for what appears under your name.

Draft-first is the whole point. New entries are created as a draft (with Strapi always, with WordPress by default). The article goes live only through your click in the CMS. You can ask the agent to publish directly, but do that only for content you've already checked. The safe way is: draft first, then read over, then approve it yourself.

The quality is in step 2. The first serve is rarely the best text. Wave the draft through unread and you publish mediocrity. The value is in the feedback round, not in the first prompt.

An article is no ranking promise. Whether it shows up on Google depends on topic, competition, and time, not on the click on "Publish." The workflow saves you the writing and the copy-pasting, it promises nothing more.

What's next

The article is live, now you want to know whether it moves anything. That's exactly what the next step is for: Have Your Agent Build a Weekly Marketing Report. "It's published" turns into "it's bringing visitors, or it isn't."