I started building English tool sites in early 2026. The goal was simple: build sites that get indexed by both Google AND AI Overviews, with minimum cost.
4 months later, I have 15 tool sites under one domain (deepfms.com) — converters, dev tools, USB-C calculators. Some are doing 200+ daily PV. Some got cited by AI Overview within days.
Here's my complete SOP, soup to nuts.
#
- Keyword Research: Not every keyword is worth your time
The Core Metric: KGR (Keyword Golden Ratio) #
KGR < 0.25: Green light. New sites can rank. #
KGR 0.25 ~ 1: Doable but needs solid content. #
KGR > 1: Don't bother. Established sites own the SERP.
My Research Process
Start with a scenario, not a tool
- ❌ "I want to build a PDF compressor"
- ✅ "What online tools do people need when building a resume?"
Pull keyword lists — SEMrush, Ahrefs, or free tools like Ubersuggest
Manually check Google's top 10 — If the top results are old/broken sites, that's your signal
Calculate KGR — Filter for <0.25
Reverse-engineer low-authority competitors — Find their feature gaps
Real Keyword Examples (All KGR < 0.25) | Keyword | KGR | Verdict | | usb-c to ethernet adapter not working | 0.12 | ✅ Go | | usb-c docking station keeps disconnecting | 0.08 | ✅ Go | | usb-c cable types explained | 0.18 | ✅ Go |
#
- Building: Static sites, cheap and fast
Once you pick a keyword, don't write a blog post. Build a tool page instead.
Why Tool Sites?
AI loves tools: When someone searches "convert kg to lbs", AI Overviews cite a working converter, not a 2000-word article #
Higher dwell time: Open tool → use → copy result. That's 40+ seconds of engagement. #
Google favors utility: Core Web Vitals updates have been kind to tool pages over content-only pages
Stack
Every tool is a single .html
file. Self-contained. No framework, no build step.
#
- GEO Injection: Make AI cite you
GEO (Generative Engine Optimization) isn't replacing SEO. It's complementing it. SEO targets Google rankings. GEO targets AI Overview citations.
My GEO Checklist (every page must have all 8)
Key Technique
Answer-direct: Structure content to give the answer immediately. No fluff intros. #
Credibility markers: Include real test data. "Verified 100+ conversions" beats theory every time. #
Niche down: Don't chase broad terms. Target "specific person + specific scenario + specific problem".
#
- Deployment: Cloudflare Pages
Why Cloudflare Pages
Free: Bandwidth limits are generous for tool sites #
CDN: 330+ data centers, T1 latency #
Auto HTTPS: No certificate management #
One-click rollback: Screw up? 30 seconds to restore
Deploy (three commands)
#
- Real Data (2 months in) | Metric | Data | | Total sites | 15 | | Fastest Google indexing | 3 days | | AI Overview citations | 4 sites | | Daily total PV | 200+ (growing) | | Build time per site | 2-4 hours |
#
- Real Case Study: AI Humanizer
While building these sites, I noticed a problem: I was writing lots of content with AI, but readers could tell. So I built an AI Humanizer tool that does two things: #
Detect — Paste AI text, identify 30+ AI tells ("it's worth noting", "furthermore", "in today's world"), give an AI score #
Humanize — One-click replacement of AI patterns with natural language
This tool itself was built using the same GEO SOP: keyword research ("make AI text sound human" KGR < 0.25), static page, GEO injection (FAQ Schema + structured data), CF Pages deploy. Idea to launch: 2 hours.
#
- The Solo Dev Playbook
The core advantage of this system is reproducibility:
One keyword list feeds N sites (batch by niche) #
Template-driven development — swap copy and variables #
GEO standards in one script — batch-inject schemas across all pages #
Cheap iteration — a site from keyword research to deploy in 2-4 hours
What's Next
- GEO content writing service (per-article, bundled with the AI Humanizer tool)
- AI private deployment for local businesses (FDE model)
*Built with deepfms.com — free online tools for developers. Check out the *AI Humanizer if you write with AI.