A content workflow for a SaaS founder on WordPress has five steps: brief, draft, review, approve and publish. Give the writer the Contributor role, so WordPress itself blocks publishing. Route every post through Pending Review. Publish only after you or an Editor sign off on the claims. Blesso is a done-for-you B2B go-to-market service, and the approval stays with you.
Key takeaways
- Give every writer the Contributor role. WordPress then hides the Publish button and offers Submit for Review instead.
- Review claims, not style. Check every number, customer name, price and link before the post leaves Pending Review.
- One person approves. A founder or an Editor moves the post to Scheduled or Published, and nobody else.
- Treat edits to live pages as a separate, riskier job. Pending Review protects new posts, not pages already published.
- After publishing, check the live URL, the date and the call to action, then log what you changed.
Why a WordPress site needs an approval step
WordPress lets you publish in one click. For a founder, that speed is the risk. A post with a wrong price, an unapproved customer name or a broken call to action goes live as fast as a correct one.
The fix does not need a plugin. WordPress ships with roles and post statuses that already model an approval step. The WordPress roles documentation defines the Contributor role as someone who can write and manage their own posts but cannot publish them. That one rule is your gate.
Step 1: write a brief before any draft exists
The brief is the cheapest review point. A wrong angle caught here costs minutes. Caught after a 1,500-word draft, it costs a rewrite. Keep the brief to one page with these fields:
- The buyer's question, in the words a buyer would type.
- The one thing the post says that other pages on that topic do not.
- The claims that need a source, such as numbers, prices and customer names.
- Claims you do not allow, such as guarantees or competitor attacks.
- The one action the reader takes at the end.
Approve the brief in writing. At this point nothing exists in WordPress, so nothing can ship.
Step 2: set up roles so a writer cannot publish
Create one account for the writer, whether that is a freelancer, an employee or an outside service such as Blesso. Assign it the Contributor role. Then check what each role can do:
| Role | Can write posts | Can publish | Use it for |
|---|---|---|---|
| Contributor | Own posts only | No | The writer |
| Author | Own posts only | Own posts | A writer you trust fully |
| Editor | All posts | All posts | You, or one named reviewer |
| Administrator | All posts | All posts | Site settings, not daily approval |
Source: the WordPress roles and capabilities page. Plugins and custom code can change these defaults, so open Users and confirm the writer's role before the first draft.
Step 3: move the draft to Pending Review
A user with the edit-posts capability but not the publish-posts capability sees a Submit for Review button instead of Publish. Pressing it sets the post to the Pending status, which the WordPress post status documentation describes as awaiting a user who can publish. Under Posts, the Pending tab lists everything waiting for you.
Pending Review marks where the post stands. It does not send a notification or hold a conversation. Agree how the writer tells you a post is ready, and where you write back your changes. Do not treat a post as approved because it has sat in the queue.
Step 4: review the claims, then approve
Founders lose hours rewriting prose they did not need to touch. Spend your review on the parts only you can judge. Work through this list in order:
- Open every link. Each number should point to a primary source, such as the standards body, the vendor's documentation or your own data.
- Check every product claim against what your product does today. Cut any claim you cannot demonstrate.
- Check every customer name and result. A name needs permission, and a result needs a window and a source.
- Check prices, plan names and limits against your pricing page.
- Read the first paragraph alone. It should answer the title's question without the rest of the post.
- Confirm the call to action points to a live page and matches the reader's stage.
WordPress cannot enforce your sign-off if you give the writer a role that includes publishing. The role setting is the control. The checklist is only a habit.
A worked example, made up for illustration
This is an invented scenario, not a customer result. A writer submits a post that says a plan costs "$49 a month" and that "most teams save six hours a week." You check the pricing page: the plan costs $59. You ask for the source of the six hours. There is none. You send two changes back, and the post stays in Pending Review until both are fixed. A Contributor cannot publish around you, so the wrong price does not reach the site.
Step 5: publish or schedule, then check the live page
Only you or an Editor moves the post forward. WordPress offers two paths. Publish sets the status to publish immediately. Choosing a future date changes the button to Schedule and sets the status to future.
If a date matters, confirm the site timezone under Settings, then General. WordPress's scheduling tutorial notes that the scheduler runs when a page loads, so a scheduled post can publish a little after its set time on a quiet site. Open the live URL after the planned time and confirm four things:
- The post is public and shows today's date.
- The title, description and featured image look right.
- The call to action links to the right page.
- No draft text, notes or placeholder links remain.
Handle edits to live pages differently
A new post waits in Pending Review. A saved edit to a published page does not. Anyone with permission to update that page changes the live version when they save. For service pages, pricing and calls to action, agree the new wording outside WordPress first. Have the page owner approve it, then apply it yourself.
WordPress revisions store each saved update. You can compare two versions and restore an earlier one. Use them to recover from a mistake. Do not use them as a substitute for approval before the change goes live.
Where Blesso fits
Blesso runs the Inbound Engine, which covers strategy, offers, funnels and content, and it counts content shipped in the first of its three weekly report tiers: activity Blesso controls. Blesso describes a miss in that tier as an operator failure. Targets are agreed before month one, so the content volume you review each week is a number you set first. The approval steps above stay with you. The founder or a named Editor presses Publish.
See the three services and how reporting works. Pricing starts at $2k a month with a three-month minimum.
FAQ
Do I need a plugin for a WordPress approval workflow?
No. WordPress includes the Contributor role and the Pending Review status. A Contributor cannot publish, so every post waits for an Editor or Administrator. Plugins add notifications and comments, but the built-in roles already stop a writer from publishing.
What is the difference between Draft and Pending Review?
Draft means the writer is still working. Pending Review means the writer believes the post is ready for someone who can publish. The Pending tab under Posts lists these posts, so the reviewer can find them without asking.
Who should have the Editor role on a small SaaS team?
Give it to one named person, usually the founder or the head of marketing. An Editor can publish any post, so each extra Editor is another person who can skip the review. Keep Administrator for site settings and plugins.
Can a scheduled post go live without a final check?
Yes. A scheduled post publishes at its set time with no further prompt. Approve the post before you schedule it, and open the live URL after the planned time to confirm the result.
How do I undo a post I published by mistake?
Switch the post to draft in the editor, which removes it from the public site. Then open Revisions to compare saved versions and restore the correct one. Search engines may have cached the page, so fix the content soon.
Put the gate in place this week
Set the writer's role to Contributor, write the one-page brief, and name who approves. Those three actions give you a gate before the first draft arrives. If you want content shipped on a weekly count you agree first, book a call and bring your ICP and your WordPress setup.