Google Patents Search Scraper

Google Patents Search Scraper exports public patent search results and patent detail metadata from Google Patents queries, URLs, or publication IDs.

Use it for prior-art discovery, assignee monitoring, inventor research, competitive IP landscaping, and structured patent datasets for analysis.

At a glance

• Extracts: patent ID, title, URL, snippet, inventor and assignee data, key dates, jurisdiction/status hints, classifications, citations, PDF URL, and scrape timestamp when available.
• Inputs: Google Patents queries, direct patent URLs or IDs, maximum records, detail enrichment toggle, and optional proxy settings.
• Best for: IP research, R&D monitoring, patent landscape snapshots, competitive intelligence, and API-based patent collection.
• Exports: Apify dataset rows downloadable as CSV, JSON, Excel, or available through the API.
• Login: no Google account, cookies, or Google API key are required.

Ready-to-run examples

Use these saved Store examples as starting points. Open any example to prefill the Actor input, then adjust URLs, keywords, limits, or filters for your own run.

• Run multiple Google Patents searches at once
• Fast Google Patents search export
• Build an EV charging patent dataset
• Search AI medical imaging patents
• Extract metadata from Google Patents URLs
• Extract metadata from patent IDs
• View all ready-to-run examples (10 examples)

What can it do?

• Export Google Patents search results: run public patent queries and save structured rows for analysis.
• Enrich known patent IDs: pass publication IDs or patent URLs to collect detail-page metadata.
• Monitor assignees and inventors: use Google Patents query operators to track companies, inventors, technologies, or date ranges.
• Collect IP research fields: save titles, assignees, inventors, dates, abstracts, classifications, citations, PDF URLs, and source links when available.
• Use as a patent data API workflow: run from Apify API, export CSV/Excel/JSON, schedule repeat searches, or expose the Actor to AI agents through Apify MCP.

Common workflows

• Search by assignee or inventor: use Google Patents operators such as assignee:(Company) or inventor:(Name).
• Build patent landscape samples: run broad technical queries with a small maxItems, then expand once the query is right.
• Enrich known IDs: paste publication IDs or Google Patents URLs into patentUrls and enable details.
• Collect API-ready patent rows: schedule repeat runs and export dataset rows into BI, notebooks, or internal databases.

Input configuration

Setting	JSON key	Description
Search queries	queries	Google Patents search strings. You can use natural language or Google Patents syntax such as assignee:(Tesla), inventor:(Smith), before:2024, or after:2020.
Patent URLs or IDs	patentUrls	Direct Google Patents URLs or publication IDs such as US7654321B2. These are processed before query results.
Maximum patent records	maxItems	Maximum rows to save across all queries and direct inputs.
Include detail-page metadata	includeDetails	Fetch each patent detail page to add richer metadata such as abstracts, citations, classifications, PDF URLs, and additional dates.
Proxy configuration	proxyConfiguration	Optional Apify Proxy settings. Leave disabled for normal public runs; enable only if Google returns temporary errors from your network.

Example input

{
  "queries": ["assignee:(Tesla) battery"],
  "patentUrls": ["US7654321B2"],
  "maxItems": 10,
  "includeDetails": true,
  "proxyConfiguration": { "useApifyProxy": false }
}

Output fields

Field	Description
query, rank	Search query and saved result rank, or null for direct patent inputs.
patentId, patentUrl, patentTitle	Normalized patent identifier, Google Patents URL, and title when available.
snippet, abstract	Search snippet and detail-page abstract when available.
inventor, inventors	Primary inventor string and parsed inventor list.
assignee, assignees	Primary assignee string and parsed assignee list.
priorityDate, filingDate, publicationDate, grantDate	Patent dates when returned by search or detail pages.
applicationNumber, publicationNumber	Patent application and publication numbers when available.
language, status, jurisdictions	Public language/status/jurisdiction hints from Google Patents data.
classifications, citations	Detail-page classification and citation values when enrichment finds them.
pdfUrl, thumbnailUrl	Public PDF and thumbnail URLs when exposed by Google Patents.
source, scrapedAt	Whether the row came from search or direct detail input, plus scrape timestamp.

Example output

{
  "query": "assignee:(Tesla) battery",
  "rank": 1,
  "patentId": "US7654321B2",
  "patentUrl": "https://patents.google.com/patent/US7654321B2/en",
  "patentTitle": "Example battery patent title",
  "inventors": ["Example Inventor"],
  "assignees": ["Example Assignee"],
  "publicationDate": "2026-01-01",
  "classifications": ["H01M"],
  "pdfUrl": "https://patents.google.com/patent/US7654321B2/en.pdf",
  "source": "search",
  "scrapedAt": "2026-07-03T09:00:00.000Z"
}

Pricing

This Actor uses paid events from .actor/actor.json.

Event	When charged	Price
start	Once when a run starts	$0.005 per run
item	Each patent search or detail record saved to the dataset	BRONZE $0.000053848 per saved patent record, about $0.053848 per 1,000 saved records

Only saved patent rows are charged as item events. A run that starts but saves no patent rows can still incur the start event.

Tips for best results

• Start with small limits: test a query with 5-10 records before collecting larger samples.
• Use Google Patents syntax: assignee, inventor, date, and quoted phrase operators can make results much cleaner.
• Enable details when you need richer fields: detail enrichment is slower but can add abstracts, classifications, citations, and PDF URLs.
• Use direct IDs for known patents: patentUrls is the cleanest path when you already have publication numbers.

Limits and caveats

• Detail fields depend on page availability: some patents do not expose every date, citation, PDF, or classification in the same way.
• No full claims extraction: this Actor collects search/detail metadata. It does not parse every claim or the full legal description text.
• Google can throttle: if you see temporary errors, lower volume or enable an appropriate proxy configuration.
• Patent data is informational: verify important legal conclusions against official patent offices or counsel.

API usage

Run from the Apify API or SDK with the same input keys shown above.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/google-patents-search-scraper').call({
  queries: ['assignee:(Tesla) battery'],
  maxItems: 10,
  includeDetails: true
});
console.log(run.defaultDatasetId);

MCP and AI agents

For AI agents, use the official Apify MCP server. The focused single-Actor URL is:

https://mcp.apify.com?tools=fetch_cat/google-patents-search-scraper

The default MCP server can search and run Actors. The focused URL exposes this Actor directly to clients that support tool-scoped MCP connections.

FAQ

Can I search by assignee or inventor? Yes. Use Google Patents query syntax such as assignee:(Tesla) or inventor:(Smith).

Can I scrape a list of patent IDs? Yes. Put publication IDs or Google Patents URLs in patentUrls.

Should I enable detail enrichment? Enable it when you need abstracts, PDF URLs, classifications, citations, or additional dates. Disable it for faster search-result snapshots.

Why are some fields empty? Google Patents does not expose every field for every record, and detail fields require available detail pages.

Can I export to CSV, Excel, JSON, or API? Yes. Use Apify dataset exports or the dataset API after the run finishes.

Related actors

• Google Scholar Profiles Scraper
• Google News Scraper
• Google Play Apps Scraper
• Google Ads Transparency Center Scraper

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.

Changelog

• 2026-07-04 - Feature: Launched Google Patents Search Scraper on Apify Store (APIA-1222)
  • This actor is now publicly available at https://apify.com/fetch_cat/google-patents-search-scraper.

0.1

• Initial public release with Google Patents query search, direct patent ID/URL inputs, optional detail enrichment, paid event pricing, and dataset output support.