Live SERP lookups

Serply answers a search query with the current results page as JSON. A Beam agent sends the queries your team maintains, reads the response the moment it arrives, and applies your rule for handling it: matched results are written to your store, and the requester hears back once the run is done. Queries that time out, return nothing, or come back with a shape your rule does not expect route to a person, who checks the query or the account quota before the agent runs that lookup again.

JSON result storage

Each Serply response is a JSON object holding the ranked results and their details. The agent reads the fields your team names, applies the rule for mapping them, and files clean records into your database or sheet. It notifies you when a batch lands. Responses that arrive with missing keys, or with values that fall outside the ranges your rule allows, are set aside and sent to a person, who reviews the raw JSON and decides whether to adjust the mapping or drop that entry before anything is saved.

Position tracking

Watching a keyword means asking Serply the same question on a regular cadence and comparing answers. A Beam agent runs those scheduled lookups, reads each position from the JSON, and records today's number against yesterday's. When a keyword moves past the limit your team set, it notifies the owner with both figures. Cases where the tracked page drops out of the results entirely, or where the jump looks unlike recent history, go to an analyst, who confirms the change is genuine before the tracker is updated.