A website Spam Score is a third-party research result whose meaning depends on the provider. It is not an official Google penalty label or a universal probability of being banned.
When checking online, keep the source, domain scope and result date with the evidence. Investigate real findings rather than treating a lower number as a promise of more traffic or revenue.
Choose the metric before entering the address
Moz’s official guide explains its Spam Score as a model based on features correlated with penalised or banned sites. It is not calculated by averaging the scores of websites linking to the queried site.
Other providers’ link-risk or research measures should not automatically be called the same metric. Read current documentation instead of applying the obsolete 0–17 description to every service.
Our definition and investigation guide explains that boundary.
Record the online result accurately
Use the provider’s current supported report and check the exact root-domain, subdomain or page scope. Keep the score distinct from results shown for individual referring sites.
A missing evaluation is unknown, not a zero-risk score. Do not assume the report names every feature triggered by your own site; inspect its actual scope and explanations.
For a hypothetical report showing one value for the queried site and another for a referring domain, keep them as separate findings. The second result does not become a direct diagnosis of the first site’s Google status.
Use those values to choose what to inspect next, recording the actual page observation rather than translating the model into a penalty claim.
Preserve useful source pages and observations so a future comparison does not depend on a changing screenshot alone.
Investigate content and link context
Review the site’s purpose, important pages and relevant references. Inspect source pages directly for current links and surrounding explanation. Record concrete concerns without automatically diagnosing a Google action.
For an existing or expired name, inspect earlier uses and evidence gaps. Archives cannot prove complete clean history or grant ownership of the former content.
Our analytics guide keeps observations and estimates separate.
Use authoritative reports for actual findings
For an authorised property, Google’s Manual Actions and Security Issues reports concern specific different findings.
A third-party score cannot substitute for either. No manual action also does not guarantee high rankings or complete security. Google’s spam policies explain relevant practices under your control.
Correct real issues and reassess evidence
Address the supported problem rather than making arbitrary changes to resemble a model’s lower-scoring sites. Google’s disavow guidance describes limited advanced use, not routine action for every high-scoring reference.
Our warning guide helps identify the reporting system. Keep changes and verification dates, and evaluate current evidence instead of expecting score reduction itself to deliver search improvements.