Google Position Checker — Keyword Rank Snapshot
Under maintenancePricing
from $8.20 / 1,000 keyword checkeds
Google Position Checker — Keyword Rank Snapshot
Under maintenanceCheck keyword ranking positions from SERP snapshots or approved live SERP collection with country/language options and rank evidence.
Pricing
from $8.20 / 1,000 keyword checkeds
Rating
0.0
(0)
Developer
junipr
Maintained by CommunityActor stats
0
Bookmarked
16
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Google Position Checker — SERP Snapshot Rank
Find a domain’s organic position in Google search-result snapshots you supply. The Actor produces one transparent result per keyword, including the matched rank and URL or an explicit not-found result.
How it works
Provide a target domain and one ordered organic-results snapshot per keyword. A snapshot can use structured organic-result objects and may also use a supported supplied HTML or text representation. The Actor normalizes the target host, inspects results up to maxPosition, applies the selected host-matching rule, and records exactly what it checked.
The Actor never sends a search query to Google and does not require a paid search-results provider.
Output fields
Results include keyword, normalized domain, found status, rank, matched URL, matched title, matched host, country, language, device, number of organic results checked, evidence source, snapshot hash, and processing timestamp.
A not-found result is useful output: it confirms that the supplied snapshot was inspected and no matching host appeared within the configured range.
Pricing
| Event | Free / Bronze | Silver | Gold / Platinum / Diamond | Trigger |
|---|---|---|---|---|
| Actor start | $0.00005 | $0.00005 | $0.00005 | Applied automatically by Apify when the run starts |
| Keyword checked | $0.00820 | $0.00738 | $0.00656 | One keyword result written, including an explicit not-found result |
Platform usage is included in the event prices. The default minimum selectable run limit is $15. No keyword row is written after the run spending limit denies its charge.
Example input
{"domain": "apify.com","maxPosition": 10,"matchMode": "HOST_OR_SUBDOMAINS","serpSnapshots": [{"keyword": "apify web scraper","country": "us","language": "en","device": "desktop","organicResults": [{"position": 1, "title": "Web scraping overview", "url": "https://example.org/web-scraping"},{"position": 2, "title": "Apify Store", "url": "https://apify.com/store"}]}]}
Matching rules
EXACT_HOST matches only the normalized hostname. HOST_OR_SUBDOMAINS also matches subdomains. URL schemes and a leading www. are normalized. Redirect targets are not fetched; matching uses the URL evidence in the supplied snapshot.
Reliability and limits
Every requested keyword needs a corresponding snapshot. Invalid URLs, duplicate keyword keys, malformed result positions, and unsupported snapshot representations return clear validation errors. Inputs are bounded to prevent unexpectedly large runs. Results are deterministic for the same canonicalized input.
Output and integrations
Download the dataset as JSON, CSV, Excel, XML, or RSS. Run summaries are saved as SUMMARY.json and SUMMARY.md. The RUN_SUMMARY key-value-store record binds the Actor, run, and immutable build IDs to exact attempted, accepted, denied, and paid-output counts for keyword-checked, including zero-output and spending-limit-denied runs. Use the Apify API, webhooks, schedules, Make, Zapier, or custom workflows for recurring rank evidence supplied by your own collection process.