This is the 100th article on GreenEngGuide. When I started this site in May 2026, I had one goal: write technical content from someone who actually stands inside Chinese factories. One month and 100 articles later, here’s what I’ve learned about writing for engineers — and where we’re going next.
The Numbers (One Month In)
| Metric | Count |
|---|---|
| Total articles | 100 |
| Environmental Engineering | 36 |
| Lithium Battery | 29 |
| Plant Design & CAD | 16 |
| Environmental Compliance | 16 |
| AI & Digital | 9 |
| WeChat (中文) | 8 published + 86 scheduled |
Monthly traffic is still small — we launched less than 30 days ago — but the content foundation is built. Google indexing is accelerating. A few articles are already ranking on page 1-2 for niche queries.
What Content Works
The “Written By Someone Who’s Done It” Advantage
The most surprising feedback: readers can tell when content comes from real experience vs. desk research. An article about baghouse filter selection written by someone who’s stood next to a clogged baghouse at 2 AM reads differently than one written from textbooks.
Examples that got the most engagement:
- Electrode coating defects — “slurry sitting in the pipe for 20 minutes is different slurry”
- Pump NPSH cavitation — “it’s always made that noise ≠ it’s fine”
- The environmental workforce crisis — Chinese version went viral on WeChat because it said what everyone in the industry thinks but few say publicly
Technical Depth > SEO Tricks
Articles with detailed parameter ranges, design equations, and comparison tables consistently outperform short “overview” articles. Engineers search for specific information:
- “What’s the typical L/G ratio for an acid scrubber?” → specific answer needed
- “How do I select between belt press and filter press?” → comparison table with real numbers
- “What’s the current lithium carbonate spot price?” → up-to-date data point
If you answer the specific question clearly and completely, Google rewards you. If you write a 300-word overview with no numbers, you’re competing with Wikipedia and losing.
Bilingual Content Creates Optionality
Writing in both English and Chinese wasn’t the original plan — but the WeChat articles (中文) now drive consistent traffic from a completely different channel. The Chinese-language environmental workforce crisis article reached ~3,000 readers on WeChat within 48 hours. That’s not viral, but it’s real people who now know the brand.
The two audiences are distinct:
- English site: SEO-driven, global audience, long-form technical
- WeChat: Social sharing, China audience, shorter and more opinionated
What Didn’t Work
Pure SEO Play Content
Early on, I tried a few articles written primarily around keyword volume rather than genuine engineering insight. They rank. They get impressions. But their time-on-page is 40% lower and they don’t convert to return visitors.
Lesson: Write for the engineer who needs the answer, not for the search crawler. The crawler will follow.
Generic Industry News
A few “Industry Roundup” style posts got almost zero traction. There are better sources for daily battery news (Benchmark Minerals, Bloomberg NEF). Unless you’re adding a specific technical analysis that only you can provide, skip the news summary.
Theory Without Application
Articles that explain concepts without connecting them to real decisions engineers face got predictably low engagement. “What is NPSH?” is a Wikipedia article. “How I calculated NPSH for a pump that was cavitating for two years and what I found in the pipe” is a story engineers will read.
What’s Coming Next
Content Roadmap (Next 30 Days)
- Deeper technical series: Instead of one-off articles, start building multi-part series (e.g., “Battery Electrode Manufacturing: From Slurry to Finished Cell” — 8 parts)
- Tools, not just articles: The two engineering calculators (pipe pressure drop, NPSH) already get 3× more time-on-page than articles. More interactive tools coming.
- China Watch: Continuing the regulatory/policy analysis for battery and environmental industries in China. This is content that’s genuinely hard to get elsewhere in English.
- Digital products: The first batch of template packs and calculation spreadsheets are being tested. This is where the site starts generating revenue beyond ads.
Business Model Evolution
The original plan: SEO → traffic → ad revenue → digital products → SaaS.
Current status:
- ✅ SEO foundation (100 articles)
- ✅ Ad integration (Google AdSense application submitted)
- 🏗 Consulting page live (first inquiries coming in)
- 🏗 Digital products (templates, calculation packs) in development
- ⏳ SaaS (Q4 2026 target)
What I’d Tell Someone Starting a Technical Blog in 2026
- Start with 50 articles, not 5. The first 5 articles feel like an achievement. But Google doesn’t take a 5-article site seriously. 50 articles is the minimum for topical authority. 100 is where things start to compound.
- Write what you know — not what you can research. The articles that perform best are the ones where I didn’t need to open a reference book. The knowledge was already in my head from 13 years of doing the work.
- Numbers are your SEO. Every parameter, range, specification, and data point you include makes your article more findable. “Typical approach temperature for cooling towers” is a query someone types. Your article needs to answer it.
- AI helps, but doesn’t replace experience. I use AI for structure, editing, and translation. But the content — the specific parameters, the failure cases, the “this is what actually happens” — comes from experience. AI without experience produces generic content that engineers immediately recognize and ignore.
- Post consistently, not perfectly. Some of our most-read articles were written in 45 minutes. Some of the ones I spent 4 hours on got single-digit views. Ship content. Learn what works. Ship more of that.
Thank You
If you’ve read any of the articles on this site — thank you. If one of them helped you size a piece of equipment, understand a regulation, or avoid a mistake — that’s exactly why this exists.
Here’s to the next 100.
— PW, June 2026