Skip to content

Google Patents Scraper API

Collect patent details, legal status, and citations through a single API call, then feed structured results into research, product, and competitive-analysis workflows.

OUTPUT FORMATSHTMLJSONMarkdown

The approach below explains what to extract, how to run a request, and which controls affect cost and reliability.

What this API is for

Use this route when you need repeatable access to patent records rather than occasional manual lookups. A scraper API returns rendered HTML for parsing, so your team can focus on analysis instead of browser and proxy management.

A practical decision checklist:

  • Define the records you need: titles, abstracts, filing dates, inventors, assignees, classifications, legal status, and citations.
  • Decide whether pages are static or JavaScript-heavy; enable rendering only when needed because it changes credit use.
  • Choose extraction rules for the exact fields, rather than downloading whole pages for manual parsing.
  • Set country targeting only when regional results matter.
  • Test with a small set of patent URLs first, then scale concurrency after checking output quality.

Use cases worth planning for

Three recurring uses are extracting structured patent information for product decisions, reviewing cited patents to benchmark innovation, and scanning industry-specific trends to spot collaboration opportunities. In each case, the value comes from consistent fields over time, not from a one-off page view.

Workflow and request controls

Manual collection is slow and difficult to scale. The standard workflow is as follows. First, create an account and obtain an API key; the starter-credit allowance and signup terms are set by the account provider and should be checked before you begin: [signup and package details]. Second, add the official Python library to your project so requests can be sent without managing proxies or browsers separately. Third, call the API for a patent detail page and receive rendered HTML ready for parsing and analysis. Fourth, apply advanced features for dynamic elements while keeping control of the workflow. For Google Patents specifically, set custom_google to true. Use country_code to scope results and extract_rules to pull targeted fields. A screenshot option can help you verify how a real browser renders a page when the HTML alone is hard to interpret.

Credits, proxies, and rendering

Credit use depends on the features enabled. Base requests start at 1 credit each. Successful JavaScript-rendering requests cost 5 credits. Premium-proxy requests cost 10 credits without JavaScript rendering or 25 credits with it. Credits are valid for one month and do not roll over. Concurrent requests mean how many requests can run at the same time. Geotargeting can route requests through 200+ countries and territories, with 40+ on classic proxies. Screenshots and extraction rules use CSS or XPath selectors to capture full-page images and structured fields.

Reliability and compliance checks

Proxy rotation and headless-browser rendering help mimic real browsing behaviour and reduce IP-based blocking risk. The platform is described as scaling with thousands of headless browsers and rotating proxies, with typical results in 1-5 seconds even on JavaScript-heavy pages. Personal data is not collected or stored from scraped sites unless explicitly requested, and the service is presented as GDPR and CCPA compliant. For a regulated workload, confirm the current compliance documentation and pricing terms with the account provider before relying on them.

Plan comparison

Before choosing a plan, compare monthly API credits, concurrent requests, JavaScript rendering, rotating and premium proxies, geotargeting, screenshots and extraction rules, priority email support, dedicated account management, and team management. Higher tiers add support and team controls; lower tiers exclude them. Prices, free-credit terms, cancellation terms, and VAT treatment are set by the account provider and should be confirmed before purchase.

Developer experience and related tools

Documentation, code samples in Java, Python, Go, PHP, Curl, and JavaScript, a knowledge base, and support are the main developer-experience items to check. Related guides cover Google Finance, Google Images, and Google Flights scraping, which are useful if your patent workflow also needs search-result or SERP data. AI extraction, JavaScript scenarios, screenshots, and no-code setup are additional options when page structure changes frequently.

Request control map
ControlWhat it changesCheck before scaling
custom_googleHandles Google crawling restrictions for patent pagesConfirm it is set to true on every Google Patents request
country_codeScopes results by countryUse only when regional variation matters
extract_rulesPulls targeted fields with CSS or XPathValidate titles, abstracts, dates, inventors, assignees, and classifications
JavaScript renderingRenders dynamic page contentBudget 5 credits per successful request
Premium proxiesChanges routing and blocking riskBudget 10 credits without rendering or 25 with rendering
ScreenshotsCaptures how a browser renders the pageUse for visual verification, not as a substitute for structured fields

Credit costs and validity are from the captured plan controls; confirm current owner terms before publication.

Frequently asked questions

What is Google Patent?

Google Patents is an online database at patents.google.com holding patents and patent applications. Pulling records from it can support competitor-innovation tracking, technology-trend review, and licensing-opportunity discovery.

What is Google Patent scraper?

It is a tool that pulls information from Google's patent database through an API. Search queries are turned into structured responses so patent information can be retrieved automatically for innovation tracking and intellectual-property research.

Is scraping Google Patents legal?

Scraping a site such as Google Patents may breach its terms of service. Get legal advice on compliance with applicable laws and regulations, obtain permission where required, and consider official APIs for data access where available.

What data can I extract from Google Patents?

Records can include patent titles, abstracts, filing dates, inventor names, assignee names, and patent classifications.

How to scrape Google Patents?

Use an HTML API with the custom_google option set to true to handle Google crawling restrictions. Options such as country_code and extract_rules can narrow requests and target the fields you need.

Does Google Patents have an API?

Google Patents does not provide a public API. Web-scraping tools can be used to extract its data programmatically.