Serp CWD
Under maintenancePricing
Pay per usage
Go to Apify Store
Pricing
Pay per usage
Rating
5.0
(1)
Developer
LR
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
3
Monthly active users
4 days ago
Last modified
Categories
Share
Serp CWD
Under maintenancePricing
Pay per usage
Pricing
Pay per usage
Rating
5.0
(1)
Developer
LR
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
3
Monthly active users
4 days ago
Last modified
Categories
Share
Inline company rows to process. Each item should contain companyName and optionally companyNumber and town.
Optional dataset ID containing company rows. Items should expose companyName or company_name, plus optional companyNumber/company_number and town.
Maximum number of searches to run after loading inline rows and dataset rows.
Number of concurrent Google SERP requests. GOOGLE_SERP allows up to 200 concurrent connections per account.
Apify proxy group to use. GOOGLE_SERP is most reliable; RESIDENTIAL is cheaper but may get blocked.
Google hostname to query. For UK search use google.co.uk.
How many SERP pages to fetch. Each page counts as a separate SERP proxy request.
Scoring mode for choosing likely company websites.
Optional Apify proxy selection. Leave empty to use the default GOOGLE_SERP group unless customProxyUrls are provided.
Optional full proxy URLs. If provided, these override Apify proxy usage and are rotated round-robin by the Apify SDK.
Optional label written to each output row and summary, e.g. dataimpulse_residential.
Store the first part of the raw Google HTML in each output row for debugging.
Key-value store key used for resumable state. Reuse the same key to continue a previous run.
When enabled, skip searches already recorded under the checkpoint key.
How many result rows to buffer before pushing them to the default dataset.
