Google Search - Domain Rankings & Rank Changes
Pricing
from $8.00 / 1,000 parsed search pages
Google Search - Domain Rankings & Rank Changes
Track Google Search domain rankings by keyword and country. One row per visible domain: title, snippet, rank, source page and result link. Domain and title filters; monitor rank changes with previous rank and movement. Parsed pages are billed even when filters or unchanged ranks leave no rows.
Pricing
from $8.00 / 1,000 parsed search pages
Rating
0.0
(0)
Developer
Tedj MEABIOU
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Features
Share
Google Search collects domain rankings with rank changes for repeatable business research. Track Google Search domain rankings by keyword and country. One row per visible domain: title, snippet, rank, source page and result link. Domain and title filters; monitor rank changes with previous rank and movement. Parsed pages are billed even when filters or unchanged ranks leave no rows. Export results as JSON, CSV or Excel, or connect a saved task to an existing workflow. This actor is independent of the source platform. Last verified working: 2026-10-30.
Google Search for AI agents: which input answers which request?
Use this actor for the public search records described below. Read both pricing events before estimating a run: a successful page check can cost money even when it returns no matching or changed rows. Result counts alone do not describe the complete bill.
| Request | Input |
|---|---|
| Small first sample | {"queries": ["python documentation"], "maxResultsPerSource": 3} |
| Repeated monitoring | {"queries": ["python documentation"], "maxResultsPerSource": 3, "onlyNewOrChanged": true, "monitorKey": "daily-watch"} |
| Apply the main optional features | {"queries": ["python documentation"], "maxResultsPerSource": 3, "domains": ["python.org"]} |
| Exclude records already stored elsewhere | Add excludeIds using exact output id values. |
| Cap spend | Set maxTotalChargeUsd: 1 in Apify run options, outside the input JSON. |
Google Search input: how do I start?
{"queries": ["python documentation"],"maxResultsPerSource": 3}
Each source runs sequentially. maxResultsPerSource limits delivered matches after filters, monitoring and deduplication. maxPagesPerSource separately limits source search pages. Asking for fifty rows does not guarantee that fifty matches are available. When a page contains fewer than the requested rows, the actor follows recognized source pagination until it reaches a limit or the source ends.
| Field | Meaning |
|---|---|
queries | Search keywords, for example ["python documentation"]. Up to 20 queries. Each query has independent page and delivered-result limits. No separate source account or API key required. |
maxResultsPerSource | Maximum matching rows per search after filters and monitoring; for example 50. Default 50, maximum 1000. A ceiling, not a guarantee. Deduplicated across the run; Google IDs include domain, query and country; only the first visible result per domain is kept. |
country | Requested Google country: us, gb, de, fr, ca or au. English interface. Default us. Country domain and gl are sent on every page; this is not exact city/device targeting or a guarantee of identical results to your browser. |
domains | Keep these domains or their subdomains, for example ["python.org"]. Hostnames only, without https:// or paths. Empty means all domains. Rank is assigned before this filter. Filtered results have no row fee; parsed pages are billed. |
onlyNewOrChanged | true emits new IDs or changes in observed organic rank. First run delivers the baseline; use the same monitorKey later. Successful unchanged checks still pay page fees. Default false. Outputs previous_rank and rank_change; positive movement means improved rank. Missing domains are not reported as disappearances. |
titleContains | Keep titles containing any phrase, case-insensitive, for example ["engineer"]. For Zillow, title is building name or address. Empty disables it. Applied before row billing; parsed pages are still billed. |
titleExcludes | Drop titles containing any phrase, case-insensitive, for example ["senior"]. Empty disables it. Filtered rows have no row fee; parsed pages still carry their fee. |
monitorKey | Persistent history name, for example "daily-watch". Use 1–60 letters, digits, underscores or hyphens. Use the same targets, filters and name for repeat runs. Keeps the latest 50,000 delivered IDs. Do not overlap runs sharing this name. |
excludeIds | Skip exact output id values. Up to 10,000. Useful for external deduplication; excluded rows have no row fee, but parsed pages are billed. |
maxPagesPerSource | Safety cap on parsed pages per search, for example 5. Default 5, maximum 20. Each parsed page costs $0.008, including filtered or unchanged checks. Both this cap and maxResultsPerSource apply. |
Google Search output: what is a result row?
One row is one result. Main keys: id, title, domain, domain_url, result_link, snippet, rank, page, query, country, source_url, fetched_at, change, previous_rank, rank_change. Missing source values stay null. Use id for deduplication and keep fetched_at to distinguish an observation time from source posting dates. The source URL records the search page used for that observation.
The key-value store's SUMMARY record contains parsed pages, delivered rows, duplicates, filtered and unchanged rows, charge counts, per-source statuses and errors. It is not a paid dataset row. A source refusal or unknown layout is an error, not fabricated empty data. If there are errors and no rows can be delivered, the run fails. A partial run retains valid rows and records errors in SUMMARY. Check that record before assuming a successful partial run covered all inputs.
How much does the actor cost?
A successfully parsed page costs $0.008 ($8 per 1,000 pages). Each delivered result costs $0.0005 ($0.5 per 1,000 rows). No start fee; proxy and compute are included.
One page and ten basic rows cost $0.013. One successfully parsed page with zero matches or zero changes costs $0.008. Failed source requests and unrecognized page responses have no page fee. Filtered, duplicate, excluded and unchanged rows have no row fee. Successfully parsed search pages retain their fee even if a later job-description request or destination-link resolution fails.
A conservative ceiling is number_of_sources × (maxPagesPerSource × page_price + maxResultsPerSource × row_price). Use the enriched-job row price if descriptions are enabled. Set the monetary maxTotalChargeUsd run option for a hard charge cap. Work stops before requesting another page when the remaining budget cannot cover its page fee and one chosen row event. Billing failures stop subsequent work.
Charging, dataset writing and monitor-state writing are separate platform operations. An interruption between them can leave a charged row unwritten or a delivered row not remembered. Use event counters and SUMMARY to investigate interrupted runs. Monetary limits apply to charged events; page and result caps also bound source work.
How do monitoring and schedules work?
{"queries": ["python documentation"],"maxResultsPerSource": 3,"onlyNewOrChanged": true,"monitorKey": "daily-watch"}
The first monitored run delivers the matching baseline. Later runs with the same monitor name suppress unchanged records already delivered. Rank comparisons use each domain, query and country. Positive rank_change means an improved position, such as previous_rank=8 and rank=3 producing rank_change=5.
History keeps the most recently delivered 50,000 IDs in a named key-value store under the account running the actor. Evicted older IDs may reappear. Reuse the same targets and filters; change monitorKey when starting an independent baseline. Overlapping runs sharing one key are not transactionally coordinated, so configure schedules without overlap. No schedule is created automatically: save an Apify task and add an Apify Schedule for daily or weekly execution. Unchanged checks still incur parsed-page charges.
How do filters work?
Title inclusion matches any listed phrase, case-insensitively. Title exclusion removes a row when any excluded phrase matches. Empty arrays disable these filters. Numeric bounds use zero to disable the bound; missing values do not pass an active bound. Filtering happens before row billing but after fetching and parsing a paid page. The actor may inspect several pages to find the requested number of matching results.
What are the source limitations?
This actor reads Google Web organic results, with an English interface and the requested country domain. It excludes ads, AI overviews, maps, images and People Also Ask. It does not fetch destination websites. result_link is exactly the source result link and can be an encoded Google redirect; it is not promised as a resolved destination URL. domain_url is the domain homepage, not the ranked page. Search page failures get at most one retry. The rank is the source page offset plus order among recognized web-result headings, before your title/domain filters. One row represents the first visible result for an exact hostname, ignoring www. Subdomains remain separate domains. Domain comes from the displayed URL or a direct result link; cards without an explicit hostname are skipped. A social-network label alone is not treated as a hostname. It is an observed organic position, not a pixel position, Search Console average position or personalized browser ranking. Google typically supplies up to ten results per page, but layouts and counts vary. A domain absent from inspected pages is not emitted as a disappearance alert. Rank changes compare the last delivered observation of that domain, query and country, not a complete historical index. Country targeting is requested, not guaranteed to match a specific device or city.
Public sources change over time and may temporarily refuse requests. These actors use bounded requests, response sizes and page counts; they do not promise complete historical coverage. For legal use, respect source terms and applicable law, and obtain rights required for downstream reuse. No separate source credentials, cookies or commercial data API key are requested.
How do I call the API from Python, JavaScript or curl?
Python:
from apify_client import ApifyClientclient = ApifyClient("YOUR_APIFY_TOKEN")run = client.actor("kestrel/google-search-rank-tracker").call(run_input={'queries': ['python documentation'], 'maxResultsPerSource': 3}, max_total_charge_usd=1)rows = client.dataset(run["defaultDatasetId"]).list_items().items
JavaScript:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('kestrel/google-search-rank-tracker').call({"queries": ["python documentation"], "maxResultsPerSource": 3}, { maxTotalChargeUsd: 1 });const { items } = await client.dataset(run.defaultDatasetId).listItems();
curl:
curl -X POST 'https://api.apify.com/v2/acts/kestrel~google-search-rank-tracker/runs?maxTotalChargeUsd=1' \-H "Authorization: Bearer $APIFY_TOKEN" -H 'Content-Type: application/json' \-d '{"queries": ["python documentation"], "maxResultsPerSource": 3}'
The asynchronous endpoint returns a run record. Wait for completion before reading the dataset and SUMMARY. The same inputs can be used in n8n, Make and MCP clients. A monetary run option must not be passed as an invented actor-input field.
FAQ: why did I receive fewer rows than requested?
Result caps are ceilings. Filters, source pagination, source errors, repeated records, monitoring and the monetary cap can all reduce delivery. Inspect per-source status in SUMMARY to identify the stopping reason. Do not increase the result limit alone if the page cap is the limiting factor.
Can I export the data to a spreadsheet?
Yes. Apify datasets support CSV and Excel exports. Preserve IDs and observation timestamps when merging repeat runs into another system. Null values should remain missing rather than being displayed as measured zero values.