Back to APIs
SEO keyword data

SEO Data API

Use one SEO API surface for prepared-keyword metrics, search-volume history, keyword suggestions, and related-query discovery.

Available SEO APIs

Choose Keyword Difficulty, Keyword Overview, Keyword Search Volume, Keyword Suggestions, or Related Keywords according to the research question.

What SEO data can you retrieve?

SocQ normalizes keyword records while preserving complete source objects for endpoint-specific fields.

Difficulty and overview signals

Compare organic difficulty, demand, paid competition, intent, and monthly observations when available.

Search-volume history

Measure prepared keyword lists with current search demand, CPC, competition, and monthly history.

Suggestion and relationship discovery

Expand a seed query into suggested or related terms with metrics and relationship context.

SocQ SEO APIs vs separate keyword integrations

SocQ places five keyword-research capabilities behind one authenticated asynchronous task and stored-result contract.

CapabilitySocQSeparate integration
CoverageDifficulty, overview, volume, suggestions, and related termsEndpoint-specific integrations
Task workflowSubmit, poll, and read normalized recordsBuild request, retry, persistence, and result handling
Result contextNormalized fields plus complete source objectsProvider-specific response objects
PricingEndpoint-specific input, request, or result pricingProvider-specific billing logic

How the SEO API works

All five endpoints use the shared SocQ asynchronous lifecycle and cursor-based stored result pages.

  1. 1. Select a workflow

    Submit a prepared keyword list or one seed query with the endpoint's supported market settings.

  2. 2. Track the task

    Poll /v1/tasks/{task_id} until the task succeeds or fails.

  3. 3. Read keyword records

    Read data.results.items and follow next_cursor while has_more is true.

Start with Keyword Overview

This example enriches a prepared term list; use the catalog cards for the other four endpoint-specific payloads.

curl -X POST "https://api.socq.ai/v1/seo/keyword-overview" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["keyword research","seo analytics"],"location_code":2840,"language_code":"en"}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Common SEO API use cases

Prepared-list prioritization

Compare demand and difficulty across terms already selected for research.

Long-tail discovery

Expand a seed into suggested and related queries for briefs or campaign planning.

Trend and intent segmentation

Group terms by available monthly demand, competition, and classified intent.

Limits and interpretation

Inputs, available fields, bounds, and billing differ by endpoint and search context.

  • Difficulty, overview, and search-volume endpoints accept prepared keyword arrays; suggestion and related endpoints accept one seed query.
  • Market, language, depth, limit, and offset support depends on the selected endpoint.
  • Returned rows or individual metrics can be absent when source data is unavailable.
  • Paid competition, organic difficulty, search volume, and classified intent are distinct signals.
  • extra remains a flexible complete source object rather than a stable normalized schema.

SEO API frequently asked questions

What is the SocQ SEO API suite?

It is a set of five authenticated asynchronous endpoints for keyword metrics, search volume, suggestions, and related-query research.

Which endpoint should I use?

Use Difficulty, Overview, or Search Volume for known terms; use Suggestions or Related Keywords to expand a seed query.

How are the endpoints priced?

Pricing is endpoint-specific: consult each catalog page for input-count, fixed-request, or returned-result billing.

Bring public profiles, content, and engagement data from different platforms into one workflow to track brands, creators, and topics and run cross-platform monitoring and analysis more efficiently.