Content best practices

Every case/news page must make provenance obvious: author-confirmed, editor-reviewed public compilation, AI-assisted cross-check, or editorial original.

Always attach primary source URLs when the page synthesizes someone else’s disclosure. Do not imply hands-on team replication unless a replication log exists.

Prefer problem/solution titles (e.g. “Claude Code billing rules explained”, “Cursor .cursorrules setup guide”) over social vanity (“solo founder hits $30K MRR”).

Revenue figures belong in metric bands and body with “publicly disclosed” wording—not as the sole SEO headline.

Lead with source quality before performance claims. If metrics are estimated, label ranges and assumptions.

Prefer verifiable references (public posts, changelogs, filings) over second-hand summaries.

Every tutorial should answer: who this is for, prerequisites, expected output, and failure conditions.

Open with TL;DR / citable facts; use tables, steps, and FAQ for GEO quotability.

Never ship English-only bodies on /zh. EN-primary rows must include i18n.zh (title + body_markdown + seo_*). Empty EN locales stay noindex.

Free content must still provide standalone value. Paid sections deepen execution detail, not hide core context.

Keep CTA wording soft on content pages; hard sell belongs on /pricing.

Disclose affiliate relationships where links may create financial incentives.

Do not present historical revenue as guarantees.

Before publish: bilingual i18n, SEO fields, source_label/url or source_platform, tags/tools_used, provenance quality, mobile layout.

After publish: verify /zh and /en robots, canonical, hreflang, and public API title_zh when primary is EN.