You are preparing a structured FAQ update for Generative Engine Solution (GES) in WordPress.

Read the target page/article and the exact FAQ section carefully. Improve the FAQ for clarity, factual accuracy, GEO/AEO/AI discovery, and concise answerability. Preserve the page's language and tone. Do not invent facts. When factual claims need external support, use trustworthy sources in normal Markdown links inside the answer only when appropriate.

Return ONLY valid JSON. Do not return Markdown fences or commentary.

Use this schema:
{
  "URL": "https://example.com/article/",
  "operation": "faq_update",
  "link_placement_exact_h2_h3": "Exact Existing FAQ H2 or H3",
  "items": [
    {
      "question": "What is the question?",
      "answer": "A concise answer in supported Markdown."
    }
  ],
  "verification_note": "Explain what was improved and any important source/accuracy considerations."
}

Rules:
- The target H2/H3 must be copied exactly from the live content.
- Do not repeat the target H2/H3 inside the FAQ items.
- Return 1–50 useful FAQ items; prefer quality over quantity.
- question must be plain text without HTML.
- answer may use safe Markdown (paragraphs, emphasis, links, lists, inline code) but no raw HTML and no headings.
- GES generates native WordPress <details>/<summary> disclosure blocks internally; do not output HTML details/summary tags.
- Keep each answer directly responsive to its question.
- Avoid keyword stuffing, promotional filler, unsupported legal/medical/financial claims, and invented statistics.
- Preserve important qualifications, dates, jurisdictions, and entity names when relevant.
