A website can receive different kinds of warnings: a search manual action, a security finding, a browser safety warning or a third-party research score. They concern different evidence and remedies. A traffic drop alone does not establish which, if any, applies.
Identify the system reporting the problem before making changes. Record the exact address, date and message so the investigation remains specific.
Check the relevant Search Console reports
For a property you are authorised to access, Google’s Manual Actions report shows relevant human-review actions. The Security Issues report concerns issues such as compromised or harmful content.
Read the affected examples and explanations. Neither an authority score nor public analytics can substitute for those reports. No manual action does not guarantee good rankings or complete security.
Record whether the finding names particular pages, a subdomain or a wider property. That scope guides the investigation and prevents one affected address from becoming an unsupported claim about every service.
Keep the reported issue separate from speculation about why visits changed. Our site assessment guide covers broader technical and content checks.
Review browser and public safety information
Google provides a Safe Browsing site-status tool. Check the relevant address and preserve the reported status and date rather than treating an old screenshot as current evidence.
A browser warning deserves investigation through the provider’s documented process. Do not assume a valid HTTPS certificate establishes that the site’s content is trustworthy or uncompromised.
Understand a remote scan’s scope
Sucuri SiteCheck documents remote checking of publicly visible site content and states that its access and results are limited. A clean remote result cannot inspect every private file or server-side component.
Review actual findings with the host or responsible technical person where needed. Keep affected paths, observed changes and relevant logs. A dashboard number is less useful than the specific issue it identifies.
Keep third-party scores separate
Moz Spam Score is an SEO research metric, not a browser safety decision or an email sender label. Our Spam Score guide explains that distinction.
Use such results to guide evidence checks, avoiding automatic diagnoses or blanket link removal. A high score is not proof of malware, and a low one does not certify absence of compromise.
Resolve documented issues and verify the correction
Investigate unauthorised pages or changes, update affected software and address access problems with the responsible provider. Removing the visible symptom may leave the underlying cause unresolved.
Follow the reporting system’s review instructions once the actual issue is corrected. Google’s spam policies supply the framework for relevant search practices, separate from security remediation.
Maintain a dated issue and change log. Recheck the affected pages and source report, then continue appropriate monitoring. The useful outcome is a verified correction in the system that raised the concern, not an unsupported promise of universal clearance.