A visitor choosing a familiar website has not chosen every destination an attacker might place behind it. Google’s March 20, 2017 review described a gibberish attack that adds keyword-heavy nonsense pages for search discovery, then redirects visitors elsewhere. The immediate concern for a site’s caretakers is the visitor being taken somewhere unrelated to the intended visit. [google-nohacked]

Another pattern carries a different risk. Google described pages with Japanese text, typically in randomly named directories, using affiliate links to stores selling counterfeit branded goods. The relevant concern is exposure to those storefronts, not the language of the page. Japanese text by itself does not establish wrongdoing, and this account does not demonstrate that a particular visitor purchased anything. [google-nohacked]

Google’s cloaked-page description adds the possibility of misplaced trust: injected material can borrow elements of a site’s template or appear as a 404 error. A familiar-looking page is therefore not enough to settle what happened. Equally, an error message alone is not proof of compromise. These are descriptions of patterns, not a diagnosis of the reader’s website. [google-nohacked]

Our editorial suggestion is a visitor-risk log separating unexpected destinations, counterfeit-shopping exposure and deceptive presentation. For each concern, distinguish an observed page or report from a possible consequence and an unanswered question. That gives faith-based and secular organizations a concrete subject for care: what a visitor may encounter, rather than only what the operator may lose. The log is our synthesis, not a Google cleanup procedure or a claim that harm has already occurred. In March 2013, Google had explicitly framed site security as a concern for operators and visitors alike, while identifying separate damage-assessment resources for spam and malware compromises. Keep that distinction in the log: the spam patterns described here do not establish that a visitor’s device was infected. [google-nohacked][google-hacked-recovery-2013]

Source documents

  1. #NoHacked: A year in reviewhttps://developers.google.com/search/blog/2017/03/nohacked-year-in-review
  2. New first stop for hacked site recoveryhttps://developers.google.com/search/blog/2013/03/new-first-stop-for-hacked-site-recovery