Presearch Search Scraper
DeprecatedPricing
from $1.99 / 1,000 search results
Presearch Search Scraper
DeprecatedScrapes normalized Presearch web results with snippets, source metadata, dates, links, safe search, API extraction, and DOM fallback.
Pricing
from $1.99 / 1,000 search results
Rating
0.0
(0)
Developer
Search API
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
15 days ago
Last modified
Categories
Security
Limited permissionsShare
This Actor searches Presearch Web and publishes normalized public result records.
Input
query(required): web-search keywords.maxItems: maximum records across all requested pages, from 1 to 500.maxPages: number of Presearch result pages to request, from 1 to 50.safeSearch: enables Presearch's explicit-content filter; enabled by default.proxyConfiguration: Apify Proxy or custom proxy configuration.
The complete input contract, including types, defaults, and bounds, is in .actor/input_schema.json.
Dataset records
Records include query, sequential position, title, canonical URL, displayed URL, domain, description/snippet, source/provider, source domain, favicon, breadcrumbs, sitelinks, author, ISO-8601 publication time plus the original source time, thumbnail, ad/sponsored flags, page number, and scrape timestamp. Optional values are omitted when unavailable. Canonical URLs are validated and deduplicated across pages.
The Actor captures the structured /results response before navigation, validates status and content type, maps only known public fields, and uses rendered result cards as a bounded fallback. Challenge pages, malformed payloads, and empty result sets fail instead of publishing placeholders.
The full dataset field schema is in .actor/dataset_schema.json.
Target availability (2026-10-25)
Every Presearch-owned web route currently redirects into a dead account origin, so this Actor fails closed instead of publishing an empty dataset:
https://presearch.com/search?q=climate%20change-> 301 https://account.presearch.com/-> 530 text/plain (17 bytes) "error code: 1016" (Cloudflare "Origin DNS error")
The redirect is host-wide, not query- or route-specific: /, /search, /results,
/api/*, /ai, /news, /videos, /images, /robots.txt and every other
*.presearch.com subdomain tested answer either the same 301 to
https://account.presearch.com/ or the same 530 error code: 1016 body. The failure
message in the run log carries the status, the full redirect chain, the page title and a
bounded body excerpt, so the refusal is self-describing. Revisit when
https://presearch.com/search?q=… renders its own result page again.
How to use
Enter a web-search query and limits in the Apify Input tab, start the Actor, and review records in the Output dataset. Current availability depends on Presearch serving its public search page.