How to Scrape ProductHunt Launch Data and Maker Profiles (2026)

The article is ready. here’s the full markdown body — paste it directly into WordPress:

—

If you want to scrape ProductHunt, 2026 is the best time to do it carefully: the site still renders server-side HTML for launch pages, but it gates maker profiles and comment threads behind a GraphQL API that rotates tokens every 24 hours. here is what actually works, at scale, without getting soft-banned.

what ProductHunt exposes and where

ProductHunt’s public surface has three layers worth scraping:

• launch pages (producthunt.com/posts/): server-rendered HTML, no auth required, contains upvote count, tagline, topics, launch date, and maker usernames
• GraphQL API (producthunt.com/frontend/graphql): the real data layer, used by the SPA; returns full maker profiles, review counts, discussion threads, and gallery assets
• maker profiles (producthunt.com/@username): partially server-rendered, but follower counts and “made” product lists are injected client-side via GraphQL

The HTML layer is stable and crawlable. the GraphQL layer requires a bearer token extracted from the page’s __NEXT_DATA__ blob or from the Authorization header in browser devtools. that token is tied to a session, not your IP, so rotating proxies alone won’t keep you alive if you reuse a stale token.

extracting the bearer token and GraphQL schema

Every ProductHunt page embeds a JSON blob in a