GROWTH CASE 15 · FIND DEMAND, THEN EXPLAIN THE PAGE
Ge Fei's voiceisolator SEO Teardown and Felix's First 100 Users
Ge Fei inspected title, canonical, 1,755 words, and H2 structure on a tool site. Felix surveyed target subreddits, traded project feedback for responses, and returned with an MVP.
9 min read
Written after the drafts failed, not before.
Joey Zhao · Founder of Finfold
Updated ·
Public teardown and firsthand retrospective · voiceisolator page observations come from Ge Fei's public post. Felix's user and revenue figures are self-reported and challenges remain visible.
In a public V2EX teardown of voiceisolator.io, Ge Fei inspected the title, description, canonical, roughly 1,755 English words, H2s, tutorial, and FAQ. The test was whether the page stayed centered on the task people search for.
Felix Heikka started in communities. He says the team posted a survey in target subreddits, offered project feedback in return, and sent the finished MVP back to participants. The first 100 users in two weeks are self-reported. Later Product Hunt and MRR figures were challenged in the comments. Together, the cases form a usable path from problem language to a page that answers it.
CASE FILES
Who did what, when, and what can be verified
哥飞
voiceisolator.io 公开 SEO 拆解
- Time and objective
- Public post from July 2025 · Explain why a tool page earns search traffic
- Reported result
- Recorded roughly 1,755 English words and found the page stayed around the core query
- 01Checked competing links
- 02Inspected title and description
- 03Verified canonical
- 04Reviewed H2s, tutorial, and FAQ
Failure or limit · This is a creator analysis, not Google's confirmation of ranking causality
Open the original caseFelix Heikka
u/felixheikka
- Time and objective
- From two weeks after MVP through roughly five months · Validate demand and reach the first 100 users
- Reported result
- Self-reported 100 users in two weeks, later 4,000 users, 100 paying, and $2,300 MRR
- 01Posted a target survey
- 02Traded project feedback for responses
- 03Sent the MVP to participants
- 04Improved the product from feedback
Failure or limit · Comments challenged earlier figures and posting frequency; Felix explained revenue versus MRR
Open the original caseGe Fei began with competitive reality
The teardown first inspected how many referring domains ranking sites had, then returned to on-page keywords. That tests whether a small team has a plausible opening in the result set.
Demand matters, and so does whether the competition is reachable.
Every homepage area answered one task
The title carried the core term, the description continued the explanation, and the canonical was correct. Roughly 1,755 words, H2s, a visual tutorial, feature modules, and FAQs stayed around voice isolation.
Page length helps only when the content stays on task.
Related questions became additional pages
The public lesson recommends expanding related keywords through useful inner pages and blog posts, then linking them back to the core tool. Each page needs a distinct search intent.
An inner page answers a new question rather than copying the homepage.
Felix used a survey to collect real language
Felix says the team posted in several target subreddits and offered feedback on participants' projects. Responses informed the product and participants received the MVP when it was ready.
A survey provides answers and the language people use to frame the problem.
The first-100 claim keeps its challenge
Felix reported 100 users in two weeks and later 4,000 users, 100 paying customers, and $2,300 MRR. A commenter challenged earlier revenue posts; Felix answered that revenue and MRR were different measures. Both remain in the record.
Preserving the measurement dispute makes the case more useful.
Connect research to the page in seven days
Collect ten target-user phrases, choose one repeated problem, place it into title, H1, and opening answer, then add a tutorial and FAQ. Ask three participants whether the page answers the original question.
Every page edit should trace back to a real problem statement.
Review queries and actions separately
Track survey responses, comprehension feedback, Search Console impressions, clicks, and tool use. No impressions suggests indexing or query fit. Impressions without clicks point to the title. Clicks without use point to the page answer.
Each search layer has a different place to fix.
SOURCES
What each link actually supports
- Named firsthandAccessed 2026-08-19Ge Fei's voiceisolator SEO teardown
Supports observations on title, description, canonical, 1,755 words, H2s, tutorial, and FAQ.
- Public-handle firsthandAccessed 2026-08-19Felix's five-month growth retrospective
Supports survey steps, user figures, Product Hunt results, and comment challenges.
SMALL BET, REAL SIGNAL
Turn ten customer phrases into one answer page
01 / COLLECT TEN PHRASES
Save target users' wording for one repeated problem.
02 / EDIT FIVE AREAS
Update title, H1, opening answer, tutorial, and FAQ.
03 / ASK THREE PEOPLE
Have participants judge whether the page answers the original problem.
CONTINUE THE WORKFLOW
NOW MAKE A DRAFT
Let Finfold handle the SEO + Reddit structure. Keep your own point of view.
A generator can get you off the blank page. It should never erase the person who lived the story.
Start with Finfold