Reading runs and outcomes

What each run outcome means, what's counted and what Serpfull never does.

Lektion
2/9
Læsetid
6 min
Sektioner
3
Gennem kurset
22%

Outcomes

  • completed: counts towards the daily allowance.
  • not_found: the URL wasn’t in the top 4 results pages. Counts towards the daily allowance.
  • blocked_by_target: the search engine showed a challenge and the run stopped. Doesn’t count.
  • timeout or provider_error: retried up to twice, then logged. Doesn’t count.
Illustrativt interface, eksempeldataRun outcomes as they appear on the runs list. Completed and not-found runs use quota.

The run timeline

Open a run to see each step: queued, searching, found at position and page, clicked, dwelled (seconds and pages visited) and completed or failed with a reason. Keyword positions store the best position observed each day.

What we never do

Runs don't solve challenges, spoof browser fingerprints or rotate network addresses to get around checks. If a run is challenged, it ends and is logged.

Tjek din forståelse

A term shows many not_found outcomes. What should you check before anything else?

Lektion 2 af 9

Reading runs and outcomes