---
updatedAt: 2025-08-13T01:14:54.000Z
agentTools:
projectIndex: https://developer.spyfu.com/llms.txt
---
# Bulk Domain Statistics (Snapshot or History)
Returns SEO and PPC metrics for multiple domains in one request. Suitable for batch enrichment, benchmarking, and portfolio monitoring.
# OpenAPI definition
```json
{
"openapi": "3.1.0",
"info": {
"title": "Domain Stats API",
"version": "v2",
"description": "Access comprehensive domain performance metrics and historical analytics to track search visibility trends, competitive positioning, and market share evolution over time. Powered by SpyFu's unmatched historical data collection spanning 18 years of continuous monitoring across both organic and paid search channels.\n\nSpyFu's Domain Stats API provides **18 years of complete historical data** for every tracked domain, built on a foundation of **1.6 trillion search results** and **152 million domains** analyzed for comprehensive performance metrics. Our database delivers **20x more paid keywords per domain** and **2x more organic keywords per domain** than SEMRush or Ahrefs. **Every domain metric updates every 15 seconds**, ensuring you have real-time performance intelligence across all 28 supported countries.\n\nWhile competitors provide basic domain snapshots with limited history, SpyFu offers complete domain timeline analysis with 18 years of historical data and live updates every 15 seconds. Our comprehensive tracking covers both organic and paid search performance since 2007, providing unmatched insight into long-term domain evolution.\n\nWith this API, you can track domain performance trends across SEO and PPC channels over time, analyze seasonal patterns and growth trajectories, benchmark domain performance against historical baselines, identify performance inflection points and strategy changes, monitor competitive domain performance evolution, and access complete domain visibility metrics spanning nearly two decades. Understand how domains have grown their search presence and learn from successful optimization strategies implemented over years.\n\nThe Domain Stats API integrates seamlessly with SpyFu's SEO Research, Ad History, and Competitors APIs to provide complete domain intelligence, enabling you to correlate performance metrics with specific keyword strategies and competitive activities.\n\nGet started with comprehensive API documentation and interactive examples at [SpyFu Developer Portal](https://developer.spyfu.com)."
},
"servers": [
{
"url": "https://api.spyfu.com/apis/domain_stats_api"
}
],
"paths": {
"/v2/getBulkDomainStats": {
"get": {
"operationId": "DomainStatsApi_GetBulkDomainStats_GET",
"summary": "Bulk Domain Statistics (Snapshot or History)",
"description": "Returns SEO and PPC metrics for multiple domains in one request. Suitable for batch enrichment, benchmarking, and portfolio monitoring.",
"parameters": [
{
"name": "domains",
"in": "query",
"description": "Comma-separated list of domains to analyze. Each domain should be provided as a root domain (example.com) without protocol or paths. Maximum of 1000 domains per request.",
"required": true,
"schema": {
"type": "string",
"examples": [
"example.com,competitor.com,industry-leader.com"
]
},
"example": "example.com,competitor.com,industry-leader.com"
},
{
"name": "countryCode",
"in": "query",
"description": "Country market to analyze. Specifically, this maps to the Google domain version to query against (e.g., google.com for US, google.de for Germany, etc.).",
"schema": {
"type": "string",
"examples": [
"US"
],
"default": "US",
"enum": [
"AR",
"AT",
"AU",
"BE",
"BR",
"CA",
"CH",
"DE",
"DK",
"ES",
"FR",
"IE",
"IN",
"IT",
"JP",
"MX",
"NL",
"NO",
"NZ",
"PL",
"PT",
"SE",
"SG",
"TR",
"UA",
"UK",
"US",
"ZA"
]
},
"example": "US"
},
{
"name": "showOnlyLatest",
"in": "query",
"description": "Controls data scope returned. If true, returns only the most recent statistics for each domain (current snapshot). If false, returns complete historical data showing trends over time for comprehensive analysis.",
"required": true,
"schema": {
"type": "boolean",
"examples": [
true
],
"default": true
},
"example": true
}
],
"responses": {
"200": {
"description": "OK",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"resultCount": {
"description": "Number of results returned",
"type": "integer",
"format": "int32",
"examples": [
1
],
"readOnly": true
},
"totalMatchingResults": {
"description": "The total number of results available that matches the query including\r\nitems that might not be included in the returned results/page.",
"type": [
"integer",
"null"
],
"format": "int64",
"readOnly": true
},
"results": {
"type": [
"array",
"null"
],
"items": {
"type": "object",
"properties": {
"domain": {
"description": "Searched domain",
"type": [
"string",
"null"
],
"examples": [
"domain.com"
]
},
"results": {
"type": [
"array",
"null"
],
"items": {
"type": "object",
"properties": {
"searchMonth": {
"description": "Month when these domain statistics were collected (1-12).",
"type": "integer",
"format": "int32",
"examples": [
5
]
},
"searchYear": {
"description": "Year when these domain statistics were collected.",
"type": "integer",
"format": "int32",
"examples": [
2021
]
},
"averageOrganicRank": {
"description": "Average organic search ranking position across all keywords for this domain during the specified month.",
"type": "number",
"format": "double",
"examples": [
41.08
]
},
"monthlyPaidClicks": {
"description": "Estimated monthly clicks received from paid search advertising across all keywords, calculated based on average ad positions and click-through rates.",
"type": "number",
"format": "double",
"examples": [
61181.88
]
},
"averageAdRank": {
"description": "Average paid search ad position across all advertised keywords during the specified month.",
"type": "number",
"format": "double",
"examples": [
1.03
]
},
"totalOrganicResults": {
"description": "Total number of unique organic keywords where this domain appears in the top 100 search results during the specified month.",
"type": "integer",
"format": "int32",
"examples": [
302731
]
},
"monthlyBudget": {
"description": "Estimated monthly Google Ads spending based on keyword positions, click-through rates, and cost-per-click data across all paid campaigns.",
"type": "number",
"format": "double",
"examples": [
6721.39
]
},
"monthlyOrganicValue": {
"description": "Estimated value of organic search traffic based on keyword rankings and equivalent cost-per-click values, representing the advertising spend equivalent of organic visibility.",
"type": "number",
"format": "double",
"examples": [
384233.16
]
},
"totalAdsPurchased": {
"description": "Total number of unique paid keywords where this domain's ads appeared on the first page of search results, measured over the last 14 data collection periods.",
"type": "integer",
"format": "int32",
"examples": [
599
]
},
"monthlyOrganicClicks": {
"description": "Estimated monthly organic search traffic clicks received from all ranking keywords during the specified month.",
"type": "number",
"format": "double",
"examples": [
290145
]
},
"strength": {
"description": "Domain authority score (0-100) indicating competitive strength and ranking consistency across high-value keywords, with higher scores representing stronger market position.",
"type": "integer",
"format": "int32",
"examples": [
75
]
},
"totalInverseRank": {
"description": "Cumulative ranking score where higher organic positions receive higher point values (position 1 = 100 points, position 2 = 99 points, etc.), summed across all ranking keywords.",
"type": "integer",
"format": "int64",
"examples": [
4971564
]
},
"areStatsNormalized": {
"description": "Indicates whether the statistics have been normalized for consistent comparison across different time periods and data collection methods.",
"type": "boolean",
"examples": [
true
]
}
},
"additionalProperties": false,
"description": "Represents comprehensive domain performance statistics for a specific month, including SEO and PPC metrics, traffic estimates, and competitive strength indicators."
}
}
},
"additionalProperties": false
}
}
},
"additionalProperties": false
}
}
}
},
"400": {
"description": "Bad Request"
},
"401": {
"description": "User failed authorization"
},
"500": {
"description": "Internal Server Error"
}
},
"tags": [
"Domain Stats API"
]
}
}
},
"components": {
"securitySchemes": {
"Basic_Authentication_Token": {
"type": "http",
"description": "Basic Authentication is a standard that involves encoding your SPYFU_API_ID:SECRET_KEY into a Base64 string. Your SpyFu API ID and Secret Key can both be found under the Account Settings -> API Usage page. Additionally, you can find the Base64 string has been pre-generated on the same page under Base 64 Key. Finally, this encoded string is sent in the \"Authorization\" header prefixed with the keyword \"Basic\":
For example, to authorize as 00000000-0000-0000-0000-000000000000:AB12WXYZ the client would send
Authorization: Basic MDAwMDAwMDAtMDAwMC0wMDAwLTAwMDAtMDAwMDAwMDAwMDAwOkFCMTJXWFla
",
"scheme": "basic"
},
"Query_Parameter_Token": {
"type": "apiKey",
"description": "An API key can be added as a query parameter. Your API key is listed as \"Secret Key\" found under the Account Settings -> API Usage page
For example, to authorize with the API key AB12WXY
/apis/example_api/GetExample?domain=spyfu.com&api_key=AB12WXYZ
",
"name": "api_key",
"in": "query"
},
"HMAC_Authentication_Header": {
"type": "apiKey",
"description": "For even more security, each request can be individually authenticated with a timestamped HMAC (Hash Message Authentication Code) signature. Composed of your secret key, a valid timestamp, the API request path, and all request parameters. Creating the signature:
Combine the pieces that will be converted into the signature.
StringToSign =
HTTP-Verb + \"\\n\" +
Timestamp + \"\\n\" +
UrlPath + \"\\n\"
QueryParameters;
Create UTF-8 encodings of the above string and of your secret key.
byte[] SecretKeyBytes = UTF-8-Encoding-Of( Upper-Case-Of( SECRET_KEY ) );
byte[] StringToSignBytes = UTF-8-Encoding-Of( StringToSign );
Use an implementation of HMAC256 using your UTF-8 secret key to encode the combined string of your request. This should then be converted to Base64 to finish creating your signature.
Signature = Base64( HMAC-SHA256( SecretKeyBytes, StringToSignBytes ) );
Using the signature:
This signature is then sent in through an Authentication header with your username.
Authentication: UserName:Signature
",
"name": "Authentication",
"in": "header"
}
}
},
"security": [
{
"Basic_Authentication_Token": []
},
{
"Query_Parameter_Token": []
},
{
"HMAC_Authentication_Header": []
}
]
}
```