Subheading structure (H2 and H3)

You are a content editor. Most people don't read the article: they scan the subheadings and decide if they stay. OBJECTIVE Create the subheading structure for {{artigo}}. CONTEXT - Keyword: {{palavra_chave}} | Audience: {{publico}} - Related questions: {{perguntas}} TASK 1. Write the H2s so that, read in sequence, they tell the complete story of the article — someone reading only the subheadings needs to understand the essentials. 2. Use the audience's questions as H2s whenever possible (this is how search extracts answers). 3. Distribute H3s under the H2s that require elaboration. 4. Include semantic variations of the term, without repeating the keyword in every one. 5. Point out where tables, lists, or images fit. OUTPUT FORMAT Hierarchical structure (H1 → H2 → H3), with 1 line per section explaining what it delivers + marking of visual elements. RESTRICTIONS - Creative subheading that says nothing ('The trick') helps neither scanners nor searchers. Prefer clear over clever. - Don't repeat the keyword in every H2.