Skip to main content

Reddit comment examples

What works in one subreddit can miss in another.

Explore how a personal story and a technical answer call for different writing choices. Use these guides to review the context before you reply to a live thread.

These are writing guides, not measured campaign results or promises of engagement.

3D coral question mark above a teal comment bubble

The short version

Read the thread before choosing a format.

A reply needs to answer the prompt and fit the community. Review these four things before deciding what to write.

01read the prompt
02check the rules
03add useful detail
04review the outcome

Compare a story-led reply with a technical answer.

These guides focus on the questions to ask when reviewing a reply: what it adds, how it fits, and what you can honestly conclude.

3D coral question mark above a teal comment bubble

r/AskReddit · Personal answers

When the prompt asks for a story

A personal answer should connect directly to the question. Include the details that make the experience understandable, and leave out a product mention when it does not help answer the prompt.

Review the opening, the amount of context, and whether the reply sounds like a real contribution to this particular conversation.

A clear story can still receive little attention. Format alone does not predict votes.

3D folder and comment cards with a coral magnifying glass

r/SEO · Technical answers

When the question needs a practical answer

A technical reply should explain its reasoning and distinguish an observation from an assumption. Give the reader enough context to decide whether the advice fits their situation.

Check whether a suggested tool or link is necessary, whether a business connection needs disclosure, and whether the answer respects the community rules.

A helpful explanation is not a guarantee of rankings, traffic, or engagement.

Different prompts need different details.

Use these questions to review a draft before posting. They are a writing checklist, not a comparison of measured performance.

Questions for reviewing personal and technical replies
Review pointPersonal replyTechnical replyCheck
OpeningAnswer the personal questionAddress the stated problemIs the connection clear?
DetailRelevant experienceReasoning and evidenceDoes it help the reader?
LengthEnough context for the storyEnough detail to assess the adviceCan anything be removed?
LinksOnly when usefulSources or relevant referencesAre links allowed here?
Business tiesDisclose relevant connectionsDisclose relevant connectionsIs the relationship clear?
OutcomeReview responses in contextReview responses in contextWhat was actually observed?

Topic, timing, moderation, and thread placement all affect the context in which a reply appears. This checklist does not establish a ranking formula.

Make the next reply useful.

Start with the thread in front of you. A useful comment still needs to fit the community, the prompt, and the rules.

  1. 01

    Check the community

    Read the current subreddit rules and recent top comments. Look for the format the conversation actually rewards.

  2. 02

    Answer the prompt

    Keep the answer useful, specific, and honest about any business connection.

  3. 03

    Measure the right thing

    Keep post totals, comment scores, visits, and useful outcomes in separate measures. A visible score does not prove a business result.

Writing guidance, with clear limits.

These pages explain how to assess a reply. They do not report a controlled experiment or measured customer campaign results.

Votes, traffic, and business outcomes need their own evidence. Review the actual thread and track the outcome you care about before drawing conclusions.

View the current package options

Have a real thread to review?

Start with the thread and the community rules. RedComments packages include aged accounts, a drip-feed option, and a replacement guarantee. Review how it works before you choose a package.