まずは今日の試合映像を観て、両チームのプレイスタイルの違いを比較してみてください。" That's a concrete first step.
FAQ section: At the end of content_html, include
Frequently Asked Questions
with 3 distinct, genuinely useful Q&As using
for each question. But the rule says: "If content_html ends with an FAQ section, all H2s BEFORE the FAQ MUST be statement headings, NOT question headings." My H2s are already statement headings. Good. Also, "Only ONE FAQ block is allowed, at the very end." I'll make sure the FAQ is the very last thing in content_html.
The FAQ Q&As must be genuinely useful. I'll make them about the matchup merits, practical viewing tips, etc. Format:
質問
回答
ラプターズ 対 ニックスのメリット・効果を徹底検証:本当に役立つ?
. But the schema says faq_items has "question" and "answer". I'll output them as plain text in Japanese.
The FAQ heading rule: "Mirror these exact 3 Q&As in the 'faq_items' JSON field for FAQ Schema markup." I'll create faq_items array with 3 objects.
Now, meta_title: I need 28-32 full-width chars. I'll craft: "ラプターズ対ニックス:メリットと効果を徹底検証" Let's count: ラ(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) 30 chars. Good. But the meta_title should match bracket hook to intent. The rule: "meta_title: Match bracket hook to intent. Recommendation/Best: [Top Picks] or [Best Options]. Comparison: [Comparison]. Review: [Honest Review] or [Pros & Cons]. Explainer/News: [Explained]. How-to/Guide: [Step-by-Step Guide]. Length: 28-32 full-width chars for CJK." So for this informational guide, maybe [Explained] or just the title itself. But the meta_title value in JSON should be the title text, possibly with brackets? The example says "Match bracket hook to intent." I think the meta_title field should contain the meta title string, which may or may not include brackets. The rule about bracket hook seems to be about how to structure the title for CTR, but the length constraint is 28-32 full-width chars. I'll just put the title without extra brackets, as the title itself is 30 chars. Or I could add "【解説】" but that might add chars. I'll keep it as the title string, 30 chars. I'll write: "ラプターズ対ニックス:メリットと効果を徹底検証" 30 chars. That's fine.
meta_description: 70-85 full-width chars. I'll craft: "ラプターズとニックスの対戦メリットを徹底分析。戦術的な効果とファンへの価値、実用性を余すところなく解説し、バスケ観戦をより深く楽しむための視点をお届けします。" Let's count: I'll count properly later. I'll aim for ~80.
Slug: "raptors-vs-nicks-analysis" or "raptors-nicks-benefits". I'll use "raptors-vs-nicks-analysis". Count: r-a-p-t-o-r-s-(-v-s-)-n-i-c-k-s-(-a-n-a-l-y-s-i-s) = 22 chars. Under 45. Good.
Image strategy: exactly 2 visual specs.
1. Featured hero: Photo, alt text, file name.
2. In-body diagram/illustration: maybe an illustration of tactical comparison.
File names must be kebab-case <45 chars. Since keyword >25 chars, shorten to max 3 core words + -featured / -body. I'll do "raptors-vs-nicks-featured" (23 chars) and "raptors-nicks-tactics-body" (25 chars). Good. Alt text: clear, descriptive, no adult/sensational keywords. e.g., "ラプターズとニックスの対戦シーン" for featured, "バスケ tacticts comparison diagram" but in Japanese alt text? Alt text is usually in English for SEO, but the rule says "Alt text: Clear, descriptive, and strictly free of adult or sensational keywords." It doesn't specify language, but since content is Japanese, alt text could be Japanese or English. I'll use English descriptive alt text as is common for SEO, but must be clear and descriptive. I'll do: "Toronto Raptors vs New York Knicks game action" and "tactical comparison diagram of Raptors vs Knicks playing styles". But need to ensure no false promises. I'll keep it generic.
Now, let's assemble the JSON. I need to be very careful with JSON string escaping. content_html will be a string with HTML. I'll use single quotes for HTML attributes as instructed: "Use single quotes ' for HTML attributes." So in JSON, I'll have content_html: '
...
...' etc. But JSON values must be double-quoted strings. I'll escape double quotes inside, but use single quotes for HTML attributes. The instruction: "The value for 'content_html' MUST be a single string of valid HTML. Use single quotes ' for HTML attributes." This means within the HTML, I should use single quotes for attributes, e.g.,
. And in JSON, the whole content_html value will be enclosed in double quotes, but I need to ensure any inner double quotes are escaped or avoided. I'll use single quotes for all HTML attributes, and avoid double quotes in HTML. For
inside FAQ, I'll just use
Question
without attributes. For
, no attributes needed. For
if I had a table, but I'm using
, so no table wrapper needed.
Let's draft the content_html string carefully.
First, BLUF paragraph:
'
etc.
But need to ensure paragraphs are 2-3 sentences. I'll write each paragraph with exactly 3 sentences, or 2 sometimes.
Let's draft all sections in HTML.
I'll start building the content_html string.
Important: The FAQ section must be at the very end, with
Frequently Asked Questions
, then 3
questions and answers. But the rule says: "At the end of content_html, include an
Frequently Asked Questions
section with 3 distinct, genuinely useful Q&As (using
for each question)." It doesn't specify the format of the answer, but typically
answer
. I'll do
Question
Answer
. But need to ensure it's within the content_html string.
Also, "HEADING 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.
Now, let's write the content step by step, keeping track of word count and character count roughly.
I'll write in Japanese, using desu/masu form.
Let's begin.
-----------------------------------------------
I need to ensure the total content is 1000-1200 words, or 1800-2500 CJK characters. Japanese characters: each Japanese character (Kanji, Hiragana, Katakana) is 1 char. Spaces and punctuation also count. My draft needs to be substantial. Let's aim for around 2000 Japanese chars. I'll write fairly detailed sections.
Let's estimate: Each sentence ~20-30 chars. 3 sentences per paragraph. If I have ~20 paragraphs, that's ~600-800 chars. Need more. I'll write more paragraphs per section, maybe 3-4 paragraphs per section, each 2-3 sentences. 5 sections * 3 paragraphs * 3 sentences = 45 sentences. 45 * 25 avg = ~1125 chars. Plus BLUF, FAQ, etc. Might be around 1300-1500 chars. I need 1800-2500. So I need more content. I'll expand each section with more paragraphs, maybe 4-5 paragraphs per section, each 2-3 sentences. That'll increase chars.
Let's plan structure:
- BLUF: 3 sentences ~75 chars
- H2 1: maybe 4 paragraphs, each 3 sentences = 12 sentences ~300 chars
- H2 2: same ~300
- H2 3: same ~300
- H2 4: same ~300
- H2 5: same ~300
-
key takeaways: maybe 5 items, each short ~50 chars total ~250
- CTA: ~50 chars
- FAQ: 3 Q&As, each Q&A maybe 2-3 sentences Q and A ~100 chars each = 300
Total roughly 300*5 = 1500 + 75 + 250 + 300 = 2125 chars. Good, within 1800-2500.
I'll write accordingly.
Now, careful about the primary keyword frequency. I'll mention the exact keyword "ラプターズ 対 ニックスのメリット・効果を徹底検証:本当に役立つ?" exactly twice. I'll put it in BLUF and in section 5 maybe. I'll also use variations like