SEO Blog Writer

Problem: content for both search and citation

Many technical posts are readable but weak in structure and evidence, making them hard to earn Google featured snippets and easy for ChatGPT, Perplexity, or Claude to ignore. gingiris-blog-writer turns article writing into a repeatable format: titles align with search intent, the first paragraph answers directly, each section carries citable evidence, and the page includes FAQ, comparison tables, and author signals.

Core workflow

• QAE structure: each section follows Question → Answer → Evidence. H2 tags target the query, the answer paragraph serves direct citation, and the evidence paragraph strengthens trust and rankability.
• Article templates: includes [X] vs [Y] comparisons, How-To guides, and [N] Best [Category] for [Use Case] listicles, suitable for tool selection, tutorials, and alternatives.
• Founder Voice rules: requires first-person phrasing, concrete numbers, limitations, timelines, named tools, and behind-the-scenes screenshots to reduce generic “AI slop.”
• SEO/GEO checklist: verifies keyword title, first-paragraph answer, Key Stats table, FAQ, comparison table, author byline, internal/external links, date, and meta description.
• Cross-posting: republishes to Dev.to, Hashnode, Medium, LinkedIn, and X, with canonical_url pointing to the original post to reduce duplicate-content risk.

Boundaries

It is closer to a writing and publishing checklist system than a full SEO/GEO audit, keyword mining tool, or live data crawler. If you need AI search visibility analysis, pair it with the referenced gingiris-geo-audit methodology. It fits independent blogs, developer documentation, and SaaS content teams, but is not intended for short copy, news releases, or social-only snippets.