seo/
traffic-estimate

The Traffic Estimate API estimates the Google search traffic of up to 1,000 domains in one request, returning each domain's monthly organic and paid visits with its organic and paid keyword counts.

Traffic Estimate API

Up to 1,000 domains
Organic and paid visits
One row per domain
3 credits / request + 0.1 credits / domain
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Traffic Estimate

A search traffic estimate puts a number on the monthly visits a website receives from Google results in a given country and language, split into organic visits with the count of keywords the site ranks for and paid visits with the count of keywords it advertises on. Lined up across hundreds of domains, these four figures rank prospect and partner lists by size, enrich account records and compare a whole category of competitors side by side.

Traffic Estimate API Features

  • Up to 1,000 domains in one requesttargets takes a list of up to 1,000 domains, and the Traffic Estimate API returns each one as its own row keyed by domain.
  • Four figures for every domainorganic_traffic and organic_keywords_count measure unpaid search visits and rankings, while paid_traffic and paid_keywords_count measure visits and keywords from search ads.
  • One market for the whole batchlocation and language parameters set the Google country and language for every domain in the list, defaulting to the United States and English.

Traffic Estimate API Parameters

ParametersRequiredDescription
targetsRequiredUp to 1000 domains to estimate, such as notion.so or figma.com, one per line or separated by commas; https:// and www. are removed.
location_codeOptionalNumeric Google country code applied to every domain in the list; 2840 for the United States is the default. Use this or location_name.
location_nameOptionalCountry name, for example United States, used instead of location_code; if you send both, they must describe the same country.
language_codeOptionalLanguage code for the search market, en by default; it must be a language available in the chosen country.
languageOptionalLanguage name, for example English, used instead of language_code; if you send both, they must match.

How to Use the Traffic Estimate API

Submit a list of domains with a market to the Traffic Estimate API and read one traffic row per domain.

  1. POST {"targets": ["notion.so", "figma.com", "canva.com"], "location_code": 2840, "language_code": "en"} to /v1/seo/traffic-estimate.
  2. Poll GET /v1/tasks/{task_id} until status is succeeded.
  3. Read the rows from results.items and follow results.next_cursor while has_more is true, which a long domain list will need.
curl -X POST "https://api.socq.ai/v1/seo/traffic-estimate" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"targets":["notion.so","figma.com","canva.com"],"location_code":2840,"language_code":"en"}'

# 3 credits per request plus 0.1 per domain in targets.

Traffic Estimate API Use Cases

  • Ranking a prospect list by search traffic: Submit a sales or partnership list to the Traffic Estimate API and sort it by organic_traffic to put the sites with the largest search audiences at the top.
  • Enriching CRM accounts: Write organic_traffic and organic_keywords_count onto each account's website field so reps can segment accounts by search size.
  • Benchmarking a whole category: Estimate every brand in a market at once and compare organic_traffic and organic_keywords_count to see who leads search in that category.
  • Spotting search advertisers in a list: Filter Traffic Estimate API rows with paid_keywords_count above zero, and rank them by paid_traffic, to find the domains already buying Google search ads.

Traffic Estimate API Pro Tips

  • Clean the list before sending: enter bare domains or site roots only, because a single entry with a path or an invalid name rejects the whole Traffic Estimate API request.
  • Remove duplicates such as example.com and www.example.com before submitting; they collapse into one row, but every listed entry counts toward the per-domain charge.
  • Join results back to your list on the domain field rather than by position, since rows can come back in a different order from targets.
  • Split a mixed list by country and send one request per market, because location and language apply to every domain in a request.
  • For a shortlist that needs position bands, traffic value and ranking changes, follow up with the Domain Overview API on each domain.

Beyond the Traffic Estimate API, 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.
  • Domain Overview API — Get one domain's organic and paid Google totals for a chosen country and language, with ranking keywords, estimated traffic and its ad cost, position bands and ranking changes.
  • Competitor Domains API — Find the domains ranking for the same Google keywords as a site in one market, with shared keyword count, average position, overlap traffic and full search totals.
  • Domain Technologies API — Detect the technologies a website runs from its domain, with categories, authority rank, social profiles and published contacts.

Explore other platforms

Combine SEO data with public data from other supported social platforms.

Traffic Estimate API — FAQ

Traffic Estimate API is a programmatic interface for estimating the Google search traffic of up to 1,000 domains in one country and language at once. It returns each domain's estimated monthly organic and paid visits together with its organic and paid keyword counts.

It covers search traffic in bulk: organic_traffic and paid_traffic estimate the monthly visits each domain gets from Google organic results and search ads in the chosen market.

Up to 1,000 domains in targets. Larger lists can be split across several requests, each billed on its own.

Each request costs 3 credits plus 0.1 credits per domain in targets, so 100 domains cost 13 credits and 1,000 domains cost 103.