Reddit Historical Archive Scraper - Old Posts by Date

Reddit Historical Archive Scraper — Old Posts & Comments by Date (No API)

Scrape years of old Reddit posts and comments by date — content that Reddit's own search and listings can no longer reach. This Reddit historical scraper queries the Arctic-Shift archive (a maintained Pushshift successor, indexed into 2026) with PullPush.io as a fallback, so you can pull deep history, full-text search comment bodies, reconstruct entire threads and dump complete user histories. Point it at subreddits, post IDs, usernames, search terms or raw Reddit URLs and get clean, flat rows. Fast, no browser, no Reddit login, no API key, no client secret, no proxy.

🏆 Why this Reddit historical scraper?

Posts + comments in flat rows · thousands of records per run · full-text comment search Reddit itself can't do · date-bounded windows going back 10+ years · export to JSON / CSV / Excel. The unofficial Reddit / Pushshift API alternative for archival, research, AI training corpora and brand monitoring.

---

✨ What this Actor does / Key features

• 🗓️ Deep historical reach — the archive backends index Reddit content from its early years to the present, so you can pull posts and comments many years old, well beyond Reddit's own search depth and listing limits.
• 🔎 Full-text comment search — search inside archived comment bodies, something Reddit's native search cannot do (it only matches post titles). Find every comment ever made mentioning a brand, term or phrase across Reddit history.
• 🧵 Full thread reconstruction — fetch a single post by ID together with all of its archived comments as a flat list with a reconstructed depth field.
• 👤 Complete user histories — pull a username's submitted posts and/or comments across their entire archived Reddit history.
• 📅 Precise date + score filters — narrow with afterDate / beforeDate (ISO YYYY-MM-DD) and a minScore threshold for time-bounded or high-engagement slices.
• 🔀 Flexible targeting — mix and match subreddits, post IDs, usernames, post search queries, comment search queries and raw Reddit URLs (auto-detected) in a single run.
• 🧱 Flat, tidy rows — every post or comment is one row with a type field (post or comment), ready for spreadsheets, warehouses and LLM pipelines.
• 🛡️ No-block backends — Arctic-Shift (primary) and PullPush (fallback) work over a direct connection with polite rate limiting, retries and exponential backoff. No login, OAuth, API key, client secret or proxy required (a proxy toggle exists for extra robustness).

🚀 Quick start (3 steps)

1. Configure — fill in any combination of Subreddits, Post IDs, Usernames, Post Search Queries, Comment Search Queries or raw Reddit URLs. Optionally add a date window, a minimum score, a sort and item caps.
2. Run — click Start. The Actor queries the archive, paginates each target and saves each post or comment as one flat row.
3. Get your data — open the Output tab and export to JSON, CSV, Excel, HTML, XML or JSONL, or pull it via the Apify API and webhooks.

📥 Input

Fill in at least one target (subreddit, post ID, username, search query or URL). Everything else is optional.

Example — a subreddit's top posts in a date window

{
  "subreddits": ["wallstreetbets"],
  "afterDate": "2021-01-01",
  "beforeDate": "2021-02-28",
  "sort": "top",
  "minScore": 100,
  "maxItems": 1000
}

Example — every comment mentioning a brand (full-text search)

{
  "commentSearchQueries": ["Notion"],
  "afterDate": "2024-01-01",
  "sort": "new",
  "maxItems": 2000
}

Example — a user's full post + comment history

{
  "usernames": ["spez"],
  "userContent": "overview",
  "maxItemsPerTarget": 500
}

Example — one post with its entire archived comment tree

{
  "postIds": ["1abc234"],
  "maxItems": 0
}

Field	Type	Description
subreddits	array	Subreddit names to scrape historically (no /r/ prefix). Each runs as a listing scrape.
postIds	array	Reddit post IDs (the alphanumeric part in /comments/XXXX/). Each post is fetched with all of its archived comments.
usernames	array	Reddit usernames (no /u/ prefix). Returns historical posts and/or comments per userContent.
searchQueries	array	Full-text search across archived posts (title + selftext), combinable with dates, subreddit and score filters.
commentSearchQueries	array	Full-text search across archived comment bodies — a unique feature Reddit's own search cannot do.
startUrls	array	Any Reddit URL — subreddit, post, user or search. Type is auto-detected; mix URL types freely.
sort	string	new (newest archived first) or top (highest score first). hot, rising, controversial, best are Reddit-algorithm-specific and fall back to new.
afterDate / beforeDate	string	ISO date bounds (YYYY-MM-DD or full ISO timestamp) for time-window queries.
minScore	integer	Only return posts/comments at or above this score (upvotes − downvotes).
userContent	string	For usernames: overview (posts + comments), submitted (posts only) or comments (comments only).
maxItems	integer	Global hard cap across all targets. 0 = unlimited.
maxItemsPerTarget	integer	Cap per subreddit / post / user / search so one big target doesn't eat the budget.
requestDelayMs	integer	Milliseconds between requests to stay under archive rate limits (default 1200).
maxRetries	integer	Retry attempts with exponential backoff on 429 / 5xx / timeout (default 5).
proxyConfiguration	object	Optional. Backends are no-block on direct connection; route through Apify Proxy for extra robustness.

Tip: to search comment bodies (impossible on Reddit itself), use commentSearchQueries. To pull a deep subreddit window, list the subreddit and set afterDate + beforeDate. To rebuild a full thread, pass its postIds — the comment tree comes back flat with a reconstructed depth.

📤 Output

Posts and comments come back as flat dataset rows, each with a type field (post or comment). Here is a trimmed sample — a post followed by a comment:

{
  "type": "post",
  "id": "l6omga",
  "fullname": "t3_l6omga",
  "subreddit": "wallstreetbets",
  "subredditNamePrefixed": "r/wallstreetbets",
  "author": "DeepFuckingValue",
  "title": "GME YOLO update — Jan 28 2021",
  "selftext": "…",
  "url": "https://www.reddit.com/r/wallstreetbets/comments/l6omga/…",
  "permalink": "/r/wallstreetbets/comments/l6omga/…",
  "domain": "self.wallstreetbets",
  "isSelf": true,
  "over18": false,
  "score": 234512,
  "upvoteRatio": 0.94,
  "numComments": 18422,
  "flairText": "YOLO",
  "createdUtc": "2021-01-28T14:03:11.000Z",
  "retrievedUtc": "2026-07-06T12:00:00.000Z"
}

{
  "type": "comment",
  "id": "gkz1abc",
  "fullname": "t1_gkz1abc",
  "parentId": "t3_l6omga",
  "linkId": "t3_l6omga",
  "subreddit": "wallstreetbets",
  "author": "diamond_hands_42",
  "body": "To the moon 🚀🚀",
  "score": 8123,
  "depth": 0,
  "controversial": 0,
  "gilded": 2,
  "permalink": "/r/wallstreetbets/comments/l6omga/_/gkz1abc/",
  "createdUtc": "2021-01-28T14:11:52.000Z",
  "edited": false,
  "distinguished": null
}

Additional output fields

These fields are also present in the dataset:

Field	Type	Description
_userContext	string	Requested username attached to user-content rows.
isGallery	boolean	Whether a post is a Reddit gallery.
isSubmitter	boolean	Whether a comment author submitted the linked post.
linkPermalink	string	Archived permalink of the post linked to a comment.
linkTitle	string	Archived title of the post linked to a comment.
scoreHidden	boolean	Whether Reddit marked the comment score as hidden.
_searchQuery	string	Search query
authorFullname	string	Author fullname
flairCss	string	Flair css
locked	boolean	Locked
preview	array	Preview
spoiler	boolean	Spoiler
stickied	boolean	Stickied
subredditId	string	Subreddit id
thumbnailHeight	number	Thumbnail height
thumbnailWidth	number	Thumbnail width

🌐 Sources, and what each one can answer

This Actor reads the Arctic-Shift archive, the maintained Pushshift successor, which indexes Reddit posts and comments into 2026.

What you ask for	Where it comes from
A subreddit's posts	Arctic-Shift
A post and its comment tree	Arctic-Shift
A user's posts and comments	Arctic-Shift
A text search scoped to a subreddit or author	Arctic-Shift
A text search with no scope	Reddit's search feed, hydrated through Arctic-Shift
A comment text search with no scope	Not available — scope it (see below)

Scoping a search. Arctic-Shift only runs a text search that names a subreddit or an author, and it is both faster and deeper than the unscoped path. You can put the scope in the query itself:

shoes subreddit:malefashionadvice
shoes author:someuser

Unscoped post searches still work — they go through Reddit's own search feed and are filled back out through the archive, so the rows carry the same columns. Unscoped comment searches are not served by any free archive any more; the run will tell you so immediately rather than returning nothing.

PullPush. This Actor used to fall back to PullPush. PullPush has withdrawn free API access and now answers every request with "this website does not provide free scraping resources", from any network. It is no longer used, and no proxy setting brings it back.

Proxies. Leave Apify Proxy on its default. Each source is contacted over the network that actually answers it — measured, not assumed — and a refused exit IP is swapped for a fresh one within a quarter of a second, up to four times, before the run tries a different route. Choosing the residential group by hand is rarely necessary and costs more bandwidth.

💡 Use cases

• Historical research & archival — collect a subreddit's posts and comments going back years for longitudinal study of a community.
• Academic & journalism work — pull date-bounded windows of Reddit discussion around an event, topic or brand.
• AI / NLP training corpora — build domain-specific datasets from years of niche-subreddit text and comment threads.
• Brand & reputation monitoring — full-text search every comment ever made mentioning your brand or product — something Reddit's own search cannot do.
• Account & thread analysis — pull a user's entire post and comment history, or fetch a single post with its complete archived comment tree.
• Sentiment & trend backfills — reconstruct how discussion of a topic evolved across a precise date range.

👥 Who uses it

Academic researchers & social scientists · data journalists · AI / NLP & ML teams building corpora · brand, PR & reputation analysts · quantitative & market researchers · community managers & moderators · OSINT and trend analysts.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the posts and comments you extract, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

Is it legal to scrape Reddit history? The Actor collects publicly available archived Reddit content. You are responsible for using the data in compliance with Reddit's terms, the archive providers' terms and applicable laws such as GDPR.

Does Reddit (or Pushshift) have a public API for old data? Reddit's own API and search only reach shallow, recent content, and Pushshift is no longer openly available. This Actor instead queries the Arctic-Shift archive (a maintained Pushshift successor indexed into 2026) with PullPush.io as a fallback — no API key needed.

Is this a Pushshift alternative? Yes. It covers the same deep Reddit history Pushshift used to serve, via Arctic-Shift (primary) and PullPush (fallback), with no API key.

Do I need an API key, a login or a proxy? No. The scraper uses public archive APIs over a direct connection — no Reddit account, OAuth, API key, client secret or proxy required. A proxy toggle is available for extra robustness but is off by default.

Can I scrape Reddit without an API key or login? Yes. It reads public archive APIs directly, so no Reddit account, OAuth, API key, client secret or proxy is required to pull old posts, comments or full user history.

How far back can I scrape / how much data can I get? The archive backends index Reddit content from its early years to the present, so you can pull posts and comments many years old — thousands of records per run, well beyond Reddit's own search depth. Use maxItems and maxItemsPerTarget to control volume and cost.

Can I search inside comment bodies? Yes — use commentSearchQueries for full-text search across archived comments. Reddit's native search only matches post titles, so this finds every comment mentioning a term across Reddit history.

How do I export old Reddit posts and comments to CSV or JSON?

Run the scraper, then download the dataset as CSV, JSON, Excel, HTML, XML or JSONL straight from the Apify Console, or pull it through the API. Every post and comment is a flat row, so it imports cleanly into spreadsheets and databases.

How do I scrape a subreddit's posts from a specific year?

List the subreddit and set afterDate and beforeDate in YYYY-MM-DD format to pull a bounded historical window, far deeper than Reddit's own listing limits allow.

How do I download a Reddit user's full post and comment history?

Add the username to usernames and set userContent to overview to return both their submitted posts and comments across their entire archived Reddit history.

How do I find every Reddit comment mentioning a brand?

Use commentSearchQueries to run a full-text search across archived comment bodies — something Reddit's own search cannot do — and pull every comment mentioning your brand or product.

🔗 More social media scrapers by logiover

Building a wider social dataset? Pair this with the rest of the logiover social-media suite:

Platform	Actor
🔴 Reddit	Reddit Search Scraper · Reddit Subreddit Scraper
💼 LinkedIn	LinkedIn Profile Scraper · LinkedIn Company Scraper
▶️ YouTube	YouTube Channel Scraper · YouTube Comments Scraper
🎵 TikTok	TikTok Hashtag Video Scraper
🟠 Hacker News	Hacker News Search Scraper
📸 Instagram	Instagram Media Downloader
🧵 Threads	Threads Scraper
📌 Pinterest	Pinterest Scraper
✉️ Substack	Substack Newsletter Scraper

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Schedule this Actor on Apify to keep a fresh archive of a subreddit, topic or brand mention. Export results to JSON, CSV or Excel, sync to Google Sheets, or push to your database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to build automated monitoring and research pipelines.

🤖 AI Agents, MCP & RAG Integration

Reddit Historical Archive Scraper works natively as an on-demand data tool for AI assistants and autonomous workflows.

Connect this Actor directly to Apify AI, Claude Desktop, Cursor, VS Code, Windsurf, LangChain, or LlamaIndex via the official Apify MCP Server — no custom wrapper code needed:

{
  "mcpServers": {
    "apify": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=logiover/reddit-historical-archive-scraper"
    }
  }
}

• Schema-typed inputs & outputs: Clean JSON records with explicit .actor/input_schema.json and .actor/output_schema.json definitions so LLM agents infer parameters and parse fields accurately without HTML noise.
• Bounded & predictable runs: Built-in volume caps and pay-per-result budget guards prevent runaway agent tool loops.
• RAG & automation ready: Stream run datasets straight into vector stores, n8n, Make, Zapier, or webhook pipelines.

💬 Support, Issues & Reviews

• Bug reports & target-site changes: Hit an unexpected empty result or selector change? Open a ticket in the Issues tab with your Run ID or sample input — we actively monitor issues and ship fixes fast.
• Feature & field requests: Need an additional data attribute or filter? Request it in the Issues tab.
• Enjoying this Actor? If it saved you engineering time, please consider leaving an honest review on Apify Store or bookmarking logiover/reddit-historical-archive-scraper — organic developer feedback helps others discover reliable tools and keeps maintenance prioritized.

⚖️ Legal

This Actor extracts only publicly available archived data and is intended for legitimate research, analytics and monitoring use. You are responsible for complying with Reddit's terms of service, the archive providers' terms, GDPR and any applicable local laws.

---

This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Reddit Historical Archive; Reddit Historical Archive and all other trademarks mentioned here are the property of their respective owners.

Reddit scraping — frequently asked questions

Do I need a Reddit API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Reddit data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Reddit scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the rows you care about really do change that fast.

How many rows can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

Is scraping Reddit legal?

This Actor collects only information that Reddit publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Reddit blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

📝 Changelog

2026-11-11

• Added reliable terminal run status telemetry and structured Apify AI / MCP Server (mcp.apify.com) tool configuration.
• Added direct Issues & Reviews support links and refreshed live maintenance verification.

2026-11-01

• Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
• README refreshed: 2 links to renamed Actors updated, 2 links to retired Actors removed; independence disclaimer added; documented 16 additional output fields.

2026-10-15

• Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
• A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
• A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
• Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
• The prefilled example for maxItems is now 666 (was 120).

2026-09-24 (later)

Search works again. PullPush has closed, and the request layer was asking the wrong network for each host.

A search for a plain word like shoes failed on the first query with HTTP 429, and the run's advice — switch to the residential proxy group — was wrong. Measured from three separate networks (a home connection, Apify's datacenter pool and Apify's residential pool), PullPush answers every free request with "this website does not provide free scraping resources". It is not an IP block, so no proxy group restores it. PullPush is now dropped from a run the moment it says so, instead of being retried for six minutes.

• Unscoped searches work again. Arctic-Shift only runs a text search that is scoped to a subreddit or author, and PullPush was what served the unscoped ones. Those queries now go through Reddit's own search feed, and the post ids it returns are hydrated back through Arctic-Shift — so a searched post carries exactly the same columns as a listed one, not a thinner row.
• Each host is now asked over the network that answers it. Measured from inside the platform, three attempts per combination: Arctic-Shift answers the platform's own egress every time and refuses the shared datacenter pool, while Reddit's feed does the reverse — it rate-limits the platform's address within a request or two and is content with a proxied one. Requests now start on the route that works for that host and fall through to the others if it stops.
• A refused exit IP is swapped immediately rather than waited out. Apify's shared pools contain addresses these hosts have already refused; the previous code backed off 5, 10, 20, 40 and 60 seconds on the same kind of refusal, which cannot help — the address is no better a minute later. A 403 now draws a fresh IP within 250ms, up to four times, before changing route. Genuine rate limiting (429) still backs off, because there the address is fine and the pace is not.
• A 2xx carrying a block page no longer counts as success. Arctic-Shift answered some proxied requests with Reddit's own block page; parsing that as JSON threw an ordinary error, which left the run reporting SUCCEEDED with zero rows. An unparseable or HTML body is now treated as a refusal, and a run that saves nothing because every target failed now fails loudly whatever the cause.
• Searches can carry their own scope. shoes subreddit:malefashionadvice or shoes author:someuser is read out of the query and sent straight to Arctic-Shift, which is faster and deeper than going via the feed.
• Unscoped comment search says so up front. No archive still serves a comment text search without a subreddit or author scope. That target now reports what to add instead of running for minutes and returning nothing.
• Records are de-duplicated per target, so a page boundary can no longer bill the same post twice.
• Two IP rotations now happen even at maxRetries: 0. Drawing a clean address is not the same as hammering a source that has refused us — and the source that has, PullPush, is no longer retried at all.

Measured after the change, from the platform: the reported failing input (shoes, from 2026-09-01, 5 items, maxRetries: 0, default proxy) returns 5 rows in 15-24 seconds across four consecutive runs.

2026-09-24

Investigated the seven columns reported as empty — the extraction is correct; the shipped example was the problem. selftext, authorFlairText, media, galleryImages, edited, distinguished and suggestedSort were all mapped to the right source fields. They came back empty because the Actor's prefilled example ran r/technology, a subreddit that shares nothing but external links. Verified against the live archive: of 100 recent r/technology posts, 0% are self posts, 0% carry flair, 0% carry media or galleries, and 0% are distinguished or have a pinned sort. There is nothing there to extract.

• Changed the prefilled example from ["technology"] to ["personalfinance", "wallstreetbets", "pics"] at 40 posts each, so a first run actually exercises the schema: post bodies, flair, media, galleries, pinned sorts and moderator posts all appear. Measured against the live archive these subreddits return selftext on 55.8%, authorFlairText on 31.7%, suggestedSort on 33.3%, galleryImages on 10.0% and media on 2.5% of a 120-row run — every one of them zero before.

• edited and distinguished stay near zero on recent posts by nature: the archives snapshot a post within minutes of publication, and moderator posts are rare in ordinary traffic. Both fill properly once you query a historical window, which is what this Actor is for — a run over r/announcements and r/AmItheAsshole before 2024-01-01 returns edited on 26.2% and distinguished on 48.8% of rows.

• Documented, in the README and in each field's description, exactly which post type each of these columns depends on, so an empty column is recognisable as "this subreddit has no such posts" rather than a broken scrape. Fixed silent data loss on any subreddit containing a gallery post. The dataset schema declared galleryImages as a string while the Actor has always emitted an array of image objects. Pushing a single Reddit gallery post therefore failed schema validation and aborted that whole subreddit — every remaining row for it was lost, and the run still reported success. Verified on a live run before the fix: r/wallstreetbets and r/pics both died with "Schema validation failed" and contributed 0 of their 40 rows. galleryImages is now declared as an array and those targets complete. This also explains part of why galleryImages looked empty in audits: the rows that would have carried it were the exact rows being rejected.

• isGallery was emitted as undefined for non-gallery posts, so the column vanished from exports entirely instead of reading false. It now defaults to false.

• No change to the parsers, the backends or the set of output columns. Nothing was removed: every one of the seven columns is real Reddit data that fills for the right subreddit.

2026-09-23

• Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
• Output verified on a live run: 40 columns returned, 80.8% of cells populated.
• Run reliability reviewed: 91.4% of public runs succeeded in the last 30 days.
• Input schema, output schema and pricing configuration reviewed.
• Noted that 7 column(s) came back empty in this sample (selftext, authorFlairText, media, galleryImages, edited, distinguished and others); these are under review.

2026-09-01

• Fixed the most common cause of a failed run. The Reddit archive backends block Apify's datacenter egress, and the run used to stop and tell you to switch the Proxy input to RESIDENTIAL by hand — after you had already lost the run. It now escalates to RESIDENTIAL automatically the first time a request chain is exhausted by blocks, and retries. Datacenter is still tried first, so a run that works on it is unchanged.
• A run is still failed loudly, with the reason, if even residential is blocked — a total block never masquerades as an empty result.

2026-08-01

• Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
• Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
• Expanded the dataset contract to 54 nullable and exhaustive post/comment fields, corrected media/gallery/upvote types, and removed non-emitted user/subreddit profile views and claims.
• Added a stable archived-thread variation that exercises comment body, parent/link IDs, vote fields, and reconstructed depth.
• Stopped treating replies with omitted ancestors as top-level comments; depth is now null when the capped archive result cannot prove the ancestor chain.

2026-08-01 — Health-check remediation

• Added the full typed comment contract, including body, parent/link IDs, vote fields and reconstructed depth, plus a thread-targeted health-check input that exercises comment rows.
• Stopped misclassifying replies as top-level comments when a capped archive result omits their parent; unknown depth is now null.
• Corrected post media/gallery/upvote schema types and removed dataset views that advertised user/subreddit profile metrics the Actor does not emit.
• The final four-input matrix verdict will be appended after post-build cloud revalidation.

2026-07-06

• ✨ README overhaul: richer post + comment output samples, ready-to-run example scenarios, cross-promo links, and clearer quick-start.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
• Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
• Added ready-to-run example tasks that cover common real-world use cases.

2026-06-15

• Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.

2026-06-07

• Docs: added coverage for using the scraper as a Pushshift alternative, exporting old Reddit posts and comments to CSV/JSON, and scraping Reddit data without an API key or login.

2026-06-05

• SEO and documentation refresh; metadata corrected to describe the Arctic-Shift primary backend with PullPush fallback (not PullPush alone).
• Verified live and rebuilt.

---

*Maintained: last verified 2026-11-11 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).