Thinking Process: 1. **Analyze the Request:** * **Topic:** "jose altuve age" * **Style:** Authoritative, comprehensive SEO article. * **Architecture:** Problem-solver Q&A style (answering core pain points). * **Structure:** * Start with a Key Takeaways summary. * Use `

`, `

` tags. * Include a comparison table (``) or checklist. * Include 3 FAQs. * Output raw HTML only (no markdown wrappers like ```html). * **Role:** Expert SEO editorial journalist. 2. **Determine Content & SEO Strategy:** * **Intent:** Users searching "jose altuve age" want a quick answer but also context about his career longevity, performance relative to age, and milestones. * **Key Data:** Jose Altuve was born on May 6, 1990. As of 2024, he is 34 years old. * **Pain Points:** Is he too old to perform? How does he compare to peers? When will he retire? * **Keywords:** Jose Altuve age, Jose Altuve birthday, Houston Astros second baseman age, Jose Altuve career stats by age. * **Tone:** Authoritative, factual, engaging. 3. **Drafting the HTML Structure:** * `` (Optional but good for raw HTML, though usually just content fragments are expected in these prompts. I will provide a semantic content fragment wrapped in appropriate tags but without the full `` boilerplate unless necessary for validity. The prompt asks for "raw HTML only", usually implying the content structure. I will include basic structural tags like `

` for semantics). * **Key Takeaways:** Use a `

` or `

` with a list. * **Headings:** `

` for title, `

` for main sections, `

` for subsections. * **Table:** Compare age milestones or stats. * **FAQ:** Use `

` with `

` for questions and `

` for answers. 4. **Content Verification (Mental Check):** * Birthdate: May 6, 1990. * Current Year: 2024 (assuming current context). * Age: 34. * Team: Houston Astros. * Position: Second Base. 5. **Writing the Content (Iterative):** * *Title:* Jose Altuve Age: Career Milestones, Performance Metrics, and Future Outlook * *Key Takeaways:* Bullet points summarizing birthdate, current age, team, and status. * *Section 1 (Direct Answer):* How old is Jose Altuve? * *Section 2 (Context):* Career longevity and performance relative to age. * *Table:* Age vs. Key Career Stats/Milestones. * *Section 3 (Future):* Contract and retirement speculation. * *FAQs:* 3 specific questions. 6. **Refining for SEO:** * Use schema-like structure (though not actual JSON-LD unless requested, semantic HTML helps). * Ensure keywords are natural. * Keep paragraphs concise. 7. **Final Review against Constraints:** * Raw HTML only? Yes. * No markdown? Yes. * Key takeaways first? Yes. * H2, H3 used? Yes. * Table included? Yes. * 3 FAQs? Yes. 8. **Constructing the HTML:** * Avoid `` or `` tags to ensure it fits as a content snippet, but use semantic tags like `

`, `

`, `

`, `

`, ``, ``, ``, `

`, `

`. * *FAQs:* ` ` with ` ` and ` `. * *Date Accuracy:* As of today (October 2023 -> May 2024 context), he is 34. I will write it generally enough or specify "as of 2024". Let's assume current date is mid-2024 for accuracy. Born May 6, 1990. 2024 - 1990 = 34. * *SEO Optimization:* Include latent semantic indexing (LSI) keywords like "Houston Astros," "MLB veteran," "contract extension," "batting average." 9. **Final Polish:** Check tag closing. Ensure no markdown symbols like `#` or `*` are used for styling, only HTML tags. * *Wait, one constraint:* "Output raw HTML only without markdown." * *Interpretation:* Do not use markdown code blocks. Just print the HTML string. * *Wait, another constraint:* "Start with a key takeaways summary." * *Implementation:* Put this at the very top of the article content. * *Table:* Make sure it's semantic. * *FAQs:* Exactly 3. Let's assemble. * ` ` * ` ` * ` ` * ` ` How Old Is Jose Altuve? * ` ` * ` ` Career Longevity and Performance by Age * `` * ` ` Contract Status and Retirement Outlook * ` ` * ` ` * ` ` Frequently Asked Questions * ` ` Q1 * ` ` A1 * ... * `` Let's write the content. * Birthdate: May 6, 1990. * Age: 34 (in 2024). * Team: Houston Astros. (Self-Correction): Ensure the HTML is valid. Use ` ` if needed, but standard text is fine. Let's generate the code. *Wait, I need to make sure I don't output markdown formatting like ```html.* I will output the text starting with ` `. *Wait, I need to check the "Problem-solver Q&A architecture style".* This means the headings should reflect questions or problems users have. Instead of "Career Longevity", use "How Does Altuve's Age Impact His Performance?". Instead of "Contract Status", use "Is Jose Altuve Too Old for Another Contract?". Let's adjust headings to match the "Problem-solver Q&A" style. * H1: Jose Altuve Age: Complete Career Timeline and Performance Analysis * Takeaways Section. * H2: How Old Is Jose Altuve Right Now? * H2: How Does Jose Altuve's Age Compare to MLB Peers? (Table) * H2: Will Jose Altuve's Age Affect His Future Performance? * FAQ Section. Okay, ready to write. *One final check on constraints:* "Output raw HTML only without markdown." This means I should not wrap the output in a code block. I will just output the text. *Wait, if I output raw text starting with `<`, the interface might interpret it as code.* The instruction says "Output raw HTML only". I will provide the text content as HTML tags. *Wait, I need to be careful about the "without markdown" instruction.* It means do not use `**bold**` or `# Header`. Use `` and ` `. It also usually means do not wrap the result in a markdown code block fence. Let's go. *Date Check:* Today is May 2024 (in my internal context). Altuve turns 34 on May 6, 2024. I will state he is 34 years old. *Table Content:* Age milestones. Age 21: MLB Debut. Age 24: First All-Star. Age 27: MVP Season. Age 34: Current Status. *FAQs:* 1. What is Jose Altuve's birthday? 2. How many seasons has Jose Altuve played? 3. Is Jose Altuve eligible for the Hall of Fame based on his age? Let's build it. *Wait, one more thing:* The prompt asks for "Problem-solver Q&A architecture style answering core pain points with FAQ." This implies the main body should also feel like it's solving problems, not just stating facts. Pain point: "Is he declining?" -> Answer with stats. Pain point: "When is he retiring?" -> Answer with contract info. Okay,