Provide 1–10 domains to view each returned website’s DataForSEO Spam Score. Compare the supplier’s 0–100 indicator as one signal for deciding which sites need a closer review.
Up to 0.03436 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
DataForSEO
Compare DataForSEO website spam scores
Provide 1–10 domains to view each returned website’s DataForSEO Spam Score. Compare the supplier’s 0–100 indicator as one signal for deciding which sites need a closer review.
You receive
Receive a list of returned domains with their DataForSEO spam scores and a returned-record count. The supplier describes a domain score as an average of page scores derived from webpage characteristics. Compare the reported values to prioritize further investigation, while keeping the website and its score clearly associated.
Start with your task
Compare the scores for [1–10 website addresses] and explain what they mean. A low score does not prove a site is unsafe or that Google has lowered its place in search results. If no score is available, say so; do not use 0.
What to know
This is a proprietary indicator, not a Google penalty probability, a percentage of spam links or a safety certificate. The result does not reveal contributing page scores, individual signals, page coverage or measurement time. A lower score does not prove safety, and a higher score alone does not justify removing or disavowing links.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
Input schema
Input schema
Field / Path
Type
Requirement
Meaning
Websites to comparedomains
array
Required
Required array of 1–10 bare domains without a protocol or www. Only this domain list is supplied; there are no page, threshold, date or filtering controls.
Minimum items
1
Maximum items
10
Domaindomains[]
string
—
Each array item is a domain string of 3–253 characters, for example example.com. Supply the domain itself rather than a webpage address.
Minimum length
3
Maximum length
253
View raw JSON
{
"type": "object",
"required": [
"domains"
],
"properties": {
"domains": {
"type": "array",
"items": {
"type": "string",
"maxLength": 253,
"minLength": 3
},
"maxItems": 10,
"minItems": 1,
"description": "One to ten bare domains without https:// or www."
}
},
"additionalProperties": false
}
Result schema
No fixed output contract is available. Field types reflect saved result evidence; individual responses can differ.
Result schema
Field / Path
Type
Meaning
Website spam indicatorsspamScores
object
Collection of returned target records with their DataForSEO spam scores and the returned-record count.
Returned website recordsspamScores.items
array
Target-and-score records. Match by target instead of assumed input order, and do not invent scores for missing targets.
Reported targetspamScores.items[].target
string
The domain label associated with this score. Use it to identify the requested website rather than relying on list position.
Proprietary 0–100 target indicator. DataForSEO explains a domain score as an average of individual page scores derived from webpage characteristics. It is not a spam-link percentage, penalty probability or safety verdict; page population and scoring details are not returned.
Returned target-record countspamScores.items_count
number
Number of target-score records delivered in the collection, not the number of pages assessed or a score.
Additional notes
Use the same provider and metric definition when comparing reports. The Bulk Spam Score reference describes this lookup, and DataForSEO’s methodology explanation discusses page features such as metadata, contact information, protocol and link structure. Matching metric names from different providers do not establish matching methods or interchangeable values.
Enter website addresses
Enter 1–10 [website addresses], such as [example.com] or [openai.com].
This score is an estimate based on webpage information. It is not a safety check and does not prove that a site contains harmful software or has been lowered in Google search. A low score does not prove that a site is safe.
Compare the scores for [1–10 website addresses] and explain what they mean. A low score does not prove a site is unsafe or that Google has lowered its place in search results. If no score is available, say so; do not use 0.
Check before taking action
The report does not say when the information was last updated or which web pages were used to calculate the score. It may not cover the whole site. Treat it as one clue and check other information before acting; do not call a site unsafe or remove links based on this number alone.
Questions about this tool.
Inputs, results and details to know before running it.
The exact lookup returns an average target spam score. DataForSEO’s explanation describes domain scoring as the mean of individual page scores, calculated from features such as metadata, contact information and link structure. This result does not show the pages, their individual scores or the features evaluated for a particular target.
No. This is DataForSEO’s proprietary metric. It does not expose Google’s decisions or Moz’s score, and matching 0–100 scales do not make different providers’ values equivalent. Name the provider when comparing results.
The score uses a 0–100 indicator scale, but it is not the percentage of spam backlinks or the probability of a Google penalty. It describes the supplier’s heuristic evaluation of the target, not a calibrated event likelihood.
The score alone does not verify safety, malware, spam or a search-engine penalty. Use it as an attributed review signal and investigate relevant evidence before taking action. A low value is not a safety certificate, and a high value is not an automatic removal or disavow rule.
This aggregate lookup does not return per-page explanations, contributing signal values or a detailed backlink list. The general methodology can explain how the metric is designed, but it cannot establish which specific factors produced this target’s returned score.
No measurement timestamp or assessed-page population is returned. The result does not establish that all pages or subdomains were freshly assessed. Treat the score as the supplier’s reported value rather than proof of a new complete crawl or a current inspection of website health.
Match records by their returned target labels. items_count is the number of score records returned, not pages assessed, and list position does not establish input order. Preserve zero, null and missing distinctly; do not assign zero or a safety verdict to a target or value that was not returned.
