Convert Your Existing FAQ to FAQPage JSON-LD

Act as a structured-data engineer. I'll paste my existing FAQ. Convert it to paste-ready FAQPage JSON-LD, tighten the answers for AI citation, and warn me about anything that would make the markup invalid.

Context: page URL [https://YOUR-DOMAIN.COM/...] · business / what we do [SENTENCE] · brand tone [warm-expert / no-nonsense / playful / premium / technical / friendly-everyday]

Existing FAQ (any format — headings, bullets, table, HTML):
[PASTE]

Answer rewrite rules: first sentence is the answer · 40-90 words · contains a specific fact, number, or example · factually defensible · matches the tone.
Keep question wording as-is unless a question is over 12 words or contains jargon — flag those for my approval instead of changing them silently.

Output:
1. Audit table: # · Question (issue if any) · Answer length · Answer issue · Action (keep / rewrite / split / cut)
2. Rewritten visible FAQ in markdown
3. Complete <script type="application/ld+json"> FAQPage block — JSON-valid, paste-ready
4. Validation and deploy notes — if I pasted HTML, every microdata attribute (itemscope, itemtype, itemprop) to remove so JSON-LD stands alone; answers where you guessed a fact; compound questions to split; where to check the block: the Schema.org validator at https://validator.schema.org; and one plain sentence telling me that Google stopped showing FAQ rich results on 7 May 2026, so this markup will not change how my page looks in Google results

Success means the JSON-LD questions match the visible FAQ word for word, and no fact in an answer is one I didn't give (flag the ones you had to assume).

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response — every section filled in, nothing deferred to a follow-up.

If a required input is missing, ask for it once before starting; otherwise proceed and label any assumption you made.

Notes: R40 refresh; tuned to vendor prompting guidance