Evergreen FAQ Content Expander

Expand the following FAQ list into a complete evergreen blog post: FAQ questions: {&{FAQ_LIST}} Topic domain: {&{TOPIC_DOMAIN}} Target audience: {&{TARGET_AUDIENCE}} Expertise level of audience: {&{EXPERTISE_LEVEL}} (e.g., complete beginner, intermediate professional) Brand/author authority claim: {&{AUTHORITY_CLAIM}} (e.g., "based on 5 years of managing X") Related blog posts to link to: {&{RELATED_POSTS}} (optional — list URLs or titles) **Deliver the following:** 1. **Post Title**: Benefit-driven, includes primary keyword, under 60 chars. 2. **Introduction** (100–130 words): Set the stakes. Why do these questions matter? Who is asking them and what are they trying to decide or understand? End the intro with a one-sentence overview of what this post covers. 3. **Expanded FAQ Answers**: For each question: - Restate the question as an H2 heading (optimized for featured snippet phrasing) - Write a 150–250 word answer following: Direct Answer → Context → Example/Caveat → Next Step - Flag any answers that should include a data table or comparison - Add a [Schema Tag] note where structured data should be applied 4. **JSON-LD Schema Markup Block**: Provide complete FAQPage schema markup for all questions. Format in code block. 5. **Internal Linking Plan**: For each answer, suggest one internal link opportunity (anchor text + hypothetical destination). 6. **Meta Description** (under 155 chars): Conversational, benefit-led, includes primary keyword. 7. **Content Freshness Checklist**: List which answers contain time-sensitive information and what to check at the 12-month update. **Anti-patterns:** - Do NOT write answers that just rephrase the question - Do NOT add disclaimers to every answer — only where genuinely needed - Do NOT make answers shorter than 120 words