> For the complete documentation index, see [llms.txt](https://suigar.gitbook.io/suigar-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://suigar.gitbook.io/suigar-docs/seo/blog-generation.md).

# AI blog generation

Last reviewed: 2026-05-28

This is the rulebook for generating Suigar blog content with AI. It should become stricter over time as we learn what works, what fails, and what search data rewards.

## Production Loop

1. Plan topic from product priority, user/search intent, audience, and internal-link opportunity.
2. Generate a brief using the topic brief template.
3. Draft an outline and metadata before writing full prose.
4. Draft with AI against the active constraint registry.
5. Run an AI critic pass for helpfulness, originality, claims, metadata, internal links, and compliance.
6. Human-review high-risk claims, gambling/financial wording, product state, and external references.
7. Insert or update the DB post only after required fields and ledgers are complete.
8. Call the secured blog revalidation endpoint with the post slug, or document the 60-second ISR wait before monitoring indexation.
9. Monitor Search Console, analytics, Core Web Vitals, crawl/indexing, and user behavior.
10. Feed learnings back into this file, `status.md`, and `optimization-log.md`.

## Topic Brief Template

```md
# Topic Brief

- Working title:
- Search intent:
- Primary audience:
- Reader goal:
- Suigar angle:
- Product/business goal:
- Funnel stage: awareness | consideration | activation | retention | partner
- Target route:
- Related product pages:
- Related docs:
- Required facts:
- Claims requiring verification:
- Risks:
- Success signal:
- Refresh trigger:
```

## Article Outline Template

```md
# Outline

- H1:
- One-sentence promise:
- Intro job:
- Section 1:
- Section 2:
- Section 3:
- Section 4:
- Product/docs bridge:
- Reader next step:
- FAQ candidates, if genuinely useful:
- What not to cover:
```

## Metadata Template

```md
# Metadata

- Slug:
- SEO title:
- Meta description:
- Open Graph title:
- Open Graph description:
- Cover image:
- Cover image alt:
- Tags:
- Author:
- Published date:
- Canonical URL:
- Internal links:
- External references:
```

## Source And Claim Ledger

Use this for every generated or assisted post.

```md
# Source And Claim Ledger

| Claim | Type                 | Source | Visible In Post | Review Status           |
| ----- | -------------------- | ------ | --------------- | ----------------------- |
|       | product              |        | yes/no          | pending/verified/remove |
|       | on-chain/mechanics   |        | yes/no          | pending/verified/remove |
|       | external             |        | yes/no          | pending/verified/remove |
|       | compliance-sensitive |        | yes/no          | pending/verified/remove |
```

Claim types:

* `product`: Suigar feature, UI, route, game, reward, or policy.
* `on-chain/mechanics`: settlement, odds, receipts, Sui mechanics, contract behavior.
* `external`: Sui ecosystem, partner, competitor, search trend, or third-party fact.
* `compliance-sensitive`: gambling, financial, reward, payout, eligibility, jurisdiction, or risk wording.

## Internal Link Checklist

* Link to a relevant Suigar product page when the reader can act after reading.
* Link to docs when mechanics, SDK, SweetHouse, rewards, or integrations need durable detail.
* Link to related blog posts when they continue the same narrative or topic cluster.
* Use descriptive anchor text; avoid "click here".
* Do not add links solely to manipulate rankings.
* Avoid linking to testnet URLs from production posts unless the post is specifically about testnet.

## AI Critique Checklist

Run this after drafting:

```md
# AI SEO Critique

- Does the post satisfy a real audience intent?
- What original Suigar-specific value does it add?
- Which claims need verification or removal?
- Is any wording legally, financially, or gambling-risky?
- Is the title specific without keyword stuffing?
- Is the meta description useful and accurate?
- Are headings natural and scan-friendly?
- Are internal links relevant and crawlable?
- Does the post duplicate another Suigar page?
- Is any section filler, generic, or trend-chasing?
- Does the reader know the next useful action?
- What constraint should be added to improve future posts?
```

## Update Policy

* Update a post when product mechanics, UI, URLs, rewards, eligibility, or facts materially change.
* Add an editor note or update date only when the content changed materially.
* Do not change dates just to make content look fresh.
* Prune or consolidate posts that become thin, duplicated, outdated, or unable to satisfy a reader goal.
* Record material updates in `optimization-log.md` when they affect search intent, indexability, canonical scope, or major claims.

## Constraint Registry

AI generation must read these constraints before drafting. Add new constraints as specific, testable rules.

| ID       | Constraint                                                                                                          | Reason                                        | Added      |
| -------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------- |
| BLOG-001 | Every post needs a named audience and search/user intent before drafting.                                           | Prevents generic keyword articles.            | 2026-05-17 |
| BLOG-002 | Every post must include a Suigar-specific angle that is not available from a generic casino/Sui article.            | Protects originality and helpfulness.         | 2026-05-17 |
| BLOG-003 | Do not make guaranteed-return, risk-free, or profit-assurance claims.                                               | Avoids unsupported gambling/financial claims. | 2026-05-17 |
| BLOG-004 | Do not publish trend summaries unless Suigar has direct product, ecosystem, data, or user guidance to add.          | Prevents trend-chasing content.               | 2026-05-17 |
| BLOG-005 | Do not target a word count. Use the length required to satisfy the reader goal.                                     | Aligns with people-first content guidance.    | 2026-05-17 |
| BLOG-006 | Claims about odds, payouts, settlement, rewards, eligibility, or chain behavior require source-ledger verification. | Reduces accuracy and compliance risk.         | 2026-05-17 |
| BLOG-007 | Intros must not reuse the same "in the fast-moving world of..." style framing.                                      | Prevents repeated AI patterning.              | 2026-05-17 |
| BLOG-008 | Production posts should not link readers to testnet unless testnet is the topic.                                    | Protects canonical production intent.         | 2026-05-17 |
| BLOG-009 | Metadata must describe the actual visible post, not a broader keyword target.                                       | Avoids misleading snippets.                   | 2026-05-17 |
| BLOG-010 | A generated post is not complete until it has a critique result and at least one next-step/internal-link decision.  | Forces review and funnel integration.         | 2026-05-17 |

## Anti-Patterns

* Mass low-value AI posts.
* Trend-chasing without Suigar relevance.
* Fake freshness.
* Unsupported gambling, payout, reward, legal, or financial claims.
* Duplicated intros, titles, conclusions, or section patterns.
* Word-count-driven filler.
* Search-only pages that would disappoint a direct reader.
* Metadata that promises more than the article delivers.
* Thin posts that paraphrase docs without adding context.
* Publishing in the DB and forgetting the secured revalidation call when immediate discovery matters.