How to Set a Monthly Guest Post Quota

The right monthly guest post quota is the number of posts your editors can truly review, edit and look after, not a number borrowed from another site. We do not give a fixed figure here, because teams, topics and post lengths differ. What follows is a method for finding your own number, the Google guidance that frames it, and a practical way to handle applicants when you are full.

If you run a blog that accepts contributed articles, a quota does two jobs. It tells readers that every post passed through an editor, and it keeps you well away from the behavior Google's spam policies describe as scaled content abuse.

The Google guidance behind a quota

Google's spam policies (Opens in a new tab) define scaled content abuse as many pages generated for the primary purpose of manipulating search rankings, and focus on large amounts of unoriginal content that offers little value to users. The same document defines link spam as creating links to or from a site primarily to manipulate rankings, and it counts buying or selling links for ranking purposes, including exchanging money for links, in that category. Among its examples are advertorials where payment is received for articles that include links passing ranking credit, and guest posts or press releases distributed on other sites with optimized anchor text. Paid links are acceptable when qualified with nofollow or sponsored.

Nothing in the document says how many posts a month is safe, so any quota is your own policy. The document tells you what to avoid: publishing at volume mainly to influence rankings. A quota based on editor capacity is a way to stay clear of that purpose.

Who, how and why

Google's guidance on helpful, reliable, people-first content (Opens in a new tab) asks who created the content, how it was created and why. It calls "why" perhaps the most important of the three and expects content to be created primarily to help people, warning against content made mainly to attract search visits. A quota gives you a ready answer to "why does this post exist": because an editor judged it useful to readers and had time to see it through.

Working out a number from capacity

Many quota debates start with "how many posts should we run?" The more useful question is "how many hours can the team give to guest posts each month, and what does one post truly cost?" The first answer is a number of hours; the second is a cost per post; the quota falls out of dividing one by the other.

The true cost of one post

A guest post is more than a read-through. List every task, and be honest about the ones that happen after publication.

A simple formula

Practical suggestion: divide the hours your team can give to guest posts in a month by the average hours one post takes across every task above, including upkeep. Rejected pitches take time too, so count their review in the denominator. Leaving upkeep out inflates the quota and lets unreviewed posts pile up as the archive grows. Treat the first result as a draft and recalculate after three months with measured times.

Timing real posts

• Record the time per task for three real posts.
• Look at the spread: if one post took far longer than the others, the average misleads.
• Spread the upkeep time of a post over the period it stays live.
• Track revision rounds per author. A high count may mean your submission guidelines need work.

Topic fit comes first

Capacity sets the ceiling. Topic fit decides who gets in.

Three screening questions

1. Does the pitch belong to a topic area your site covers?
2. Does it serve a reader need you can name?
3. Does your site already cover the same ground well?

If any answer is no, decline, even when you have free capacity. A quota is a ceiling, not a target to fill.

Leaving spare hours alone

If a month brings too few suitable pitches, do not fill the gap with weaker pieces. Spend the time on upkeep: update older posts, repair links, connect orphaned articles. Publishing to hit a number is the habit that scaled content policies warn about.

First-time pitchers and returning authors

Authors do not all cost the same. Practical suggestion: treat the difference as a scheduling fact, not as a reason to relax checks.

• A first-time pitcher needs a fuller read: topic fit, source quality, the history of the author's other work and a clear agreement on corrections.
• A returning author may need fewer revision rounds, so the post may cost less, but the same link and rel review applies.
• An author who has caused problems before gets the same fair read, with the earlier notes in front of the editor.

When you calculate the quota, keep two average costs instead of one if your log shows a clear gap. Otherwise a run of first-time pitches will quietly overrun a quota built on the cheaper average.

Using the form to protect editor time

Incomplete or unsuitable pitches eat capacity faster than anything else. Build your form so that weak pitches filter themselves out before an editor reads a word.

What the form should ask

• What is the topic, and what does the reader gain?
• Has the piece appeared elsewhere, or will it?
• How many outbound links does it contain, and where does each one go?
• Is any link connected to a commercial arrangement?
• Will the author be reachable for corrections after publication?
• Which sources does the piece rely on?

The first two questions screen for originality and fit. The link questions speed up the rel review and the commercial check. The last two show the cost of upkeep before you commit to it. A good form shortens the first read and keeps the quota from filling with work that should never have entered the queue.

Linking form and quota

If the form stays open while the quota is full, pitches pile up. Say on the form that slots may be full and that pitches can go on a waiting list. That sets expectations and saves you from writing the same explanation again and again.

Saying no when you are full

Instead of a flat refusal, consider a waiting list. It respects the pitcher's effort and pre-filters next month's candidates.

How the waiting list works

• Only pitches that pass the topic filter go on the list.
• Tell the pitcher the quota is full, when you will look again, and that the date is not a commitment.
• Review the list at the start of each month and drop pitches whose topic has aged.
• If the draft is ready, say the author is free to place it elsewhere.
• Keep the list in a log: pitch date, topic, status, last reply.

A reply you can send

Hello, we reviewed your pitch and the topic fits our site. Our guest slots for this month are full. We have added your idea to a waiting list that we will review at the start of [month]. This is not a promise to publish. If your draft is ready, you are welcome to place it elsewhere. We will write to you when our schedule is clear.

The draft says three things on purpose: a positive note about the topic, a plain statement that the quota is full, and a limit on expectations. Respecting the pitcher's time protects your reputation as a publisher.

When you go over

Quotas sometimes get exceeded: a strong piece arrives, a campaign period looms, another post is withdrawn at the last minute. Write the rule for overruns before one happens.

Rules for an overrun

1. Log it: which post, why, who approved it.
2. Deduct it from the following month; shift the quota rather than ignore it.
3. Never postpone upkeep because of an overrun; postpone another post instead.

An overrun is not necessarily a mistake, but unlogged overruns wear the quota down. The quarterly review looks at how many there were and why.

Urgent requests

Sometimes an author or brand wants a post live right away. Treat urgency as a reason to move another post, not to shorten the review. Note which post was postponed so that the total stays within the quota and the rushed post is not exempt from the checks that every post gets.

Balancing topics and months

A total is not enough; the posts need a spread. If a month's whole quota goes to one topic, your coverage narrows and readers of other sections get nothing new. See our editorial calendar and topic ownership sheet for ways to distribute the quota across months and sections.

Limits per topic

Practical suggestion: give each main topic a ceiling so that none can take over the quota, and a floor so that no core area goes empty. Set the proportions against your own topic map.

Keeping a buffer

• Revision buffer: a post needing five rounds instead of three occupies the space of two.
• Upkeep buffer: the review calendar for live posts creates monthly work.
• Request buffer: link and update requests arrive unplanned.
• Absence buffer: holidays and sickness change monthly capacity.

An unused buffer is not wasted. It turns into upkeep or update work in the next month.

Sponsored and unsponsored posts together

Some guest posts are paid and some are not. The mix affects how you divide the quota and what you tell readers. Here the only question is where paid posts sit in the quota.

Practical suggestion: one total quota, with a written promise that paid and unpaid posts get the same review. Giving sponsored posts a lighter check, or excluding them from the quota, weakens the promise you make to readers. The rule that paid placements carry sponsored comes straight from Google's guidance on qualifying outbound links. For the seller's side of the topic, read our article on the publisher perspective on selling backlinks on your site, and for pricing see sponsored post rate card for publishers.

Putting the quota in your policy

Publish the rules on your policy page. Say that the number of accepted posts depends on capacity, name the acceptance criteria, state that paid and unpaid posts get the same review and that paid links are marked sponsored, mention the waiting list and say that posts are reviewed after publication.

A one-page quota brief for the team

Everyone who can ask for a guest post slot should be able to find the same page. Keep it short.

• The current monthly quota and the date it was last recalculated.
• The inputs behind it: available hours, average cost per post, buffer.
• The topic filter in three questions.
• The ceiling and floor for each main topic.
• Who approves an overrun and where it is logged.
• The waiting list rules and the reply draft.
• The date of the next quarterly review.

If someone proposes a change to any line, the change goes through the quarterly review unless the person who owns the quota approves it earlier.

Interpreting the data honestly

Once the quota runs for a few months you will have data: published posts, hours spent, rejected pitches, waiting list size. Handle it with care. A single month is a weak basis for a conclusion, and a post count says nothing about quality.

What the data can tell you

• Which task grows when a post is complex: review, fact checks or revisions?
• Do posts from first-time authors cost more than posts from returning ones?
• Which topics produce the heaviest upkeep after publication?
• How long does the average pitch wait on the list before it is published or dropped?

What the data cannot tell you

The numbers cannot tell you whether the posts improved your search performance, because many other factors affect it and Google documentation makes no promise about guest posts and rankings. They also cannot tell you whether readers valued a post. Use reader feedback, comments and your own editorial judgment for that. Keep the quota data for what it measures: workload and process.

Testing the quota against reality

A quota only works if it is tested against reality. Once a quarter, compare the number of hours you planned with the hours actually logged, and adjust the figure instead of stretching the team. If the quota keeps being exceeded without a plan, the number is wrong, not the team.

The quarterly check

A quota is not set once and forgotten. Teams grow, archives grow and upkeep work grows. Ask these questions each quarter.

• Did the number of published posts end up below or above the quota, and why?
• Was the upkeep time enough, or are overdue reviews piling up?
• Do rejected pitches suggest your topic area is widening or narrowing?
• How many waiting list pitches were published, and how many lost their relevance?
• Is the editors' workload balanced?

The answers move the quota up or down. Overdue reviews that keep piling up mean the quota is too high. Free capacity combined with too few suitable pitches means the problem is the pitch channel, not the quota.

When the numbers and the team disagree

Quota data tells you something is off, not always what. Read the signal before you adjust the number.

Quota errors to watch for

Making sure the team knows

If only editors know the quota, requests for fast publication from marketing or sales can break it. Share the decision and its reasons with everyone. When an urgent request arrives, decide who chooses which post to postpone, and make that person the owner of the quota.

How a quota shapes author relations

A quota changes how you speak to authors. It lets you say "not this month" without saying "not good enough", and it gives you a respectful way to keep strong pitchers close. Keep a short note for every waiting list entry, such as why the topic is attractive, so that when a slot opens you can act quickly and the author feels remembered rather than processed.

Example scenario: a two-editor recipe blog

Example scenario: a recipe blog with two editors starts accepting guest posts. The editors decide how many hours a month they can give to guest content, then publish the first three posts with measured task times. The result is longer than their guess: source checks and upkeep took more time than expected.

They redo the calculation and set the quota lower than first planned. In the first two months the quota fills. In the third, two pitches are off topic and are declined, and the spare capacity goes to updating older posts. In the fourth, a strong pitch arrives when the quota is full; it goes on the waiting list and the author receives the reply draft above.

The quota here acts as a safeguard rather than a target: it leaves the editors time to look after what they have already published.

Quota checklist and decision rule

1. Monthly guest-post hours set?
2. Every task measured, including upkeep?
3. Review of rejected pitches counted?
4. Topic filter written down?
5. Paid and unpaid posts reviewed alike?
6. Waiting list and reply draft ready?
7. Quarterly review in the calendar?

Decision rule: capacity gives the ceiling, topic fit decides who enters, and if upkeep time is running out, lower the quota. Never fill spare capacity with weak posts.

Frequently Asked Questions

How many guest posts a month is safe?

Google documentation gives no number. It defines scaled content abuse as many pages generated primarily to manipulate rankings. Calculate from your own capacity.

How do I calculate a quota?

Practical suggestion: divide the editor hours available each month for guest posts by the real time of one post, upkeep included. Recalculate with measured times in the first months.

Should sponsored posts sit outside the quota?

Practical suggestion: no. Count them in the total, review them the same way and mark paid links sponsored.

What should I do with spare capacity?

Do not fill it with weak posts. Use it for upkeep, updates and connecting orphaned posts.

What do I do when the quota is full?

A waiting list is one option if the topic fits. Tell the pitcher the quota is full and that the list is not a commitment.

How often should I review the quota?

The documentation sets no schedule. Practical suggestion: a quarterly review, plus a recalculation when your team or archive size changes.

Conclusion

A monthly guest post quota comes from real editor capacity: the hours available divided by the true time of one post, upkeep included, and reviewed every quarter. Topic fit decides who gets in, paid and unpaid posts go through the same review, and spare capacity is never filled with filler. When you are full, a waiting list and a clear reply keep the relationship with pitchers healthy.

If you are looking for guest post placements planned around editorial capacity and reviewed by an editor, take a look at our guest post service.