On April 23, 2026, Google quietly updated its report-quality-issues page. The change is small in word count and large in consequence: when a spam report you submit triggers a manual action against the reported site, Google will now forward the text of your report to that site’s owner as part of the manual-action notification.
The era of anonymous spam reports is, practically speaking, over. The reporter’s identity is not exposed, but every word you wrote in the submission is.
The exact wording Google added
To comply with regulations, we must send the submission text to the site owner to help them understand the context of a manual action, if one is issued.
Google Search Central, report-quality-issues, last updated 2026-04-23 UTC
Google also strengthened the warning at the top of the form: do not include personally identifying information in your submission. Reports that contain PII risk being discarded outright, both for privacy reasons and because they cannot be safely shared with the recipient.
How we got here — the April 2026 timeline
This change did not arrive in a vacuum. The April 23 clarification is the third entry in a tight ten-day sequence on Google’s Search Central updates feed:
- April 13 — A new spam policy was added for back-button hijacking, slotted under the malicious-practices section.
- April 14 — Google clarified that spam report submissions may now be used to take manual action against violations. Until that point, reports were treated as inputs to the algorithmic spam-detection system, not as direct triggers for human review.
- April 23 — Google further clarified when and why a manual action might follow a spam report, and added the regulatory-transparency clause that forwards the report text to the recipient.
The Google note for the April 23 update reads simply: “To address feedback we received about the change on using spam reports to take manual action.” Translation: the SEO community pushed back on April 14, and Google answered with the transparency clause to balance the new enforcement power with reciprocal openness toward the targeted site.
What this practically means
Three operational changes follow directly from the new wording.
- Spam reports can now meaningfully damage a competitor. Before April 14 a report was a vote into a model. Now it can land as a Search Console notification at the recipient’s end.
- The wording of every report you file is now reader-facing. If you described a competitor’s tactics in colorful language, that language reaches their team verbatim. Treat every report as something you would be comfortable signing.
- The reporter’s identity is not disclosed, but the report itself often contains identifying signal — internal vocabulary, specific URL patterns you only see if you work in the space, observations that a competitor would recognize. “Anonymous” is now closer to “unsigned” than to “unknowable.”
If you report competitors
We, at Taptwice Media, have always advised clients to use spam reports sparingly, and only against clear policy violations rather than tactics they happen to dislike. After April 23 the bar gets higher: write reports the way you would write a regulatory complaint, not the way you would vent to a colleague.
- State the policy violation. Name the specific Google policy clause being broken (cloaking, doorway pages, scaled content abuse, link spam, back-button hijacking, etc.) and link to the policy page if relevant.
- Show the evidence. URLs, screenshots referenced in plain text, dates observed. Facts the recipient cannot dispute.
- Strip personal information. No employee names, no client names, no internal identifiers. Beyond Google’s PII rule, this protects you from inadvertent self-disclosure.
- No editorializing. “This site uses a doorway-page network of 412 pages targeting [keyword variants]” is useful evidence. “This site is run by spammers who deserve to be deindexed” is venting and adds no signal.
If you might be reported
The flip side is also new. If a manual action lands on your site, the Search Console notification will include the report wording. That gives you something prior generations of penalized site owners did not have: a direct read of the accusation.
- Read the report carefully. The specific tactics named in the report are the ones your reconsideration request needs to address. Generic “we cleaned up our content” responses do not match the specificity of the new notifications.
- Treat the report as a partial threat model. If a competitor noticed and documented a pattern, others may have too. Audit beyond the cited URLs.
- Do not retaliate. Filing a counter-report against the suspected reporter is exactly the kind of behavior the new transparency clause discourages. Manual actions are not a duel.
Why we expect this to keep evolving
The phrase “to comply with regulations” is doing a lot of work in the new wording. Google did not specify which regulations, but the pattern matches GDPR-style obligations to disclose the reasoning behind automated and semi-automated decisions that affect a person or business. The Digital Services Act in the EU has similar transparency requirements for content-moderation actions on large platforms, and several US states are inching toward parallel frameworks.
The likely trajectory: reports get more transparent, manual actions become more explainable, and the cost of both reporting carelessly and being reported goes up. For brands building durable AI and search visibility, the work has not changed — ship original information, structure content for retrievability, watch what algorithms and answer engines say about you, and respond to issues with evidence rather than emotion.
That last piece — watching what is said about you — gets harder to do casually as the surface expands across Google, AI engines, and now adversarial spam-report channels. Brand mention tracking across AI engines and sentiment control exist precisely to compress that surface back into a single dashboard your team can act on.
Sources
- Google Search Central — Report quality issues to Google (last updated 2026-04-23 UTC)
- Google Search Central — What’s new in Google Search (April 13, 14, and 23, 2026 entries)
