Related Keywords
Related keywords are queries linked through the searches-related-to graph, with depth, demand, CPC, competition, difficulty, and intent signals. These relationships and measurements support adjacent-topic discovery, topic-map expansion, and candidate comparison.
Features
- Related-search graph expansionFollow direct or recursive query relationships from one seed with depth values from 0 through 4 rather than requiring phrase containment.
- Keyword measurement objectsReturn available search volume, CPC, paid competition, monthly history, difficulty, and intent information for each connected query.
- Preserved relationship contextKeep source depth, related-keyword paths, complete keyword_data, and other variable fields in extra for detailed graph interpretation.
Parameters
| Parameters | Required | Description |
|---|---|---|
query | Required | Required non-empty seed keyword or phrase. One task accepts one query. |
location_code | Optional | Optional positive numeric search-market code. |
location_name | Optional | Optional search-market name alternative to location_code. When filled, it takes precedence over location_code. |
language_code | Optional | Optional search-language code from 2 through 10 characters. |
language | Optional | Optional search-language name alternative to language_code. When filled, it takes precedence over language_code. |
depth | Optional | Relationship depth from 0 through 4. The default 1 returns directly connected queries. |
results_limit | Optional | Requested maximum from 1 through 1,000 related keywords. Fewer rows may be returned. |
offset | Optional | Zero-based number of source rows to skip before collecting the requested result window. |
How to Use
Submit one seed query with a relationship depth, market controls, and a bounded result window, then read related records from the completed asynchronous task.
- Choose one non-empty query, a location_code, a language_code, a depth from 0 through 4, a results_limit from 1 through 1,000, and an offset of 0 or greater.
- POST the payload to /v1/seo/related-keywords and save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or returns a failure.
- Read data.results.items, then request the returned next_cursor while has_more remains true.
curl -X POST "https://api.socq.ai/v1/seo/related-keywords" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"keyword research","depth":1,"results_limit":100}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Adjacent-topic discovery: Use the returned query text and relationship context to find connected topics that do not need to contain the seed phrase.
- Topic-map expansion: Compare depth and related-keyword paths to extend one seed from direct neighbors into a broader query graph.
- Keyword candidate assessment: Combine related terms with available demand, cost, competition, difficulty, monthly history, and intent to prepare a reviewable candidate set.
Pro Tips
- Start with depth 1 for direct relationships; raise depth only when a broader graph is worth the larger and potentially less direct candidate pool.
- Use Keyword Suggestions instead when every returned term should retain the seed words, because related queries can use different phrasing.
- Keep query, location_code, language_code, and depth fixed when comparing result windows so relationship and market context remain comparable.
- Treat offset as a row count rather than a page number, and increase it by the number of source rows you intend to skip.
- Read keyword, metrics, monthly_searches, and search_intent from normalized fields first, then inspect extra for source depth and relationship paths.
- Do not infer identical intent from graph proximity, and allow optional measurements and variable extra fields to be absent.
Related APIs
Use these APIs when you need a different type of public SEO data.
- Google Organic SERP API — Retrieve one live Google result page by query and market with normalized destinations, ranks, element types, and full result details.
- Keyword Difficulty API — Compare organic ranking difficulty for a submitted keyword batch, returning each available keyword with its normalized score.
- Keyword Overview API — Enrich a submitted keyword batch with available demand, paid competition, difficulty, monthly-search, and intent context.
- Keyword Search Volume API — Measure known keywords with available search volume, CPC, paid competition, and monthly search history.
- Keywords for Site API — Generate keywords relevant to one website with available demand measurements, monthly history, market context, and complete source rows.
- Keyword Suggestions API — Expand one seed query into matching long-tail terms with available demand measurements, monthly history, intent context, and complete source rows.
- Ranked Keywords API — Find keywords a domain, subdomain, or page ranks for, with matching URLs, positions, search measurements, intent, and complete source elements.
- Relevant Pages API — Inventory indexed pages for one domain with organic and paid ranking distributions, modeled traffic, and estimated cost context.
- Search Intent API — Classify primary and secondary search intent for a submitted keyword batch while preserving source probabilities and complete records.