04
DiscussionForumPosting schema and how Hacker News content surfaces in Google
In late 2023, Google launched the Discussions and forums search feature and the Forum filter, both of which surface threads from Reddit, Hacker News, Stack Exchange and similar discussion sites prominently. Hacker News threads now appear regularly in commercial-intent and technical-decision queries on Google, often outranking the brands the threads discuss. The technical mechanism is Schema.org's DiscussionForumPosting markup, which Google specifically rewards with rich-result eligibility. The Poper Hacker News Feed Widget emits DiscussionForumPosting JSON-LD for every story it renders, with author (the HN username), datePublished (the story timestamp converted to ISO 8601), upvoteCount (HN points), commentCount (descendants from the Firebase payload), articleBody (the title plus URL or the self-text for Show HN and Ask HN posts) and a sameAs link back to the canonical news.ycombinator.com/item URL. The result is that your embedded HN block is eligible for the same Discussions rich-result treatment as Hacker News itself, which is meaningful for product-comparison pages, dev-tool landing pages, indie maker portfolios and tech blog archives. The only widget catch is that Google requires the embedded content to clearly attribute Hacker News as the source. The Poper widget does that by default with a 'via Hacker News' link in each thread footer pointing to the canonical item URL. Disabling that attribution voids both the schema spec and HN's content policy, so it is not a configurable option.