SERP Organic Result Extractor

Extract organic search-result entries from supplied SERP HTML or public query runs, preserving rank, title, URL, domain, snippet, sitelinks, and source...

Who it is for

SERP Organic Result Extractor helps seo agencies, content teams, market researchers, founders validating search demand extract organic search-result entries from supplied SERP HTML or public query runs, preserving rank, title, URL, domain, snippet, sitelinks, and source evidence. It produces schema-valid dataset rows, evidence-backed KVS reports, safe diagnostics, and capped pay-per-event pricing for predictable Apify Store runs.

Turn captured search pages into clean organic-result rows for rank tracking, domain research, snippet analysis, and result-set comparisons. Ads, People Also Ask blocks, local packs, shopping modules, and other feature cards are excluded from the organic stream.

Evidence contract

The actor emits only facts visible in supplied HTML, explicit input records, or a permitted public URL response. It never creates rankings, questions, modules, suggestions, titles, snippets, or page metadata to fill an evidence gap. A missing source produces a schema-valid status row explaining what input is needed.

Network access is conservative. Only HTTP and HTTPS URLs are accepted; localhost, loopback addresses, private IPv4 ranges, and disallowed domains are rejected. The runtime does not follow links discovered in a page. Challenge and access-denied pages are recorded as blocked evidence and are not solved or circumvented.

Input modes

• Pass serpHtmlInputs with a query and captured HTML for deterministic extraction.
• Pass htmlInputs when your collection system already stores page HTML.
• Pass a public snapshot URL in startUrls; optional allowedDomains limits where the actor may connect.
• Pass queries without HTML to receive an explicit source-required status row, never invented rankings.

Example input

{
  "queries": [
    "best workflow software"
  ],
  "serpHtmlInputs": [
    {
      "sourceUrl": "https://example.com/serp",
      "query": "best workflow software",
      "html": "<article class=\"organic-result\" data-rank=\"1\"><a href=\"https://vendor.example/workflow\">Workflow Platform</a><cite>vendor.example</cite><p class=\"snippet\">Automate recurring work.</p></article>"
    }
  ],
  "maxResultsPerQuery": 10,
  "maxSnapshots": 1,
  "maxChargeUsd": 50
}

Dataset output

Each dataset item is one JSON object, which makes the result directly usable in Apify integrations, exports, webhooks, and downstream data pipelines.

• resultPosition, normalized from visible data-position or data-rank evidence
• title, resultUrl, displayedUrl, and domain
• visible snippet text and optional sitelinks
• query, search-engine label, snapshot key, HTTP status, and blocked status

Common evidence fields include sourceUrl, sourceType, pageTitle, issueCode, severity, evidenceSnippet, recommendation, httpStatus, and scannedAt. Fields without source evidence are null rather than guessed.

Reports and retained evidence

When includeReport is true, the actor writes a Markdown summary, CSV records, JSON issue rows, evidence excerpts, and run metadata to key-value storage. Set includeRawSnapshots only when retaining capped HTML is appropriate for your workflow; it is off by default.

The report metadata records the actor, timestamp, row count, issue codes, severity totals, consumed input fields, pricing mode, platform-usage setting, and maximum-charge default. This provides a compact audit trail for scheduled comparisons.

Pricing

This actor uses pay per event. Apify platform-usage pass-through is off. Charges are accepted before the corresponding paid dataset row or report is written.

Event	Price
actor-start	$0.08000
query-snapshot-scanned	$0.01000
live-serp-page-rendered	$0.02750
serp-result-record-extracted	$0.00950
report-generated	$0.18000

maxChargeUsd is a strict pre-output budget. A value of zero prevents the first charge and therefore prevents paid output. If Apify rejects a charge, partially accepts it, or reports an event limit, the actor stops before writing the affected output and records billing status.

Higher-tier Store discounts are expected where supported. The event prices above remain the locked base prices.

Limits and predictable runs

• maxPages, maxSnapshots, and actor-specific record caps limit work before analysis.
• maxQueries limits distinct search contexts.
• Public fetches are additionally constrained by allowedDomains, timeoutMs, requestDelayMs, and a fetch cap.
• Reports are optional and raw HTML retention is opt-in.
• Query-only input produces an explicit source-required row instead of an empty or fabricated result.
• Dataset rows and report files follow the declared Actor schemas.

Responsible use

Process only public content or material you are authorized to analyze. Respect website terms, rate limits, privacy obligations, intellectual-property rights, and applicable law. Avoid sending personal or confidential information in HTML or input records unless your workflow is authorized to process it.