Skip to content

Google Scholar Scraper for Citation Data

Google Scholar search pages depend on JavaScript and active bot detection.

OUTPUT FORMATSHTMLJSONMarkdown

A hosted scraping API takes over proxy rotation, fingerprint handling and browser rendering so your code only sends a URL and reads back the result. This page explains what the Google Scholar scraper returns, which request options control rendering, geo-routing and extraction, and how credits are consumed.

What a Google Scholar scrape returns

Each Google Scholar result carries a consistent set of paper fields: title, authors, abstract snippet, citation count, publication venue, publication year, and a cited-by URL. The API renders the JavaScript on the page and returns those fields as structured JSON when you supply extraction rules. Teams typically use this for citation analysis, mapping author affiliations into academic networks, or assembling publication dates into research timelines.

Request options that shape the response

A small set of parameters covers most Google Scholar needs. Use this map to pick only the options your task actually requires, since several of them change the credit cost per request.

Worked example: one paper, one request

Suppose you want the metadata for a single paper page. You send the paper's Google Scholar URL with your API key, enable JavaScript rendering, and pass extraction rules that map CSS selectors to field names. The response comes back as parsed JSON containing the title, authors, abstract snippet, citation count, venue, year and cited-by URL. If you would rather describe the fields in plain language than write selectors, the AI extraction option accepts a natural-language specification instead. The same pattern scales to a list of paper URLs: loop over the URLs, keep the field mapping fixed, and store each JSON object alongside the source URL so results stay traceable.

Build or buy: a short decision checklist

Before committing to a self-managed scraper, check the following. If most answers point to the hosted option, the API removes work that is not core to your research or product.

  • Do you already run and maintain a headless browser fleet and rotating proxy pool? If not, the hosted API replaces that infrastructure.
  • Does the target page require JavaScript execution and fingerprint spoofing to load reliably? The API handles both server-side.
  • Do you need geo-specific results? A country code routes the request through a residential IP in that country.
  • Do you need structured output rather than raw HTML? Extraction rules or AI extraction return parsed JSON directly.
  • Do you need to control spend per request? Credit cost varies by option, so choose the minimum set that works.
  • Do you need a specific language stack? SDKs exist for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too.

Two different limits: concurrency vs. target throttling

The API enforces concurrency limits per plan rather than per-target rate limits. That means your ceiling is the number of requests you can have in flight at once, not a fixed number of Google Scholar calls per minute. Separately, Google Scholar itself may throttle aggressive request patterns. If you see throttling, the fix is on your side: space out requests or spread them across multiple sessions. Raising your plan's concurrency will not solve target-side throttling, and spacing requests will not raise your concurrency ceiling.

How credits are consumed

Requests start at one credit each, and options add cost. {{OWNER_CREDIT_COST_PER_OPTION}}. {{OWNER_CREDIT_VALIDITY}}. {{OWNER_FREE_TRIAL_CREDITS}}. {{OWNER_PAID_PLAN_STARTING_PRICE}}. The plan table below lists the published tiers; treat the prices as a dated reference and confirm current pricing before subscribing.

Published plan tiers

The table below reproduces the published plan tiers with their credit allowances, concurrency, and feature availability. Prices are exclusive of VAT. These figures are a dated reference from the original publication and should be checked against current pricing before purchase. {{OWNER_CANCELLATION_TERMS}}

Getting started

Create an account to receive an API key and free trial credits. Install the SDK for your stack, or send a plain HTTP request. Test the request in the dashboard builder first, then move the generated snippet into your codebase. Documentation and per-language code samples are available for each supported language.

Published plan tiers
PlanPrice (per month)API creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$1975,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$991,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices are exclusive of VAT. Figures are a dated reference from the original publication; confirm current pricing before purchase.

Frequently asked questions

How do I handle JavaScript when scraping Google Scholar?

Set render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.

Can I scrape Google Scholar from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.

What's the rate limit for scraping Google Scholar?

The API applies concurrency limits per plan rather than per-target rate limits. If Google Scholar throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Google Scholar?

Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response returns parsed JSON.

Which programming languages can I use to scrape Google Scholar?

Any language. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Use whatever your stack already relies on.

How much does it cost to scrape Google Scholar?

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.