Here's a thinking process:
- Analyze User Input:
- User wants a complete article of at least 900 words.
- Topic: "if you were or if you was"
- This appears to be about grammar: the correct usage of "if you were" vs "if you was"
- The topic is grammatically specific, likely targeting English language learners.
- Check Constraints & Guidelines:
- No meta opening sentences (no "Okay, here's a comprehensive article...", no "This article will discuss...", no introductions about the writing process)
- Must match language of title: title is in English, so article must be entirely in English.
- Start directly with main content of article body
- No explanations that text is an article/SEO content
- No evaluating/commenting on writing process
- Output must begin with first paragraph of article body, without greetings/intros/meta descriptions
- Professional content creator specializing in educational topics
- High-value, SEO-friendly, emotional connection
- In-depth, easy to understand, relevant for various backgrounds
- Factually accurate, engaging, motivating
- Compete on Google first page without losing authenticity/human touch
- Natural writing style, friendly yet professional
- Clean structure: opening paragraph introduces topic + functions as meta description with main keyword
- Clear subheadings: Introduction, Steps, Scientific Explanation, FAQ, Conclusion
- Use bold for important points, italic for foreign terms/light emphasis
- Use lists for sequences/important info
- SEO principles: Markdown formatting (H2, H3), bold, lists, natural main keyword and LSI keywords, avoid keyword stuffing, no external links, original/informative/worthy of backlinks
- Main objectives: help users produce strong SEO articles, provide info that answers questions and expands understanding
- Identify the Core Topic:
- "if you were or if you was" is about subjunctive mood vs indicative mood in English grammar.
- "If you were" is correct for hypothetical/subjunctive situations, especially with "if I were he/she/it" or formal contexts.
- "If you was" is common in informal/dialectal speech, but grammatically incorrect in standard English formal contexts.
- Need to cover: rules, usage, common mistakes, examples, exercises, maybe a bit of history/linguistics, and practical tips.
- Structure the Article per Guidelines:
- Must start directly with the first paragraph of article body.
- Opening paragraph should introduce topic and function as meta description containing main keyword.
- Use clear subheadings: Introduction, Steps, Scientific Explanation, FAQ, Conclusion. (Note: "Scientific Explanation" might be a bit forced for grammar, but I'll adapt to "Grammatical Explanation" or keep as requested? The instructions say "such as Introduction, Steps, Scientific Explanation, FAQ, and Conclusion." I should use those exact section names or similar? It says "Use clear subheadings for every important section such as Introduction, Steps, Scientific Explanation, FAQ, and Conclusion." I'll use those as section titles, maybe adjusting "Scientific Explanation" to "Grammatical Explanation" or keep it as is. I'll stick to the exact names to be safe, or use "Grammatical Explanation" but the instruction says "such as", meaning those are examples. I'll use: Introduction, Steps, Grammatical Explanation, FAQ, Conclusion. Actually, to match exactly, I'll use: Introduction, Steps, Scientific Explanation (but adapt content), FAQ, Conclusion. I think it's fine to use those headings.)
- Use bold for important points, italic for foreign terms/light emphasis.
- Use lists for sequences/important info.
- At least 900 words.
- Main keyword: "if you were or if you was" or similar. I'll use that naturally.
- Semantic/LSI keywords: subjunctive mood, indicative mood, conditional sentences, were vs was, hypothetical situations, English grammar, grammar rules, if clause, etc.
Let's outline:
- Opening paragraph: introduces the common confusion, contains main keyword, serves as meta description. Must be engaging, no "Okay here's...Even so, " style. Just dive in. Because of that, - H2: Introduction (or maybe the opening already covers intro, but I'll have a separate Introduction section? The instruction says "Use clear subheadings for every important section such as Introduction, Steps, Scientific Explanation, FAQ, and Conclusion." So I need these sections. The opening paragraph is separate? It says "The opening paragraph should introduce the topic and also function as a meta description containing the main keyword." And "Start directly with the main content of the article body". So the first paragraph is the opening paragraph, then I need subheadings. Even so, i'll structure: first paragraph (opening), then H2 sections: Introduction, Steps, Scientific Explanation, FAQ, Conclusion. But the first paragraph might be considered the introduction. Here's the thing — to be safe, I'll make the first paragraph a brief opening that serves as meta description, then have the sections start after that. Or I can integrate the opening into the Introduction section but ensure the very first paragraph is the one that functions as meta description. The instruction: "The opening paragraph should introduce the topic and also function as a meta description containing the main keyword." and "Start directly with the main content of the article body, without greetings, introductions, or meta descriptions." Wait, contradictory? So "without greetings, introductions, or meta descriptions" but also "The opening paragraph should introduce the topic and also function as a meta description containing the main keyword. " I think means: don't write a separate meta description line; the first paragraph itself should serve that purpose, and shouldn't have "In this article we will...On the flip side, " or "Hello readers... And ". It should naturally introduce the topic and contain the keyword. So I'll write the first paragraph in a way that introduces the topic and has the keyword, but without saying "This article is about..." explicitly. Then I'll have subheadings after that.
Let's plan the flow:
- Paragraph 1: Introduce the "if you were vs if you was" dilemma naturally. Also, contains main keyword. In real terms, no "Okay" or "In this article". - Then H2: Introduction (but maybe the first paragraph already is the intro. I'll make a second section "Introduction" that elaborates, or I'll merge. To follow "use clear subheadings for every important section such as Introduction, Steps, Scientific Explanation, FAQ, and Conclusion", I'll include those as H2/H3 sections. I'll make the first paragraph outside the sections? Practically speaking, actually, Markdown structure: I can have a paragraph, then H2 sections. The first paragraph should be the opening. Practically speaking, then I'll have H2: Introduction, but that might duplicate. I'll make the first paragraph a standalone opening that serves as meta description, then H2: Introduction (which can overlap but I'll make it distinct enough), or I'll skip having a separate Introduction H2 if the first paragraph covers it. But the instruction says "Use clear subheadings for every important section such as Introduction, Steps, Scientific Explanation, FAQ, and Conclusion." It doesn't say I must have all of them, but lists them as examples. I'll include all five to be safe: Introduction, Steps, Grammatical Explanation (or Scientific Explanation), FAQ, Conclusion. I'll adjust "Scientific Explanation" to "Grammatical Explanation" but the keyword might not match. I'll keep "Scientific Explanation" and frame it as the linguistic/scientific basis of the rule. Or I can use "Grammar Rules" but I'll stick to the list. I'll use exactly: Introduction, Steps, Scientific Explanation, FAQ, Conclusion. I'll make the content fit.
Let's draft paragraph 1: "The choice between 'if you were' and 'if you was' trips up even confident English speakers, especially when texting friends or posting on social media. Think about it: in formal writing, the distinction matters because it reflects the subjunctive mood, a grammatical tool used for hypothetical or unreal situations. Understanding when to use 'were' versus 'was' not only polishes your grammar but also helps you express ideas about wishes, dreams, and counterfactual scenarios with precision It's one of those things that adds up..