📣 SERP Share of Voice - Keyword Visibility Tracker
Pricing
Pay per event
📣 Track your and competitors' position-weighted share of search visibility across a keyword set, over time. Works from SERP results you supply — the reliable path, since Google returns a JS shell to server-side requests. Optional Bing/DuckDuckGo live fetch.
The primary input path. An array of {"keyword": "...", "rank": 1, "url": "https://...", "title": "..."} rows from ANY SERP source or actor you already use. Google is deliberately not scraped here (it returns a JS shell to server-side requests) — bring your own results and this actor does the analytics.
[ { "keyword": "best running shoes", "rank": 1, "url": "https://nike.com/running-shoes", "title": "Best Running Shoes | Nike" }, { "keyword": "best running shoes", "rank": 2, "url": "https://adidas.com/running", "title": "Running Shoes | adidas" }, { "keyword": "best running shoes", "rank": 3, "url": "https://runnersworld.com/gear/best-running-shoes", "title": "The Best Running Shoes, Tested - Runner's World" }, { "keyword": "marathon training plan", "rank": 1, "url": "https://adidas.com/training/marathon", "title": "Marathon Training Plan | adidas" }, { "keyword": "marathon training plan", "rank": 2, "url": "https://runnersworld.com/training/marathon-plan", "title": "Marathon Training Plan - Runner's World" }, { "keyword": "marathon training plan", "rank": 3, "url": "https://nike.com/marathon", "title": "Marathon Guide | Nike" }]Maps each result URL to a brand. Format: {"Your Brand": ["yourdomain.com"], "Competitor A": ["competitor-a.com", "blog.competitor-a.com"]}. Subdomains are matched to the domain you list (e.g. shop.yourdomain.com matches yourdomain.com automatically) — you only need to list a subdomain explicitly if it belongs to a DIFFERENT brand than its parent domain.
{ "Nike": [ "nike.com" ], "adidas": [ "adidas.com" ], "Runner's World": [ "runnersworld.com" ]}The exact brand name (a key in brandMap) that head-to-head gaps and the summary's "yourSoV" are computed against. Leave blank to skip head-to-head rows.
Optional override for the default position-weighting (CTR-style decay) curve. Array of integers in basis points (10000 = 100%), index 0 = rank 1. Apify input schemas have no float type, so this is expressed in basis points rather than a 0-1 fraction. Leave empty to use the documented default curve (rank 1 worth roughly 10-15x rank 10).
[]Optional. {"keyword": 1000, ...} monthly search volume per keyword. When supplied, each result's position weight is multiplied by its keyword's volume, so visibility on a high-volume term counts for more than the same rank on a rarely-searched one. Omit to weight every keyword equally.
{}Secondary, optional path. "supplied" (default) uses only the results you pass in above — the reliable option. "bing"/"duckduckgo"/"bing+duckduckgo" additionally fetch live results server-side for the keywords you list below. Google is NOT an option: it serves a JavaScript shell (no organic results, no AI Overview) to server-side requests and cannot be scraped this way.
Only used when fetchMode is not "supplied". The keyword list to fetch live results for from Bing and/or DuckDuckGo.
[]Upper bound on organic results parsed per keyword when fetchMode is not "supplied".
Optional market hint passed to Bing (e.g. "US", "GB") when fetchMode includes bing. Ignored otherwise.
How many keyword/source fetches to run in parallel when fetchMode is not "supplied".
Per-request timeout in milliseconds for live Bing/DuckDuckGo fetches.
When true (and this isn't the first run), brand rows whose share-of-voice trend is "flat" are omitted from the dataset. Keyword, head-to-head and mover rows are always included.
Hard cap on rows pushed to the dataset this run. 0 = no cap.
Ignore any previously stored share-of-voice state and treat this run as a fresh first run (no movement, no dropout/new-entrant detection).
How many past runs to keep in each brand's rolling share-of-voice history, so you can chart it over time without your own database.
How many keyword-level biggest-gain and biggest-loss rows to emit per run.
Name of the named key-value store used to persist share-of-voice history between runs. Use a different name to run independent, non-interfering trackers (e.g. per client or per keyword set).