To report search spam to Google, use the channel that matches the issue and describe a specific, reproducible behavior. A competing page ranking above yours, a short article or AI-assisted writing is not enough to establish a violation. The useful starting point is what the page actually does.
Google's current search-quality reporting guidance says reports help improve spam-detection systems and may also be used to take manual action. Submission is not confirmation of a violation, a promise of individual action or a guaranteed removal deadline.
Choose the right reporting route
| Issue | Where to start | Important distinction |
|---|---|---|
| Spam, deceptive pages or suspected ranking manipulation in Search | The spam-report link on Google's search-quality guidance page | Match the observed behavior to a current category |
| Phishing or malicious software | The Safe Browsing links on that same guidance page | A security report is different from a general quality complaint |
| Copyright or another legal issue | Google's legal reporting process | Provide the information required for the product, jurisdiction and claim |
| Exposed private personal information | The applicable personal-information removal process | Use the specific eligibility criteria instead of pasting private information into a spam complaint |
| Your own website has been hacked | Repair the site and investigate the Search Console Security Issues report | Reporting another site cannot fix your service or replace a security review |
Google's legal help distinguishes legal and product-policy requests. The same content may be reported through both paths, but each request must be filed separately. A removal from Google also does not remove the material from the website hosting it.
Report the behavior, not a label
The Search Quality User report documentation describes categories covering spam content, spam behavior, deception, low quality and unnatural links. Read the relevant category before selecting it. Checking every category does not make the supporting facts stronger.
- Scraped or scaled content: identify the copied material, source and lack of added value, or the specific pattern of unhelpful pages. A detector's AI percentage is not a policy verdict.
- Misleading behavior: record the entry URL, conditions and subsequent action. A legitimate migration, login difference or mobile layout change is not automatically cloaking or a deceptive redirect.
- Misrepresented functionality: explain what the page offers and what actually happens when that function is used. Separate a reproducible problem from a one-off network failure.
A tool such as Ahrefs can help locate publicly observed pages or links, but a vendor score does not establish a violation. Open the actual page and distinguish the tool's observation date from the date on which the behavior occurred. Do not present an incomplete crawl as a complete account of a website.
A practical evidence note
Prepare a short factual note before opening the form. The following is a teaching template, not a submitted report:
Page: the specific URL where the issue occurs.
Observed: date, time and time zone.
Entry conditions: direct visit or the relevant search query; device, region or login state when needed.
Behavior: the passage, feature or redirect that can be reproduced.
Category: the policy category the facts appear to match.
Steps: where to start, what to select and what happens next.
Limitations: details that have not been confirmed.
“The download control on this URL leads to this different destination under these conditions” is more inspectable than “the whole domain is black hat.” Whether the behavior violates a policy still depends on the facts and the applicable definition. Do not add invented counts, processing statistics or assumptions about the owner's intentions.
Screenshots can help locate a problem when the chosen process accepts them, but they are not a substitute for URLs and a clear description. Use the actual form's attachment rules; there is no general rule that a particular file size, number of URLs or weekday makes a complaint succeed.
Keep personally identifying information out of a spam submission
Google's current reporting page explicitly says not to include personally identifying information in the submission. To comply with regulations, it must send the submission text to the site owner to provide context if a manual action is issued. Google says it will not process a submission it determines contains personally identifying information.
Do not include names, personal contact details, credentials or other identifying information in a search-spam narrative, and do not assume the narrative will remain visible only to Google. If the issue is exposure of private information itself, use the dedicated removal route and follow its requirements. The two workflows serve different purposes.
Check before sending, then track the right outcome
- Revisit the exact page. Confirm that the reported issue is still present rather than repaired or legitimately migrated.
- Separate the site's behavior from an advertisement, third-party embed or local browser problem.
- Check that the evidence supports the selected category and the full scope of the claim.
- Remove identifying information and unsupported assumptions. Submit through the appropriate official route.
- Keep the actual confirmation and your submitted text. Follow any channel-specific request for further information.
There is no supported promise that a report filed on Tuesday will be processed faster, that several URLs guarantee a review or that a site will lose rankings within a fixed number of days. A later ranking change alone does not establish that your report caused it.
If your original content is being outranked by a scraping site, investigate your own indexing, canonical signals and page quality as a separate task. A spam report, a copyright claim and a reconsideration request are different mechanisms; one does not substitute for the others or guarantee your own rankings will improve.