Wikipedia Scraper: Articles & Pageview Trends

Wikipedia articles plus the daily traffic data behind them.

Why pageviews are the point

Article text is freely downloadable in bulk, that part isn't hard. Per-article daily traffic is the valuable half: how many people looked up a company, a drug, a candidate, a film or a product, day by day, going back to 2015.

That's a free demand signal, and it's what this Actor is really for.

Field	Example
totalViews	184,203
averageDailyViews	6,140
peakViews, peakDate	31,502, 2026-07-14
trendPercent	+42.8, second half of the window vs the first

Set includeDailyPageviews: true to also get one row per day for charting.

Article content

Field	Example
title, displayTitle, description	Python (programming language), General-purpose programming language
extract	the lead summary
fullText	complete article as plain text, up to 40,000 chars (includeFullText)
image, thumbnail
latitude, longitude	for places
pageId, url, lastModified, isDisambiguation

Example input

{
  "titles": ["Tesla, Inc.", "Rivian"],
  "includePageviews": true,
  "pageviewDays": 90,
  "includeDailyPageviews": true
}

Don't know the exact title? Use searchQueries and the Actor resolves matches for you.

Any language

language: "de" reads German Wikipedia, with German pageviews. Works for he, fr, es, ja, ru and every other edition, and comparing traffic for the same topic across languages is a genuinely useful geographic signal.

Who this is for

• Market & trend research: public attention on a brand, product or person over time
• Finance: attention spikes on a company, dated to the day
• SEO & content: what people actually look up, and whether it's growing
• AI / dataset builders: clean article text with no HTML parsing
• Journalists: when did interest in this topic spike, and by how much

Article data and pageview analytics in one row

Two official Wikimedia APIs, no key on either:

You want	Source	Input
An article by exact title	the Wikipedia REST summary API	titles
Articles matching a keyword	the Wikipedia search API	searchQueries
How many people read it	wikimedia.org/api/rest_v1 pageviews	includePageviews

Per article: title, summary, full plain text when includeFullText is on, description, main image, coordinates for anything with a location, the canonical URL, and the page ID.

Pageview analytics is the half most tools skip. With includePageviews you get total views over your window, the daily average, the peak day and its count, and a trend direction, so an article is a time series rather than a snapshot. includeDailyPageviews returns the day-by-day series itself.

Any language edition via language: en, he, de, fr, es, it, ru, ja, zh, ar, pt, nl, pl, and the rest. Pageviews are counted per edition, so the same subject in two languages is two genuinely different audiences and comes back as two rows.

Notes

• Pageview data starts in 2015 and lags by about a day, so the window always ends yesterday.
• Pageviews are keyed to the exact article title. The Actor resolves your input to Wikipedia's canonical title first, so redirects and casing are handled.
• includeDailyPageviews multiplies your row count by the window length, 90 days × 10 articles is 900 extra rows. It's off by default for that reason.
• includeFullText costs one extra request per article.
• Set a max charge per run in the run options for a hard spend ceiling. The Actor honors it and stops cleanly.

Pricing

Pay per result. One row = one article (or one day of pageviews). Articles that don't exist come back as error rows and are not charged.