Keyword Overview
Keyword overview records combine search demand, paid competition, organic difficulty, monthly observations, and classified intent for known search terms. These complementary signals support term-list enrichment, opportunity comparison, research segmentation, and time-aware demand analysis.
Features
- Known-keyword batch inputEvaluate from 1 to 1,000 prepared keywords under one selected search market and language context.
- Demand and paid-search fieldsPreserve available search volume, CPC, competition, competition level, competition index, and monthly observations for demand and paid-market comparison.
- Organic difficulty and intentInclude available keyword difficulty and search-intent information alongside demand fields so distinct signals remain connected to the same term.
- Complete overview rowRetain keyword_info, keyword_properties, search-result metadata, and other returned objects in extra when they are present.
Parameters
| Parameters | Required | Description |
|---|---|---|
keywords | Required | Required list of 1 to 1,000 known, non-empty keywords, with a maximum of 80 characters per item. |
location_code | Optional | Positive numeric search-market code. The Playground defaults to 2840 for the United States. |
language_code | Optional | Search-language code applied to the batch. The Playground defaults to en. |
How to Use
Submit a bounded list of known keywords with code-based market settings, then read normalized fields and complete overview objects from the asynchronous result records.
- Prepare 1 to 1,000 non-empty known keywords, each no longer than 80 characters.
- POST keywords with location_code and language_code to /v1/seo/keyword-overview, then save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
- Read data.results.items and inspect extra.keyword_info or extra.keyword_properties for source fields that are not promoted; follow next_cursor while has_more is true.
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 trueBest Use Cases
- Keyword-list enrichment: Join returned keyword_info and keyword_properties fields to a prepared term list for a common research record.
- Demand and competition comparison: Compare search volume, CPC, paid competition, and keyword difficulty without treating paid and organic signals as interchangeable.
- Intent and trend segmentation: Use search-intent information with monthly search observations to organize known terms by likely purpose and demand pattern.
Pro Tips
- Deduplicate keywords before submission because charges are calculated from the input count.
- Keep location_code and language_code fixed when comparing terms so the selected search context remains consistent.
- Omit results_limit because the keywords array controls this batch and the overview operation has no documented result-limit control.
- Read extra.keyword_info and extra.keyword_properties for the complete overview because not every direct source value is promoted to a normalized top-level field.
- Treat missing fields as unavailable data rather than numeric zero, and match returned records by keyword instead of array position.
- Interpret CPC and competition as paid-search signals, while keyword_difficulty represents estimated organic competition.
Related APIs
Use these APIs when you need a different type of public SEO data.
- Keyword Difficulty API — Compare organic ranking difficulty for a submitted keyword batch, returning each available keyword with its normalized score.
- Keyword Search Volume API — Measure known keywords with available search volume, CPC, paid competition, and monthly search history.
- Keyword Suggestions API — Expand one seed query into matching long-tail terms with available demand measurements, monthly history, intent context, and complete source rows.
- Related Keywords API — Follow related-search paths from one seed query with depth controls, available keyword measurements, intent context, and complete source rows.
Combine SEO data with public data from other supported social platforms.