We need to produce JSON with keys: summary, category, article_html. Must be valid JSON. The article must have exactly one H1 at start with primary keyword. Primary keyword: "best books to read best sellers fiction books to read best sellers" is long phrase; but we need H1 with primary keyword. We can use "Best Books to Read: Top Fiction Best Sellers" or similar. But the instruction: "Exactly ONE H1 at start with primary keyword". So H1 should contain the primary keyword. The primary keyword given: "best books to read best sellers fiction books to read best sellers". That's odd. Maybe we combine: "Best Books to Read: Fiction Best Sellers". But we must include the entire phrase? Let's read: "Write a detailed SEO article about: best books to read best sellers fiction books to read best sellers". So the primary keyword may be "best books to read best sellers". Or maybe "best sellers fiction books to read". We need to include the phrase exactly? The instruction: "Exactly ONE H1 at start with primary keyword". So we should use the phrase "best books to read best sellers" as H1. But that phrase is weird. Maybe we can use "Best Books to Read: Fiction Best Sellers" which includes "best books to read" and "best sellers". But to be safe, maybe use "Best Books to Read: Fiction Best Sellers". That's not exactly the phrase but includes key parts.
But the instruction might enforce the exact phrase. Might cause mismatch. Could produce H1: "Best Books to Read Best Sellers". That includes both "best books to read" and "best sellers". But we also need "fiction" maybe. The phrase "best books to read best sellers fiction books to read best sellers" is repeated. Could just use "Best Books to Read: Fiction Best Sellers". This includes all key parts. Ok.
Other rules: H2 for 5-7 main sections. H3 for subsections. P tags: 2-3 per section, each 100-150 words. That's a lot of words: 2-3 p per section * 5-7 sections = 10-21 paragraphs; each 100-150 words; total words 1000-3150. Minimum 1500 words. So we need maybe 7 sections, each with 3 paragraphs: 7*3=21 paragraphs. Each 120 words average => 2520 words. Good.
We also need UL/OL lists with 5-10 items. We need some lists.
We need to include book recommendations with authors and key takeaways.
Also must end with 3-5 FAQ questions as H3.
We need to output valid JSON. article_html must be a string containing the entire HTML. Need to escape quotes properly.
Also must not include markdown or code fences. So output JSON only.
We need to ensure the JSON string has no unescaped double quotes inside. We'll use single quotes inside? Actually JSON requires double quotes for keys and string values. Inside the string, we need to escape double quotes. We'll produce the article_html string with escaped quotes. Use `\"` for double quotes inside. Also we need to escape backslashes. We can use single quotes around JSON? No, JSON must use double quotes. So we need to escape internal quotes.
We need to produce the article_html with appropriate tags. Let's outline sections:
H1: "Best Books to Read: Fiction Best Sellers"
H2 sections (7):
1. The Rise of Modern Fiction Best Sellers
2. Must-Read Contemporary Fiction
3. Timeless Classics That Still Sell
4. Genre‑Specific Best Sellers to Explore
5. Debut Authors Who Became Household Names
6. How to Build Your Personal Bestseller Shelf
7. Resources for Keeping Up with New Best Sellers
Add UL/OL lists within.
H3 subsections within each section maybe 1 or 2.
Total 7 H2s.
We need at least 3-5 FAQ H3 at end.
Be careful: we need exactly one H1 at start. So no other H1.
Now we need to write paragraph content: 2-3 paragraphs per section, each 100-150 words. That's long. We need to write content. Provide 3 paragraphs per section. 7 sections => 21 paragraphs. Each 120 words ~ 2520 words. We need to write about 120 words each, but we can approximate.
We need to embed lists: in some sections.
Also include book recommendations: at least each section list some books, authors, key takeaways.
Let's craft content.
We must not exceed time. We'll write about 120 words each.
Paragraph 1 for Section 1: talk about rise of modern fiction best sellers, industry changes, etc.
Paragraph 2: talk about reading trends.
Paragraph 3: talk about why best sellers matter.
Section 2: Must-Read Contemporary Fiction.
Paragraph 1: introduction to contemporary novels.
Paragraph 2: list of books with authors and takeaways.
Paragraph 3: why these are impactful.
List maybe inside paragraph 2? Use UL.
Similarly for other sections.
We also need at least one list per section.
Let's start writing.
We also need to include at least 3-5 FAQ H3 at end.
Let's produce.
We need to make sure each paragraph is 100-150 words. We'll approximate.
Let's write each paragraph with ~120 words. We'll count approximate. We'll produce.
We'll need to escape quotes.
We'll produce JSON with the article_html string.
Let's start.
We also need category: "howto".
Summary: 2-3 sentence SEO meta description (150-160 chars). We'll craft.
Let's write summary: "Discover the top fiction best‑seller books for avid readers. Explore contemporary classics, genre favorites, and debut authors with key takeaways. Build your personal bestseller shelf today." Count words? Let's count characters: We'll approximate 150-160.
Let's count: "Discover the top fiction best‑seller books for avid readers. Explore contemporary classics, genre favorites, and debut authors with key takeaways. Build your personal bestseller shelf today."
Count characters:
- Discover (7) + space 1 =8
space etc. Let's just approximate 150-160; likely fine.
Now produce JSON.
We need to ensure no newlines inside string? Allowed but must escape. We'll use newline \n maybe.
Let's craft article_html.
We need to ensure double quotes are escaped. We'll use \" for quotes inside HTML attributes. But we can avoid quotes inside attributes by using single quotes? In HTML, attributes can be in double quotes. We'll use double quotes and escape them. We'll need to escape them in JSON string.
We'll write article_html as a string with \n for line breaks. Eg:
"
we would need quotes. We can avoid quotes.
We just need
Best Books to Read: Fiction Best Sellers
\n...
" We need to escape quotes around attribute values. Since we are using double quotes for JSON string, inside we need to escape double quotes. So we can write