> ## Documentation Index
> Fetch the complete documentation index at: https://docs.videntic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Blog generation

> Turn a ranked content gap into a draft in your CMS — ready for editorial review.

Blog generation is the last-mile of Videntic's workflow: take a content gap, hand it to Sira's Content Creator specialist, get back a draft, and publish it to Shopify or WordPress as an unpublished draft. Your team reviews, edits if needed, and clicks publish in the CMS.

## Why blog generation exists

Closing content gaps is the single highest-leverage thing you can do for AI Visibility. But writing good GEO-aware content takes time — and most teams don't have the bandwidth to turn ten ranked gaps into ten shipped posts a month.

Blog generation compresses that cycle. Every draft:

* Targets a specific prompt from your gap list.
* Follows GEO‑16 best practices by default (headings, microcontent, structured data, evidence).
* Adapts to your brand voice if you've uploaded brand documents.
* Lands in your CMS as a draft — never auto-publishes.

## The flow end-to-end

<Steps>
  <Step title="Pick a gap">
    From **Content gaps**, click the gap you want to close. You'll see the prompt, recommended content type, suggested angles, and competitor evidence.
  </Step>

  <Step title="Draft with Sira">
    Click **Draft with Sira** inside the gap. The Content Creator specialist writes a full draft against the brief — usually in 30–90 seconds for a standard blog post.
  </Step>

  <Step title="Review and edit">
    The draft opens in the Drafts editor. You can edit inline, ask Sira for revisions ("shorter", "add a comparison table", "more skeptical tone"), or regenerate entire sections.
  </Step>

  <Step title="Send to your CMS">
    When you're happy, click **Publish to \[Shopify/WordPress]**. The draft is pushed to your CMS as an *unpublished* draft with title, body, metadata, and schema markup pre-populated.
  </Step>

  <Step title="Final editorial in CMS">
    Your team opens the CMS, gives the draft a final pass, and hits publish. Videntic never publishes live posts on your behalf.
  </Step>
</Steps>

<Info>
  Drafts are never published automatically. Videntic only creates drafts inside your CMS — the publish button stays with your team.
</Info>

## What's in a generated draft

Every draft includes:

* **Title and slug** optimized for the target prompt.
* **Meta description** inside the CMS metadata field.
* **Structured body** with H2/H3 hierarchy, microcontent-friendly intros, and evidence-backed claims.
* **Schema.org markup** (Article, FAQ, HowTo, or Product as appropriate) generated and attached automatically.
* **Internal links** to relevant pages on your site, based on Videntic's content index.
* **Suggested featured image placement** — you supply the asset in your CMS.

## Revise a draft with Sira

From inside the Drafts editor, chat with Sira the same way you would anywhere else. Common revision requests:

* *Shorten the intro to three sentences.*
* *Add a comparison table with the competitors mentioned.*
* *Make the tone more skeptical — less salesy.*
* *Regenerate the conclusion with a stronger CTA.*
* *Rewrite this paragraph without the word "leverage".*

Sira edits inline — you don't lose work across the rest of the draft.

## Publish options per CMS

### Shopify

Requires a one-time connection from **Settings → Integrations → Shopify**. See [Shopify integration](/integrations/shopify) for the connection flow. Once connected, drafts push to your store's blog section as unpublished articles.

### WordPress

Requires your WordPress site URL and an application password. See [WordPress integration](/integrations/wordpress) for the setup. Drafts push as unpublished posts under the configured author.

## Plan availability

Blog generation is available on **Pro** and **Max** plans. On **Basic**, you can see gap briefs and angles but can't hand briefs to Sira for drafting or push to a CMS. See [Plans & billing](/billing/plans).

## Where drafts live

All drafts — whether sent to a CMS or not — are saved under **Content → Drafts** in the app. You can come back to a draft, edit it, regenerate sections, or delete it at any time. Sending to a CMS creates a draft there *and* keeps the Videntic draft for your records.

## Related

<CardGroup cols={2}>
  <Card title="Content gaps" icon="lightbulb" href="/features/content-gaps">
    The input end of the blog generation flow.
  </Card>

  <Card title="Sira AI" icon="sparkles" href="/features/sira-ai">
    The Content Creator specialist does the writing.
  </Card>

  <Card title="Shopify integration" icon="shop" href="/integrations/shopify">
    Connect your Shopify store to enable one-click drafts.
  </Card>

  <Card title="WordPress integration" icon="wordpress" href="/integrations/wordpress">
    Connect WordPress for the same flow.
  </Card>
</CardGroup>