A repeatable domain spam check should leave a record you can compare next time. Otherwise, a collection of screenshots labelled “clean” or “high risk” tells you little about what changed, what was checked or which problems remain unresolved.
For a domain you operate, build a review sheet that separates search-policy findings, website safety, email reputation and third-party link research. Use it after a relevant change or new concern, and as part of a maintenance routine suited to the services you run.
Define the domain and the services being reviewed
Record the exact domain, important subdomains and public website addresses. Identify the authorised Search Console property, website administrator and email provider where applicable. An old hosting IP or a retired subdomain can produce a result that does not describe the current service.
Our DNS guide explains why registration, nameserver delegation and service records are different facts. Keep a recent service inventory so a mail-server change is not mistaken for a change to website content.
If you are considering a purchase rather than reviewing your own operation, use the pre-purchase spam review. Public research cannot provide all the evidence available to an authorised owner.
Give each check its own result and scope
In an authorised property, Google’s Manual Actions report supplies manual search-policy findings. Record the property and result you actually reviewed. An absence of manual actions is not a guarantee about every ranking system or future search performance.
The separate Security Issues report addresses harmful and compromised content. Record any finding, sample affected URLs and investigation status. Do not combine these two reports into one unexplained “Google blacklist” column.
For public safety research, Google’s Safe Browsing site-status tool provides a different check. A result is evidence about that system at that time, not a complete history of every page or service. A failed lookup should remain unconfirmed.
Build a record that survives the next review
| Field | What to record |
|---|---|
| Identifier | Exact domain, subdomain, page or IP checked. |
| System | Report or provider, with the relevant definition. |
| Observation | The result shown, date and evidence location. |
| Interpretation | What the result supports and what remains unknown. |
| Action | Responsible person, next check and completion evidence. |
Keep sensitive exports in an appropriate location rather than embedding account data or credentials in a shared spreadsheet. A colleague should be able to repeat the permitted check without needing your password.
Review email reputation only where it is relevant
The Spamhaus Domain Blocklist documents domain-based filtering. If mail delivery is the concern, also preserve actual rejection messages and identify the system named in them. A domain result and a sending-IP result are not interchangeable.
A listing needs its particular explanation and correction route. A domain not found in one list is not certified acceptable to every receiving provider. Avoid interpreting ordinary third-party link scores as measurements of whether an email will reach the inbox.
Compare evidence, not incompatible score scales
A vendor metric can help prioritise investigation. Moz’s Spam Score documentation describes a feature-correlation measure, not this domain’s confirmed Google penalty status. Record the exact product and units instead of copying a bare number.
Review important referring pages and content changes relevant to the concern. An increase in repeated links can reflect a site-wide placement; investigate the source and context rather than deleting every unfamiliar reference. Our backlink analysis guide provides a structured inspection approach.
In a hypothetical review, the owner reports remain unchanged while one vendor changes its displayed value. That supports checking the vendor’s scope and data, not announcing a new manual action. If the opposite occurs and an owner report identifies a problem, follow that evidence even when a third-party score looks reassuring.
Finish with supported actions and open questions
Assign each genuine finding to the person who can resolve it. Record what changed and how the correction was verified. Keep unavailable account evidence, missing tool data and unanswered provider queries visible.
For the next review, compare the same identifiers and systems where possible. A useful routine produces a clear change record and proportionate actions; it cannot guarantee permanent reputation, search visibility or freedom from every possible form of abuse.