Forem: gong junhao

How One Indie Dev Went from 0 to 15K Organic Visits in 8 Weeks

gong junhao — Tue, 12 May 2026 13:15:16 +0000

The Situation

Eight weeks ago, I had a SaaS product with exactly zero organic traffic.

Not "low traffic." Zero. No blog posts ranking. No backlinks. No domain authority. Just a landing page collecting dust on page 47 of Google.

I'm a solo developer. No marketing budget. No SEO team. No time to write 50 blog posts and pray.

I needed a strategy that would work with limited time, limited money, and zero existing traffic.

Here's exactly what I did, week by week.

The Problem with "Standard SEO Advice"

Every SEO guide I read told me the same thing:

Do keyword research
Find high-volume, low-competition keywords
Write content targeting those keywords
Build backlinks
Wait 6-12 months

That's great if you're a funded startup with a content team. I'm one person who codes and markets between 10pm and 1am.

The standard playbook was built for teams with budgets. I needed a different approach.

The Shift: Competitor-First SEO

Instead of starting with keyword volume, I started with what my competitors were already ranking for.

The logic is simple:

If a competitor ranks for a keyword, there's proven demand
If I'm not ranking for that keyword, it's a gap
Content gaps are easier to fill than finding new keywords from scratch

This is "competitive intelligence" and it changed everything for me.

Week 1: Analysis

Time spent: ~4 hours total

I identified my 3 closest competitors — not the big players, but the indie tools solving the same problem for the same audience.

For each competitor, I pulled:

Their top-ranking keywords
Their best-performing pages
Keywords they rank for that I don't appear on at all

What I found:

47 keywords where competitors ranked and I had zero presence
12 of those keywords had clear search intent I could match
6 were "comparison" or "alternative" keywords (high intent)

Priority: I ranked all 47 keywords by difficulty, search intent, and relevance to my product. Picked the top 5 to start.

Week 2-3: First Content

Time spent: ~3 hours per article

I wrote 2 pieces of content:

A comparison page: "[My Tool] vs [Competitor A]"
- 2,200 words with screenshots and pricing comparison
- Clear recommendation scenarios
An alternative page: "Best [Competitor B] Alternatives"
- 1,800 words, 5 alternatives listed honestly
- Focused on specific use case

Key lesson: Write for the exact person searching "[competitor] alternative" — they're already looking for a solution.

Week 4: First Results

3 pages indexed (2 new + homepage)
14 impressions, 2 clicks

The comparison page was already climbing.

Week 5-6: Second Wave

Published 3 more pages. Total: 5 pages, ~10,000 words.

Results:

847 impressions, 52 clicks
Comparison page ranking #8
Alternative page ranking #14

Week 7-8: The Acceleration

Google started trusting my site more. Pages jumped from page 2 to page 1.

Week 8 results:

Monthly organic visits: ~15,000
Total pages published: 7
Keywords in top 10: 8
Keywords in top 30: 23
Paying customers from organic: 3

At $29/month each, that's $87/month from 7 pages and zero ad spend.

The Key Insight: Precision > Volume

7 targeted pages > 50 generic blog posts
Competitor keywords > random high-volume terms
Comparison pages > "ultimate guides"
Weekly gap analysis > "set and forget" calendars

Math: 50 posts × 50 visits = 2,500 vs 7 pages × 2,000+ visits = 14,000+

The Weekly Workflow

Monday (30 min): Check for keyword gaps
Tuesday (30 min): Prioritize 1-2 keywords
Wed-Thu (2-3 hrs): Write content
Friday (30 min): Review Search Console

Total: 4-5 hours/week

What I'd Do Differently

Start with comparison pages first
Don't overthink keyword difficulty
Update existing pages before writing new ones

Try It Yourself

If you're an indie dev with zero traffic:

3-5 competitor keywords to target
Write honest comparison content
Weekly habit of checking gaps

I built SerpPilot to automate this workflow. Free to start — 100 keywords, 3 competitors, 10 AI outlines/month.

No credit card. Built by a solo dev for solo devs.

👉 Start free at SerpPilot

Questions? Drop a comment — I read every one.

I Built an SEO Tool Because Every Existing One Sucked for Solo Devs

gong junhao — Sun, 10 May 2026 09:57:54 +0000

TL;DR: I'm a solo developer. I was tired of paying $99+/month for SEO tools designed for agencies. So I'm building SerpPilot - competitive intelligence + content execution for indie devs and small teams.

Join the waitlist: https://serppilot.alterme.top

The Problem Nobody Talks About

Every indie developer knows the drill: you build something, launch it, and then... crickets. You need traffic. You need SEO. So you Google "best SEO tools" and land on the same recommendations:

Ahrefs: $99/mo (Lite)
SEMrush: $139/mo (Pro)
Moz Pro: $99/mo (Standard)

These are great tools. Seriously. If you're an agency managing 50 clients, they're worth every penny.

But if you're a solo founder bootstrapping a side project? You're paying enterprise prices for features you'll use 10% of.

The Real Cost of "Affordable" SEO

Let me break down what actually happened to me over 6 months:

Month 1-2: Signed up for Ahrefs Lite ($99/mo). Used it to:

Check my domain rating (it was 3)
Look up 10-15 keywords
Stare at the backlink profile feeling overwhelmed

Month 3: Added Mangools ($29/mo) for "simpler" keyword research. Now paying $128/mo total.

Month 4: Subscribed to Surfer SEO ($89/mo) for content optimization. $217/mo.

Month 5: Realized I needed a content brief tool. Added Frase ($15/mo). $232/mo.

Month 6: Added up all the costs. $1,350+ on SEO tools in 6 months. For a project making $200/mo.

This is the dirty secret of the SEO tool industry: they're all designed for agencies and enterprises. The "starter" plans are strategically limited enough that you'll need to upgrade - or buy another tool to fill the gaps.

What I Actually Needed

After wasting months bouncing between tools, I realized I only needed three things:

1. Competitor Keyword Intelligence

Not 10 billion keywords. Just: what are my competitors ranking for that I'm not? Give me the top 50 opportunities, sorted by volume and difficulty.

2. Content Gap Discovery

Compare my domain against 2-3 competitors. Show me the keywords they rank for but I don't. Prioritize by opportunity score.

3. Actionable Content Outlines

Not generic AI slop. Actually analyze the top 10 SERP results for a keyword and tell me: here's your H2 structure, here's the word count target, here are the must-have sections.

That's it. Three features. No backlink database of 35 trillion URLs. No rank tracking for 10,000 keywords. No site audit with 847 issues I'll never fix.

SerpPilot: The 20% That Drives 80%

I'm building SerpPilot around this philosophy: the 20% of SEO that drives 80% of results for small teams.

Here's what it does:

Competitor Keyword Insight

Enter any competitor's domain. See their top-ranking keywords, traffic pages, and content strategy. Understand their playbook in 5 minutes, not 50.

Content Gap Discovery

Side-by-side domain comparison. Find high-value keywords they rank for - but you don't. Sorted by opportunity score so you know exactly what to tackle first.

AI Content Outline Generator

Pick a target keyword. SerpPilot analyzes the top 10 SERP results and generates an optimized outline - H2/H3 structure, word count targets, must-have sections.

Pricing That Won't Make You Cry

Free: 100 keywords/mo, 3 competitors, 10 AI outlines
Pro: $29/mo - everything you need for a small team
Team: $79/mo - for growing teams

No "contact sales" for basic features. No $99 entry point. No upsell hell.

Why Now?

The SEO tool market is going through the same disruption that happened to design tools (Figma vs Adobe), email tools (Resend vs SendGrid), and analytics (Plausible vs Google Analytics).

Indie devs and small teams are rejecting bloated, overpriced tools. They want:

Focused features (not kitchen-sink)
Honest pricing (not bait-and-switch)
Fast workflows (not 47-step setups)

SerpPilot is built for this shift.

What's Next

I'm launching SerpPilot in the next few weeks. The waitlist is open now:

https://serppilot.alterme.top

Early adopters get:

Pro plan free for 3 months
Priority access to new features
Direct input on the product roadmap

If you're an indie dev struggling with SEO, I'd love to hear your story. What's your biggest SEO pain point?

buildinpublic

The 5-Minute Demo Privacy Routine I Wish I Used Earlier

gong junhao — Tue, 17 Feb 2026 23:37:17 +0000

I used to think privacy leaks in screen recordings were rare edge cases.

They are not.
Most of the leaks happen in ordinary moments:

autofill dropdowns
internal tab names
random notifications
customer identifiers in widgets

So I moved to a simple workflow before every recording:

Open a dedicated browser profile for demos.
Turn on Do Not Disturb.
Close chat/email/password-manager overlays.
Run a 30-second dry walkthrough.
Blur sensitive zones before recording.
Rewatch the first 10-15 seconds before sharing.

This process is short enough to use every time, and it cuts accidental exposure risk significantly.

For the blur step, I use BlurMate, a lightweight Chrome extension that lets me place movable blur overlays quickly.

Website: https://blurmate.devstorex.top

If you record tutorials or client demos, what step in your process catches the most hidden leaks?

Before You Hit Record: 7 Small Privacy Checks That Save You Big Trouble

gong junhao — Tue, 17 Feb 2026 08:54:18 +0000

A lot of creators think privacy leaks in screen recordings are about “big mistakes.”

In practice, it’s usually tiny UI details:

autofill dropdowns
internal URLs in tabs
customer names in chat widgets
calendar popups
notification banners

And once a clip is shared, it spreads fast.

My 7-point pre-record checklist

Use a dedicated browser profile for demo recording.
Turn on Focus / Do Not Disturb.
Close chat, mail, and password manager popups.
Test-click form inputs before recording.
Hide bookmarks and tab titles if possible.
Blur sensitive regions in advance.
Rewatch the first 15 seconds before publishing.

Why this matters

Most teams don’t leak data because of hacks.
They leak because of workflow gaps.

A small checklist prevents rework, legal stress, and trust damage.

What I use in step 6

I built a lightweight Chrome extension called BlurMate for exactly this use case.
It lets you add a movable blur overlay on any area of a page while recording or presenting.

If you publish demos, tutorials, onboarding videos, or support walkthroughs, this can help:

https://blurmate.devstorex.top

How I blur sensitive UI before recording a SaaS demo (a simple Chrome workflow)

gong junhao — Sat, 14 Feb 2026 03:24:33 +0000

I nearly shipped a product demo recording that had a customer’s email address sitting in the UI.

Not because I’m reckless. Because I was rushing, I had 10 tabs open, and “I’ll blur it later” felt easier than doing it right.

Here’s the simple Chrome workflow I use now when I’m recording SaaS demos (Loom, Meet, OBS, whatever). It’s designed to prevent the common leaks: names, emails, IDs, internal URLs, and random notifications.

Step 1: Make the demo screen boring

Use a dedicated Chrome profile for demos.
Keep the bookmarks bar clean.
Keep only the extensions you need.
Pin only the tabs you will actually show.

If you share your full desktop, you’re one notification away from an awkward moment. I prefer sharing a single window when possible.

Step 2: Kill notifications everywhere

OS Focus / Do Not Disturb.
Slack/Teams/Discord DND.
Browser extension popups.

This is the fastest “risk reduction per minute” step.

Step 3: Blur sensitive regions before you hit record

Some sensitive info can’t be removed without breaking the flow (think: account dropdowns, invoices, user tables, admin pages).

So I blur it before recording. Not in post.

Step 4: Do a 5-second dry run

Record 5 seconds, click through the first two screens, stop, rewatch.

This catches the stuff you don’t notice while presenting: tab titles, autocomplete suggestions, recent files dialogs, and tiny popups.

A small tool that helped me

I built a Chrome extension called BlurMate to make the “blur first” step less error-prone. It lets you place blur overlays on top of the page (no upload required).

Product site: https://blurmate.devstorex.top

A Pre-Recording Privacy Checklist for SaaS Demos (That Actually Works)

gong junhao — Fri, 13 Feb 2026 00:48:08 +0000

If you share your screen for demos or onboarding calls, privacy leaks usually come from workflow gaps, not security breaches.

I used to rely on post-editing to blur sensitive details. It worked sometimes, but it was slow and stressful. One missed frame was enough to expose user data.

Now I use a pre-recording workflow, and it has made demos safer and faster.

The Checklist

1. Prepare demo-safe data first

Use synthetic names, test emails, and non-real account identifiers before recording.

2. Mark high-risk fields

Identify where sensitive data can appear:

names
email addresses
phone numbers
addresses
account/order IDs
payment-related values

3. Mask before recording

Do not wait until editing. Pre-mask sensitive zones before hitting record.

4. Refresh and verify persistence

Many apps rerender fields on refresh. Confirm your masking still holds after reload.

5. Run a 30-second dry run

Quickly review the test clip. Catch sidebars, popups, autocomplete, and notification leaks early.

6. Record final only after checks pass

This single habit dramatically reduces editing work and privacy risk.

Why this approach works

Most exposure incidents are tiny mistakes under time pressure. A repeatable process beats ad-hoc fixes every time.

For small teams and solo founders, this also reduces stress before client-facing demos.

Optional tool support

You can run this checklist manually, but browser-first masking tools make it much easier to stay consistent.

Product website: https://blurmate.devstorex.top

If you have your own no-leak workflow, I’d love to compare notes in the comments.

The Hidden Privacy Risk in Every Screen Recording (And a Practical Fix)

gong junhao — Thu, 12 Feb 2026 01:54:21 +0000

If you share your screen for demos, tutorials, or client calls, you're one tab away from exposing personal or confidential data.

Most people assume privacy leaks come from hacks. In reality, many leaks happen in normal workflows: screen sharing, quick recordings, and live demos where one field is forgotten.

Why post-editing is not enough

A common workflow is: record first, blur later.

At scale, this breaks:

It is slow and repetitive.
Dynamic content is easy to miss.
One missed frame can expose sensitive info.
Team quality becomes inconsistent.

A safer workflow: protect during capture

A better approach is to protect data in the browser before and during recording.

A simple repeatable flow:

Run a pre-record checklist.
Detect likely sensitive fields.
Blur them before recording starts.
Verify persistence after refresh.
Do a short dry run.

This reduces editing time and lowers avoidable risk.

What should be treated as sensitive?

Start with:

full names
email addresses
phone numbers
addresses
account/order/reference IDs
payment-related fields

Even if one field looks harmless, combinations can identify real people.

Team best practices

Use a shared safe-demo checklist.
Keep a clean demo dataset.
Define must-blur zones for recurring flows.
Add privacy review to content QA.

Practical tooling

I built BlurMate for this browser-first workflow, mainly for creators and SaaS teams that do frequent demos.

Use cases:

product walkthroughs
onboarding recordings
customer support demos
live presentations

If you want to test this approach:
https://blurmate.devstorex.top

The goal is simple: fewer privacy mistakes, less editing overhead, and more confidence when you hit Record.