Skip to main content
Thirdwatchthirdwatch
Social & news

Compare Hacker News Scraper Side by Side

Compare Hacker News Scraper Side by Side — a practical guide with a ready-to-run configuration and structured output.

Editorial illustration for social & news
Sep 16, 2026 · 2 min read · 452 words
View the Apify scraper →

Need to compare hacker news scraper across targets? Thirdwatch's Hacker News Scraper turns it into structured rows — the fields you need, ready to export.

Skip the setup: Run this as a ready-to-go task on Apify — pre-loaded with the configuration from this guide.

Why Compare side by side works

Put the same fields side by side for every target — the deltas are where decisions happen. This guide shows the configuration that pulls hacker news scraper data from Hacker News Scraper.

How does this compare to the alternatives?

Manual copy-paste works for a handful of rows; dedicated per-site scrapers on other platforms either gate the same data behind sign-in or charge flat monthly fees regardless of usage.

Why this Actor

  • Purpose-built for Hacker News Scraper — no generic crawling config to tune
  • Pay-per-result pricing — you pay only for rows that come back
  • Structured output ready for JSON/CSV export or API consumption
  • No login, cookies, or API keys needed for the public surfaces it reads

How to do it in 3 steps

Step 1: Configure the input

Set the inputs as shown below — feeds takes the targets, and the optional fields bound the run size.

Step 2: Run the Actor

Run it from the console, the API, or the linked saved task. One dataset row is written per record.

Step 3: Use the output

Every row carries the fields shown in the sample — export as JSON, CSV, or feed it straight into your pipeline.

{
  "feeds": [
    "top"
  ],
  "maxResultsPerFeed": 50,
  "includeComments": false,
  "maxCommentsPerStory": 10
}

Each dataset row looks like:

{
  "id": 49771110,
  "type": "story",
  "feed": "top",
  "rank": 1,
  "title": "Exfiltrate Your Weights",
  "text_html": null,
  "author": "RohanAdwankar",
  "score": 452,
  "comment_count": 174,
  "child_ids": [
    49774661,
    49771331,
    49772710,
    49774638,
    49771905,
    49774220,
    49774470,
    49771459,
    49771634,
    49771298,
    49771451,
    49771357,
    49771281,
    49772843,
    49773339,
    49773581,
    49772101,
    49772446,
    49771791,
    49772132,
    49771301,
    49774315,
    49772902,
    49773626,
    49771654,
    49772688,
    49772353,
    49771588,
    49772381,
    49772111,
    49771681,
    49771835,
    49771361,
    49771267,
    49772246,
    49772492,
    49771945,
    49773399,
    49773313,
    49772422,
    49771705,
    49772589,
    49771598,
    49773889,
    49771431,
    49771751
  ],
  "parent_id": null,
  "parent_story_id": null
}

What to watch for

Rate the targets reasonably — large batches benefit from modest concurrency. Source sites may throttle heavy bursts; retry once and widen filters if a target surface is thin.

Related use cases

Run the Hacker News Scraper on Apify Store — pay per result, free to try, no credit card to test.

Frequently asked questions

What does Hacker News Scraper return?

One dataset row per result — with the fields shown in the sample output. Export as JSON, CSV, or Excel.

How do I control run size?

`feeds` selects the targets and the max/limit fields bound how many rows come back. Start small, then scale.

Can I run this on a schedule?

Yes — save it as a task and attach a schedule in Apify Console for daily/weekly pulls.

Is this data public?

The Actor collects publicly visible data only — the same information a logged-out visitor sees.

What formats can I export?

JSON, CSV, Excel, XML, or direct API access to the dataset — plus webhooks and integrations.

What if a run returns fewer rows than expected?

The source limits some results; retry once, and widen the query or filters if the target surface is genuinely thin.

Related