From Brief to Published WordPress Post: The No-Copy-Paste Workflow for a Marketing Team of 1 to 5
Ask a marketer how long a blog post takes and they will tell you about the writing. Ask them to time it and a different picture appears. The draft took forty minutes with ChatGPT or Claude. Getting it onto the site took an hour and ten.
That hour is the handoffs. Paste the draft into WordPress and the headings are bold paragraphs, the list is flat, the two images are empty blocks. Fix that. Then title, slug, excerpt, featured image, alt text, caption, categories, tags, meta title, meta description, focus keyword. Then the schedule. Then preview, notice the intro was for a different headline, go back to the chat. Then do it again for the next post.
This post is about that hour: why it exists, the eleven fields that make up most of it, where each one should be set once instead of twice, and the mechanics of a publish that carries all of them into WordPress with nothing installed on the site.
The cost is the handoffs, not the writing
AI made the draft nearly free and left the rest of the pipeline untouched. Three handoffs remain, and each is a place where time and errors leak.
The paste. Chat tools render Markdown; WordPress receives plain text or HTML that does not map to blocks. Headings arrive as bold text or lose their levels, lists flatten, images land as paragraph blocks, curly quotes and special characters can garble, and a table becomes a run of words. There are whole tools whose only job is cleaning ChatGPT output for WordPress, which tells you how routine the damage is. Ten minutes per post, minimum.
The fields. A chat draft is a body. A WordPress post is a body plus about eleven other things, every one of which a person now types into the editor’s sidebar. This is the biggest leak and it gets its own section.
The re-review. The draft was reviewed in the chat. It is now a different object, in WordPress, with a featured image, an excerpt and a slug that nobody reviewed. So it gets reviewed again, and the second review finds the headline changed and the intro did not. The cycle-time post traces how these loops turn a one-day post into a five-day one.
The 11-field tax
Here is the list. It is worth reading slowly, because most teams have never written it down and are surprised by its length.
| Field | Where it is typed today | Where it should be set once |
|---|---|---|
| Title | WordPress, after the paste | The brief (working title), finalized at copy approval |
| Slug | WordPress, usually auto-generated badly | Derived from the approved title, checked once |
| Excerpt | WordPress, written on the spot | The draft; it is the first paragraph’s job |
| Featured image | Uploaded to the media library, then attached | Made for the approved copy, attached at publish |
| Alt text | The media library, often skipped | Written with the image, from the brief |
| Caption | The media library, almost always skipped | Same |
| Categories | Ticked in the sidebar | The brief; the category is a planning decision |
| Tags | Typed in the sidebar | The brief or the draft |
| Meta title | The SEO plugin’s box | The brief (the target keyword is already there) |
| Meta description | The SEO plugin’s box | The draft; the excerpt usually does double duty |
| Focus keyword | The SEO plugin’s box | The brief; it is the reason the post exists |
| Schedule and status | The publish panel | The calendar; the post already has a slot |
Twelve rows, eleven fields plus the schedule, and in a copy-paste workflow every one is a second write: information that already existed (in the brief, in the draft, on the calendar) typed again by hand into a sidebar. Skipped fields are the usual outcome, which is why so many marketing blogs have no alt text and a meta description that is the first 155 characters of the body.
The pattern is the same one that kills project management boards: a second write with no mechanism to keep it in sync. The fix is the same too. Set each field once, at the step where the information is born, and carry it forward.
The workflow, in order
Five steps, one system, and the order matters.
1. Brief. Audience, target keyword, working title, the angle, the call to action, the category, the calendar slot. Most of the eleven fields are decided here, before a word of body exists. The brief-to-calendar post covers what a brief needs to hold.
2. Draft. Written inside brand voice from the brief. Title, excerpt, meta description and tags are populated from the brief and the draft, not left for later. The draft is a post object with fields, not a wall of text in a chat.
3. Review gate, copy only. A review pass flags unsourced numbers, claims outside the brand’s facts file, and voice violations, then one person approves the copy. No images yet. The founder bottleneck post explains why copy is gated before images: every headline change after an image exists throws the image away.
4. Images, for approved copy. The featured image is generated or chosen for the final headline, with alt text and caption written at the same time from the brief. The logo, if any, is composited from the real file; the on-brand featured image post covers why plugin-generated featured images all look the same.
5. Publish. One action sends the post to WordPress with body, title, slug, excerpt, featured image, alt text, caption, categories, tags, meta title, meta description, focus keyword, status and schedule, all set from the object that already held them. Nothing is typed in the WordPress sidebar. The post appears on the site as scheduled, or as a draft if the team wants a last look in place.
The important property is not the tool; it is that the eleven fields travel with the post from step one and are written into WordPress exactly once.
The mechanics: how a publish carries the fields
None of this needs a plugin, and it is worth understanding why, because the plugin question is where most teams go wrong.
WordPress has shipped a REST API in core since 2016 and Application Passwords since version 5.6. An Application Password is a credential tied to one WordPress user, named for the application that uses it, usable only for API calls and not for logging into the admin, and revocable on its own without changing the user’s real password. An external tool holding that credential can create a post, set its status and date, attach categories and tags by ID, upload a media item and set it as the featured image with alt text and caption, write the excerpt, and update all of it later.
Three consequences for a marketing team.
- Nothing runs on the site. No PHP, no admin-level plugin, no shared AI keys in the WordPress database. The plugin-versus-external post walks through why that matters after the 2025 and 2026 vulnerability disclosures in the most popular AI plugin.
- Scope is a user role. Create a dedicated WordPress user with the Editor or Author role, issue the Application Password to that user, and the external tool can never touch settings, plugins, themes or other users, because the user it acts as cannot either.
- Revocation is one click. If the credential leaks or the tool is retired, revoke that one password. The site is untouched.
The SEO fields are the one place the mechanics vary: meta title, description and focus keyword live in whichever SEO plugin the site runs, and a publish integration writes to the fields that plugin exposes. Check that the tool you use writes to yours.
WordPress itself defaults to draft-for-a-human. The Abilities API that shipped in WordPress 6.9, and the MCP adapter that followed, are the platform’s own route for AI agents to act on a site, and their default content abilities let an agent draft a post for a person to publish rather than publish directly, unless the site owner enables that and binds the agent to a user with the capability. The platform’s default is the same gate a marketing team wants.
Where the draft comes from does not matter
The workflow above does not care whether the draft was written by a person, by a chat assistant, or by an agent. What it cares about is that the draft becomes a post object with fields at step two and is reviewed at step three. Teams that draft in ChatGPT or Claude can keep doing that and still skip the paste: with an MCP connection the assistant drafts directly into the workspace as a draft with its fields populated, a person approves it, and the publish carries it to WordPress. The assistant never gets a publish button; the draft-only rule is what keeps the approval real.
Marqeable’s blog editor is built as the post object in this workflow: title, slug, excerpt, featured image with alt text and caption, categories, tags, meta title, meta description, focus keyword, author, template, status and publish date live on the piece; the draft is written from the brief inside brand voice; the review pass runs before a person approves the copy; images are made for approved copy inside the brand harness; and one publish creates or updates the WordPress post through the REST API with an Application Password, setting the fields and the schedule. The same piece can be repurposed into the email and the LinkedIn post in the same campaign, which is a different post’s subject. The eleven fields are typed once, on the day the brief is written, and never again.
Frequently asked questions
Why does pasting from ChatGPT into WordPress break the formatting?
The chat renders Markdown; WordPress receives plain text or HTML that does not map to blocks. Headings lose levels, lists flatten, images become empty blocks, special characters garble. Ten minutes of cleanup per post before any field is filled.
What is the 11-field tax?
Title, slug, excerpt, featured image, alt text, caption, categories, tags, meta title, meta description, focus keyword, plus schedule and status: everything a WordPress post needs beyond the body, typed a second time into the sidebar on every post in a paste workflow.
Can I publish to WordPress from an external tool without a plugin?
Yes. The REST API and Application Passwords are in WordPress core. An Application Password is per-application, API-only, tied to a user role, and revocable alone. A tool holding it can create and update posts with all their fields, with nothing installed.
What should the workflow look like end to end?
Brief, draft, copy review gate, images for approved copy, one publish that carries every field and the schedule. The fields are set where the information is born and written into WordPress once.
The bottom line
AI made the draft cheap and left the pipeline expensive. The expense is the paste that breaks formatting, the eleven fields typed a second time, and the re-review of an object nobody reviewed the first time. Write the fields once, in the brief and the draft, gate the copy before the images exist, and publish through the REST API with a scoped, revocable credential so every field and the schedule arrive together with nothing on the site. The forty-minute draft then takes forty minutes.
Marqeable runs your campaigns, answers every visitor, text, and email in seconds, and turns them into booked jobs and meetings - even at 9pm on a Saturday. We’re in private beta with a small early cohort. Get early access
