Accepting Guest Posts on a Cafe Blog: Rules and Attribution

Thomas Garner

Oct 7

11 min read

A local roaster you buy beans from offers to write a post about single origin sourcing. A regular who happens to be a food writer asks if they can contribute something about the neighborhood. Both offers are genuinely flattering, and both raise a question most cafe owners have never had to think through: should you say yes, and if you do, what happens next.

Short answer: a small cafe can accept contributor posts safely, but only if a few rules are written down before the first post ever goes live, not figured out on the fly, in a hurry, after something is already written and half ready to publish. Those rules cover what topics are allowed, who checks the facts before publishing, how the author gets credited, and how any links inside the post are treated. Skipping this step is what turns a well meaning contribution into a headache later.

This post leads with the fix, a one page policy you can copy and adapt, then explains the reasoning behind each rule, including what Google's own guidance actually says about links inside contributed content and about low quality contributions published at scale.

Why a Written Policy Matters More Than It Sounds

The instinct with a small blog is to treat every contributor request individually, deciding case by case whether a particular offer sounds good. That works fine for the first one or two, and then it quietly stops working the moment a third or fourth person asks and you realize you have been applying different standards each time without meaning to. A written policy, even a short one, removes that inconsistency and gives you something to point to when a request does not fit, without it feeling like a personal rejection.

A policy also protects the cafe's own credibility. A blog is an extension of your business, and a post that reads as an obvious plug for someone else's product, written by that someone else, with no disclosure and no editorial oversight, reflects on your shop's judgment just as much as it reflects on the guest writer's. Deciding the rules in advance, rather than in the moment a specific offer arrives, keeps that judgment consistent.

None of this needs to be elaborate, and none of it needs to slow down a genuine, welcome contribution once the rules are settled. A one page document, something you could hand to a prospective contributor before they start writing, covers the essentials: what topics fit your blog, what the fact checking process looks like, how the byline and short bio will read, and what your rule is on links inside the piece. That single page does most of the protective work a much longer policy would, without requiring legal review or a formal contract for a small local blog.

A Copyable Contributor Policy

Start with topics. State plainly what your blog covers and what it does not, tied to your own shop's actual focus, coffee, the neighborhood, your specific events, rather than leaving it open ended. A roaster writing about sourcing practices relevant to the beans you actually serve fits. A guest post that is really just an advertisement for an unrelated product or service does not, and saying so up front, before a draft is written, avoids an awkward conversation after the fact.

Next, fact checking. State who reviews a contributed piece before it publishes, whether that is you personally or someone else on your team, and what happens if a factual claim in the draft cannot be verified. A simple standard, anything stated as fact gets checked against a source before it goes live, or gets rephrased as an opinion if it cannot be verified, keeps the blog's credibility intact regardless of who wrote a given piece.

Then attribution. Every contributed post should carry a clear byline with the writer's actual name, a short bio that states who they are and why they are qualified to write about the topic, and, where relevant, a note that they are a guest contributor rather than a staff writer. This is not just politeness. It tells a reader exactly who is speaking and why, which matters more for a coffee sourcing post written by an actual roaster than a generic staff post ever would.

Finally, links. State your rule plainly before a single draft comes in: links inside a contributed post should serve the reader, not the contributor's own business interests, and any link to the contributor's own site or product should be limited, clearly relevant, and disclosed rather than buried inside body text disguised as a neutral reference. This rule is the one most likely to cause friction later if it is not set before a post is written, since a contributor who has already written three paragraphs with five links to their own shop will resist removing them far more than they would have resisted a rule stated up front.

What Google Actually Says About Links in Contributed Content

Google's own published guidance on link best practices covers exactly this situation, and it is worth knowing the actual position rather than a secondhand version of it. Google's guidance on qualifying outbound links describes using rel attributes such as nofollow, sponsored, or ugc on links where a site owner has not fully vetted the destination or where the link exists as part of a commercial arrangement, including many contributor and guest posting relationships. The underlying idea is that a link should not be treated by search engines as an unconditional endorsement when the relationship behind it involves any kind of exchange or unvetted third party content.

Google's spam policies separately address content published at scale with little editorial oversight, describing this as a risk when a large volume of contributed or guest content is published primarily to manipulate search rankings rather than to genuinely inform readers. A small cafe accepting the occasional, relevant post from a real local roaster or a real community member sits nowhere near what that guidance is describing, but the underlying principle still applies at any scale: content exists to serve the reader, not to move links around for someone's ranking benefit.

The practical takeaway is not complicated. Treat any link inside a contributor's post the way you would treat any other link on your site, relevant to the reader, honestly disclosed if it points back to the contributor's own business, and never accepted purely as payment for the post itself. A contributor asking to trade a post for an unrelated, unqualified link is a request worth declining outright, regardless of how well written the piece is.

Marking Who Actually Wrote It

Beyond the visible byline, there is a technical layer worth understanding even for a small blog, though it does not need to become a project in itself. Schema.org's Article type includes an author property, which can point to a Person type carrying the writer's name and, optionally, a URL to more information about them. This is the same structured data vocabulary search engines already use to understand standard content, and using it consistently for both staff and contributor posts is a small, low effort step that makes the actual authorship of each piece clearer to search engines as well as to readers.

Whether your blog platform supports contributor specific author profiles depends on the platform itself. Some blogging tools let you set up a distinct writer profile with its own name, photo, and bio that displays automatically wherever that person's posts appear. Others handle this more manually, through a byline written directly into the post body along with a short bio block at the end. Either approach accomplishes the same underlying goal, clear, consistent attribution, and a manual byline is a perfectly sound fallback where a platform does not offer built in contributor profiles.

Whichever method your platform supports, consistency matters more than sophistication here. A contributor whose byline appears differently formatted on every post, sometimes with a bio, sometimes without, sometimes with a link and sometimes not, reads as sloppy regardless of how good the writing itself is. Deciding the exact byline format once, as part of the same policy document that covers topics and links, keeps every future contributed post looking like it belongs on the same blog.

Handling a Request You Have to Decline

Not every offer fits, and how you decline matters for a small local business more than it might for a larger publication, since the person asking is often someone you will see again, a regular, a neighboring business owner, a supplier you buy from. A written policy makes declining easier precisely because it lets you point to a standard rather than making a judgment call about that specific person's writing or their specific request.

A short, kind response works best: thank them for the offer, point to the specific part of your policy the request does not fit, whether that is topic, links, or verification, and, where it makes sense, suggest a narrower version that would fit better. A roaster who pitched a post that reads mostly as a product advertisement might happily rewrite it as a informative piece about sourcing once the distinction is explained plainly, rather than framed as a rejection of them personally.

Keep a simple, ongoing record of who has contributed and what was published, even for a small blog with only a handful of posts a year. This is not about tracking people suspiciously. It is about having an easy reference when a returning contributor asks to write again, so you can check quickly whether their last piece followed the rules and whether a new pitch fits the same standard, rather than starting the whole evaluation over from scratch every single time someone returns with a new idea.

What This Should Never Become

A contributor policy exists to make good posts easier to accept, not to turn your blog into a marketplace. This post is not encouraging a cafe to seek out guest posting opportunities on other sites, and it makes no claim that accepting guest posts improves your own search rankings, because no verified data supports that specific claim and the actual value here is about credibility and content variety, not a documented ranking effect.

It should also never involve paying for placement or accepting a post specifically because the contributor offered payment or a trade in exchange for links, since that shifts the relationship from genuine content sharing into something closer to a paid link arrangement, which is exactly the kind of relationship Google's own link guidance asks publishers to disclose rather than hide. If an offer feels more like a transaction than a genuine contribution, it is worth declining, regardless of how the offer is framed.

It is worth holding this same standard even when the offer comes from someone you like working with, a supplier, a friend, a regular you would never want to disappoint. The written policy is what makes that easier, not harder, because it lets you say the standard applies to everyone rather than making the moment personal. A supplier relationship built on good coffee and reliable delivery does not need a blog post attached to stay strong, and a blog post that only exists because saying no felt awkward rarely reads as genuine to your actual readers anyway, no matter how carefully it gets edited afterward.

Frequently Asked Questions

Should I accept guest posts?

A small cafe can accept guest posts safely, but only with a few written rules in place first: what topics fit your blog, who fact checks the draft, how the byline and bio are formatted, and how links inside the post are treated. Deciding these in advance, rather than case by case, keeps the process consistent and protects your blog's credibility.

What should a cafe contributor policy cover?

Four things at minimum: which topics fit your blog and your shop's actual focus, who checks factual claims before publishing, how the writer's byline and short bio will appear, and a clear rule that links should serve the reader rather than the contributor's own business interests. A one page document covering these four areas is enough for most small blogs.

Does Google allow links inside guest or contributor posts?

Yes, with conditions. Google's guidance on qualifying outbound links describes marking links with rel attributes such as nofollow, sponsored, or ugc when a relationship involves an exchange or unvetted third party content, rather than letting every link read as an unconditional endorsement. Google's spam policies separately warn about contributed content published at scale mainly to manipulate rankings. For a cafe blog, keep any link to the contributor's own business limited, relevant, and disclosed, and never accept a link as payment for the post.

Will accepting guest posts help my cafe rank higher in search?

This post makes no such claim, because no verified data supports it. The real value of a genuine, relevant contribution, such as a post from a roaster you buy from or a regular who writes about food, is credibility and content variety for your readers. Google's link guidance asks publishers to disclose paid or exchanged links with rel attributes like sponsored, and its spam policies flag scaled, low oversight guest content, so treating guest posts as a ranking tactic points the wrong direction.

What if a contributor wants to include several links to their own business?

Set that expectation before the post is drafted, not after. A reasonable rule limits links to the contributor's own site to what is clearly relevant and disclosed, rather than allowing several links buried inside body text. Stating this up front avoids the friction of asking a contributor to remove links from an already written draft.

How should I credit a guest writer?

Every contributed post should carry a clear byline with the writer's real name, a short bio explaining who they are and why they are qualified to write on the topic, and, where relevant, a note identifying them as a guest contributor rather than a staff writer. Consistent formatting across every contributed post matters more than any single stylistic choice.

Does my blog platform support separate contributor profiles?

It depends on the platform. Some blogging tools support a distinct writer profile with its own name, photo, and bio attached automatically to that person's posts. Where that is not available, a manual byline and bio written directly into each post is a perfectly sound alternative, as long as the format stays consistent post to post.

What is schema markup's Article author property, and do I need it?

Schema.org's Article type includes an author property that can point to a Person type carrying the writer's name and optionally a link with more information about them. It is a small, low effort addition that helps clarify authorship to search engines, but it is a nice to have detail, not a requirement for a small cafe blog to function well.

Should I ever pay a contributor for a post, or accept payment for placement?

This post advises against accepting a post specifically because the contributor is offering payment or a link trade, since that shifts the relationship toward a paid link arrangement, the exact kind of relationship Google's guidance says should be disclosed rather than hidden. If an offer feels transactional rather than genuine, it is reasonable to decline it.

How can Hillcane help set up a contributor policy for my cafe blog?

Hillcane can draft a one page contributor policy tailored to your shop, covering four rules: which topics fit, who fact checks a draft before it goes live, how the byline and short bio read, and how links are handled, including the nofollow, sponsored, and ugc attributes Google describes. We can also set up author markup using the schema.org Article author property so attribution stays consistent. Reach out at hillcane.co/contact or call (256) 384-2449 to talk through what that would look like for your blog.

Work with Hillcane

A roaster offers to write a post for your blog. Before you say yes, a small cafe needs a few written rules about topics, links, and credit.

If you want help building a simple contributor policy for your cafe blog, reach Hillcane at hillcane.co/contact or call (256) 384-2449.