". So content_html includes the BLUF and H2s and FAQ.
I'll write content_html with BLUF paragraph, then H2s, then FAQ.
For keyword frequency: I'll mention the exact keyword "シカ完全攻略ガイド:初心者から上級者までの決定版" in the BLUF maybe, or in a sentence. Let's see: BLUF currently: "シカの生態や行動パターンを理解し、初心者から上級者まで段階的にスキルを高めるための決定版ガイドです。安全で倫理的な現場対応を基礎から解説し、実践的な知識を身につけることを目的としています。" That includes "決定版ガイド" but not the full keyword. I could add the full keyword there. Let's modify BLUF to include the exact keyword once: "シカ完全攻略ガイド:初心者から上級者までの決定版として、シカの生態や行動パターンを理解し、初心者から上級者まで段階的にスキルを高めるガイドです。安全で倫理的な現場対応を基礎から解説し、実践的な知識を身につけることを目的としています。" That includes the full keyword once. Then I might mention it once more later, maybe in the conclusion or a H2. But H2s are statement headings, I could have one H2 include the keyword? Maybe not, as headings are already set. I'll include the keyword once in BLUF, and perhaps once in the content later naturally. To be safe, I'll aim for 2 times total in content_html.
Let's draft BLUF with keyword:
"
"
That's 2 sentences, includes keyword once.
Now, I need to ensure total character count for content_html is within 1,800-2,500 CJK chars. Let's estimate later.
Now, table: I'll include a comparison table of tracking signs or something. Must wrap in div.table-responsive. I'll make a simple table of シカの痕跡 types.
Example table:
痕跡の種類
特徴
足跡
土や雪に残り、方向と大きさで推測可能
糞
食性に応じて形状が異なり、生息域の確認に役立つ
rubbed tree
樹皮に rubbed 痕が残り、領域表示のサイン
But need to ensure facts are accurate. I'll keep it generic and plausible.
Now, image strategy: exactly 2 visual specs.
1. featured: Photo, alt text, file name kebab-case <45 chars.
2. in-body: diagram/illustration, alt text, file name.
Let's define:
- Position: featured, image_type: Photo, alt_text: シカの足跡と森林の様子, file_name: sika-footprints-featured.webp (check length: sika-footprints-featured is 25 chars, + .webp = 31, under 45). ai_prompt: English prompt for image generation. I need to write a concise prompt.
- Position: in-body, image_type: Illustration, alt_text: シカの追跡ルートと地形の関係, file_name: sika-tracking-route-body.webp (length: sika-tracking-route-body is 23 chars). ai_prompt: something.
Ensure filenames are kebab-case, all lowercase. "sika-footprints-featured" is lowercase, good. "sika-tracking-route-body" also.
Now, meta_title: "シカ完全攻略ガイド:初心者から上級者までの決定版" (21 chars, within 28-32). I'll use that.
meta_description: 70-85 full-width chars. I'll craft: "シカの生態や追跡技術を初心者でも分かりやすく解説。基本から上級者の高度なテクニックまで網羅した決定版ガイドです。今すぐスキルを深めましょう。" Count chars: Let's count roughly. シ(1)カ(2)の(3)生(4)態(5)や(6)追(7)跡(8)技(9)術(10)を(11)初(12)心(13)者(14)でも(15)分(16)か(17)る(18)よ(19)う(20)に(21)解(22)説(23)。(24)基本(25)から(26)上(27)級(28)者(29)の(30)高(31)度(32)の(33)テ(34)ク(35)ニ(36)ク(37)まで(38)網(39)羅(40)し(41)た(42)決(43)定(44)版(45)ガ(46)イ(47)ド(48)。(49)今(50)すぐ(51)ス(52)キ(53)ル(54)を(55)深(56)め(57)ま(58)す(59)。(60) That's 60 chars. I need 70-85. I'll add more: "野外での経験を積みたい方に向けた実用的な内容です。" Let's add: "野外での経験を積みたい方に向けた実用的な内容です。" Count additional: 野(61)外(62)で(63)の(64)経(65)験(66)を(67)積(68)み(69)た(70)方(71)に(72)向(73)け(74)た(75)実(76)用(77)的(78)な(79)内(80)容(81)です(82)。(83) Now total 83 chars. Good within 70-85.
Slug: "sika-complete-guide" (16 chars). Good.
extracted_keywords: ["シカ完全攻略ガイド:初心者から上級者までの決定版", "シカ追跡ガイド"] or just primary and one LSI.
Now, faq_items: mirror the 3 Q&As.
Let's structure faq_items array:
[
{
"question": "シカの追跡に必要な基本装備は何ですか
シカ完全攻略ガイド:初心者から上級者までの決定版 guide overview