We need to write a blog article for focus keyword: “[INSERT FOCUS KEYWORD HERE]” but the user gave placeholder. Actually they likely expect we replace placeholder with something? The instruction says “Write an authoritative, highly engaging, and comprehensive blog article for the Focus Keyword: [INSERT FOCUS KEYWORD HERE]”. So we need to treat the focus keyword as that placeholder? Probably they want us to produce article for that placeholder, but that seems weird. However later they give traffic-growth writing rules for “what information to include in a float plan”. So the focus keyword is actually “what information to include in a float plan”. Indeed later they say: TRAFFIC-GROWTH WRITING RULES (apply to this entire article about “what information to include in a float plan”). So the focus keyword is “what information to include in a float plan”. So we need to write article about that. So we will treat focus keyword = “what information to include in a float plan”. We’ll need to embed that phrase many times.
We need to produce HTML only, no markdown fences. Use headings h1, h2, h3, p, ul, ol, table etc. Must maintain readability: short sentences, simple words, Flesch-Kincaid 95+. That’s extremely high readability (like very easy). Use short words, 1-2 syllable, sentences under 10-12 words average. We need to produce ~1500-3000 words. That’s a lot while keeping sentences super short. But we can do many short sentences.
We need 10 question sections, each with 10 paragraphs (so 100 paragraphs total). Each paragraph 2-4 lines max, short sentences. We’ll need to craft simple language.
We also need a Table of Contents linking to H2 sections.
We need FAQ section with 3-5 quick questions.
We need final thoughts.
We need meta description and SEO title comments at end.
We need feature image prompt comment.
We need word count comment.
We need content ideas comment block.
We must not use markdown fences. Use plain HTML.
We must avoid complex words. Use simple words like boat, water, plan, etc.
We need to ensure we use the focus keyword exactly: “what information to include in a float plan”. We’ll need to use it in title, early intro, at least two H2s.
We must not use overused buzzwords.
We need to avoid generic intro fluff; jump directly into relatable scenario.
Let’s outline:
Title: maybe “What Information to Include in a Float Plan – Simple Guide for Boaters”. Must be 50-65 characters. Include focus keyword at beginning. So title: “What Information to Include in a Float Plan – Easy Guide”. Count characters: Let’s count: “What Information to Include in a Float Plan – Easy Guide”. That’s maybe ~55. Good.
SEO title comment:
Meta description: 120-140 characters, include focus keyword. Something like: “Learn what information to include in a float plan to stay safe on the water. Simple steps, checklists, and tips for every boater.” Count characters: Let’s count roughly: “Learn what information to include in a float plan to stay safe on the water. Simple steps, checklists, and tips for every boater.” That’s about 114? Let’s count: We’ll need 120-140. We’ll adjust later.
Feature image prompt: describe a boater holding a float plan document on a dock at golden hour.
Now main content: Need to identify 10 most frequently asked questions about what information to include in a float plan. We’ll generate plausible FAQs:
1. What is a float plan and why do I need one?
2. What basic details should I put in a float plan?
3. How do I describe my boat and equipment in a float plan?
4. What passenger and crew info should I include?
5. What trip route and timing details are needed?
6. How do I add emergency contacts and communication plans?
7. What safety gear info belongs in a float plan?
8. How often should I update my float plan?
9. Who should I leave my float plan with and how?
10. What are common mistakes to avoid when making a float plan?
Each question as H2, then 10 paragraphs.
We need to keep sentences very short. Use simple words.
We also need to embed lists and tables where helpful.
We need to keep readability high: Use 1-2 syllable words mostly. Avoid long words like “information” (4 syllables) but it’s needed as part of keyword; we can use it but limited. However the keyword itself has many syllables; but we need to use it naturally. We’ll try to keep other words simple.
We need to ensure Flesch-Kincaid >95. That is extremely easy text. Usually to get that high, need very short words and sentences. We’ll aim for average sentence length ~5 words, and average syllables per word low.
We’ll need to watch out.
Let’s craft each paragraph with maybe 3-4 sentences, each sentence 5-7 words.
We’ll use words like “boat”, “plan”, “water”, “safe”, “tell”, “show”, “list”, “add”, “check”, “call”, “go”, “come”, “see”, “make”, “write”, “keep”, “use”, “need”, “do”, “can”, “will”, “is”, “are”, “the”, “and”, “to”, “of”, “in”, “on”, “for”, “with”, “at”, “by”, “as”, “but”, “or”, “if”, “then”, “so”, “yet”. Avoid complex words like “equipment” (3 syllables) maybe okay but we can use “gear”. Use “boat” not “vessel”. Use “person” not “individual”. Use “phone” not “communication device”. Use “call” not “telecommunicate”. Use “map” not “navigational chart”. Use “time” not “schedule”. Use “day” not “date”. Use “name” not “identifier”. Use “number” okay.
We need to avoid words like “necessarily”, “additionally”, “furthermore”. Use simple connectors.
We’ll need to include the focus keyword phrase many times; that phrase itself is long and complex but it’s required. We’ll try to limit its usage to maybe 4-6 times total.
Now we need to produce HTML. Let’s start.
We’ll include
for title.
Then intro paragraph(s) 100-140 words.
We’ll need to ensure intro includes focus keyword within first 100 words.
Let’s craft intro: maybe 120 words.
We’ll write short sentences.
Now we need Table of Contents: