..."` and the string content will use single quotes. I must ensure no unescaped double quotes inside the HTML string, or I'll escape them with ". Better to just use single quotes inside and keep the JSON double-quoted string simple. I'll be careful. Let's outline the content_html structure: - BLUF paragraph (2-3 sentences) - H2: "Core Rules Framework" (statement heading) - Content paragraph(s) - H2: "Practical Fan Etiquette" - Content with table maybe - H2: "Preparation Checklist" - Content - FAQ section:

Frequently Asked Questions

- 3

questions with answers - Editorial disclaimer div Wait, rule: "If content_html ends with an FAQ section, all H2s BEFORE the FAQ MUST be statement headings, NOT question headings." My H2s are statement headings, good. Also: "FAQ Section (Single FAQ Block Only): At the end of content_html, include an
コリチアンズとボタフォゴの基本ルールと知っておくべきマナー入門ガイド guide overview
コリチアンズとボタフォゴの基本ルールと知っておくべきマナー入門ガイド guide overview

Frequently Asked Questions

section with 3 distinct, genuinely useful Q&As (using

for each question). Mirror these exact 3 Q&As in the "faq_items" JSON field for FAQ Schema markup." So the FAQ section has

Frequently Asked Questions

, then three

Question?

followed by

Answer.

コリチアンズとボタフォゴの基本ルールと知っておくべきマナー入門ガイド
コリチアンズとボタフォゴの基本ルールと知っておくべきマナー入門ガイド
. The H2s before that (the main section H2s) must be statement headings, not questions. I'll ensure my main H2s are like "1. Core Rules Framework" but wait, I can't use numbered H2s if they imply a listicle count unless the count matches. The rule says: "If the title, slug, or image filename promises a specific listicle count (e.g. "10 Tips", "7 Steps", "5 Mistakes"), the content_html MUST literally contain that exact number of distinct, numbered actionable items (using sequential
    or numbered

    headings)." I'm not using a listicle count in title. I'll use thematic H2s without numbers, or if I number, I need to match. Safer to use unnumbered statement H2s. I'll use H2s like "Core Rules Framework", "Practical Fan Etiquette", "Preparation Checklist". These are statement-style. Let's draft the Japanese content mentally, ensuring word count and constraints. **Keyword check**: "corinthians x botafogoの基本的なルールと知っておくべきマナー". I need to mention this exact phrase 2-3 times naturally. I'll put it in the first paragraph, maybe in an H2, and once more in body. **BLUF opening**: "コリチアンズとボタフォゴの試合やイベントに参加する際、知っておくべき基本ルールとマナーを押さえておくことは非常に重要です。このガイドでは、スタジアムでの振る舞いからチケット購入まで、初心者の方がまず知っておくべきポイントをわかりやすく解説します。" That's 2 sentences? Actually 2 sentences. Good. **H2 sections**: I'll do 4 H2s maybe, or 5. Let's plan 4 main sections plus FAQ. Let's start writing. I'll be very careful with character counts and constraints. **Important**: The article must be 1000+ words in Japanese, which is roughly 1800-2500 characters. I need to generate substantial text. I'll write paragraphs of 2-3 sentences each, but accumulate enough paragraphs to reach length. Let's outline the structure in JSON schema, then fill content. I need to output: ```json { "meta_title": "...