ClawHub

SEO Blog Writer — E-E-A-T Content System for SaaS & Startups

🇺🇸 SEO Blog Writer — Write blog posts that rank on Google AND get cited by AI search. E-E-A-T content system for SaaS & startups. QAE writing pattern (Question→Answer→Evidence), founder voice injection, Key Stats tables, FAQ Schema generation, comparison article framework, and cross-posting with canonical URLs. 🇨🇳 SEO 博客写手 — 写出同时在 Google 排名和被 AI 搜索引用的文章。E-E-A-T 内容系统：QAE 写作模式（问题→回答→证据）、创始人声音注入、关键数据表格、FAQ Schema 生成、竞品对比文章框架。 🇯🇵 SEOブログライター — GoogleランキングとAI検索引用の両方に最適化されたブログ記事を作成。E-E-A-Tコンテンツシステム：QAEライティングパターン、ファウンダーボイス、キーデータテーブル、FAQスキーマ生成。 🇰🇷 SEO 블로그 라이터 — 구글 랭킹과 AI 검색 인용 모두에 최적화된 블로그 글 작성. E-E-A-T 콘텐츠 시스템: QAE 글쓰기 패턴, 창업자 목소리, 핵심 데이터 테이블, FAQ 스키마 생성. Triggers: "write blog post" | "SEO article" | "content writing" | "blog SEO" | "E-E-A-T content" | "SEO copywriting" | "SaaS blog" | "content marketing" | "write article" | "blog optimization" | "写博客" | "SEO 文章" | "内容写作"

Audits

Pass
ClawScanPass

Agentic behavior and permission review.

Static analysisPass

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install gingiris-blog-writer

SEO Blog Writer — E-E-A-T Content System

Write blog posts that rank on Google AND get cited by ChatGPT, Perplexity, and Claude.

Core Writing System: QAE Pattern

Every section follows the Question → Answer → Evidence pattern:

## [H2: Natural language question people actually search]

[Direct answer in 1-2 sentences — this is what AI engines extract]

[Evidence: data, case study, personal experience, expert quote]

[Key Stats table or comparison matrix if applicable]

Why QAE Works

  1. For Google: H2 matches search queries → featured snippet potential
  2. For AI Search: Direct answer paragraph → high citation probability
  3. For Readers: Clear structure → lower bounce rate → ranking signal

Article Templates

Template 1: Comparison Post ("[X] vs [Y]")

---
title: "[Product A] vs [Product B]: [Year] Honest Comparison"
description: "Real [use case] comparison between [A] and [B]. I tested both for [duration]. Here's what actually matters."
schema: FAQPage, Article
---

## TL;DR — Which One Should You Pick?
[2-sentence direct recommendation based on use case]

## Quick Comparison Table
| Feature | Product A | Product B | Winner |
|---------|-----------|-----------|--------|
| [criteria 1] | ... | ... | ... |

## My Testing Setup
[Establish E-E-A-T: how you tested, your credentials]

## Deep Dive: [Criterion 1]
[QAE pattern for each evaluation criterion]

## FAQ
[3-5 questions with concise answers → FAQ Schema]

Template 2: How-To Guide

---
title: "How to [Achieve X] in [Year] ([N] Steps)"
description: "[Result] in [timeframe]. Step-by-step from [start state] to [end state]."
schema: HowTo, Article, FAQPage
---

## The Short Answer
[Direct answer: what to do in 1-2 sentences]

## Key Stats
| Metric | Value | Source |
|--------|-------|--------|
| [relevant stat] | [number] | [source] |

## Step 1: [Action verb + specific outcome]
[QAE pattern]

## Common Mistakes
[Numbered list — AI loves extracting these]

## FAQ
[Schema-ready Q&A pairs]

Template 3: "[N] Best [Category] for [Use Case]"

---
title: "[N] Best [Tools/Methods] for [Specific Use Case] ([Year])"
schema: Article, ItemList, FAQPage
---

## Our Top Picks at a Glance
| Rank | Tool | Best For | Price |
|------|------|----------|-------|

## How We Evaluated
[Methodology — builds E-E-A-T]

## 1. [Tool Name] — Best for [specific use case]
### Key Stats
| Metric | Value |
[QAE pattern per item]

## FAQ

Founder Voice Injection Rules

To pass E-E-A-T signals and avoid "AI slop" detection:

  1. Use first person: "I tested", "We found", "In my experience"
  2. Include specific numbers: "After 3 months, our traffic grew 47%"
  3. Admit limitations: "This didn't work for us because..."
  4. Reference timeline: "Back in Q3 2025, when we first tried..."
  5. Name real tools you used: "We tracked this in Ahrefs/Mixpanel/..."
  6. Show behind-the-scenes: Screenshots, dashboards, actual emails

SEO + GEO Optimization Checklist

Before publishing, verify:

  • Title contains primary keyword naturally
  • First paragraph directly answers the search intent
  • At least one Key Stats table per article
  • FAQ section with 3-5 questions (for FAQ Schema)
  • Comparison table if the topic involves alternatives
  • Author byline with real credentials and links
  • Internal links to 2-3 related articles
  • External links to 2-3 authoritative sources
  • Publication date visible
  • Meta description includes CTA and keyword

Cross-Posting Strategy

After publishing on your main blog:

  1. Dev.to — Republish with canonical_url pointing to original
  2. Hashnode — Same, with canonical
  3. Medium — Import with canonical (Settings → Import)
  4. LinkedIn Article — Shorter version with link back
  5. Twitter/X Thread — Key takeaways as a thread

⚠️ Always set canonical URL to your original post to avoid duplicate content penalties.

Related Skills