Prevention of spam generated by users on your site on Google

Spammers often use open forms for comments and other forms of entering content, creating spam content on the site. Hosting platforms can be subject to a similar type of abuse: spammers can create many sites that violate policemen policies and do not have significant value for the Internet.

Prevention of abuse on your site or platform is usually not difficult. Even simple measures, such as adding an unusual call for users before they can interact with your site, can scare away spamers.

Tell users that spam on your site on Google is not allowed

Publish a clear policy of combating violations and bring it to users, for example, in the process of registration. Also, let the trusted users report the content that they consider spam on your site on Google.

How to identify spam accounts on your Google website

Keep records of registrations and other users' actions on your platform and try to identify typical spam patterns, such as:

Time spent on filling out the form
The number of requests sent from one IP address range
User agents used in registration
User names or other values selected during registration

These signals can help create a user reputation system that will be useful not only for interacting with them, but also for the identification of spamers. Since many spammers want their content to be indexed in search engines, add noindex tag to meta-data for records coming from new users who do not have reputation on your site. After some time, when the user earns a reputation, you can allow the indexation of his content. This will significantly reduce the motivation of spamers to interact with your site.

Since the spammers are often motivated by adding a link to your site, add the nofollow or UGC attribute for all links in unverified content on your Google website.

Using manual approval for suspicious interactions of users on your Google website

Manual approval (or moderation) of some user interactions can significantly reduce the spam level on your site, preventing the immediate creation of content that can be spam. Although moderation adds a load on daily work, it is an effective way to deal with spam. That is why, for example, the moderation of comments is built into most content management systems (CMS).

Using black lists to prevent repeated spam attempts on your Google website

After you find one spam profile, make the process of removing other spam accounts simple. For example, if you notice several spam profiles from one IP address, add this IP to the blocked list. For CMS (for example, WordPress), there are plugins such as Akismet that can help, but adding IP addresses to the lock list on your firewall will also be an effective method.

Blocking automatic registration of accounts on your site on Google

In your form of registration, you can use recaptcha or similar verification tools to allow sending only by human users and prevent automatic scripts from creating many sites on your hosting.

Monitoring of abuse on your site on Google

Follow the signs of spam, such as redirects, a large number of advertising sections, certain spam keywords and large blocks of encoded JavaScript on your site. For this, Site search operators can help: and Google Alerts.
Pay attention to the log of the web server to identify sharp bursts of traffic.
Monitor your site for phishing attacks and infected pages. For example, you can use the Google Safe Browsing API to regularly check URLs from your site.
Develop several reliability checks. For example, if you mainly focus on users from Japan, how likely it is that thousands of user interactions occur from IP addresses from Italy in one night? There are a number of tools for determining the language of recently created sites, for example, libraries for language detection or API Google Translate V2.

To obtain additional recommendations for combating abuse on your Google website and improving its safety, you can contact the SEO of SEO.Computer for any issue for email info@seo.computer or through WhatsApp by number +79202044461.

ID 133