Relevant Pages
Relevant pages are indexed URLs with measurable organic or paid search visibility, including keyword counts, position buckets, modeled traffic, cost estimates, and movement signals. These page-level measurements support visibility inventories, footprint comparison, traffic-value review, and repeated snapshot analysis.
Features
- Domain-level page inventoryReturn absolute URLs for pages of one domain that have measurable organic or paid relevance in the selected search index.
- Organic ranking distributionPreserve organic keyword counts across position buckets together with new, rising, falling, and lost ranking counts when exposed.
- Paid search footprintExpose available paid keyword counts, position ranges, modeled traffic, and estimated paid traffic cost for each page.
- Complete page metric objectsKeep nested organic, paid, and other variable page-level measurements in extra while normalizing the page URL for stable identification.
Parameters
| Parameters | Required | Description |
|---|---|---|
target | Required | Required domain without https:// or www., such as example.com. |
location_code | Optional | Positive numeric search-market code. The Playground defaults to 2840. |
location_name | Optional | Optional search-market name alternative to location_code. When filled, it takes precedence over location_code. |
language_code | Optional | Search language code from 2 through 10 characters. The Playground defaults to en. |
language | Optional | Optional search-language name alternative to language_code. When filled, it takes precedence over language_code. |
results_limit | Optional | Requested maximum from 1 through 1,000 indexed page records. 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 correctly formatted domain with market controls and a bounded source window, then read each relevant page from the completed asynchronous task.
- Choose one domain without https:// or www., a location_code, a language_code, a results_limit from 1 through 1,000, and an offset of 0 or greater.
- POST the payload to /v1/seo/relevant-pages 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/relevant-pages" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"target":"microsoft.com","location_code":2840,"language_code":"en","results_limit":5}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Search-visible page inventory: Use returned page URLs to build a domain inventory limited to pages with measurable indexed search relevance.
- Organic footprint comparison: Compare organic keyword counts, ranking buckets, and movement fields to identify how visibility is distributed across pages.
- Paid search page review: Use paid keyword counts, position ranges, modeled traffic, and estimated cost to compare the paid footprint of returned pages.
- Page visibility snapshots: Store repeated records by page_address and market to compare ranking distributions and modeled traffic across collection times.
Pro Tips
- Remove https:// and www. from target before submission because this endpoint expects a domain rather than a complete page URL.
- Use the returned url as the page identifier; text is the same URL fallback and does not contain page body content.
- Keep target, location_code, language_code, results_limit, and offset fixed when comparing repeated result windows.
- Treat offset as a source-row count rather than a page number, and store it separately from the task-result next_cursor.
- Read organic and paid measurements from extra.metrics, and allow nested metric groups or individual fields to be absent.
- Interpret etv and estimated_paid_traffic_cost as modeled search estimates rather than private analytics or observed revenue.
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.
- Related Keywords API — Follow related-search paths from one seed query with depth controls, available keyword measurements, intent context, and complete source rows.
- Search Intent API — Classify primary and secondary search intent for a submitted keyword batch while preserving source probabilities and complete records.