We need to write detailed SEO article about "best books to read for teens romance". Must return valid JSON: keys: summary, category, article_html. The article must follow rules:
- Exactly ONE H1 at start with primary keyword. Primary keyword likely "best books to read for teens romance" or maybe "best teen romance books". The H1 must be at start, no other H1s.
- H2 for 5-7 main sections. So maybe 6 sections. Each H2 section will have 2-3 P tags (100-150 words each). That's large. 2-3 paragraphs per section, each paragraph 100-150 words. So each section 200-450 words. 6 sections => 1200-2700 words. Minimum 1500 words. We'll aim for ~1700-1800 words.
- Also include UL/OL lists 5-10 items.
- Strong for key terms.
- End with 3-5 FAQ questions as H3.
- Include specific book recommendations, authors, key takeaways.
- Actionable tone.
We must write article_html in HTML string. Must be valid JSON string. Must escape quotes. We'll produce article_html as raw HTML (no escaping needed inside JSON? Actually JSON string must escape double quotes. We'll produce as JSON object with string values. We'll need to escape double quotes. But we can use single quotes inside HTML? In HTML attribute values we use double quotes. That would need escaping. We can use single quotes for attributes or escape. Safer to escape double quotes in JSON string. But easier: use single quotes for attributes. But still need to escape double quotes around JSON key/value. We'll produce JSON with double quotes for keys and values, but inside the article_html string we need to escape double quotes. Use backslashes. That is tedious. However we can produce the JSON such that the article_html string contains raw HTML with single quotes for attributes, so we don't need to escape double quotes inside. But there will still be double quotes in tags like etc. Those are not double quotes. So we can use single quotes for attributes.
Let's plan article structure:
H1: "Best Books to Read for Teens Romance"
H2 sections:
1. "Why Teen Romance Books Matter"
2. "Top 10 Must-Read Teen Romance Books"
3. "Modern Twists: Contemporary Teen Romance"
4. "Classic Romance Gems for Teens"
5. "Finding Your Perfect Match: How to Choose the Right Book"
6. "Beyond the Page: How to Discuss Romance Books with Teens"
Each section will have 2-3 paragraphs (100-150 words). We'll write 2 paragraphs per section.
Also include UL/OL lists for book lists.
Include book recommendations with authors, key takeaways.
At the end, 3-5 FAQ questions as H3.
Word count: each paragraph 120 words approx. 2 paragraphs per section => 240 words per section. 6 sections => 1440 words. Add FAQ maybe 3 paragraphs each 120 words => 360 words. Total ~1800 words.
Ok.
Let's draft.
Need to use for key terms like "teen romance".
Also use
etc. Those are not double quotes. So we can use single quotes for attributes.
Let's plan article structure:
H1: "Best Books to Read for Teens Romance"
H2 sections:
1. "Why Teen Romance Books Matter"
2. "Top 10 Must-Read Teen Romance Books"
3. "Modern Twists: Contemporary Teen Romance"
4. "Classic Romance Gems for Teens"
5. "Finding Your Perfect Match: How to Choose the Right Book"
6. "Beyond the Page: How to Discuss Romance Books with Teens"
Each section will have 2-3 paragraphs (100-150 words). We'll write 2 paragraphs per section.
Also include UL/OL lists for book lists.
Include book recommendations with authors, key takeaways.
At the end, 3-5 FAQ questions as H3.
Word count: each paragraph 120 words approx. 2 paragraphs per section => 240 words per section. 6 sections => 1440 words. Add FAQ maybe 3 paragraphs each 120 words => 360 words. Total ~1800 words.
Ok.
Let's draft.
Need to use for key terms like "teen romance".
Also use list for books.
Paragraph 1, 2 paragraphs each section. Each paragraph 100-150 words. We'll write 120 words each.
Let's start writing.
We must ensure the H1 only once at start. Then H2 sections. Then at the end H3 for FAQs.
Ok.
Now we need to produce JSON.
In JSON, we need to escape the double quotes inside article_html string. We'll use single quotes for attributes, but we still have double quotes for JSON string boundaries. So for article_html string, we need to escape any double quotes inside. But we can avoid double quotes inside the string by using single quotes for attributes. However, the HTML tags themselves like have no quotes. So we can keep them. So only double quotes appear if we used attributes like class="..." etc. We can avoid attributes. So article_html string will not contain double quotes. That will avoid escaping. Let's not use attributes.
Ok. Let's craft article_html string.
We'll produce article_html like:
Best Books to Read for Teens Romance
Why Teen Romance Books Matter
...
...
Top 10 Must-Read Teen Romance Books
...
...
... list ...
...
But we need exactly 2-3 P tags per section. So we need 2 paragraphs. We can also add UL after paragraphs. That's okay.
Let's craft each paragraph.
We need to count words roughly 120 words. We'll approximate.
Ok.
Paragraph 1 for section 1: talk about emotional development, empathy, etc.
Paragraph 2: benefits of reading romance, etc.
Similarly for each section.
Let's write.
Also include specific book recommendations with authors: e.g., "The Princess Diaries" by Meg Cabot, "Eleanor & Park" by Rainbow Rowell, "Anna and the French Kiss" by Stephanie Perkins, "The Fault in Our Stars" by John Green, "If I Stay" by Gayle Forman, "To All the Boys I've Loved Before" by Jenny Han, "The Kissing Booth" by Beth Reekles, "The Summer I Turned Pretty" by Jenny Han, "Fangirl" by Rainbow Rowell, "Love, Simon" by Becky Albertalli. Classic: "The Secret Garden" (not romance?), "Romeo and Juliet" etc. But for teen romance, we can include "The Taming of the Shrew" maybe not. We'll include "The Perks of Being a Wallflower" maybe.
Ok.
Let's craft.
We also need 5-10 items list. We'll add UL of 10 books.
Ok.
Now let's craft the article_html string. We'll need to ensure we don't break JSON.
Also we need to include tags for key terms.
Let's write.
We'll produce JSON string with triple quotes? Actually we need to output JSON object.
We'll produce:
{"summary":"...","category":"howto","article_html":"..."}.
Will need to escape newlines? In JSON string, newlines are allowed as \n? Actually JSON strings cannot contain literal newlines unless escaped. So we need to escape them. But we can embed \n as line breaks. That can be done. But easier: we can include the article_html as a single line string with \n escapes. That's fine.
But we can also include actual newlines within the string? In JSON, newlines must be escaped. So to be safe, we should escape newline characters as \n. We'll produce a single-line string with \n for readability.
Thus article_html will have \n between tags. We'll escape double quotes if any. But we will not have double quotes.
Ok.
Let's craft article_html string with \n.
We'll produce:
"Best Books to Read for Teens Romance
\nWhy Teen Romance Books Matter
\n
...
\n
have no quotes. So we can keep them. So only double quotes appear if we used attributes like class="..." etc. We can avoid attributes. So article_html string will not contain double quotes. That will avoid escaping. Let's not use attributes.
Ok. Let's craft article_html string.
We'll produce article_html like:
Best Books to Read for Teens Romance
Why Teen Romance Books Matter
...
...
Top 10 Must-Read Teen Romance Books
...
...
- ... list ...
..."}.
Will need to escape newlines? In JSON string, newlines are allowed as \n? Actually JSON strings cannot contain literal newlines unless escaped. So we need to escape them. But we can embed \n as line breaks. That can be done. But easier: we can include the article_html as a single line string with \n escapes. That's fine.
But we can also include actual newlines within the string? In JSON, newlines must be escaped. So to be safe, we should escape newline characters as \n. We'll produce a single-line string with \n for readability.
Thus article_html will have \n between tags. We'll escape double quotes if any. But we will not have double quotes.
Ok.
Let's craft article_html string with \n.
We'll produce:
"Best Books to Read for Teens Romance
\nWhy Teen Romance Books Matter
\n
...
\n