The complete guide to embedding the Product Hunt feed on a website
Product Hunt has been the canonical daily launch feed for the indie maker scene since Ryan Hoover launched it as an email list in late 2013, and it remains the discovery surface that founders, investors, reporters, and tool collectors check first thing in the morning more than a decade later. After AngelList acquired Product Hunt in 2016, the platform institutionalized the daily Product of the Day cadence, the weekly Top 10 aggregation, the monthly cat-themed Best Of badges, the Golden Kitty Awards at year end, and a topic taxonomy that now spans more than 50 categories from AI Agents to Web3 to No-Code. The product hunt feed widget is how editorial sites, maker dashboards, investor scout tools, and tech newsletters surface that daily launch leaderboard inside their own surface area, instead of forcing readers and team members to context-switch to producthunt.com every morning. This guide is specifically about the FEED widget (the discovery feed of new launches across the platform), not the reviews widget (which embeds a single product's upvote count and Maker comment thread for indie SaaS founders post-launch). The two widgets serve completely different jobs. This guide walks through what actually matters when you choose and configure a Product Hunt feed widget in 2026: the practical difference between the official Product Hunt RSS feed (which is a flat chronological list with no ranking) and a real third-party feed widget that pulls live ranked data from the Product Hunt API v2 GraphQL endpoint, why daily and weekly feed cadences matter for different reader contexts, the role of topic and Collection feeds in editorial workflows, the Hunter and Maker layer that makes Product Hunt distinct from any other launch platform, the dominance of AI launches on the daily leaderboard from 2024 onward, and the operational consideration of GraphQL complexity budgeting on multi-feed dashboards. The guide is opinionated where it matters because the wrong feed configuration on the wrong page wastes the reader attention you fought for in the first place.
04
Schema.org ItemList markup, Lighthouse, and editorial-page pagespeed on multi-feed dashboards
Editorial sites and scout dashboards routinely embed two, three, or four Product Hunt feeds on the same page. The daily Product of the Day in the sidebar, the topic-filtered AI Agents feed in the main content well, the weekly Top 10 in the secondary rail, and a Hunter Watchlist in the footer is a common pattern for a tech newsletter homepage. Naive iframe-based or React-bundled feed widgets break this pattern because each embedded feed adds a noticeable Performance, LCP, or CLS hit, and four feeds on a page can drop a Lighthouse Performance score from 95 to 60 on a Ghost or Substack template. Poper handles this with a single shared script tag that bundles all feeds on a page into one async runtime, lazy-loading the visual rendering as each feed scrolls into view. The widget ships under 40 KB gzipped for the runtime regardless of how many feeds are on the page, so a single-feed sidebar embed and a four-feed dashboard pay essentially the same pagespeed cost. Schema.org ItemList markup is auto-injected for each feed (a single ItemList per embed, with each launch as a ListItem with Product or SoftwareApplication typing), so search engines can crawl your curated feed as structured data rather than as opaque JavaScript-rendered content. This matters for editorial SEO: a tech newsletter homepage with a properly-marked-up daily Product of the Day feed gives Google a crawlable signal of fresh structured content updating daily, which feeds the Discover and News surfaces. The widget also handles the case where Product Hunt renames a topic (the AI to AI Tools and AI Agents split in 2024 broke many third-party widgets that hard-coded the old topic slug) by gracefully falling back to the parent topic and surfacing a one-line builder warning so the site owner can update the configuration. Validate your Lighthouse score before and after embedding using PageSpeed Insights at pagespeed.web.dev, and validate the Schema.org markup using the Rich Results Test at search.google.com/test/rich-results. Both should pass with no warnings on a properly configured embed.