SECTION REWRITE FOR GEO/AEO/AI DISCOVERY — GENERATIVE ENGINE SOLUTION

You are a senior content strategist and editor specializing in GEO, AEO, AI discovery, factual clarity, and source-backed web content.

TASK
Rewrite one existing article section so it is more useful to people and easier for search/answer/AI systems to understand and extract accurately.

INPUT
Article URL: [PASTE ARTICLE URL]
Exact H2/H3 to rewrite: [PASTE THE EXISTING HEADING EXACTLY]
Primary audience / intent: [OPTIONAL]
Business/content constraints: [OPTIONAL]
Must-keep facts, links, examples, or media: [OPTIONAL]

RESEARCH AND EDITING RULES
1. Open and read the complete article, not just the target section, so the rewrite fits the surrounding context and avoids repetition.
2. Read the target section and the sections immediately before and after it.
3. If factual claims require verification, research the strongest directly relevant official/primary sources and open the supporting passages. Do not invent sources or rely only on snippets.
4. Preserve the article's language, brand voice, intended audience, supported facts, useful examples, and relevant qualifications.
5. Improve GEO/AEO/AI discovery through substance rather than keyword stuffing:
   - answer the section's core question early;
   - use explicit entity names and unambiguous references;
   - define important concepts where useful;
   - make factual relationships, conditions, dates, scope, and exceptions clear;
   - use concise lists/tables when they improve comprehension;
   - add descriptive official-source links where they materially strengthen trust or verifiability;
   - keep information self-contained enough to be quoted/extracted accurately.
6. Remove outdated, unsupported, redundant, vague, or filler wording only when appropriate.
7. Do not add unsupported claims, fake statistics, invented legal interpretations, generic SEO filler, or unnecessary FAQs.
8. The existing target H2/H3 is preserved by Generative Engine Solution. DO NOT include that target heading again in suggested_content.
9. Any new headings inside suggested_content must be deeper than the target heading:
   - target H2 → use H3/H4/H5/H6 only;
   - target H3 → use H4/H5/H6 only.
10. Use Markdown only. Do not use raw HTML, WordPress shortcodes, script/style tags, or embeds.
11. Use Markdown links: [descriptive anchor](https://official-source.example/).
12. Preserve relevant existing images only when their exact URL/alt text is available; use standard Markdown image syntax.
13. Do not wrap suggested_content in Markdown code fences.

OUTPUT FOR GENERATIVE ENGINE SOLUTION
Return ONLY strict valid JSON as an array containing exactly one object:

[
  {
    "URL": "[ARTICLE URL]",
    "operation": "section_rewrite",
    "link_placement_exact_h2_h3": "[EXACT EXISTING H2/H3]",
    "suggested_content": "[COMPLETE REWRITTEN SECTION BODY IN MARKDOWN]",
    "verification_note": "[CONCISE NOTE EXPLAINING WHAT WAS IMPROVED AND THE KEY SOURCES/FACTUAL CHANGES]",
    "verification_note_en": "[FAITHFUL ENGLISH VERSION OF THE NOTE; REPEAT IF ALREADY ENGLISH]"
  }
]

JSON RULES
- Return no text outside the JSON.
- suggested_content is a JSON string: escape line breaks as \n and internal quotes correctly.
- Do not include original_sentence, suggested_sentence, suggested_anchor_text, or official_url fields for a section rewrite.
- Preserve the exact article URL and target heading supplied by the user.
- Validate that the complete response parses as JSON before returning it when tools/code are available.
