Tutorial

How to Scrape Google Scholar with TypeScript

Step-by-step guide to scraping Google Scholar search results using TypeScript and the Scavio API. Get paper title, authors, citation count as structured JSON.

Google Scholar contains valuable data — paper title, authors, citation count, abstract snippet, and more. Scraping this data directly means dealing with anti-bot detection, CAPTCHAs, IP rotation, and constantly breaking selectors. The Scavio API handles all of that and returns clean, structured JSON from a single POST request.

This tutorial shows you how to scrape Google Scholar using TypeScript and the Scavio API. By the end, you will have a working TypeScript script that fetches real-time Google Scholar data and parses the results.

Prerequisites

  • TypeScript installed on your machine
  • A Scavio API key (free tier includes 500 credits/month — no credit card required)

Step 1: Install Dependencies

Install fetch to make HTTP requests:

Bash
npm install typescript tsx

Step 2: Make Your First Google Scholar Search

Send a POST request to the Scavio Google Scholar API endpoint with your query. The API returns structured JSON with paper title, authors, citation count, and more.

const API_KEY = "your_scavio_api_key";

interface GoogleScholarResult {
  search_metadata: { status: string };
  organic_results: Array<{ position: number; title: string; link: string; snippet: string }>;
}

const response = await fetch("https://api.scavio.dev/api/v1/search", {
  method: "POST",
  headers: {
    "x-api-key": API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ query, tbs: "" }),
});

const data: GoogleScholarResult = await response.json();
for (const result of data.organic_results?.slice(0, 5) ?? []) {
  console.log(`${result.position}. ${result.title}`);
  console.log(`   ${result.link}\n`);
}

Step 3: Example Response

The API returns structured JSON. Here is an example response for a Google Scholar search:

JSON
{
  "search_metadata": { "status": "success" },
  "organic_results": [
    {
      "position": 1,
      "title": "Retrieval-Augmented Generation for Large Language Models: A Survey",
      "link": "https://scholar.google.com/scholar?hl=en&q=retrieval+augmented+generation",
      "authors": ["Y. Gao", "Y. Xiong", "X. Gao"],
      "publication_year": 2024,
      "cited_by": 1240,
      "snippet": "We survey RAG approaches that combine parametric and non-parametric memory..."
    }
  ]
}

Every field is structured and typed — no HTML parsing, no CSS selectors, no regex extraction. Your TypeScript code can access any field directly.

Step 4: Full Working Example

Here is a complete, runnable TypeScript script that searches Google Scholar and prints the results:

/**
 * Scrape Google Scholar search results with full type safety.
 * Run with: npx tsx google-scholar-search.ts
 */

const API_KEY = process.env.SCAVIO_API_KEY!;

interface GoogleScholarResult {
  search_metadata: { status: string };
  organic_results: Array<{ position: number; title: string; link: string; snippet: string }>;
}

async function searchGoogleScholar(query: string): Promise<GoogleScholarResult> {
  const response = await fetch("https://api.scavio.dev/api/v1/search", {
    method: "POST",
    headers: {
      "x-api-key": API_KEY,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({ query, tbs: "" }),
  });

  if (!response.ok) {
    throw new Error(`Scavio API error: ${response.status}`);
  }

  return response.json();
}

const results = await searchGoogleScholar("retrieval augmented generation 2024");
console.log(JSON.stringify(results, null, 2));

Why Use Scavio Instead of Scraping Google Scholar Directly?

  • No proxy management. Direct scraping requires rotating proxies to avoid IP bans. Scavio handles all of this server-side.
  • No CAPTCHA solving. Google Scholar aggressively blocks automated requests. Scavio returns clean data every time.
  • Structured JSON output. No HTML parsing or CSS selector maintenance. Get typed, consistent data from every request.
  • Multi-platform in one API. Search Google, Amazon, YouTube, and Walmart from the same API key with the same authentication pattern.
  • Free tier included. 500 credits/month with no credit card required. Each search costs 1 credit.

Frequently Asked Questions

Scraping publicly available data from Google Scholar is generally legal, but you should review Google Scholar's Terms of Service. Using the Scavio API avoids the legal gray areas of direct scraping since Scavio handles all data collection through proper channels and returns structured results via API.

Direct scraping of Google Scholar requires managing proxies, CAPTCHAs, rate limits, and anti-bot detection. The Scavio API handles all of this for you. Send a POST request with your query and get structured JSON back — no proxy management or browser automation needed.

The Scavio API returns structured JSON with paper title, authors, citation count, abstract snippet, publication year. All data is returned in a clean, consistent format that is easy to parse in TypeScript.

Scavio offers a free tier with 500 credits per month. Each API request costs 1 credit regardless of which platform you search. No credit card required to start. Paid plans start at $30/month for higher volumes.

Scavio returns Google Scholar results in 1-3 seconds on average. Results are fetched in real time from Google Scholar — there is no caching layer or stale data. Every request returns live results.

Start Scraping Google Scholar with TypeScript

Get your free Scavio API key and start fetching Google Scholar data in TypeScript. 500 free credits/month — no credit card required.