A look at Paul Bradshaw's Scraping for Journalists — what it teaches, where it has aged, and whether it still earns a place on a reporter's shelf in 2026.
Long before "data journalism" had its own conference circuit, Paul Bradshaw wrote a book to convince reporters that they could get data off the web themselves — no computer-science degree required. Scraping for Journalists, first self-published on Leanpub in 2012 and updated iteratively since, remains one of the most approachable on-ramps into gathering data from the web for people who do not think of themselves as programmers. This review covers what the book does well, where time has caught up with it, and what to pair it with today.
What the book is
Bradshaw is a British journalist and academic (he founded the MA in Data Journalism at Birmingham City University and writes the long-running Online Journalism Blog). The book reflects that background: it is practical, newsroom-minded, and relentlessly focused on getting a usable dataset rather than on elegant code.
Its central bet is that scraping is a gradient, not a cliff. The early chapters start with techniques "no more complicated than a spreadsheet formula" and build up, one small step at a time, toward genuinely powerful extraction. Crucially, it was published on Leanpub's iterative model — released in stages, expanded and corrected in response to reader feedback — so it grew from a handful of chapters toward a fuller book over time, with the opening chapter offered as a free download.
The through-line is a real reporting mindset: find the data, get it into a table, clean it, and interrogate it for a story. That framing has aged far better than any specific tool it names.
What it teaches
The book walks a non-programmer up the ladder of scraping techniques, roughly:
- Spreadsheet formulas — using Google Sheets functions like
IMPORTHTMLandIMPORTXMLto pull tables and lists off a page without writing a line of code. Still one of the fastest ways to grab a simple HTML table. - Browser tools and extensions — point-and-click scrapers and helpers (the book uses the era's "Scraper" Chrome extension and OutWit Hub) to select and export data visually.
- Cleaning and refining — using OpenRefine (which the book calls by its old name, Google Refine) to de-duplicate, cluster messy values, and reshape data into something analyzable.
- Stepping up to code — a gentle introduction to more programmatic scraping for the pages that simple tools can't handle, plus the vocabulary (HTML structure, patterns, queries) a reporter needs to talk to a developer.
Along the way it teaches "computer-page literacy" — reading a page's structure, understanding what a query is doing — which is the transferable skill that outlasts any particular app.
Strengths
- It removes the fear. For a reporter who has never scraped anything, the graduated approach genuinely works. You get a win in chapter one and keep getting them.
- Task-first, not tool-first. Every technique is tied to getting a real dataset for a real story, which is exactly how newsroom learning sticks.
- Cheap and updatable. The Leanpub model means the price is low and the author can (and did) revise it, so it never froze at a single moment in time.
- A bridge to developers. Even reporters who never write code come away able to specify what they need and understand what is possible — valuable when you brief a technical colleague or a scraping service.
Weaknesses — and where it has aged
Being honest about a 2012-rooted book in 2026:
- Some named tools have moved or died. OutWit Hub still exists; "Google Refine" is now OpenRefine; the specific Chrome "Scraper" extension has been superseded by newer point-and-click tools (Web Scraper, Instant Data Scraper, Data Miner). ScraperWiki, a staple of that era's data-journalism tutorials, is gone. Treat tool-specific steps as illustrative, not gospel.
- The web got harder to scrape. Much data now loads via JavaScript and sits behind anti-bot defenses and CAPTCHAs that a spreadsheet formula can't touch. The book's gentle techniques still work on plenty of pages, but the modern reality often needs headless browsers or a hidden-API call.
- It is a primer, not a production manual. As the original scraping.pro review noted, it doesn't pretend to cover scheduled, large-scale business extraction — pagination at volume, proxies, monitoring, storage. That's simply out of scope.
None of this sinks the book; it just means you read it for the approach and supplement the specifics with current tools.
Companion reference: The Data Journalism Handbook
If Scraping for Journalists teaches the how-to of getting data, The Data Journalism Handbook explains the why and the workflow around it — and the two pair naturally.
Released in 2012 as a free, open-source book by the European Journalism Centre and the Open Knowledge Foundation (with a print edition from O'Reilly), the Handbook collects how leading newsrooms turn raw data into stories. Its well-known poster — composed by Liliana Bounegru and Lulu Pinney, following the book's own design — lays out the whole data pipeline on a single sheet: from getting raw data, through understanding and cleaning it, to delivering it to an audience as stories, visualizations, or apps. It's a genuinely useful wall chart for orienting a newcomer to where scraping fits in the larger process (scraping is the "getting" stage; the story is everything after).
Worth knowing: a fully rewritten Data Journalism Handbook 2 (edited by Bounegru and Jonathan Gray) followed years later and is freely readable online at datajournalism.com. Between them, the Handbooks give the strategic map and Scraping for Journalists gives the field skills.
Who should read it in 2026?
- Reporters and researchers new to data who want to stop asking others for spreadsheets and start building their own — this is still an excellent first book.
- Students on journalism or communications courses who need practical, low-intimidation exposure to scraping and cleaning.
- Non-technical analysts in any field (not just newsrooms) who occasionally need to pull structured data off a web page.
Who should skip it: developers who already scrape for a living, and anyone who needs scheduled, large-scale extraction — for that you want a modern engineering stack (or an outsourced pipeline), not a beginner's primer. If you want a broader shelf, see our roundup of the best web scraping books.
Verdict
Scraping for Journalists has dated in its specific tools but not in its philosophy. Its core lesson — that anyone willing to learn a few techniques can liberate data from the web, one small step at a time — is as true now as it was in 2012, and the graduated, story-first approach is still the best way to bring a nervous beginner up to speed. Read it for the mindset and the ladder of techniques; update the tool names as you go (OpenRefine, current browser extensions, a headless browser when JavaScript gets in the way); and keep the Data Journalism Handbook nearby for the bigger picture.
And when a story needs data at a scale that beginner tools can't reach — thousands of pages, a schedule, sites that fight back — that's where a done-for-you data-as-a-service pipeline picks up: you keep the reporting, we handle the extraction and hand over clean, structured data.