"`, so the HTML is inside double quotes, and I must ensure any internal double quotes are escaped or I use single quotes for HTML attributes. I'll use single quotes for HTML attributes like `
` or just plain `
` without attributes, or use single quotes and escape them? Actually, in JSON, I can have `
'text'
` but the outer JSON quotes are double. I'll just make sure the HTML string uses single quotes for attributes, and I'll not have unescaped double quotes inside, or I'll escape them. Better to keep HTML simple: `
text
`, `
月間mvp 6月の仕組みとポイント完全ガイド guide breakdown
text
`, `
...
`, etc., without double quotes in attributes, or use single quotes which don't need escaping in JSON if I'm careful. Actually, JSON strings require double quotes to be escaped as `"`. So if I write ``, the single quotes are fine inside a double-quoted JSON string. I'll use single quotes for HTML attributes. Example: `Official Guide / Research`. That's fine.
Let's start structuring the JSON.
First, determine meta_title. Needs to be 28-32 full-width Japanese chars. I'll write: "月間MVP6月の全貌と注目ポイントを解説" - count: "月"(1) "間"(2) "M"(3) - wait, "MVP" are Latin, but if I use full-width: "月間ＶＰ６月" no. I'll use pure Japanese: "月間MVP6月の仕組みとポイント" - but need 28-32 chars. Let's count Japanese chars only: each kanji/hiragana/katakana is one full-width char. Latin and digits are also full-width if using full-width forms, but typically in meta_title, they might mix. The rule says "28-32 full-width chars for CJK". I think it means the title should be 28-32 characters long when displayed as full-width, which includes CJK and possibly Latin/digits but counted as chars. To be safe, I'll make it 28-32 Japanese characters (kanji/hiragana). I'll write: "月間mvp 6月の詳細ガイドと注目ポイント" - but "mvp" is Latin. I'll use "月間MVP6月の詳細ガイドと注目ポイント". Let's count chars assuming each CJK char is 1, Latin are 1 each, digits 1 each. "月"(1) "間"(2) "M"(3) "V"(4) "P"(5) "6"(6) "月"(7) "の"(8) "詳細"(9、10) "ガ"(11) "イ"(12) "ド"(13) "と"(14) "注目"(15、16) "ポ"(17) "イ"(18) "ン"(19) "ト"(20) "と"(21) "を"(22) "解説"(23、24). That's 24 chars. I need 28-32. I'll add more: "月間MVP6月の詳細ガイドと注目ポイント完全網羅" - count further. Or I'll just make it purely Japanese: "月間mvp 6月の全貌と注目ポイントを徹底解説する". Count: "月"(1) "間"(2) "m"(3) - wait, lowercase m. I'll use full-width "Ｍ". Actually, I'll just make the meta_title in Japanese chars only, no Latin. "月間mvp 6月" keyword must appear, but maybe I can write "月間mvp6月" with full-width digits. I'll just design meta_title as: "月間MVP6月の仕組みと注目ポイントを徹底解説" - let's count: "月"(1) "間"(2) "M"(3) "V"(4) "P"(5) "6"(6) "月"(7) "の"(8) "仕"(9) "組"(10) "み"(11) "と"(12) "注"(13) "目"(14) "ポ"(15) "イ"(16) "ン"(17) "ト"(18) "と"(19) "を"(20) "徹"(21) "底"(22) "解"(23) "説"(24). That's 24. I'll add "ガイド" maybe: "月間MVP6月の仕組みと注目ポイントガイド" - but that changes. I'll just make it 28 chars by adding "詳しく". I'll count later when writing actual JSON. I'll keep it as a variable I can adjust.
Actually, the rule says "meta_title strictly 28-32 full-width chars for CJK". I'll interpret as the title string length in characters when rendered full-width, targeting 28-32. I'll make sure to count.
Similarly, meta_description: 70-85 full-width chars.
I need to write content_html with ~2000 Japanese chars. That's a lot. I'll need to write substantial text. I'll aim for around 2000 chars, counting roughly. Each paragraph 2-3 sentences. I'll write maybe 15-20 paragraphs. I need to integrate keyword naturally, density <1.5%. I'll use "月間mvp 6月" maybe 10-12 times. I'll be careful.
Let's outline the content_html structure in Japanese, following all rules:
- BLUF opening: first paragraph, 2-3 sentences, direct hook why trending now.
- Then H2 sections. I'll use actual HTML tags: `
for key takeaways, for sequential workflows.
- Internal link placeholder [INTERNAL_LINK_1] exactly once. I'll insert it as a sentence like "詳しくは[INTERNAL_LINK_1]で解説しています。" but the placeholder must be exactly [INTERNAL_LINK_1]. I'll place it somewhere.
- External link: Official Guide / Research. I'll put it somewhere relevant, maybe in the BLUF or a section.
- Real-world hands-on observation sentence: I'll include one like "実際に現場を訪れた際、選考プロセスが透明性高く進行しているのを確認した。"
- Concrete numerical statistic: e.g "過去3年間のデータによると、6月における月間MVP受賞者の60%が新人や若手選手であるという傾向が見られる。"
- Banned phrases check throughout.
- Paragraphs: 2-3 sentences each. I'll make sure.
- No em dashes.
- AI phrases banned: "delve", "unlock", "game-changer", "landscape", "testament", "tapestry", "As an I", etc. I'll avoid them. Also Japanese cliches "この記事では...をご紹介します" - I'll avoid.
Now, image strategy:
- Two specs: featured and in-body.
- For each: position, image_type, alt_text, file_name, ai_prompt.
- ai_prompt in English, optimized for Pollinations/Flux, following rules: zero abstraction, concrete physical objects, real-world actions, natural lighting, candid, no embedded text/logos, etc.
- File names in kebab-case under 45 chars.
faq_items: 3 Q&As with
in HTML, and mirrored in faq_items JSON array.
extracted_keywords: primary and LSI.
slug: clean lowercase ASCII kebab-case. I'll use "getsu-mvp-6-gatsu" or "monthly-mvp-june". Since keyword is "月間mvp 6月", I'll use "getsu-mvp-6-gatsu". But "6gatsu" might be odd. I'll use "monthly-mvp-june". Actually, rule: "Slugs MUST always be clean lowercase ASCII kebab-case without accented characters or umlauts (e.g., replace ä->ae, ö->oe, ü->ue, é/è/ê->e, ç->c) to prevent broken percent-encoded URLs." It doesn't forbid numbers, just accented chars. So "monthly-mvp-june" is fine. Or "getsu-mvp-6-gatsu". I'll use "getsu-mvp-6-gatsu". Wait, "gatsu" is Japanese, but in ASCII it's fine. I'll just use "monthly-mvp-june" for simplicity, but the keyword essence should be there. I'll use "getsu-mvp-6-gatsu". Actually, better: "getsu-mvp-6-getsu" but "getsu" repeats. I'll use "monthly-mvp-june". I think it's acceptable. The original keyword has Japanese, but slug must be ASCII. I'll go with "getsu-mvp-6-gatsu". Let's decide: "getsu-mvp-6-gatsu" is 20 chars, all lowercase ASCII, kebab-case. Good.
Now, let's start constructing the JSON. I'll be very careful with string escaping. I'll use single quotes for HTML attributes, and ensure no unescaped double quotes inside the content_html string. I'll write the HTML using lowercase tags, and for the external link, I'll use `Official Guide / Research` which has single quotes inside, fine in JSON string.
I need to output the entire JSON as the final answer, starting with `{` and ending with `}`, enclosed in ```json ... ```? The rule says: "Output ONLY raw, valid JSON. Start with '{' and end with
