温度 時間 油汚れ 除去
..."` where the HTML inside uses `'` for attributes. I need to make sure the HTML doesn't contain unescaped `"` that break JSON, or if it does, I escape them. But I can just avoid `"` in HTML by using `'` everywhere, including for tags? No, HTML tags themselves don't have quotes around tag names, but attributes do. I'll use `'` for all attributes. Example: `
...
`. That's valid HTML. And in JSON, it'll be `"
...
"` which is fine because the `'` won't break JSON.
- I need to produce exactly the JSON structure specified.
- The content must be in Japanese, but the JSON keys are in English. The `content_html` will contain Japanese text inside HTML tags.
- I need to ensure the Japanese text is natural, no banned phrases, paragraph length 2-3 sentences, etc.
- I need to include specific sections: BLUF, Why it's gaining attention, How it works, Opportunities and risks, Common misconceptions, Who it's relevant for, Soft CTA.
- FAQ section at the end with 3 Q&As, and also `faq_items` array.
- Image strategy with exactly 2 specs: featured and in-body.
- AI prompt rules for Pollinations AI / Flux.
- Table, ol, ul, internal link placeholder `[INTERNAL_LINK_1]` exactly once, external link `Official Guide / Research` exactly once.
- H1 title and meta title constraints: max 28-32 full-width chars for CJK. Primary keyword is "温度 時間 油汚れ 除去" which is 12 chars? Actually: 温度 (2) 時間 (2) 油汚れ (3) 除去 (2) total 9 full-width chars? Wait, each kanji/katakana/hiragana is one char. So "温度 時間 油汚れ 除去" has spaces? In Japanese, spaces are not typical, but the keyword is given with spaces. For CJK char limit, I need to count characters excluding spaces? The prompt says "28-32 full-width chars for CJK". The keyword "温度 時間 油汚れ 除去" if removed spaces becomes "温度時間油汚れ除去" which is 9 chars. I need to make an H1/meta_title that includes this keyword and is within 28-32 chars. I can add more words to reach 28-32. E.g., "温度と時間での油汚れ除去ガイド" - let's count: 温度(1) と(1) 時間(1) で(1) 油汚れ(3) 除去(1) ガイド(2) total? Actually, in full-width chars, each Japanese character counts as 1. Latin/numbers count as 1 each usually, but the prompt says "28-32 full-width chars for CJK". I'll assume Japanese characters count as full-width. I'll make the H1 something like "温度と時間での油汚れ除去完全ガイド" - count: 温(1) 度(1) と(1) 時間(1) で(1) 油(1) 汚(1) れ(1) 除(1) 去(1) 完全(1) ガイド(2? actually ガイド is 4 chars: ガ, イ, ド, but often counted as 4). Let's count properly: 温(1) 度(2) と(3) 時間(4で) で(5) 油(6) 汚(7) れ(8) 除(9) 去(10) 完全(11,12) ガ(13) イ(14) ド(15). That's 15 chars. I need 28-32. I can add more descriptive words: "温度と時間の油汚れ除去に関する完全ガイドと実践的ステップ" - this might get long. I'll aim for exactly 28-32. Let's count later. The meta_title must be max 60 chars for Latin, but for CJK it's 28-32. The `h1_title` should be concise and click-worthy, max 28-32 full-width chars. I'll make sure.
- Primary keyword density <1.5%. I need to use the keyword naturally. I'll use it in H1, first paragraph, maybe one more time, but keep density low. The keyword is "温度 時間 油汚れ 除去" - with spaces. In Japanese text, I might write it as a phrase or separate. I need to integrate naturally. I'll use it as "温度と時間の油汚れ除去" or similar. I need to be careful about density. I'll track manually.
- I need to include 1 real-world hands-on experience sentence.
- At least 1 concrete numerical statistic/percentage benchmark with context.
- Actionable step-by-step guidance.
- At least 1 comparison/data
.
- Use for sequential workflows and
for key takeaways.
- Insert raw plain `[INTERNAL_LINK_1]` placeholder exactly ONCE in the body text.
- Insert exactly 1 authoritative external reference link: `Official Guide / Research`.
- Heading limits: Strictly create 5-6 main H2 sections for the article body (excluding FAQ). Use H3 for sub-points.
- FAQ section at the end of content_html with
Frequently Asked Questions
and 3
Q&As. Mirror these exact 3 Q&As in the `faq_items` JSON field.
- Visual strategy: exactly 2 visual specs (featured hero, in-body diagram/infographic). AI prompts in English, optimized for Pollinations AI / Flux. Rules: zero abstraction, style anchor, text restrictions, context lock. File names in kebab-case under 45 chars.
- Language purity: 100% pure Japanese. CJK char limits 1,800-2,500 chars. Clean ASCII slug.
This is extremely detailed and constrained. I need to produce valid JSON with all these fields populated correctly. The main challenge is ensuring the Japanese content meets all constraints while the JSON structure is valid.
Let's start planning the content structure in Japanese, then wrap it in JSON.
First, outline the article in Japanese, respecting paragraph limits (2-3 sentences each), banned phrases avoided, etc.
Structure:
- BLUF opening (first paragraph): direct 2-3 sentence hook about why temperature/time grease removal is trending now.
- H2 sections (5-6 total):
1. Why it is gaining attention/trending in Japanese
2. How it works (Beginner-friendly breakdown)
3. Opportunities and realistic risks (Balanced view)
4. Common misconceptions
5. Who this topic is relevant for
6. Soft CTA (maybe combined or separate)
- Each H2 can have H3 sub-points.
- Table somewhere.
- OL for sequential workflows.
- UL for key takeaways.
- `[INTERNAL_LINK_1]` placeholder exactly once.
- External link `Official Guide / Research` exactly once.
- Real-world hands-on sentence.
- Concrete numerical statistic with context.
- FAQ section at end with 3 Q&As.
- Image strategy with 2 specs.
Let's draft the Japanese content mentally, ensuring paragraph length.
I need to count CJK characters for the whole article: target 1,800-2,500 chars. That's a lot. Each Japanese sentence is roughly 10-20 chars. 1,800-2,500 chars is about 90-125 sentences. With 2-3 sentences per paragraph, that's 30-63 paragraphs. I need to be concise but thorough. I'll aim for around 2,000 chars.
Let's start building the JSON step by step.
First, determine the H1/meta_title.
Primary keyword: "温度 時間 油汚れ 除去" (9 chars without spaces, 12 with spaces? Actually spaces are half-width usually, but in CJK char count, maybe not counted. The prompt says "28-32 full-width chars for CJK". I'll assume the H1 should be in Japanese, around 28-32 Japanese characters. I'll make it: "温度と時間の油汚れ除去完全ガイドと実践ステップ". Count: 温(1) 度(2) と(3) 時間(4で) で(5) 油(6) 汚(7) れ(8) 除(9) 去(10) 完全(11,12) ガ(13) イ(14) ド(15) と(16) 実(17) 践(18) ス(19)テ(20)プ(21). That's 21 chars. I need 28-32. I can add more: "温度と時間の油汚れ除去に関する実践的完全ガイド". Count additional: に(22) 関(23) す(24)る(25) 実(26) 践的? Actually 的 is one char. Let's count properly later. I'll aim for exactly 29 chars. I can adjust.
Actually, the prompt says: "H1 Title and meta_title MUST be concise and click-worthy (max 60 chars for Latin, 28-32 full-width chars for CJK)." So `h1_title` should be 28-32 full-width chars. I'll make sure.
`meta_title` might be Latin/English mixed? It says "max 60 chars for Latin". But the content is Japanese. I could make meta_title in Japanese too, but the char limit is for Latin. I'll make meta_title in Japanese but count chars as full-width? Or I can mix. To be safe, I'll make meta_title a Japanese sentence within 60 full-width chars, which is easy. Or I can make it Latin-friendly but the prompt says "Clear Meta Description with CTA". I'll just use Japanese characters, each counts as 1 full-width char. 60 chars is plenty for a Japanese sentence.
Slug: URL-friendly ASCII slug. I'll use something like `temperature-time-grease-removal` but in ASCII. Actually, slug should be ASCII, so maybe `ondo-jikan-abura-yogire-joho` or `temp-time-grease-removal`. I'll use `ondo-to-jikan-abura-yogire`.
Now, the JSON fields:
- `meta_title`: string
- `meta_description`: string
- `slug`: string
- `h1_title`: string (28-32 full-width chars)
- `bluf_summary`: string (2-3 sentence direct answer for AI Overviews) - but wait, the BLUF is supposed to be the very first paragraph of `content_html`. The schema has `bluf_summary` as a separate field. The prompt says: "BLUF (Bottom Line Up Front) Opening: The very first paragraph of content_html MUST be a direct 2-3 sentence hook explaining why the topic is trending/relevant now with direct facts/summary. Optimized for AI Overviews." And the schema has `bluf_summary`. I think `bluf_summary` is a concise version, maybe the same as the first paragraph or a summary. I'll make `bluf_summary` a 2-3 sentence string, and `content_html` starts with a `
` that contains the BLUF. They could be identical or similar. I'll make `bluf_summary` a concise version, and the first paragraph in `content_html` the full BLUF. But the prompt says "The very first paragraph of content_html MUST be a direct 2-3 sentence hook". So `content_html` first paragraph is the BLUF. `bluf_summary` might be a separate meta summary. I'll set `bluf_summary` as a 2-3 sentence string that encapsulates the BLUF, and `content_html` starts with `
...BLUF...
`.
- `content_html`: single string of valid HTML, Japanese text, with all sections, paragraphs 2-3 sentences, banned phrases avoided, table, ol, ul, internal link placeholder, external link, etc.
- `faq_items`: array of 3 objects with `question` and `answer`. These must mirror the exact 3 Q&As in the FAQ section at the end of `content_html`.
- `image_strategy`: array of exactly 2 objects (featured and in-body). Each has `position`, `image_type`, `alt_text`, `file_name`, `ai_prompt`. `ai_prompt` in English, optimized for Pollinations AI / Flux, following the rules.
- `extracted_keywords`: array of primary and LSI keywords.
I need to ensure the Japanese content doesn't use banned AI phrases: "In conclusion", "In today's digital era", "delve", "unlock", "game-changer", "landscape", "testament", "tapestry", "As an AI", "Penting untuk dicatat", "seperti yang kita ketahui". I must avoid these in Japanese too? The list is mostly English, but I should avoid literal translations or equivalent cliches. I'll just write naturally.
Also, no em dashes (—). I'll use commas or full stops.
Paragraphs: 2-3 short sentences each. I'll make sure every `
` has 2 or 3 sentences.
Now, let's draft the content_html mentally, section by section.
First, determine the topic: "温度 時間 油汚れ 除去" translates to "temperature time grease removal" or "removing grease with temperature and time". This likely refers to cleaning grease using appropriate temperature and time, perhaps in cooking, automotive, or household cleaning contexts. As an SEO expert, I need to interpret it broadly. Given the keyword, it's probably about how temperature and time affect grease removal effectiveness, maybe for car engines, kitchen cleaning, or stain removal. I'll assume it's about household/kitchen grease removal using temperature (hot water) and time (soaking). I'll make it informative and practical.
Let's start writing. I'll think in Japanese, but output JSON.
I need to be very careful with the JSON syntax. I'll construct the JSON object step by step, ensuring all strings are properly quoted with `"` inside JSON, and HTML inside `content_html` uses `'` for attributes. I'll avoid `"` in HTML by using `'` everywhere. For the external link, the prompt says: `Official Guide / Research`. This uses `'` for href and no quotes around the text, but the text has spaces. In JSON, this string will be enclosed in `"`, so I need to escape any `"` inside. The link as given uses `'` which is fine. I'll use `Official Guide / Research`. Inside the JSON string, this will be `"Official Guide / Research"`. The `'` won't break JSON because JSON uses `"` for delimiting strings. So that's fine.
Internal link placeholder: `[INTERNAL_LINK_1]` exactly once in body text. I'll insert it as plain text inside a paragraph or wherever, but exactly once.
Table: I need at least 1 comparison/data
. I'll create a simple table comparing temperature ranges and effectiveness/time for grease removal. Use `
`, `
`, `
`, `
`. I'll make sure it's valid HTML.
OL for sequential workflows: `` with `
`. The prompt says "Use H3 for sub-points." and "Strictly create 5-6 main H2 sections for the article body (excluding FAQ)." So I'll have exactly 5 or 6 H2 headings in the body. Plus the FAQ H2 at the end, but that's excluded from the 5-6 count? The prompt says "excluding FAQ". So the body has 5-6 H2s, then the FAQ section has its own H2. I'll make sure the body H2s are 5 or 6.
Let's plan the 5-6 H2 sections:
1. Why it is gaining attention/trending in Japanese (日本語) - H2
2. How it works (Beginner-friendly breakdown) - H2
3. Opportunities and realistic risks (Balanced & grounded view) - H2
4. Common misconceptions - H2
5. Who this topic is relevant for - H2
6. Maybe a CTA section, but I can combine with the last or make 5 H2s. The prompt says 5-6 main H2 sections. I'll do 6 to be safe, but I need to count. I'll do 6: 1. Trending reasons, 2. Mechanism, 3. Opportunities & risks, 4. Misconceptions, 5. Relevant audience, 6. Practical steps/soft CTA. But the CTA might be part of the last section. I'll structure carefully.
Actually, the sections list in requirements:
- Why it is gaining attention/trending in Japanese (日本語).
- How it works (Beginner-friendly breakdown).
- Opportunities and realistic risks (Balanced & grounded view).
- Common misconceptions.
- Who this topic is relevant for.
- Soft CTA (e.g., learn more, compare options, stay informed).
These are 6 sections. I'll make each an H2. That's 6 H2s, which is within 5-6.
Now, let's draft the Japanese text for each section, ensuring 2-3 sentences per paragraph, total length.
I'll start with the BLUF opening paragraph. It must be the first paragraph of `content_html`. 2-3 sentences. Something like: "最近、温度と時間の調整による油汚れ除去方法が注目を集めています。適切な温度設定と時間管理が、頑固な油汚れの落とし方の鍵となっているからです。" That's 3 sentences. Good.
Now, section 1 H2: "なぜ今、温度と時間の油汚れ除去が注目されているのか". I'll write a paragraph or two with 2-3 sentence paragraphs.
I need to integrate the primary keyword naturally. The keyword is "温度 時間 油汚れ 除去". I'll use it as a phrase, maybe in the H2 and first paragraph. Density <1.5%. I'll use it maybe 2-3 times in the whole article. With ~2000 chars, using it 3 times is about 0.5% maybe. I'll track.
Let's start drafting. I'll write the content in Japanese mentally, then format into HTML strings.
Important: I must not use banned phrases. I'll avoid "結論から言うと" maybe? Not banned, but "In conclusion" is banned. I'll just use natural transitions.
Let's begin.
I'll create the JSON structure first, then fill in values.
Due to the extreme length and complexity of drafting a full 1800-2500 char Japanese article within the constraints, I'll need to be very efficient. I'll write the content concisely but ensuring all elements are present.
Let's outline the `content_html` string structure:
```
BLUF paragraph 1
BLUF paragraph 2
BLUF paragraph 3
Section 1: Why it's trending
Paragraph
Section 2: How it works
Paragraph
... and so on.
```
I'll include a table, an OL, a UL, the internal link placeholder, external link.
Let's start building the JSON step by step in my thought process, then output.
I need to ensure the Japanese text is natural and meets character count. I'll aim for the article body to be around 2,000 CJK chars. I'll count roughly.
Let's start with the meta_title. I need 28-32 full-width chars for H1. I'll make: "温度と時間の油汚れ除去完全ガイドと実践ステップ". Let's count chars:
温(1) 度(2) と(3) 時間(4で) で(5) 油(6) 汚(7) れ(8) 除(9) 去(10) 完全(11,12) ガ(13) イ(14) ド(15) と(16) 実(17) 践(18) ス(19) テ(20) プ(21). That's 21. I need 28-32. I'll add "に関する" maybe: "温度と時間の油汚れ除去に関する完全ガイドと実践ステップ". Count additional: に(22) 関(23) す(24)る(25) (space? not full-width char maybe, but in Japanese text, space is often half-width. I'll avoid space. I'll use "に関する" as three chars: に(22) 関(23) する? Actually する is two chars: す(24) る(25). So "に関する" is 4 chars? に, 関, そ, る? Wait, "に関する" is three kanas: に, 関, そ, る? Actually, "に関する" is four characters: に(1), 関(2), そ(3), る(4). But in Japanese, it's often written as "に関する". I'll just count visually. To reach 28-32, I can add "方法とコツ". Let's not overcomplicate; I'll make the H1 exactly 29 chars by adjusting. I'll write it and count later. Actually, the prompt says "H1 Title and meta_title MUST be concise and click-worthy (max 60 chars for Latin, 28-32 full-width chars for CJK)." I'll make H1 a string of exactly 29 full-width Japanese characters. I'll design: "温度と時間の油汚れ除去に関する実践的完全ガイド". Count: 温(1) 度(2) と(3) 時間(4で) で(5) 油(6) 汚(7) れ(8) 除(9) 去(10) に(11) 関(12) す(13) る(14) 実(15) 的(16) 的? Wait 的 is one char. So 実的? Actually "的" is one char. "実践的" is two chars: 実(1) 的(2). So let's count properly:
- 温: 1
- 度: 2
- と: 3
- 時間: 4 (time is two chars: 時間? Actually 時間 is two chars: 時 and ん? No, 時間 is two chars: 時 and 間. So that's 2 chars. But in my count, I'm treating each Japanese character as one full-width char. So "時間" is 2 chars. I need to be careful. The prompt says "full-width chars for CJK". Each CJK character is one full-width char. Hiragana/katakana are also full-width. So "時間" is two full-width chars: 時 and 間. "油汚れ" is three: 油, 汚, れ. "除去" is two: 除, 去. "完全" is two: 完全. "ガイド" is four: ガ, イ, ド, but actually ガイド is four chars: ガ, イ, ド, and maybe ？ no, it's four: ガ, イ, ド, and the small ょ? Actually, in Unicode, "ガイド" is four characters: U+30B0, U+30A4, U+30C9, U+30B9? Wait, "ガイド" is usually 4 chars: ガ, イ, ド, but the "u" sound? Let's not get bogged. I'll just ensure the total count is around 29-31 by using a mix I can count. I'll use simple words I can count.
Let's design H1: "温度と時間の油汚れ除去ガイド". Count: 温(1) 度(2) と(3) 時(4) 間(5) の(6) 油(7) 汚(8) れ(9) 除(10) 去(11) ガ(12) イ(13) ド(14). That's 14 chars. Too short. I'll add "完全版": "温度と時間の油汚れ除去完全ガイド". Count add 完全(2) so 16. Still short. I'll add "と実践ステップ": "温度と時間の油汚れ除去完全ガイドと実践ステップ". Count: add と(1) 実(2) 践(3) ス(4) テ(5) プ(6). So total 16+6=22. Still need 28-32. I'll add "に関するノウハウ": に(23) 関(24) そ(25) る(26) ノ(27) ウ(28) ハ(29) ウ(30). That's 30 chars. Let's verify: "温度と時間の油汚れ除去完全ガイドに関するノウハウ". Count each char:
1: 温
2: 度
3: と
4: 時
5: 間
6: の
7: 油
8: 汚
9: れ
10: 除
11: 去
12: 完全
13: ガ
14: イ
15: ド
16: に
17: 関
18: そ
19: る
20: ノ
21: ウ
22: ハ
23: ウ
That's 23 chars. I need 28-32. I'll add "と詳細な方法": と(24) 詳細(25,26? 詳細 is two chars: 細 and 詳? Actually 詳細 is two chars: 詳細. In Japanese, each kanji is one char. So 詳細 is 2 chars. I'll count as 2. So 23+2=25. Then と(26) 方法(27,28? 方法 is two chars: 方 and 法). This is getting messy. I'll just aim for a reasonable length and not obsess over exact char count, as long as it's within 28-32. I'll make it "温度と時間の油汚れ除去に関する実践的ガイド". I'll count later if needed. The JSON output will have it as a string; the system will validate. I'll just ensure it's Japanese and seems within range.
Actually, I can just make the H1: "温度と時間の油汚れ除去完全ガイド". That's 16 chars approx. But the prompt says 28-32 full-width chars for CJK. I must comply. I'll add more words to reach at least 28. I'll write: "温度と時間の油汚れ除去に関する完全ガイドブック". Count: add に(?) 関(?) そ(?) る(?) 完全(2) ガ(1) イ(1) ド(1) ブ(1) ッ(1) ッ? This is too error-prone. I'll instead make the H1 a sentence that's naturally longer. In Japanese, a title can be longer. I'll just put "温度と時間の油汚れ除去に関する実践的ステップと注意点". I'll count in the JSON output moment. For now, I'll prioritize content and adjust H1 char count in the final JSON by counting precisely.
Let's change strategy: I'll define the H1 as a string I can count exactly. I'll use only single kanas and count. I'll make it 29 chars long. I'll use a mix of hiragana and kanji I can count.
Example: "温度と時間の油汚れ除去についての基礎と実践". Count:
1:温
2:度
3:と
4:時
5:間
6:の
7:油
8:汚
9:れ
10:除
11:去
12:に
13:つ
14:いて
15:の
16:基
17:礎
18:と
19:実
20:践
That's 20. I need 28-32. I'll add "ステップ": ス(21) テ(22) ッ(23) プ(24). Add "方法": 方法(25,26). Add "と注意": と(27) 注(28) 意(29). So "温度と時間の油汚れ除去についての基礎と実践ステップと注意". Count: let's list:
温(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)
That's 27. I need 28-32. Add one more char, e.g., "まとめ" (2 chars) or just add "方". I'll add "方" (28). So the H1 is "温度と時間の油汚れ除去についての基礎と実践ステップと注意方". But "注意方" means "way of paying attention". It's fine. Let's count the last part: "と注意方" is と(25) 注(26) 意(27) 方(28). Yes, 28 chars. But the prompt says 28-32 full-width chars. 28 is at the lower bound. I'll make it 29 or 30 to be safe. I'll add "のコツ" (の(29) コ(30) ッ(31) ッ? Actually の is one char, コツ is two: コ, ツ? I'll just stop at 29. I'll design: "温度と時間の油汚れ除去についての基礎と実践ステップと注意". Count again carefully, treating each Japanese character as one. I'll do it in the final output. For now, I'll just ensure the H1 string is Japanese and I'll count precisely when writing the JSON.
Actually, I realize I can just make the H1: "温度と時間の油汚れ除去完全ガイド28文字目指す". No, that's cheating. I'll just write a natural Japanese H1 and trust it's within range, or I'll count in the final step. The prompt is strict, but I'll do my best.
Let's move on to other fields. I'll build the JSON structure and fill Japanese content last.
I need to create the `content_html` with proper HTML. I'll use `
` for paragraphs, `
`, `
` for sections, `
`, ``, `
`. I'll ensure each `
` has 2-3 sentences. I'll avoid banned phrases.
Let's draft the Japanese content in a structured way, then convert to HTML strings.
Due to the extreme length of the article (1800-2500 CJK chars), I need to generate a substantial amount of text. I'll write it paragraph by paragraph, ensuring constraints.
