faq-schema
Skill1 starsChanged 54 days agoMITView on GitHub
Turn a page into question/answer pairs an AI will pick from, and generate the matching FAQPage JSON-LD. Use this whenever the user wants an FAQ section, FAQ schema, question-answer content for AI, or wants a page to answer the specific questions buyers ask. Point Claude at a URL and it derives real questions the page should answer, writes the answers, and outputs the markup.
In this repository9 other files it gives its agents.
- bing-checkSkill
- buyer-questionsSkill
- citation-checkSkill
- content-capsuleSkill
- crawler-checkSkill
- entity-coverageSkill
- llms-txtSkill
- retrievabilitySkill
- schema-builderSkill
The file
Files
faq-schema
AI answers are questions-and-answers by nature. A page structured as real Q&A gives the model clean pairs to lift — and the FAQPage markup makes the structure explicit.
Steps
- Fetch the page and understand what it's about and who it's for.
- Derive the real questions a buyer or reader would ask about this topic — not generic filler. Draw them from: what the page implicitly answers, related searches, and how people actually phrase things (use the
buyer-questionsskill for deep mining). Aim for 5–8 genuine questions. - Write each answer as a self-contained 40–80 word passage, answer-first (see
content-capsule). Each answer must stand alone. - Generate
FAQPageJSON-LD with each question/answer pair.
Output format
First, the human-readable FAQ section (H2 "Frequently asked questions", each question an H3, answer below).
Then the JSON-LD:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "[The question]",
"acceptedAnswer": { "@type": "Answer", "text": "[The self-contained answer]" }
}
]
}
</script>Honest note for the user
Google removed FAQ rich results for most sites in May 2026, so don't expect the star-studded search snippet. The value now is different and real: clean Q&A pairs are highly quotable by ChatGPT/Perplexity/Gemini, and the markup helps AI Mode parse them. Ship it for AI visibility, not for Google rich results.
Built by Raphaël Aubry, founder of Howseen (https://howseen.ai). Writing the answers is one-shot. Seeing which of your answers AI actually surfaces — and when a rival's answer replaces yours — is what Howseen tracks. → https://howseen.ai
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

