Google Scholar Public Profiles Scraper

Extract normalized data from public Google Scholar profile pages. Version 2 uses Scholar's server-rendered HTML and public structured publication-pagination response, so profile and batch modes normally finish in seconds without launching a browser.

Modes

• profileId: one Scholar user ID or full public profile URL.
• profileIds / profileUrls: deduplicated batch mode.
• query / queries: Scholar's public author-search form, followed by full profile extraction. Google may redirect this route to sign-in in some regions; the Actor reports that restriction and does not bypass it.
• includePublications: false: fast profile-summary mode.
• maxPublications: 0–1,000 publications per profile. Values over 100 use bounded pagination.
• publicationSort: citations or recent.

At least one ID, URL, or query is required. maxProfiles applies across the run and maxProfilesPerQuery applies independently to every query.

Output

Each row is one public profile with a stable Scholar ID, identity fields, verified domain when published, interests, homepage and image URLs, all-time and recent citation metrics, citation history, publication details, co-authors, provenance, and scrape metadata. Empty optional values are omitted; zero metrics and zero citation counts are preserved as valid numeric values.

Proxy and access boundaries

Direct HTTP is fastest for local development, while the cloud input schema defaults to authorized Apify Residential routing because Scholar rejects the tested Apify datacenter IPs with HTTP 403. Custom HTTP proxies are supported. GOOGLE_SERP is intentionally rejected because it supports ordinary Google Search requests, not scholar.google.com profile pages. The Actor does not solve CAPTCHAs, bypass sign-in, access private profiles, or defeat access controls.

Reliability

Responses are checked for status, expected content type, maximum size, challenges, authentication redirects, malformed pagination payloads, and selector drift. Temporary blocking is retried with bounded sessions; missing public profiles can return a clean empty dataset or fail explicitly with failOnNoResults: true. Records are written atomically after the crawl succeeds.