Google Patents Scraper — New Patent Alerts avatar

Google Patents Scraper — New Patent Alerts

Pricing

from $2.80 / 1,000 patents

Go to Apify Store
Google Patents Scraper — New Patent Alerts

Google Patents Scraper — New Patent Alerts

Search Google Patents by keyword, assignee, inventor, CPC class and office — publication number, title, abstract excerpt, assignee, inventor, priority/filing/publication/grant dates and Google's family legal stage where computed. Monitoring mode: only-new patents. $0.004 per patent, no start fee.

Pricing

from $2.80 / 1,000 patents

Rating

0.0

(0)

Developer

Magnova

Magnova

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

Every new patent publication worldwide, as clean structured records — search the whole Google Patents corpus by keyword, assignee, inventor, CPC class or office, with a monitoring mode that delivers only what's newly published.

Google Patents indexes patent publications from more than 100 patent offices — tens of thousands of new documents publish every week, and the firms that watch them (competitors filing, technologies emerging, portfolios moving) pay hundreds of dollars a month for watch services. This Actor reads Google Patents through the same public search endpoint its own search page uses (no API key, no login) and turns it into flat, analysis-ready records: publication number, title, abstract excerpt, assignee, inventor, the priority / filing / publication / grant dates, and Google's family legal stage for the patent's office.

It is built scraper-first, with monitoring as a mode: your first run pulls the current corpus for your slice (a keyword, a competitor's assignee name, a CPC class), and scheduled runs after that deliver only the patents you haven't seen — the new-publication alerts that snapshot patent scrapers never offer.

Sample output

A real record, as delivered:

{
"recordType": "PATENT",
"publicationNumber": "AU2026208139A1",
"patentUrl": "https://patents.google.com/patent/AU2026208139A1/en",
"patentTitle": "Selective extraction of lithium from clay minerals",
"abstractSnippet": "SELECTIVE EXTRACTION OF LITHIUM FROM CLAY MINERALS Processes for extracting lithium from a clay mineral and compositions thereof are described. The extraction process includes providing a clay mineral comprising lithium, mixing a cation source with the clay mineral, performing a high-energy mill …",
"office": "AU",
"kindCode": "A1",
"isGrant": false,
"language": "en",
"priorityDate": "2020-01-03",
"filingDate": "2026-07-27",
"publicationDate": "2026-08-13",
"inventor": "Turner Boris CALDWELL",
"assignee": "Tesla, Inc.",
"familyLegalStage": "ACTIVE",
"familyCountryStatus": [
{ "countryCode": "WO", "stage": "NOT_ACTIVE" },
{ "countryCode": "US", "stage": "ACTIVE" },
{ "countryCode": "CN", "stage": "ACTIVE" },
{ "countryCode": "AU", "stage": "ACTIVE" },
{ "countryCode": "MX", "stage": "UNKNOWN" }
],
"matchedQueries": ["solid state battery"]
}

What you get

Each delivered record (recordType: "PATENT", charged) carries:

FieldWhat it is
publicationNumberThe publication's stable number as published by its office (e.g. US12438891B1, EP4270591A1) — the dedupe key
patentUrlThe publication's page on Google Patents
patentTitleThe patent title, cleaned of search highlight markup (on at least 95% of records)
abstractSnippetThe abstract excerpt exactly as indexed by Google Patents — a search snippet that can end mid-sentence; the full abstract lives on the patent page (on at least 85% of records)
office / kindCodeThe publishing office's two-letter code, and the publication number's WIPO kind-code suffix (B1, A1, S1, …) shipped raw — kind-code meanings are office-specific, so no label is invented for them
isGranttrue when the publication is a granted patent (it carries a grant date), false for application publications
priorityDate / filingDate / publicationDate / grantDateThe register dates (filing date on at least 95% of records; priority date where the publication claims priority — first filings claim none) — grant date only on grants
inventorThe first-listed inventor, exactly as published (on at least 90% of records) — a publication can name more inventors; the search index returns the first
assigneeThe primary assignee, exactly as published (on at least 90% of records)
familyLegalStageGoogle's family-level legal stage for this patent's office — ACTIVE, NOT_ACTIVE or UNKNOWN. Present where Google has computed the family's status: usual for grants and multi-office families, often absent on brand-new first filings. It is a family indicator — a pending application reads ACTIVE — not the document's precise legal status
familyCountryStatusThat family stage for every office in the family: a list of {countryCode, stage}
matchedQueriesKeyword runs only: the query that surfaced this patent
languageThe document's language code as indexed

Every run ends with one SUMMARY record (never charged): how many publications matched, how many were read, delivered, skipped as duplicates or out of window, and whether the run stopped at a cap. If Google Patents cannot be read, the run writes one ERROR record plus the summary instead of pretending there were no new patents — and in monitoring mode the state is not advanced, so the next run catches up.

What is never in a record: contact data. Patent registers publish inventor and assignee names, and those ship exactly as published — but the source carries no emails, phone numbers or addresses, and if an email address ever appeared inside a text value it would be stripped before the record ships.

Three ways to run it

1. Corpus (default). A run delivers the matching publications for its publication window — the last backfillDays complete publication days (default 7), or an explicit dateFrom/dateTo range (up to 366 days). This is the first-run sale: pull a month of a competitor's publications, a quarter of a technology class, and analyse them offline.

2. Monitoring mode. Select one of your key-value stores in the Monitor state store input and schedule the run (daily or weekly — patent offices publish on weekly cycles). The first run delivers the window's patents as a charged baseline; every later run delivers only patents the store hasn't seen. Set Start monitoring silently (monitorOnlyNew) to skip the baseline: the first run just remembers the current patents, and you receive only what appears afterwards. Patents a run couldn't deliver (cap reached, timeout) stay unseen and are delivered by the next run.

3. Cursor mode. Hold your own state in Make, Zapier or your scheduler: pass publishedSince (an ISO date) and each run delivers patents published on or after that date — stateless incremental, no store needed. Publication dates are day-granular, so the cursor compares by day, boundary-inclusive, and the window is enforced on every record's own publication date: nothing older than the cursor is ever delivered or charged. (Google assembles its result sets per search, so a cursor run can surface in-window patents that a different, broader search's own capped result set didn't happen to include — the cursor is exact about dates, Google is approximate about sets.)

One source limit, honestly: Google serves at most about 1,000 results per search. A very broad search (say, "machine learning" over a quarter) tops out near that cap per query — the SUMMARY flags it (queryCapReached). Narrower filters, several keyword queries (each is its own search), or split date windows reach deeper corpora.

Inputs

InputWhat it does
queriesKeyword searches, one search per entry (up to 10); every other filter applies to each
assigneesAssignee name filter (OR) — organisation names as published
inventorsInventor name filter (OR) — Google's inventor name search
cpcCodesCPC class filter (G06N, G06N20/00, H04L9/00, …)
officesPatent-office filter (US, EP, WO, CN, JP, …)
backfillDaysPublication days back from yesterday (default 7, max 92)
dateFrom / dateToExplicit window (overrides backfillDays; max 366 days)
publishedSinceStateless cursor: patents published on/after this date
monitorStoreYour key-value store for only-new delivery
monitorOnlyNewSkip the charged baseline; start silently
maxResultsCap on delivered (charged) patents per run (prefilled 250, max 5,000)
maxTotalChargeUsdHard stop for the run's charges

Filters within one field combine with OR, fields combine with AND — Google's own search semantics. CPC codes work as a filter; a record does not list the patent's CPC classifications (the search index doesn't return them — they live on the patent page), and this listing doesn't pretend otherwise.

Pricing

$0.004 per patent delivered — that's $4.00 per 1,000 patents (SILVER $0.0034, GOLD+ $0.0028), no start fee.

Not charged: duplicates and already-seen patents, results outside your window, results with no usable publication date, silently seeded patents (monitorOnlyNew first runs), ERROR records and the SUMMARY. A scheduled monitoring run on a day with nothing new costs nothing.

Worked example: watching four competitors' assignee names on a weekly schedule, surfacing roughly 800 new publications a month, costs about $3.20 a month. A one-off 1,000-patent landscape pull costs $4.00 once.

Examples

New machine-learning publications from the last 7 days (a typical corpus pull):

{ "queries": ["machine learning"], "backfillDays": 7, "maxResults": 250 }

Daily monitoring of one assignee's new publications, started silently, with your store attached:

{ "assignees": ["Toyota"], "backfillDays": 3, "monitorOnlyNew": true, "monitorStore": "<your key-value store>" }

A technology-class corpus for one quarter:

{ "cpcCodes": ["G06N20/00"], "dateFrom": "2026-05-01", "dateTo": "2026-07-31", "maxResults": 5000 }

Google Patents API

This Actor is the no-code way to work with Google Patents' public search index: it handles the query syntax, the 100-per-page pagination up to Google's per-search cap, cross-search and cross-run dedupe, window and cursor enforcement, and family-status flattening for you. Compared with snapshot patent scrapers, you get the same index data — plus the delta: only-new delivery and a cursor mode the website tools don't offer.

Searching trademarks instead?

Patents and trademarks are different registers. If your watch is brand-side — new trademark filings, owners, classes — use Magnova's USPTO Trademark Search, which reads the official USPTO trademark register. Honest trade-off: that one covers US trademarks only, from the register itself; this one covers patent publications from 100+ offices via Google's index. Invention-side, you're home here; brand-side, that's your actor.

Use cases

  • Competitive intelligence: watch rivals' assignee names and get only their new filings and grants — never the same corpus twice.
  • Patent-watch services & agents: build client alerts on the monitoring mode instead of re-pulling whole searches weekly.
  • Technology scouting: follow a CPC class or keyword field; a weekly digest of what just published.
  • Portfolio & freedom-to-operate triage: corpus pulls by assignee, office and window, with family stage per office for first-pass screening.
  • AI agents: structured, deduped patent data with stable IDs, ready for pipelines and RAG — call it via the Apify API or MCP like any other Actor.

Using this Actor with AI agents (MCP)

The Actor is agent-ready: every input and output field is described, the example input runs as-is, and a single call with the prefill works zero-shot. Typical agent flow: run once with your filters for the corpus, then schedule runs with a monitor store and consume only the new PATENT records; stop conditions are explicit (stoppedByMaxCharge, stoppedByResultCap, streamComplete, queryCapReached in the SUMMARY).

FAQ

Is this official patent data? The publications are official patent-office documents; Google Patents is Google's public index of them. Legal-stage fields are Google's own computed family indicators — useful for triage, not a legal conclusion (Google says the same about its status data).

Does it need an API key or account? No. The search index is public and logged-out, and the Actor needs no Google account, login or key — and neither do you.

Why did my first monitoring run deliver so much? That's the baseline: the current window delivered once, so later runs can deliver only what's new. Prefer to start from zero? Turn on Start monitoring silently.

Why did a broad search stop around 1,000 results? That's Google's per-search serving cap, not this Actor's — the SUMMARY's queryCapReached flag tells you when it happened. Split the window or narrow the filters to go deeper.

Why is a patent's CPC classification not in its record? The search index filters by CPC but doesn't return a document's classifications; those live on the patent page (one click from patentUrl). Rather than fetch a multi-megabyte page per patent, the record ships what the index genuinely returns.

How fresh is it? A run covers complete publication days up to yesterday by default, so a daily schedule is the natural cadence — but Google adds new publications to its search index on its own schedule, and a document can publish days to weeks before the index serves it. What a run returns is what the index currently serves for your window; the monitoring mode is built for exactly this, since a patent the index adds late is still delivered the first run that can see it.

Google Patents is Google's public index of published patent documents from over 100 patent offices — patent publications are public records by design. This Actor reads only that public, logged-out search index: no login, no API key, no CAPTCHA bypass. Records carry inventor and assignee names exactly as published in the official registers, and no personal contact data. Legal-stage fields are Google's own family-level indicators, provided for triage — not legal advice.