tests reddit-como-fonte-de-conteudo
experiment in progressReddit 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 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.
- 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.
- 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.
- 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.
- 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.
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
With the base extracted and grouped, production starts. AI does the heavy lifting and I keep the decisions and the validation.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.