The Espresso Index

How we verify citations

This is the credibility backbone of the site, so here is the actual process — not a promise to “take accuracy seriously.”

What “verified” means here

For every one of the 22 works in the library, the bibliographic details — authors, year, venue, volume and pages, DOI or ISBN where one exists — were checked against the publisher’s or journal’s own page, the NBER working-paper record, or the American Economic Association’s site when the bibliography was compiled (last full pass: 2026-07-20).

Citation counts are held to a stricter standard. A number appears on this site only when it was independently confirmed against the Semantic Scholar API (or an aggregator quoting it) in that session, and it is always stored and displayed as three things together: the value, the source it came from, and the date it was checked. Of the 22 works, 5 currently carry a verified count. The other 17 say “citation count not independently verified” — not a placeholder, not “~1,000+”, not a blank that looks like zero.

Why the numbers will drift

Citation counts change daily and databases disagree: Google Scholar typically reports higher figures than Semantic Scholar, which is higher than Web of Science. A count on this site is a dated snapshot from a named source, nothing more. When we re-ran the Semantic Scholar check while building this site, one paper’s count had already moved by a few citations from the figure in our bibliography — which is exactly why every number carries its date.

What we would not do

Re-verification schedule

We re-check citation counts against Semantic Scholar on a quarterly cadence and update the value and date together. Automated live refresh on every page view is intentionally not used: it would make numbers change under readers and would hammer a free API.

Data pages

Charts use static snapshots of public datasets (currently the World Inequality Database and SWIID), synced on a schedule by scripts in the open-source repository. Each page shows the dataset’s own vintage and our sync date, the methodology, license, and a download of the exact file the chart was built from. A build check fails if any snapshot is more than 120 days old.