Write SEO and AEO-optimized long-form blog posts

Blog Writer Skill produces a long-form blog post or article for SEO and AEO (answer engine optimization) purposes. It activates when a user asks to write a blog post, create an article, generate blog content, write a long-form post about a topic, or use the blog writer. The skill writes to the dominant search intent and not merely the keyword. The article should solve a recognizable problem and make the next product action clear without turning an informational article into an unsupported sales pitch.

Use it when creating or revising a long-form article meant to capture a specific search intent and guide readers to a relevant next step. It fits inside a content pipeline: it receives output from the seo-aeo-content-cluster skill and feeds output to the seo-aeo-content-quality-auditor and seo-aeo-internal-linking skills.

The skill cannot guarantee rankings or traffic, since search performance depends on the actual site, competition, content quality and indexing. The word count is bounded, with a minimum of 800, a maximum of 3000 and a default of 1500, so it is not meant for very short posts or book-length content.

The input is a JSON object with these fields: topic, primary_keyword, secondary_keywords, target_audience, tone (informational, conversational, authoritative or persuasive), word_count, an optional cluster_context taken from the content cluster output, internal_link_targets, an optional product_cta with its destination, optional search_intent_evidence such as observed SERP or API evidence, and optional distribution_platforms.

The output always follows one exact section order:

1. An H1 title optimized for the primary keyword.
2. A TL;DR block of two to three sentences that directly answers the core question, written to be lifted by AI engines.
3. An introduction with a hook, a clear statement of the problem in the first two lines, and the primary keyword within the first 100 words.
4. A What Is section whose very first line is a single clean, extractable definition sentence, followed by two or three paragraphs of context.
5. A Why it matters or core problem section using bullets or a numbered list.
6. A How it works main body, the deepest section, with H3 subheadings and at least one comparison table if two or more things are compared.
7. Optional Practical Steps, as a numbered list with at most two sentences per step, and optional Common Mistakes as a short bullet list.
8. A Frequently Asked Questions section.
9. A conclusion that restates the TL;DR answer in new words with one call to action sentence.
10. Internal links, external links, a product CTA and external distribution notes covering the platform, adaptation angle, canonical-link decision and backlink target.

The AEO requirements are strict: a TL;DR immediately after the H1, a definition sentence first in the What Is section, a comparison table when comparing options, exactly 5 FAQ entries with direct answers of two to three sentences, lists in at least two sections, the primary keyword in the H1, first 100 words, at least one H2 and the meta description, a product CTA when the article supports conversion, and internal links to a foundational page and the product where relevant.

The SEO requirements: exactly one H1 with the primary keyword, 4 to 6 H2s without keyword stuffing, H3s only inside H2 sections, word count within the input range, natural keyword use with no forced density percentage, and no duplicate headings.

The process runs in ten steps: read cluster context, review search intent evidence, write the TL;DR first, build the heading skeleton, write the definition, write the FAQ from long-tail and secondary keywords, insert internal links at natural transitions, add external sources only when authoritative and relevant, check keyword placement, and finish with an AEO, conversion and claim-verification pass.

It connects to the content cluster, content quality auditor and internal linking skills in the same SEO and AEO family.

Content marketers, SEO specialists and founders who want structured, answer-engine-friendly articles that follow a consistent template.