Content revised 21 October 2026.
Scraping can raise different concerns depending on what happens. Copied content, excessive server requests and distorted reports need separate evidence and responses.
Identify the behaviour
Review actual requests and copied URLs rather than calling every bot an attacker. A permitted crawler or integration has a different purpose from abusive extraction. Preserve useful evidence before making broad access changes.
Assess technical impact
If requests affect availability, work with the host or responsible engineer on appropriate controls. Avoid blocking legitimate resources blindly. A scraper’s existence does not prove that it caused a performance or ranking change.
Handle copied material carefully
Keep publication records and review permissions and appropriate reporting routes. Duplicate content does not automatically mean an original page receives a penalty. Canonical selection, legal rights and website security are different investigations.
Official guidance: Google canonicalisation context.