tests reddit-como-fonte-de-conteudo

experiment in progress

Reddit as a content source

What if the content strategy came only from real questions people post on Reddit? Real users, real problems and no dependence on third-party search volume tools. This test wants to find out whether that brings acquisition.

posts analyzed
2,690
communities
2
clusters
13
pieces planned
68
// the hypothesis
The questions asked on r/SEO and r/TechSEO are the same ones people type into Google or ask an AI, even when keyword tools say the volume is zero.

Day to day, I would never skip keywords and volume. Here the scope is a test: the whole content plan comes from Reddit, to see whether it can bring acquisition to those famous zero-volume keywords that someone still clicks on.

// the process
  1. 01

    Collection

    I collected posts from r/SEO (1,458) and r/TechSEO (1,232) with a scraper we built, combining the new and top sorts to get past Reddit’s 1,000-post limit. Total cost: about US$ 3.

  2. 02

    Grouping into topics

    Every post was classified into a cluster and subcluster. The number of posts in each subcluster becomes the demand signal, instead of search volume.

  3. 03

    Creation

    Each cluster becomes a pillar page and supporting pieces, produced with AI and validated by me. The step by step is right below.

  4. 04

    Tracking

    The pieces go live with the reddit tag and indexing requested in Search Console. The focus is presence in AI snippets and Google impressions, cluster by cluster.

// where the demand is

Posts per cluster across both communities. Career and market (243) and community and news (235) were left out of the plan.

  • Architecture and technical SEO343 posts
  • Tools, data and automation332 posts
  • AI, GEO/AEO and LLMs257 posts
  • Content and on-page256 posts
  • Indexing and crawling230 posts
  • Drops, updates and penalties228 posts
  • Link building and backlinks126 posts
  • Structured data and SERP features105 posts
  • Performance and rendering82 posts
  • General strategy and beginners82 posts
  • Local SEO73 posts
  • Spam, black hat and self-promotion46 posts
  • E-commerce and platforms28 posts
// how the content is made

With the base extracted and grouped, production starts. AI does the heavy lifting and I keep the decisions and the validation.

  1. 01

    Content plan

    13 pillars and 55 supporting pieces, one per recurring question. Slugs are fixed from the start so internal linking across clusters works.

  2. 02

    Real pains

    For each piece, the writer reads the titles and texts of the subcluster posts. That is where the angle and the questions the article answers come from.

  3. 03

    Google research

    One search per piece and an analysis of the top 3 pages: structure, formats, sourced data and what is missing. The gap becomes the piece’s edge.

  4. 04

    Writing

    One AI agent per cluster writes following a style guide. The pillar links to every supporting piece and each one links back to the pillar.

  5. 05

    Images in Flow

    Each article marks where diagrams, flowcharts and tables go. Images and covers are generated in Google Flow with Nano Banana, in the site palette, and exported as light WebP.

  6. 06

    Review and publishing

    Style, link and meta description review, English translation and my own validation. Real cases, screenshots and sources to confirm stay flagged, and the site will not publish while anything is pending.

// what I will measure

Google impressions

Whether pages planned only from Reddit show up for real searches, even without visible volume.

Presence in AI answers

Whether the pieces appear in AI Overviews and other AI-generated answers.

Clicks on zero-volume keywords

Whether the queries that bring clicks are the ones no tool would show.

// insights

What the human review of the first pieces found, good and bad. Each fix becomes a rule in the style guide and a check in the publishing flow, so it also applies to the next ones.

what worked

  • Answer before context

    The openings answer the question in the first sentence and only then explain why. That is what someone arriving from Google or from an AI answer needs.

  • Summary up top

    Every article opens with a highlights box, so you get the essentials before reading the whole piece.

  • No wall of text

    Tables when the information is comparative, commands ready to copy, and paragraphs that connect instead of turning into loose lists.

  • Plain language, clear stance

    Direct sentences, no marketing vocabulary and a clear position, skeptical of the GEO hype.

  • Source next to the number

    Data comes with a link to the study right next to it, which helps readers and AI models trust what is written.

what needed fixing

  • Internal terms in the text

    One article said “This supporting piece shows the manual method first”. “Supporting piece” is what we call it in our content organization, not something readers understand, and it is the kind of trace that gives away automated production.

    fixInternal terms went into the banned list of the style guide, were replaced in the articles, and the site will not publish text that still has them.

  • A number that changed meaning in the summary

    A Cloudflare analysis shows 78% of sites have a robots.txt and only 4% include any rule for AI bots. In the main article’s summary, the 78% became “sites that have not decided anything about AI bots”, with no source. That is exactly the part an AI is most likely to quote.

    fixThe summary was corrected, and the site now blocks any number in the highlights box that does not appear in the body of the article.

  • Questions in English, content in Portuguese

    The topics come from English-speaking communities, but the main version of the articles is in Portuguese. There is demand in Brazil, just smaller: “llms.txt” gets 200 searches a month there against 2,500 in the US, according to Ahrefs.

    fixIt is part of the test design. The articles are also published in English, and the point is noted for tests in other segments.