Two of our guide pages are instructions and one is a list, so only one of them emits a HowTo

Try this: curl -s https://pub-trivia.app/guides/how-to-host-a-pub-quiz \ | grep -o '"@type":"HowTo"' # "@type":"HowTo" curl -s https://pub-trivia.app/guides/pub-quiz-round-ideas \ | grep -o '"@type":"HowTo"' # nothing Two pages in the same cluster, built from the same component, with the same metadata pipeline behind them. One of them is a numbered procedure a reader follows from start to finish. The other is a list of ideas you pick from. Only the first one is a HowTo, and the restraint is the part of structured data that is actually hard. We run a 72 page marketing site for quiz software. There are six JSON-LD builders behind it, and the rule they all follow is one sentence long. Every builder is fed the data the page renders Structured data has one rule that matters more than the schema itself: it must describe what is visibly on the page. Every builder here takes the same data the page renders from, so the two cannot disagree: a FAQ block and its `FAQP