The thorough index of Google penalties and how to retrieve

There is a great deal of Fear, Uncertainty, and Doubt regarding Google penance, the most repeated one among them is misunderstanding an algorithm for a penance.

Penguins and Panda, the high profile updates are algorithms, not penance. To provide the desired result spontaneously, algorithms depend on a set of orders and calculations.

In the matter of Panda and Penguin, the key objective of Google is to recompense or reward websites in the search results that successfully attain their “quality standards” as explained by Webmaster Guidelines. For the web sites that glide through the algorithms but fail to fulfill Google’s quality standards, Google recruits an army of human reviewers for reviewing and rating them.

Existing on the inaccurate side of an algorithm definitely feels like a penance. The net outcome can be similar:

Extensive loss of organic traffic followed by disastrous consequences.

It is important to understand the difference between having your website affected by a manual penance vs. triggering an algorithm. It regulates how to act in terms of advancing a retrieval strategy.

The most remarkable distinction in dealing with an algorithmic event vs. dealing with a penalty is the requirement and chance to communicate directly with Google.

A website that is penalized by Google will get a manual action statement through Google search console. Once the voted violation is fixed, there is a requirement to describe the inception of the problem as well as the resolution in a “Reconsideration request”. On contrary, there is no requirement to file such review appeal to escape an algorithmic complexity.

Now, let us concentrate on familiar manual penances and the procedures for recovery.

Cloaking or Sneaky Redirects

Cloaking is an action of presenting the users & the search engine crawlers with different contents. Both activities violate webmaster instructions.

This penance comes in two forms:

1. Partial matches affecting a section of your website.

2. Site-wide matches affecting your entire website.

The Fix

1. Operate to Google Search Console>Crawl>Fetch as Google, and then get pages from the affected sections of your website.

2. Distinguish the content on your web page with the content delivered by Google.

3. Rectify any differences between the two so they conclude being identical.

4. Examine all redirects and eliminate redirects that:

send users to an unanticipated end.

conditionally redirect or redirect only those users coming from a certain source.

Are otherwise “sneaky”

5. Submit a reconsideration request after fixing these problems.

Pro Tip: These types of redirects are frequently developed by CMS plugins, maybe in your .htaccess file, or could be written in JavaScript.

Cloaking: First Click Free Violation

This Cloaking penance is imposed against websites that display full content to Google but obstruct content viewable to users, basically, users coming from Google’s resources in conformity with Google’s First Click Free policy. If a website requires users to register, logging in or to subscribe to see the full content, then it is not in agreement with the policy.

This is another penance that comes in two forms:

Partial matches affecting a section of your website.

Site-wide matches affecting your whole website.

The Fix

1. The content displayed to users coming from Google’s services must be identical as displayed to Google. Develop any edits required to come into agreement.

2. Submit a review appeal after fixing the problem.

Pro Tip: Utilize Google’s “First Click Free” procedure. Authorize users to glance the entire website without having to log in, subscribe or register when coming in from Google’s services.

Cloaked Images

Cloaking is applicable to images as well. For instance, serving images that:

-are concealed by another image.

-are non-identical from the served.

-redirect users away from the image.

The Fix

1. Display the accurate same image to Google as the users of your site.

2. Submit a review appeal after solving the issue.

Pro Tip: Examine any plugins you have installed to verify they aren’t generating any image of cloaking problem.

Hacked Site

Hackers are frequently looking for exploits in WordPress and various content management systems to insert malicious content and links. This is usually cloaked and complex to detect and fix.

When Google picks up on this, a notification “This Site is hacked” is inserted into the search result for affected pages. This usually leads in a demotion in the organic search results.

The Fix

1. Contact your web host and establish a support team.

2. To prevent any further damage, Quarantine your site.

3. To help recognize the hacking type, use search console.

4. Analyze the nature of the damage, if it is a spam or if it is a malware.

5. Identify the vulnerability to find out how the hacker got access.

6. Clean your site to secure the vulnerability that allowed the hacker to have access.

7. Request a review and inquire Google to re-examine your hacked labeling.

Pro Tip: Be Proactive. Always have a clean and advanced support for your website. Install website protection trait on your website. If you are challenged technologically, use a website protection platform like Sucuri for security.

Hidden Text or Keyword Stuffing

The title says it all. Google has uncovered your website accountable for keyword stuffing or using hidden text.

This is another penance that comes in two forms:

-Partial matches affecting a section of your website.

-Site-wide matches affecting your entire website.

The Fix:

1. Browse to Google Search Console>Crawl> Fetch as Google then get pages from the affected sections of your site.

2. Search for hidden text that is identical in color to the body of the web page.

3. Look for the unseen text using CSS styling or locating.

4. Separate or re-design any unrevealed text so that it is evident to a human user.

5. Remove or fix any paragraphs of recurring words without any framework.

6. Secure