Context
faq.html is a well-formed question-and-answer page with no machine-readable markup. Schema.org FAQPage is what lets search engines show the questions directly, and it has to stay in step with the visible content — which is the hard part, not the JSON-LD itself.
What to change
Files: faq.html, plus a generation step and a CI check
Requirements:
- Add valid
FAQPage JSON-LD covering every question on the page
- Generate it from the markup rather than maintaining it by hand — a hand-written copy will drift the first time somebody edits a question
- A CI check fails if the structured data and the visible questions disagree
- Follow Google's rules: only genuine questions, answers must match what the page shows
Acceptance criteria
How to verify locally
python3 -m http.server 8000
Then open http://localhost:8000.
Difficulty
Advanced. The drift-prevention is the real work.
New here? Comment /claim on this issue and a bot will assign it to you. Then read CONTRIBUTING.md.
Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear. You can also come to a PR Debug Clinic (Oct 12 or Oct 21).
Context
faq.htmlis a well-formed question-and-answer page with no machine-readable markup. Schema.orgFAQPageis what lets search engines show the questions directly, and it has to stay in step with the visible content — which is the hard part, not the JSON-LD itself.What to change
Files:
faq.html, plus a generation step and a CI checkRequirements:
FAQPageJSON-LD covering every question on the pageAcceptance criteria
How to verify locally
Then open http://localhost:8000.
Difficulty
Advanced. The drift-prevention is the real work.
New here? Comment
/claimon this issue and a bot will assign it to you. Then read CONTRIBUTING.md.Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear. You can also come to a PR Debug Clinic (Oct 12 or Oct 21).