Docs menu

Crawlora Docs

Build a SERP Monitoring Workflow

Build a SERP monitoring API workflow for rank tracking, competitor visibility, result URL history, and search-result change alerts.

Try first API Copy examples Plan credits

Overview

Build a SERP monitoring API workflow for rank tracking, competitor visibility, result URL history, and search-result change alerts.

What you will build

Define keyword list
Select country and language
Track target and competitor domains
Schedule requests
Store organic results
Compare rank changes
Alert on movement

APIs used

Only endpoints that exist in the generated endpoint metadata are linked here. Missing optional endpoints are intentionally omitted.

GETBingapiKey3 credits/request

Search Bing web results

/bing/search

Returns normalized Bing web search results for a query string, including organic results, optional context panel data, related queries, people-also-ask questions, news modules, video modules, and page-based pagination. Empty optional blocks are omitted from the JSON response. Locale defaults to country=us and lang=en-us. Results are fetched with a Chrome-impersonated request client and return 503 on a genuine transport failure or challenge page. Bing occasionally serves a well-formed page whose results share no significant term with the query; when every hedged attempt hits this, the response is still returned as 200 with data.low_confidence set to true (and the X-Low-Confidence header) instead of being withheld, so callers get Bing's real answer plus an honest signal to double-check it rather than nothing. Queries that use the site: operator (for example site:gov.hu) are not supported: Bing serves a bot-verification challenge for them, so they are rejected with 400 before any request is made. Use the DuckDuckGo (/api/v1/duckduckgo/search), Brave (/api/v1/brave/search), or Yahoo (/api/v1/yahoo-search/search) search endpoints for domain-restricted searches instead.

View docs Try in Playground

GETBraveapiKey3 credits/request

Search Brave

/brave/search

Returns normalized web search results from Brave Search for a query string, along with offset-based pagination, related queries, discussions, videos, and the right-side knowledge card when Brave includes one. Use time_range for preset ranges or date_from/date_to for a custom YYYY-MM-DD range. Locale defaults to country=us and lang=en-us.

View docs Try in Playground

GETDuckDuckGo SearchapiKey3 credits/request

Search DuckDuckGo web results

/duckduckgo/search

Returns normalized DuckDuckGo web search results for a query string: title, destination URL, description, and hostname, plus page-based pagination. DuckDuckGo wraps every result link in its own click-tracking redirect; this endpoint always returns the decoded destination URL, never the raw redirect link. Results are fetched from DuckDuckGo's own server-rendered search page.

View docs Try in Playground

POSTGoogle TrendsapiKey3 credits/request

Google Trends trending term detail

/google/trends/trending/detail

Returns the Explore detail widgets for a single trending term, including interest over time, regional interest, top/rising related queries, and related topics when Google returns them.

View docs Try in Playground

Data model

Field	Notes
keyword	Workflow field; map to exact endpoint response fields from endpoint docs.
country	Workflow field; map to exact endpoint response fields from endpoint docs.
language	Workflow field; map to exact endpoint response fields from endpoint docs.
result_url	Workflow field; map to exact endpoint response fields from endpoint docs.
title	Workflow field; map to exact endpoint response fields from endpoint docs.
snippet	Workflow field; map to exact endpoint response fields from endpoint docs.
rank	Workflow field; map to exact endpoint response fields from endpoint docs.
checked_at	Workflow field; map to exact endpoint response fields from endpoint docs.
request_id	Workflow field; map to exact endpoint response fields from endpoint docs.
credits_used	Include when response or usage data makes it available.

Step-by-step workflow

1.Define keyword list
2.Select country and language
3.Track target and competitor domains
4.Schedule requests
5.Store organic results
6.Compare rank changes
7.Alert on movement

Example request

This example uses the real Search Bing web results endpoint. Exact request fields come from the endpoint metadata.

Recipe request

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/bing/search?q=coffee&page=1&count=10&country=us&lang=en" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example response

Use endpoint detail pages for exact response schemas. This recipe does not invent response fields.

Generated example response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "results": [
      {
        "position": 1,
        "title": "OpenAI - Reddit",
        "url": "https://www.reddit.com/r/OpenAI/",
        "description": "OpenAI is an AI research and deployment company. OpenAI's mission is to ensure that artificial general intelligence benefits all of humanity...",
        "hostname": "www.reddit.com",
        "display_url": "https://www.reddit.com › OpenAI",
        "favicon": "https://th.bing.com/th/id/ODLS.A2450BEC-5595-40BA-9F13-D9EC6AB74B9F..."
      }
    ],
    "pagination": {
      "page": 1,
      "count": 10,
      "next_page": 2
    }
  }
}

Storage/output suggestion

Store one row per keyword, engine, result, and check in a relational table or analytics warehouse so rank changes can be compared over time.

Error handling

Validate required inputs before calling Crawlora
Retry 429 and temporary 5xx responses with capped backoff
Log endpoint, input, timestamp, and request ID when present
Treat empty results as a state your application can handle
Open /docs/errors for production retry guidance

Rate-limit and credit planning

Estimate usage by multiplying requests by endpoint credit cost. The table below only shows real credit costs available from the billing constants.

Endpoint	Credit cost	Docs
Search Bing web results	3 credits/request	/docs/bing/bing-search
Search Brave	3 credits/request	/docs/brave/brave-search
Search DuckDuckGo web results	3 credits/request	/docs/duck-duck-go-search/duckduckgo-search
Google Trends trending term detail	3 credits/request	/docs/google-trends/google-trends-trending-detail

Production checklist

Keep API keys server-side
Use request timeouts
Back off on rate limits
Store raw responses or source IDs for auditability
Monitor credits and failures
Avoid unnecessary refreshes
Review responsible-use requirements

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

Related APIs and pages

Search Bing web results Search Brave Search DuckDuckGo web results Google Trends trending term detail /use-cases/serp-monitoring /use-cases/white-label-serp-tracking-api /use-cases/serp-rank-checker-api /platforms/bing /platforms/brave /platforms/google-trends

Build this workflow with real endpoint docs

Use this recipe for workflow shape, then rely on endpoint reference pages for exact paths, request schemas, response schemas, and credit costs.

Browse APIs Try Playground

Docs menu

Crawlora Docs

Build a SERP Monitoring Workflow

Build a SERP monitoring API workflow for rank tracking, competitor visibility, result URL history, and search-result change alerts.

Try first API Copy examples Plan credits

Overview

Build a SERP monitoring API workflow for rank tracking, competitor visibility, result URL history, and search-result change alerts.

What you will build

Define keyword list
Select country and language
Track target and competitor domains
Schedule requests
Store organic results
Compare rank changes
Alert on movement

APIs used

Only endpoints that exist in the generated endpoint metadata are linked here. Missing optional endpoints are intentionally omitted.

GETBingapiKey3 credits/request

Search Bing web results

/bing/search

View docs Try in Playground

GETBraveapiKey3 credits/request

Search Brave

/brave/search

View docs Try in Playground

GETDuckDuckGo SearchapiKey3 credits/request

Search DuckDuckGo web results

/duckduckgo/search

View docs Try in Playground

POSTGoogle TrendsapiKey3 credits/request

Google Trends trending term detail

/google/trends/trending/detail

Returns the Explore detail widgets for a single trending term, including interest over time, regional interest, top/rising related queries, and related topics when Google returns them.

View docs Try in Playground

Data model

Field	Notes
keyword	Workflow field; map to exact endpoint response fields from endpoint docs.
country	Workflow field; map to exact endpoint response fields from endpoint docs.
language	Workflow field; map to exact endpoint response fields from endpoint docs.
result_url	Workflow field; map to exact endpoint response fields from endpoint docs.
title	Workflow field; map to exact endpoint response fields from endpoint docs.
snippet	Workflow field; map to exact endpoint response fields from endpoint docs.
rank	Workflow field; map to exact endpoint response fields from endpoint docs.
checked_at	Workflow field; map to exact endpoint response fields from endpoint docs.
request_id	Workflow field; map to exact endpoint response fields from endpoint docs.
credits_used	Include when response or usage data makes it available.

Step-by-step workflow

1.Define keyword list
2.Select country and language
3.Track target and competitor domains
4.Schedule requests
5.Store organic results
6.Compare rank changes
7.Alert on movement

Example request

This example uses the real Search Bing web results endpoint. Exact request fields come from the endpoint metadata.

Recipe request

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/bing/search?q=coffee&page=1&count=10&country=us&lang=en" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example response

Use endpoint detail pages for exact response schemas. This recipe does not invent response fields.

Generated example response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "results": [
      {
        "position": 1,
        "title": "OpenAI - Reddit",
        "url": "https://www.reddit.com/r/OpenAI/",
        "description": "OpenAI is an AI research and deployment company. OpenAI's mission is to ensure that artificial general intelligence benefits all of humanity...",
        "hostname": "www.reddit.com",
        "display_url": "https://www.reddit.com › OpenAI",
        "favicon": "https://th.bing.com/th/id/ODLS.A2450BEC-5595-40BA-9F13-D9EC6AB74B9F..."
      }
    ],
    "pagination": {
      "page": 1,
      "count": 10,
      "next_page": 2
    }
  }
}

Storage/output suggestion

Store one row per keyword, engine, result, and check in a relational table or analytics warehouse so rank changes can be compared over time.

Error handling

Validate required inputs before calling Crawlora
Retry 429 and temporary 5xx responses with capped backoff
Log endpoint, input, timestamp, and request ID when present
Treat empty results as a state your application can handle
Open /docs/errors for production retry guidance

Rate-limit and credit planning

Estimate usage by multiplying requests by endpoint credit cost. The table below only shows real credit costs available from the billing constants.

Endpoint	Credit cost	Docs
Search Bing web results	3 credits/request	/docs/bing/bing-search
Search Brave	3 credits/request	/docs/brave/brave-search
Search DuckDuckGo web results	3 credits/request	/docs/duck-duck-go-search/duckduckgo-search
Google Trends trending term detail	3 credits/request	/docs/google-trends/google-trends-trending-detail

Production checklist

Keep API keys server-side
Use request timeouts
Back off on rate limits
Store raw responses or source IDs for auditability
Monitor credits and failures
Avoid unnecessary refreshes
Review responsible-use requirements

Responsible public web data workflows

Read Crawlora terms

Related APIs and pages

Build this workflow with real endpoint docs

Use this recipe for workflow shape, then rely on endpoint reference pages for exact paths, request schemas, response schemas, and credit costs.

Browse APIs Try Playground