SEO Use Cases · How to
SEO for agencies: how to run client blog programs at scale
Part of the guide SEO for small business: a practical plan for 2026
An agency can run blog programs for many clients by making every client follow the same pipeline: a one page brief, a monthly topic plan, drafts that go through a fixed approval step with a deadline, scheduled publishing straight into the client's CMS, and one monthly report. The parts that break at scale are approvals that stall, facts nobody checked, and writing capacity. Fix those three and 20 client blogs run like 5.
The pipeline every client blog goes through
Run every client through the same stages, with the same owners and the same deadlines. What differs per client is the brief, not the process.
| Stage | Owner | Output | Deadline |
|---|---|---|---|
| Onboarding | Account lead | One page brief, CMS access, approval contact | Week 1 |
| Monthly plan | Strategist | Topic list mapped to the client's services | 5 working days before the month |
| Drafting | Writer or tool, then editor | Drafts with sources and internal links | Rolling, two weeks ahead of publish |
| Approval | Client contact | Approve or request changes | 5 working days per draft |
| Publishing | Account lead or scheduler | Post live in the client's CMS | Scheduled date |
| Refresh | Strategist | Updates to posts that lost clicks or sit on page two | Monthly, from month 3 |
| Report | Account lead | One page summary | First week of the month |
The wider question of how to scope and price SEO retainers is covered in SEO for agencies: how to package and deliver it. This page is only about the blog program inside that retainer. If your clients are mostly small local businesses, the fundamentals in our SEO plan for small businesses are what the blog has to support.
Onboarding: get the brief right once
Every quality problem later traces back to a thin brief. Collect these on day one and store them where every writer and every tool can read them:
- Services and prices the client actually sells, and which ones they want more of.
- Areas served and customer types.
- Banned claims: guarantees, medical or legal statements, competitor mentions, anything their regulator restricts.
- Voice samples: three to five pieces the client wrote and likes.
- Pages that convert: service pages, booking forms, pricing. Every post should link to one.
- Approval contact: one named person with authority to approve, plus a backup.
- CMS access: a dedicated editor account or integration in the client's name, never the owner's login.
Monthly planning: tie topics to what the client sells
Plan each client's month as a small cluster: one hub topic tied to a service, and three to six supporting posts that answer the questions customers ask before buying it. A plumbing client's month might be "boiler replacement" as the hub, with posts on costs, signs a boiler needs replacing, combi versus system boilers, and what happens on installation day.
Agree the number of posts in the contract and keep it steady. For a young client domain, a steady pace of one or two posts a week is easier for search engines to absorb and easier for the client to approve than bursts of ten.
Approval flows that do not stall
Approvals are where agency content programs lose the most time. A draft waiting three weeks for a reply pushes the whole calendar back. Three rules fix most of it:
- Write the deadline into the contract. For example: "Drafts not approved or commented on within 5 working days publish as scheduled." Clients accept this when it is agreed up front.
- One channel, one link. The client should approve from a single link, not by digging through email threads and shared documents.
- Change requests go back to draft automatically, so nothing half edited goes live.
Choose a publishing mode per client, and change it as trust builds:
| Mode | How it works | Use it when |
|---|---|---|
| Draft | Posts land in the CMS as drafts; someone publishes by hand | The client wants to press publish themselves |
| Approval | Client approves each post before it publishes | The first two or three months, and regulated industries |
| Auto | Posts publish on schedule without approval | Long-standing clients, low risk topics, after months of clean approvals |
Regulated clients (lawyers, dentists, accountants, financial services) should stay on approval permanently. The client is the expert who has to stand behind the claims.
Quality control at volume
At 10 or more clients, you cannot rely on one editor's memory. Put checks into the process:
- Facts: every statistic, price and date needs a source the editor can open. Remove anything that cannot be traced.
- Claims: check each draft against the client's banned claims list.
- Links: one link to the relevant service page, links to related posts, no links to the client's competitors.
- Duplication: two clients in the same trade must not get near-identical posts with the names swapped.
That last point is a policy risk, not just a quality one. Google's scaled content abuse policy covers "many pages" generated "for the primary purpose of manipulating search rankings and not helping users," and it applies "no matter how it's created." Content that adds specific, local, client-only detail is the safeguard.
Reporting the blog program
A content report should answer three questions in the first screen: what shipped, what changed, and what happens next month. For a blog program, that means posts published against plan, new posts indexed, impressions and clicks for posts from the last three months, and leads from blog pages if the client tracks them. Add whether the client is named in AI answers for their main buyer questions, if you track it.
Report on clicks from older posts too, since posts usually take months to reach their level. The full monthly template is in SEO client reporting for agencies, and the branding side is in white label SEO reporting.
What Postbing does in this pipeline, and what it does not
Postbing covers the planning, drafting, approval, publishing, refresh and content report stages above. It is built for this use, but it is one part of an agency's stack, not the whole service.
What the Agency plans include, as of November 2026:
| Agency | Agency Pro | |
|---|---|---|
| Price | $199 a month ($1,990 a year) | $399 a month ($3,990 a year) |
| Articles | 120 a month, pooled across clients | 300 a month, pooled |
| Client sites | 25 | 100 |
| Team seats | 10 | 25 |
| AI visibility questions per site per week | 30 | 40 |
Credits reset on the 1st of each month and do not roll over. As a sizing example, 12 clients at 8 posts a month is 96 articles, which fits inside Agency's 120.
Features that map to the pipeline: per client brand voice trained from the client's own writing; a publishing mode per site (draft, approval or auto); client approval links where the client approves or requests changes without logging in, a change request sends the article back to draft and the agency is emailed; white-label branding with the agency's name and logo; a monthly client report link showing articles, topics, pipeline, AI visibility change and Search Console metrics when connected; and refreshes that rewrite underperforming posts around their real Search Console queries.
What it does not do, so plan for these separately:
- No link building, of any kind. Postbing never sells, places or exchanges backlinks.
- No technical audits, Business Profile management or ad work.
- No native connector for Wix, Squarespace or HubSpot. Those clients can only be reached through the signed webhook, which needs something on the receiving side (Zapier, Make, n8n or custom code). WordPress, Shopify, Webflow, Ghost and Notion are native.
- The public API manages accounts and projects only; there are no article endpoints for building your own client portal.
- No ranking or citation guarantees, for you or your clients.
More detail is on Postbing for agencies.
FAQ
How many client blogs can one person manage?
There is no reliable industry figure, and it depends on posts per client and how much editing each needs. Track hours per client for two months with a fixed pipeline, then set your own limit from that data.
How do agencies get clients to approve blog posts on time?
Put an approval deadline in the contract, such as 5 working days after which drafts publish as scheduled, and give the client one link to approve or request changes. Stalled approvals are a process problem, not a client problem.
Should agencies use AI to write client blog posts?
It can work if a person checks facts and claims and each post contains detail specific to that client. Google's scaled content abuse policy targets pages made to manipulate rankings without adding value, however they are created.
Can clients approve Postbing articles without an account?
Yes. On the Agency and Agency Pro plans, clients get an approval link where they approve or request changes without logging in. A change request sends the article back to draft and emails the agency.
Sources
- Google Search Central: Spam policies: scaled content abuse definition, accessed 16 November 2026
- Postbing pricing page and product documentation: Agency and Agency Pro prices, limits, approval links, white-label, client reports, publishing modes and connectors as of November 2026, accessed 16 November 2026
Related reading
Last updated: November 16, 2026. Spotted an error? Email support@postbing.com and we will fix it. Editorial policy.
Try Postbing free
Postbing reads your site, plans a month of topics from what your customers search for, writes in your voice and publishes to WordPress, Shopify, Webflow or Ghost. Your first article is free.
Try Postbing freeNo card needed. No link exchanges, ever.