SEO APIs for Search Results, Keywords, and Rankings
Query live Google organic results, compare keyword demand and ranking difficulty, expand seed terms, uncover the keywords and pages driving a site's search visibility, and classify search intent. Every endpoint uses the same SocQ API key, asynchronous task flow, and normalized result format.
Available SEO APIs
Choose by input and research goal: use Google Organic SERP for one query; Keyword Difficulty, Keyword Overview, Keyword Search Volume, or Search Intent for prepared lists; Keyword Suggestions or Related Keywords for seed terms; and Keywords for Site, Ranked Keywords, or Relevant Pages for domain and page research.

seo/google-organic-serp
Search0.1 credits / result

seo/keyword-difficulty
Search0.1 credits / keyword

seo/keyword-overview
Search0.15 credits / keyword

seo/keyword-search-volume
Search24 credits / request

seo/keywords-for-site
Search0.1 credits / result

seo/keyword-suggestions
Search0.1 credits / result

seo/ranked-keywords
Search0.1 credits / result

seo/related-keywords
Search0.1 credits / result

seo/relevant-pages
Search0.15 credits / result

seo/search-intent
Search0.1 credits / keyword
What SEO data can you retrieve?
Use normalized top-level fields for common analysis, with complete source objects retained when an endpoint returns additional context.
Google organic results
Retrieve titles, destination URLs, rank positions, result element types, and available result details for one query and search market.
Search demand and paid metrics
Measure available search volume, CPC, paid competition, and monthly search history for prepared or discovered keywords.
Organic ranking difficulty
Compare available 0–100 keyword difficulty scores across lists of up to 1,000 terms in a selected market.
Keyword discovery
Expand a seed query or website into suggested and related terms with demand metrics, monthly history, and relationship depth where available.
Site and page visibility
Find ranking keywords, URLs, positions, estimated traffic context, indexed pages, and ranking distributions for a domain, subdomain, or page.
Search intent
Classify supplied keywords with available primary and secondary intent labels and probability scores.
SocQ SEO APIs vs DataForSEO
SocQ is the simpler fit when your product needs core Google search intelligence and public social data behind one API key, one task lifecycle, and one normalized result model. DataForSEO offers a broader specialist SEO catalog with more product-specific methods and controls.
| Capability | SocQ | DataForSEO |
|---|---|---|
| Best fit | Core Google SERP, keyword, ranking, page, and intent workflows alongside public social-data APIs | Dedicated SEO and SEM infrastructure with broader search-engine, backlink, on-page, business, merchant, and app data |
| Authentication | One Bearer API key for SEO and supported social-data endpoints | Basic Authentication with an API login and generated password |
| Request model | Direct JSON object payloads and one asynchronous submit, poll, and stored-result flow | Product-specific Live or Standard methods with arrays of task objects |
| Result model | Normalized top-level fields plus complete source context | Native nested tasks and results shaped by each API product |
| Cost visibility | Credit rules on each endpoint card, estimates before submit, and final usage in the dashboard | Pay-as-you-go pricing that varies by API, method, priority, result depth, and optional parameters |
How the SEO API works
Each endpoint follows the same asynchronous lifecycle while accepting the input shape required by its research workflow.
1. Choose the input shape
Submit one query, a prepared keyword list, a seed term, or a target domain or page, then set the supported market and language fields.
2. Track the task
Poll /v1/tasks/{task_id} until processing succeeds or fails, with backoff after temporary pressure responses.
3. Read normalized results
Read data.results.items and follow next_cursor while has_more is true.
Keyword Overview is a useful starting point when you already have terms to evaluate. Open an endpoint card for the exact payload used by another workflow.
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 tools"
],
"location_code": 2840,
"language_code": "en"
}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueCommon SEO API use cases
SERP research and monitoring
Capture the organic results, destination URLs, element types, and rank positions returned for a query in a selected market.
Keyword prioritization
Compare demand, CPC, paid competition, organic difficulty, and monthly history across an existing keyword portfolio.
Long-tail and content planning
Expand seed terms into suggestions and related queries for content briefs, topic clusters, and campaign planning.
Competitor visibility research
Find the keywords, ranking URLs, positions, and estimated traffic context associated with a public competitor domain or page.
Page opportunity analysis
Inventory relevant indexed pages and ranking distributions to identify pages and topics for deeper review.
Intent routing and reporting
Use primary and secondary intent labels to segment terms for content, paid search, product pages, or reporting pipelines.
Limits and interpretation
Results depend on the selected endpoint, search market, language, source availability, and the scope of the submitted query, keywords, domain, or page.
- Each endpoint has its own payload contract: some accept keyword arrays, while others accept one query, seed term, domain, subdomain, or page URL.
- Location, language, depth, result limits, and offset support vary by endpoint; use the corresponding endpoint page as the request contract.
- Google Organic SERP returns a live result-page query; keyword and site metrics are analytical signals and should not be treated as the same kind of snapshot.
- Returned rows, individual metrics, monthly observations, intent labels, or probability scores can be absent when source data is unavailable.
- Search volume, paid competition, organic difficulty, estimated traffic, and classified intent are distinct signals rather than interchangeable scores.
- The extra field preserves flexible source context and is not a stable normalized schema.
- These endpoints authenticate with a SocQ API key and do not read private Google Ads or Google Search Console account data.
SEO API frequently asked questions
What is the SocQ SEO API?
The SocQ SEO API is a set of asynchronous REST endpoints for adding Google search intelligence to applications through the same API key and task workflow used across the SocQ platform.
What does the SocQ SEO API suite cover?
It covers Google organic results, keyword demand and difficulty, keyword discovery, site and page visibility, and search-intent classification through authenticated asynchronous endpoints.
Which SEO endpoint should I use?
Use Google Organic SERP for one result page; Difficulty, Overview, Search Volume, or Search Intent for prepared keyword lists; Suggestions or Related Keywords for seed expansion; and Keywords for Site, Ranked Keywords, or Relevant Pages for domain and page research.
Do I need Google Ads or Search Console credentials?
No. Requests authenticate with your SocQ API key, and these endpoints do not access private Google Ads or Google Search Console account data.
Are all SEO API results live?
Google Organic SERP runs a live result-page query. Keyword, intent, site, and page metrics depend on source availability and should be interpreted according to the selected endpoint.
How are the SEO endpoints priced?
Pricing is endpoint-specific. Each endpoint page shows whether credits are calculated from submitted inputs, a fixed request cost, or returned results.
Combine data across platforms for more complete business insights
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.
Amazon API
Search public Amazon products and collect normalized product details, Best Sellers, reviews, and seller-profile records from supported marketplaces.
Douyin API
Retrieve public profiles and videos, search videos, collect one page of comments or creator videos, and inspect a known live room.
Instagram API
Look up or find public profiles and collect follower-list records, following relationships, authored posts, profile-tagged posts, hashtag results, Reels, transcripts, comments, account counts, engagement metrics and media metadata through one asynchronous workflow.
YouTube API
Collect supported public YouTube channel profiles, video details, channel videos, comments, Shorts, keyword and hashtag results, and available transcripts through one normalized asynchronous workflow.
X API
Collect public profiles, follower and following relationships, posts, replies, quotes, retweeters, search results, and current trends. Use consistent results for research and monitoring.
Facebook API
Collect public Facebook Page profiles, posts, group posts, comments, keyword-matched events, and available video transcripts with normalized identity, content, source, format, place, media, reaction, attendance, and engagement fields.