A source-backed Rankhog guide to r/golang: public rules, community context, posting fit, and startup-promotion risk before you publish.
Members
382.1K
Community age
Created Nov 2009, 16 years
To post
No minimum in the rules
To comment
No minimum in the rules
Self-promotion
Allowed with conditionsDo not include engagement hooks. Open source Go tools are welcome, but avoid closed-source paid software not aimed at Go developers.
Links
Allowed with conditionsDo not post links to pirated copies of copyrighted material.
Promo risk
MediumFrom the rules, not from removal counts
Checked October 30, 2026 from the community's public Reddit pages:
Subreddit guides combine public Reddit source URLs, captured rules, visible verification dates, and Rankhog's account-safety workflow.
Rule summary
[>]
Be friendly and welcoming.: Post is not in keeping with an inclusive and friendly technical atmosphere.
[>]
Be patient.: Remember that people have varying communication styles and that not everyone is using their native language. (Meaning and tone can be lost in translation.)
[>]
Be thoughtful.: Productive communication requires effort. Think about how your words will be interpreted. Remember that sometimes it is best to refrain entirely from commenting. Check for your answer in the [subreddit FAQs](https://www.reddit.com/r/golang/wiki/r_golang_faqs/) and the [Tour of Go](https://go.dev/tour/welcome/1) before posting common questions, please.
[>]
Be respectful.: In particular, respect differences of opinion. Do not include "engagement hooks", like exhortations to subscribe to some channel or redundantly asking what others think.
[>]
Be charitable.: Interpret the arguments of others in good faith, do not seek to disagree. When we do disagree, try to understand why.
[>]
Be constructive.: Avoid derailing: stay on topic; if you want to talk about something else, start a new conversation. Avoid unconstructive criticism: don't merely decry the current state of affairs; offer - or at least solicit - suggestions as to how things may be improved. Avoid snarking (pithy, unproductive, sniping comments) Avoid discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict. Avoid microaggressions Do not post "Ask an AI"
[>]
Be responsible.: What you say and do matters. Take responsibility for your words and actions, including their consequences, whether intended or otherwise.
[>]
Follow the Go Code of Conduct: As a part of the Go community, this subreddit and those who post on it should follow the tenets laid out in the Go Code of Conduct: https://golang.org/conduct Treat everyone with respect and kindness. Be thoughtful in how you communicate. Don’t be destructive or inflammatory.
[>]
Must be Go Related: Posts must be of interest to Go developers and related to the Go language. This includes: - Articles about the language itself - Announcements & articles about open source Go libraries or applications - Dev tools (open source or not) specifically targeted at Go developers We ask that you not post about closed-source / paid software that is not specifically aimed at Go developers in particular (as opposed to all developers), even if it is written in Go.
[>]
Do Not Post Pirated Material: Do not post links to or instructions on how to get pirated copies of copyrighted material.
[>]
Job Listings Go in the Who's Hiring? Post: We have a monthly "Who's Hiring?" post that will stay pinned to the top of the subreddit. To avoid too much noise from companies, please post job openings there. Please keep in mind, this is for 1st party postings only. No 3rd party recruiters.
[>]
AI Policy: No GPT or other AI-generated content is allowed as posts, post targets, or comments. This is only for the content itself; posts about GPT or AI related to Go are fine. Posts of projects have [different rules](https://www.reddit.com/r/golang/wiki/project_requirements/). As it is not easy to determine what is and is not AI, posts will be removed based on their appearence.
Works well
Announce an open source Go library or application with a short explanation of the problem it solves and a link to the source code.
Share a dev tool built specifically for Go developers, as long as the post is about the tool's usefulness to people writing Go.
Write an article about the Go language itself, like a technique, a pattern, or a lesson from a real project.
Ask a question about Go after checking the subreddit FAQs and the Tour of Go so you are not repeating a common question.
Announce a Go related event, since the community description explicitly includes events in its scope.
Avoid
Posting anything written by an AI, because the “AI Policy” says posts are removed based on their appearance even when the topic itself is fine.
Sharing a paid or closed-source tool that serves all developers rather than being aimed at Go developers in particular, which “Must be Go Related” rules out.
Adding calls to subscribe to a channel or asking readers what they think just to farm replies, since “Be respectful” names those as engagement hooks.
Dropping a job opening as its own post, because “Job Listings Go in the Who's Hiring? Post” keeps all hiring in the monthly pinned thread and bars third party recruiters.
Asking a common question before checking the subreddit FAQs and the Tour of Go, which is what “Be thoughtful” asks of you.
Pasting an AI summary as a comment or using a link that resolves to AI content, both of which the “AI Policy” treats as violations.
What r/golang Is For
r/golang is a community for people who build with the Go programming language. The public description says it is a place to ask questions and post articles about Go and related tools, events and such. The rules make the picture sharper. Posts must be of interest to Go developers, which covers articles about the language itself, announcements about open source Go libraries or applications, and dev tools aimed at Go developers specifically. The people here are working programmers who answer questions, discuss the language, and share what they have built or found useful.
Rules That Matter Before Posting
The rule that decides everything about promotion is “Must be Go Related”. It welcomes articles about the language, announcements about open source Go libraries or applications, and dev tools aimed at Go developers, but it asks you not to post closed-source or paid software that is not specifically aimed at Go developers, even if it is written in Go. The “AI Policy” is strict and unusual. No AI-generated content is allowed as posts, post targets, or comments, and because it is hard to tell what is AI, posts get removed based on their appearance. “Be respectful” bans engagement hooks, like asking people to subscribe to a channel or repeatedly asking what others think. “Job Listings Go in the Who's Hiring? Post” keeps all hiring talk in the monthly pinned thread and only allows first party postings, with no third party recruiters. Finally, “Do Not Post Pirated Material” applies if you ever link to code, books, or other copyrighted things.
What To Post
A good post here is written by a human, about Go, and useful to someone who writes Go all day. If you built an open source tool that makes Go development easier, announce it plainly. Say what it does, link the source, and answer questions honestly in the comments. Articles about the language itself also fit. Before you post a question, check the subreddit FAQs and the Tour of Go, because the rules ask you to rule out common questions first. Keep the tone friendly and constructive, offer suggestions rather than complaints, and stay on topic. If you want feedback on your post idea, ask it in a normal human way, not as a vague what do you all think prompt.
What To Avoid
Several things will get a post removed here. The “AI Policy” bans AI-generated content in posts, post targets, and comments, and the moderators say they judge by appearance, so do not use AI to write anything you plan to share. “Must be Go Related” rules out closed-source or paid software that is not aimed specifically at Go developers, even if you built it with Go. “Be respectful” bans engagement hooks, so avoid exhortations to subscribe to a channel or redundantly asking what others think. “Be constructive” asks you to stay on topic, avoid sniping comments, and not post an “Ask an AI” post. “Job Listings Go in the Who's Hiring? Post” means job openings only go in the monthly pinned post, first party only, no third party recruiters. “Do Not Post Pirated Material” bans links to or instructions for getting pirated copies of copyrighted material. “Be thoughtful” also asks you to check the subreddit FAQs and the Tour of Go before posting common questions.
Use Rankhog before posting in r/golang
Want the version that does not run out? Subscribers get unlimited tool runs and more careful checks before posting.
Start your 7-day free trial. Card required. $99/month after trial. Next, connect a verified Reddit account; no strategy starts until you explicitly start Rankhog.
Can I post my dev tool here if my company makes it?
Yes, if the tool is open source and aimed at Go developers in particular, since “Must be Go Related” explicitly welcomes announcements and articles about open source Go libraries, applications, and dev tools.
I have a paid product that happens to be written in Go. Can I promote it?
Not as a plain post. The rules ask you not to post about closed-source or paid software that is not specifically aimed at Go developers, even if it is written in Go.
Where do I post a job opening?
Yes, but only inside the monthly pinned “Who's Hiring?” post, and only as a first party posting from the company itself.
Can I use AI to draft my post?
No. The “AI Policy” bans AI-generated content as posts, post targets, and comments, and removes posts based on their appearance, though posts about AI as a Go topic are fine.
Can I discuss AI topics at all, like a Go library for machine learning?
Yes. The “AI Policy” says posts about GPT or AI related to Go are fine, so the topic is allowed while AI-written content is not.