惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

美团技术团队
T
The Blog of Author Tim Ferriss
C
Check Point Blog
博客园_首页
J
Java Code Geeks
云风的 BLOG
云风的 BLOG
L
LangChain Blog
小众软件
小众软件
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
Vercel News
Vercel News
博客园 - Franky
V
V2EX
IT之家
IT之家
U
Unit 42
N
Netflix TechBlog - Medium
腾讯CDC
Apple Machine Learning Research
Apple Machine Learning Research
Microsoft Azure Blog
Microsoft Azure Blog
罗磊的独立博客
博客园 - 叶小钗
H
Help Net Security
V
Visual Studio Blog
GbyAI
GbyAI

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How I Built a Review Site with 800+ Articles Using AI
武乐丹 · 2026-05-23 · via DEV Community

武乐丹

How I Built a Review Site with 800+ Articles Using AI

The stack, the workflow, and what actually worked


A few months ago, I wanted to build a review site for Chinese consumer brands — products like GaN chargers, USB-C hubs, smart home devices, and laptops that are popular in Asia but don't get much coverage in English-language tech blogs.

The goal was simple: produce useful, data-driven reviews at scale. No clickbait, no affiliate-first garbage. Just honest comparisons with real specs and real user feedback.

Here's how I built it, what the workflow looks like, and what I learned along the way.


1. The Stack

The site runs on a minimal stack:

  • Next.js (static export) — fast builds, great DX
  • Decap CMS — Git-based CMS so editors don't need a database
  • Vercel — free hosting, instant rollbacks
  • GitHub — content and code in one repo

No backend to manage. Every article is a Markdown file in the repo. Decap CMS gives the content team a nice UI on top, but the source of truth is Git.

2. Why AI for Content?

I didn't want to build yet another AI-generated content mill. The approach was different:

  • Research first: AI gathers product specs, pricing, and real user reviews from multiple sources
  • Human structure: Each article follows a template (overview → specs → performance → real user feedback → verdict)
  • Data verification: Pricing and specs are checked against official sources before publishing
  • Images are real: No AI-generated product images. Every photo comes from official brand sites or verified listings

The AI handles the heavy lifting — research, formatting, translation of Chinese reviews — while humans control the quality bar.

3. The Content Pipeline

Here's the actual workflow for each article:

  1. Product selection — Identify trending products on JD.com, Taobao, and Tmall
  2. Spec collection — Pull official specs from brand sites and verified product pages
  3. User review aggregation — Collect real buyer feedback (good and bad) from verified purchasers
  4. Article generation — Structure everything into a consistent, readable format
  5. Review pass — Check all specs against official sources, verify pricing, remove any hallucinated claims
  6. Image sourcing — Download official product images from brand sites (no guessing CDN URLs)
  7. Publish — Commit to Git, Vercel deploys automatically

4. What Actually Worked

✓ Real data beats SEO tricks

The articles that perform best aren't the ones with keyword-stuffed titles. They're the ones with actual benchmarks and real user experiences. A USB-C cable buying guide with measured charging speeds and compatibility testing gets more engagement than any generic listicle.

✓ Consistency matters more than perfection

Publishing 3-5 articles daily (focused, well-researched ones) built organic traffic faster than trying to write one perfect article per week. Search engines reward freshness.

✓ User reviews are gold

Chinese e-commerce platforms have incredibly detailed review systems, often with photos. Translating and aggregating authentic user feedback gives articles depth that pure spec sheets can't match.

5. What Didn't Work

✗ Pure AI generation

Early tests with full AI generation produced articles that looked good but lacked depth. They'd say "great product" without explaining why. The fix was adding real user quotes and verified test data.

✗ Guessing CDN image URLs

We tried building an automated image pipeline using pattern-matched CDN URLs. It failed constantly. The solution was going back to sourcing images manually from official brand sites.

✗ Over-optimizing for search

The first batch of articles tried too hard to match search patterns. They read like SEO sludge. The fix was writing for humans first and treating keywords as a secondary concern.

6. Numbers After 800 Articles

  • 800+ published articles across 19 categories
  • 100% real product images (every article has at least one genuine photo)
  • Organic traffic growing steadily since launch
  • AdSense approved and running

Not explosive growth, but steady, sustainable progress.

7. Key Takeaways

  1. AI is a multiplier, not a replacement — The best results come from AI handling research and structure while humans handle verification
  2. Content quality is a flywheel — Good content attracts better readers, which attracts better engagement, which signals quality to search engines
  3. Don't skip the boring parts — Checking specs against official sources, sourcing real images, and verifying user reviews takes time but builds trust
  4. Ship fast, iterate faster — Get the first 50 articles up, then improve based on what the data tells you

If you're building something similar or have questions about the workflow, drop a comment below. Happy to share more details about specific parts of the pipeline.