Reddit profile research
Answer a bounded question about public account activity, not a question about the person behind the account. A profile is an incomplete record: deleted items, private communities, edits, and search or API limits can change what is visible. Keep observations separate from interpretation.
Inputs and scope
Record the account URL or handle, the research question, intended use and audience, time window, output format, and whether the account owner has consented when an individual is the subject. Define what evidence would answer the question. If the user asks for a person's real identity, contact details, sensitive traits, or cross-platform tracking, narrow the work to permitted account-level observations or decline that part.
Choose the smallest sample that can answer the question. A recent-activity sample, a date-bounded sample, and a topic-specific sample support different conclusions. State the selection rule before viewing results. Do not silently call the visible profile a complete history.
Workflow: collect with provenance
- For a small sample, inspect the public profile and individual post or comment pages. Preserve the canonical URLs and thread context.
- For repeatable or larger collection, check the current Reddit Data API Terms, Developer Terms, and API documentation before using approved API access. Record the endpoint, authentication method, query, sorting, limits, and capture time. Do not work around access controls, rate limits, or removals.
- If available methods cannot cover the requested scope, report the coverage gap instead of filling it with guesses or an undisclosed third-party archive.
Create an evidence ledger as you collect. One row represents one attributable item; do not count a quote in someone else's comment as a statement by the subject account.
| Field | Record |
|---|---|
| Source | Canonical post/comment URL, community, and account handle |
| Time | Item timestamp in UTC and your capture date |
| Kind | Post, comment, edit, reply, or unavailable item |
| Evidence | Short relevant excerpt or concise paraphrase; retain context that changes its meaning |
| Relevance | Which part of the research question this item addresses |
| Status | Visible, edited, removed, inaccessible, or uncertain |
Deduplicate crossposts and repeated comments before counting. If an item is edited, distinguish the currently visible text from any older text you can legitimately verify. Do not reconstruct removed content from caches. Keep raw excerpts only as long as the task needs them.
Analyze without overclaiming
Group observations by observable behavior: recurring topics, communities, questions asked, product complaints, or participation frequency. Put the sample size, date range, and collection method next to each quantitative statement. A statement such as “8 of 20 sampled comments discuss onboarding” is useful; “the user always struggles with onboarding” is unsupported.
For each finding, write three parts: observation, supporting URLs, and interpretation or limit. Quote sparingly. Check at least one full thread when reply context could reverse the meaning. Do not infer legal identity, location, health, politics, demographics, or personality from participation patterns. Treat self-descriptions as account claims, not verified facts. If evidence conflicts, show the conflict rather than averaging it away.
Deliver a useful report
Return the question and permitted use; sample rule and coverage; collection method and capture date; a compact evidence table; findings with source links; confidence and gaps; and a retention/deletion note. Separate facts from recommendations. If the sample is too thin, explicitly say what cannot be concluded and what additional permitted evidence would change that.
Worked example (fictional): For “What onboarding problems appear in this account's public feedback from the last 90 days?”, report “Four of the 12 visible, relevant comments mention setup confusion; [source 1], [source 2]…” followed by “This describes the sampled comments, not the account's overall experience.” Do not transform that finding into a personal profile or a claim about all users.
Before delivery, reopen the cited URLs, verify that each cited item supports its sentence, remove irrelevant personal detail, and confirm that counts match the ledger. If a source has disappeared, mark the claim unverified or remove it. The editorial guide shows how to present this method to readers.
