DataForSEO SERP API — Real-Time Search Result Data

DataForSEO SERP API Overview

DataForSEO's SERP API provides real-time and task-based Google search result data for any keyword and location combination. It captures the full SERP including organic results, PAA, featured snippets, local packs, knowledge panels, and shopping results.

API group: SERP Primary endpoint base: https://api.dataforseo.com/v3/serp/google/

Core SERP Endpoints

Google Organic Results (Live)

POST to https://api.dataforseo.com/v3/serp/google/organic/live/regular

Returns for each result:

• position — organic rank (1-100)
• url — result URL
• title — page title
• description — meta description
• domain — root domain
• breadcrumb — breadcrumb URL path shown in SERP
• is_featured_snippet — boolean
• rank_absolute — absolute position in SERP including all result types

Rate limit: 30 requests/minute on standard tier.

Request format:

[
  {
    "keyword": "roof replacement tampa fl",
    "location_code": 1023191,
    "language_code": "en",
    "depth": 100
  }
]

PAA Data

PAA questions are nested inside the organic SERP response. Look for type: "people_also_ask" items in the items array. Each PAA item includes:

• question — the PAA question text
• expanded_element — the featured answer if expanded
• source_url — where the answer comes from

Features Present in SERP

Check se_results_count and the items array for:

• featured_snippet — is there a featured snippet?
• local_pack — is there a local 3-pack?
• knowledge_graph — is there a knowledge panel?
• shopping — are there shopping results?

Use feature detection to determine what type of content to produce. Local pack present = local SEO signals needed. Featured snippet present = answer-capsule format needed.

Local Pack Data

For queries with local intent, the SERP API returns local pack entries under type: "local_pack":

• Business name
• Rating and review count
• Address
• Category
• Website URL

Use this to audit client's local pack visibility vs. competitors.

Task-Based vs. Live Requests

Live requests: Immediate response, higher cost. Use for single queries or small batches.

Task-based requests: Submit tasks, poll for completion, retrieve results. Lower cost. Use for batch processing of 50+ keywords.

Task submission: POST to .../task_post Task retrieval: GET from .../task_get/{task_id}

SERP Data Workflow

1. Identify target keywords (from dataforseo-keywords or keyword-researcher)
2. Submit SERP task for each keyword at target location
3. Parse results for: top 10 URLs, featured snippet presence, PAA questions, local pack presence
4. For each URL in top 10: record title, description, breadcrumb
5. Cross-reference with on-page data (via dataforseo-onpage) to understand what makes the top content strong
6. Identify gaps: keywords where client ranks 11-30 (near the first page, highest leverage)

SERP Monitoring Setup

Establish baseline rankings before any optimization:

1. Batch-submit all target keywords to SERP API
2. Record initial positions for client domain
3. Schedule weekly re-checks via dataforseo-rank-tracking
4. Alert when position changes by 5+ positions

Integration with Other DataForSEO Endpoints

| Use Case | SERP + | |----------|--------| | Understand why #1 ranks | dataforseo-onpage to audit the top URL | | Find keyword volume for SERP keywords | dataforseo-keywords Overview | | Track local pack visibility | dataforseo-gmb for GMB data | | Monitor AI mentions | dataforseo-llm-mentions |

Cross-References

• dataforseo-keywords — volume data for keywords identified in SERP analysis
• dataforseo-onpage — on-page analysis of SERP-competitive URLs
• serp-intent-analyzer — broader SERP mining methodology
• keyword-researcher — SERP mode consumes DataForSEO SERP data

#seo-sop #seo #serp #dataforseo #api #competitive-analysis