Why communities reward help, not promotion
The content distribution channels guide places communities among the earned channels and puts the principle in one line: distribution here is participation, not promotion. A community exists for its members. They come to ask a question, compare experiences and get an answer from someone who has dealt with the same problem. Every post that helps them makes the community more useful; every post that exists to send them somewhere else makes it less so. Moderators, and the members themselves, defend the first against the second, which is why link-dropping gets accounts removed and why the same guide lists treating communities as billboards among its common mistakes.
That makes community work different from the other channels in the content plan. Search and email reward a piece for existing and being good. Social accounts reward posting in the platform's format. Communities reward a person: the member whose answers people have learned to trust. The content is useful there only through that person, as the evidence behind an answer or the fuller version of it. Hosting a community of your own is a different job from taking part in other people's, and the guide to running a brand community group covers it.
Search adds a second reason to keep the work honest. The spam policies guide records that Google's link spam policy includes forum comments with optimised links, and that its user-generated spam policy covers spammy posts in forum threads. The outbound links guide explains that Google's documentation recommends sites mark links in user-generated content with the UGCContent about a brand made by customers or creators rather than by the brand itself. value. A link in a community post is a link for the reader who asked, not a ranking signal to collect, and it is worth posting only when that reader is better off for it.
| What the community wants | What promotion offers instead | What happens |
|---|---|---|
| An answer to the question asked | A link to a page that might answer it | The post is ignored, downvoted or removed |
| Experience from someone who has done it | A brand voice | Members discount it |
| A conversation | A broadcast | No replies, and no second chance |
| Members it can trust | An account that only posts links | The account is banned |
| Relevant further reading, now and then | A link in every post | The links are treated as spam |
Finding the communities where the question is asked
Start from the questions, not the communities. The audience research guide records that communities fill the gap search data leaves: forums, review sites, professional groups and social threads hold unprompted questions in the vocabulary of the people asking them. The research that built your question bank already shows where those questions are asked. Go back to those places with a different purpose.
For each candidate community, note what it is for, who takes part, how active it is, what questions come up again and again, and whether your organisation's subject belongs there at all. Prefer communities where your readers already spend time over large general ones where they are a small fraction of the members. Local businesses will find many of their communities are neighbourhood and town groups, which the local content and community marketing guide covers, including their norms.
Choose few and stay. A presence in a handful of communities, kept up over months, builds the trust that makes an occasional link welcome; a single post in many communities builds nothing. The choice follows the same logic as the rest of the content strategy: the audience and its questions decide where the effort goes, and the channel is judged on whether it reaches them.
Reading the rules before the first post
Every community has rules, and most have rules about self-promotion: whether links to your own content are allowed at all, where they may appear, how much a member must take part before posting them, whether members must say who they work for, and whether commercial accounts are allowed. Some communities ban links to members' own sites outright, some allow them only in designated threads, and some leave it to the moderators. The rules differ from one community to the next and change over time, so read them in each one, every time you return after a break.
Read beyond the written rules. Look at how moderators have handled self-promotion in practice, which posts with links were welcomed and which were removed, and how members react to someone who works for a company. The local community guide makes the same point for local groups: they have norms, usually written, and the business that answers questions helpfully and mentions itself only when asked earns more from a group than the one that posts an offer every week and is removed. If the rules are unclear, ask a moderator before posting, not after.
Then take part before you link. Answer questions you can answer without any link, add to discussions, thank people who helped you. The community learns who you are from those posts, and you learn what it values. This is general practice rather than a rule from any source this site cites, and it is the practice most communities' rules point towards.
Answering first, linking second
The rule for every post is the same: answer the question in full in the thread itself, so that the person who asked is helped even if they never click anything. Then, where the rules allow and only where it adds something, link your piece as further reading.
A good answer is written for the person who asked, in the community's tone, at the length the question deserves. It gives the answer first, the steps or the reasoning next and the caveats that matter for their situation. If your piece holds a diagram, a worked example or a longer method the thread cannot carry, that is the moment for a link, introduced by what the reader will find there: "I wrote a step-by-step version with photographs here", not a bare address.
A link that is the answer, with a line such as "this explains it", is a link drop, however good the page. So is the same link pasted into several threads, or a link to a page that only partly answers the question. When another member's resource answers better than yours, link that instead; members notice who links to others.
| Answer style | What it looks like | How it is received |
|---|---|---|
| Full answer, no link | The answer, the reasoning and the caveats in the thread | Welcomed; builds the member's standing |
| Full answer with further reading | The same, plus a link to a fuller version, introduced by what it adds | Welcomed where links are allowed |
| Partial answer with "see my guide" | A line or two, then the link | Often treated as promotion |
| Link only | A bare link, or "this explains it" | Removed as a link drop |
| Same link in many threads | Copy and paste across questions | Treated as spam, and the account is banned |
Saying who you work for
When you share content your organisation published, or recommend its products, say so in the post, plainly and where readers will see it: "I work for the company that made this" or "I wrote this guide for my employer". A line in a profile that few people open is not enough on its own.
There are two reasons. The first is the community's own rules, many of which require it. The second is the endorsement principle the site's guides record from regulators. The reviews and social proof guide sets out, from the FTC's business guidance, that endorsements from people with a material connection to a business, including staff, must say so. The influencer contracts and disclosure guide records that the FTC's endorsement guidance expects material connections to be disclosed clearly and conspicuously, and its published questions and answers cover common situations. A staff member recommending the company's guide or product in a thread is endorsing it, and the reader is entitled to know who is speaking.
The same applies to anyone the organisation asks or rewards for posting: agencies, freelancers, partners and customers given something in return. This section describes general practice and what the site's guides record from the FTC's guidance. It is educational, not legal advice, and the exact wording is for your adviser and the regulator's own guidance.
What never to do: link drops, fake accounts and seeded threads
Some practices are against community rules everywhere, and several are named in the sources this site cites.
- Link drops. Posting links with little or no answer, or the same link across many threads. Communities remove them; forum comments with optimised links are on the spam policies guide's list of link spam examples.
- Keyword anchors and signature links. Links whose words are the query you want to rank for, in posts or signatures. A community link is for readers, and the ugc value Google recommends on such links says so.
- Fake accounts. Accounts that pretend to be independent members, whether run by staff, an agency or a tool. The guide to AI claims and consumer protection warns that seeding comments or replies with generated accounts creates endorsers that do not exist, and the reviews guide records that fake reviews are prohibited.
- Seeded threads. Asking a question from one account in order to answer it with a link from another, or asking colleagues to post questions your content happens to answer.
- Undisclosed staff and paid posters. Employees, agencies or anyone rewarded for posting who do not say so.
- Buying upvotes or engagement. It misrepresents what members think, and communities treat it as manipulation.
- Arguing with moderators in public. If a post is removed, read the rule it broke and ask privately if you are unsure.
If a tactic would embarrass you if a moderator or a journalist traced it back to your organisation, do not use it. The reputational cost of being caught astroturfing in a community your customers use is larger than anything the tactic could bring.
Measuring what community work brings
Count outcomes, not posts. The number of answers posted measures effort; what the effort brought is in your analytics and in what you learn.
| What to measure | Where to find it | What it tells you |
|---|---|---|
| Visits referred by each community | Analytics referral reports, filtered by the community's domain | Whether members follow your links |
| What those visitors did next | Key events for the referred sessions | Whether they were the readers the piece was for |
| Tagged-link visits | Campaign reports, only where the community's rules allow tagged links | Which threads and pieces drove visits |
| Replies, thanks and follow-up questions | The threads themselves | Whether your answers helped |
| Removed posts or moderator warnings | Your own log | Whether you are reading the rules correctly |
| New questions collected | Your question bank | Which pieces to write or update next |
| Time spent | Your own records | The cost to set against all of the above |
Referral reports work without any tagging, because visits from a community arrive with its domain as the referrer. If the community's rules allow tagged links, tag them as the naming conventions and UTMs guide describes, so each community reports separately; where a tagged UTMURL tags identifying traffic source. link would look odd or break a rule, leave it plain. Community answers also extend ReachUnique people who saw an ad. in ways analytics will not show: members who read an answer without clicking, and people who later search for the brand. Ask new customers where they heard of you.
The most durable return is often the questions. Every thread shows how people describe their problem and what they have already tried. Add them to the question bank, and when the same question keeps coming up with no good answer, write the piece. If your community answers draw few replies or visits, the content not getting engagement page covers the wider diagnosis.
Running a community of your own, with moderation rules, response standards and community health measures, is a different job, covered in the community management guide.
A knitting pattern designer in craft forums (illustrative)
Kiteloom Knitting Patterns answers questions in craft forums
Kiteloom Knitting Patterns, an invented knitting-pattern designer run by one person, has a free tutorial on rescuing dropped stitches. She joins 3 craft forums where her customers ask for help. The first allows links to members' own sites only after 30 posts; the second allows them in any thread if the poster says it is their own work; the third bans them, except in a monthly thread for members' projects. For six weeks she posts no links at all, answering 25 questions about knitting technique in full. Then, when a member asks how to pick up a dropped stitch three rows down, she writes the method out in the thread in six short steps and adds: "I wrote a tutorial with photos of each step, and I sell patterns, so I'm biased: [link]." In the third forum she never links in answers, and posts the tutorial only in the monthly thread, saying she designed it. Her analytics show 380 visits referred by the three forums over three months, 52 sign-ups to her pattern newsletter from those visits, and no removed posts. She stops counting answers posted, and adds 14 questions she had not heard before to her question bank, 2 of which become new tutorials.
Common mistakes
- Posting before reading the rules. Every community sets its own; read them in each one before the first post.
- Linking before taking part. A newcomer whose first post is a link is treated as a spammer, and usually is.
- A link as the answer. Answer in the thread first; link only as further reading.
- The same link across many threads. It is the pattern moderators and spam policies describe.
- Not saying who you work for. Readers are entitled to know, and the endorsement principle the site's guides record says so.
- Fake accounts and seeded threads. They create endorsers that do not exist, and the damage when they are found is lasting.
- Spreading thin. One post in many communities builds no standing; a steady presence in a few does.
- Tagging links where the rules forbid it. Use referral reports instead.
- Counting posts. Measure referred visits, what visitors did and the questions collected.
- Treating someone else's community as your own. Moderation, rules and tone are theirs; running a community is a different job.
