How to brief a writer for a guest post that actually gets accepted

A guest post is only as good as the brief behind it. A writer given a vague instruction, a keyword, and a deadline will produce a vague article. A writer given a clear audience, a specific angle, real evidence, and honest guidance on the link will produce an article an editor wants to publish. The difference is rarely talent. It is almost always the brief.

Briefing a writer is not about controlling every sentence. It is about giving the writer what they need to make good decisions: who the article is for, what it should argue, what evidence supports it, and what the host site expects. This article explains how to write a brief that gets guest posts accepted, and how to review the result without rewriting it yourself.

Start with the audience and the host site

Every brief should begin with the reader. Who will read this article, what do they already know, and what problem are they trying to solve? A guest post for business owners needs a different tone and depth than one for marketing managers, and a writer who does not know the audience will guess, usually wrongly.

Include details about the host site: its name, its audience, links to two or three recent articles in a similar style, and any guidelines the editor has given. A writer who has read the site will match its tone naturally. A writer who has not will produce an article that feels imported, and editors reject imported articles quickly.

Define the angle and the argument

A topic is not an angle. “Guest posting” is a topic. “Why small businesses should start with one placement a month” is an angle, because it takes a position and promises a specific answer. The brief should state the angle in one sentence, and say what the article should conclude. A writer who knows the argument can build towards it. A writer who does not will wander.

Give the writer room within that angle. The brief should define the destination, not every turn of the road. Writers do their best work when they understand the point and have freedom in how they reach it. A brief that dictates every paragraph produces stiff, lifeless writing. A brief that defines the argument and trusts the writer produces work worth publishing.

Provide evidence, examples, and sources

Generic articles are usually generic because the writer had nothing specific to work with. The brief should supply the raw material: real examples from the business, numbers the business can stand behind, stories from client work, and links to sources the writer should use or avoid. The business owner’s knowledge is the asset; the brief is how it reaches the writer.

Be honest about what is not available. If there are no statistics, say so, and suggest the writer use examples instead. If a claim cannot be supported, remove it from the brief. An article built on invented evidence will be rejected by a good editor, and published by a poor one, and neither outcome helps the business.

Set the link, length, and style requirements

The brief must be explicit about the link: the destination page, the preferred anchor text or phrasing, and where in the article it should appear. It should also state the required length, the heading structure if one is needed, and the tone. These details prevent the most common revision: an article that is well written but unusable because the link is wrong or the length is far off.

Explain why the link exists, in plain terms, so the writer can place it naturally. A writer who understands that the link points to a service page explaining the process will weave it into the argument. A writer told only to “include this link” will bolt it on. The article on the guest posting workflow from pitch to published link, explained step by step shows where the link fits in the wider process, and why its placement matters as much as its destination.

Review with useful feedback, not rewrites

When the draft arrives, review it against the brief, not against an ideal article in your head. Check the angle, the accuracy, the link, and the tone. Give feedback that is specific and actionable: point to the paragraph that needs work, say what is wrong, and say what would fix it. Vague feedback, such as “make it better,” wastes a revision round and frustrates the writer.

Allow one revision round as standard, and a second only for genuine problems. Endless revision is a sign that the brief was unclear, not that the writer is poor. If the same problems recur across writers, the brief needs improving. If one writer consistently misses the mark, the writer needs replacing. Either way, the brief is the lever that fixes it.

Frequently asked questions

How long should a writer brief be

One to two pages is enough for most guest posts. Shorter than a page, and the writer will have to guess. Longer than two pages, and the writer will skim it. A good brief is dense with useful detail and free of repetition: audience, angle, evidence, link, length, tone, and deadline.

Should I let the writer choose the topic

An experienced writer in the business’s niche can suggest good topics, and their suggestions are worth hearing. The final choice should rest with the business, because the topic must fit the host site, the link destination, and the business’s goals. Treat the writer as an adviser on topics, not the decision maker.

How much should I pay for a guest post article

Enough to attract a writer who can do the research and write to a publishable standard. Very cheap writing is cheap because it is rushed and generic, and it will be rejected by good editors or ignored by readers. A fair rate for a well-researched article is an investment in acceptance, not an expense to minimise.

What if the writer misses the deadline

Build buffer into the schedule, so a late draft does not stall the programme. A single missed deadline is usually a scheduling problem; repeated misses are a reliability problem. Agree the deadline and the consequences in advance, and keep a small queue of briefs ready so another article can move forward while one is delayed.

Should the writer know the article is a guest post

Yes, always. The writer needs to know the host site, its audience, and its guidelines, and that the article will be reviewed by an editor. Hiding that information produces articles written for the wrong reader. Transparency about the purpose of the article is part of a good brief, not a secret to keep from the writer.

A good brief is a mark of respect: for the writer, for the editor, and for the reader. It says that the business takes the article seriously, and it gives everyone involved the best chance of producing work worth publishing. Write the brief carefully, and the acceptance rate will take care of itself.