Google Spam Reports Can Lead to Manual Actions: Read the Current Policy Carefully
Google may use spam reports for manual actions and may share submission text with the affected site owner. Report observable behavior without personal data.
Published August 9, 2026: Google now states that it may use a spam report to take manual action against violations. The same documentation warns that the submission text may be sent to the site owner to explain the context of an action, so reporters should not include personally identifying information.
This does not turn a report into an automatic penalty request. A report is evidence submitted for Google’s review. The practical task is to identify the correct form, cite observable policy-relevant behavior, remove personal data, and preserve enough context for the issue to be evaluated.
What Google’s current wording means
Google’s quality-issue page says reports help it understand how to improve spam-detection systems. For spammy, deceptive, or low-quality pages, it adds that Google may use a report to take manual action against violations. “May” is the important boundary: the reporter does not decide whether a violation exists or which response is appropriate.
The page also separates spam from malware and phishing. Those issues have different forms and response systems. Choosing the closest category reduces ambiguity and avoids turning a security incident into a general ranking complaint.
| Observed issue | Primary route | Useful evidence |
|---|---|---|
| Ranking manipulation or deceptive page | Search spam report | URLs, visible pattern, relevant spam policy |
| Malicious or unwanted software | Malware notification | Affected URL, browser or scanner evidence |
| Page impersonating another to steal data | Safe Browsing phishing report | Impersonated entity, deceptive URL, capture |
| Copyright or legal removal request | Relevant legal process | Rights and jurisdiction-specific information |
Write for review, not retaliation
A useful report names the page, identifies the observable technique, and maps it to a current policy. It avoids assumptions about the site’s owner, motives, revenue, or identity. Replace “this company is a scam” with a reproducible observation such as “these five doorway URLs show substantially similar pages and redirect visitors to the same destination.”
- List the smallest representative set of URLs.
- Describe what a reviewer can see or reproduce.
- Link the relevant Google spam-policy section.
- State the date, device, and location only when they affect the behavior.
- Remove names, email addresses, account details, and other personal information.
- Keep the raw evidence privately in case the public behavior changes.
Do not submit a competitor merely because it ranks above you. A disagreement with relevance or quality is not automatically evidence of a documented spam technique.
Assume the submission text may be disclosed
Google says it must send the submission text to the site owner to help explain the context of a manual action, if one is issued. It also says a submission containing personally identifying information may not be processed. Write every sentence on the assumption that the affected owner could read it.
That boundary protects both privacy and evidence quality. Do not include an employee’s name, a private email thread, customer information, an account number, or an IP address that can identify a person. If sensitive evidence is essential to a legal or security matter, use the process designed for that matter rather than placing it in a general spam report.
A URL can contain personal information in its path or query string. Review the full URL before submitting it, and provide a sanitized representative URL where possible without making the issue impossible to verify.
Separate a report from an outcome
Google does not promise individual feedback, a manual action, a ranking change, or a timeline. A later movement in Search cannot be attributed to the report without direct evidence. Automated systems, recrawling, site changes, competitors, and manual review can all overlap.
| Evidence layer | Can be recorded? | Interpretation limit |
|---|---|---|
| Report submitted | Yes, with date and reference | Does not prove acceptance |
| Manual action shown to owner | Yes, if owner provides evidence | May not reveal the reporter |
| Search visibility changed | Yes, as an observation | Does not prove the report caused it |
| Page removed or repaired | Yes, with dated captures | Owner or host may have acted independently |
Use the process as an internal quality check
The same evidence template can improve a site’s own review. Before accusing another page, ask whether your templates create doorway pages, scaled low-value sections, expired-domain abuse, hidden redirects, misleading functionality, or third-party content published without oversight. Google’s spam policies apply to techniques, not to who reports them.
Keep policy claims current. Google can revise definitions and examples, so link the exact policy section and record the review date. The back-button hijacking audit shows how to turn one deceptive-behavior concern into a reproducible technical review without assigning intent prematurely.
Ask a question or join the discussion