Skip to content

Reading runs and outcomes

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

Lesson
2/6
Reading time
6 min
Sections
3
Through the course
33%

Outcomes

  • completed: counted against the quota.
  • not_found: the URL wasn't in the results searched. Free.
  • blocked_by_target: the search engine showed a challenge and the run stopped. Free.
  • timeout or provider_error: retried up to twice, then free.
Illustrative interface, sample dataRun outcomes as they appear on the runs list. Only completed 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.

Check your understanding

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

Lesson 2 of 6

Reading runs and outcomes