Google updates in 2022
Rating: 0 / 0

Google updates in 2022

  • 24 January 2023 - 13:11. answered

Has your site suddenly dropped traffic by 5 (!) times, and its efficiency has decreased dramatically? Do not rush to blame everyone and everything, for example, specialists in search engine promotion or filling a resource with content. Most likely, they have nothing to do with it. And you, like many website owners around the world, have become a victim of another Google update. The search engine periodically (usually several times a year) makes adjustments to the ranking mechanisms of sites in search results. Let's face it, Google is not too willing to disclose all the algorithms for forming its "love" or "hate" for a particular web resource. It's just that competent SEO promotion specialists intuitively, based on rich experience, like pilots in an ocean raging during a storm, conduct customer sites through dangerous shoals, bypass steep cliffs and other obstacles to the promotion of the resource. 

Why is there a comparison with the marine theme? It's very simple: the fact is that almost everyone calls the next update that took place in May 2022 a real disaster. The sites were "shaking" in the output worse than the ships opposing the ninth shaft. Therefore, only a team of professionals who are engaged in site support can bring a web resource out of such a peak. And if there are no such "sea wolves" at hand? Well, then it remains only to pray and put yourself in the hands of fate. What if she turns to face you, and not another place that is not too desirable in such a situation? Moreover, Google promises that after the changes, some pages, on the contrary, will be able to dramatically increase their rating. So as a result of the storm, not everyone will crash and run aground — you see, some nondescript at first glance boat will rise to the crest of the wave. Then she will proudly stare at the competitors from the very top and survive her "moment of glory". 

But jokes aside, what actually happens during such updates, and how to handle the situation?

The word is provided by Google  

Let's listen to the representatives of the most popular search engine in the world, providing them with our comments. So, through the mouths of its employees, Google claims that:

  1. The released updates are designed to make the ranking more fair, and the search results will better match the users' requests. That is, everyone should be happy.
  2. Updates, including those of 2022, are not directed against or, on the contrary, in the interests of a certain category of resources or specific sites. Supporters of the big conspiracy theory can sleep peacefully.
  3. Updates are likely to affect the rating of many web resources to one degree or another, although it is unknown in which direction. Just like when a ship overcomes the ninth wave — someone will be on the crest of a wave, and others will drown in the depths of the waters. So-so perspective, don't you think?
  4. In many cases, site owners do not need to change anything (why not specify who specifically should not worry?) But, if the ranking and traffic have decreased, then you should not think that something is wrong with your site. It's just that now the search engine sees the situation differently. But for someone, the effectiveness of the site may increase! (I wonder if it's like a lottery?)
  5. Updates are needed to better evaluate the quality of content. But then Google almost threatens (or warns). If you are confident in the high quality of the information presented on your site, and taking care of the visitors of the resource is one of the main priorities, then there is nothing to worry about. Like, everything will be "in chocolate". But in fact, not everything is so rosy.

What should the owners of sites that have been affected by the update do? 

In fact, the members of the Google team really do not fully understand how the search robot will behave when the ranking algorithms change. In this sense, they are not lying, because, in fact, the right to "execute and pardon" has been transferred into the hands of artificial intelligence. Unfortunately, the result of updates cannot be predicted, but it is quite possible to minimize the possible negative effect of their implementation. The accumulated experience, intuition and well-coordinated joint work of webmasters are designed to help in this.

When a solid web studio is engaged in SEO promotion of your site, which simultaneously conducts other projects, then the so-called collective intelligence and comparison of the situation with other resources will allow you to "get to the truth" faster. Then the team will work together to understand what the new search engine algorithms want from the site, and quickly find the optimal solution. Otherwise, you will have to surrender to the will of providence and, like ancient navigators, rely on the favor of Poseidon or Neptune (in our case, the lord of the depths of the Internet has a different name that every user of the world Wide web knows

  • Comments from the site (57)
Adding a comment
tGhYxqFm'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),12)||' , Jan. 24, 2023, 1:11 p.m.
0
555
reply
CJK8DF8g')) OR 91=(SELECT 91 FROM PG_SLEEP(12))-- , Jan. 24, 2023, 1:11 p.m.
0
555
reply
tyPF0SWT') OR 338=(SELECT 338 FROM PG_SLEEP(12))-- , Jan. 24, 2023, 1:10 p.m.
0
555
reply
47jdzcHl' OR 20=(SELECT 20 FROM PG_SLEEP(12))-- , Jan. 24, 2023, 1:10 p.m.
0
555
reply
ydsNw2sj'; waitfor delay '0:0:12' -- , Jan. 24, 2023, 1:10 p.m.
0
555
reply
1 waitfor delay '0:0:12' -- , Jan. 24, 2023, 1:10 p.m.
0
555
reply
(select(0)from(select(sleep(12)))v)/*'+(select(0)from(select(sleep(12)))v)+'"+(select(0)from(select(sleep(12)))v)+"*/ , Jan. 24, 2023, 1:10 p.m.
0
555
reply
0"XOR(if(now()=sysdate(),sleep(12),0))XOR"Z , Jan. 24, 2023, 1:10 p.m.
0
555
reply
0'XOR(if(now()=sysdate(),sleep(12),0))XOR'Z , Jan. 24, 2023, 1:09 p.m.
0
555
reply
if(now()=sysdate(),sleep(12),0) , Jan. 24, 2023, 1:09 p.m.
0
555
reply
129' , Jan. 24, 2023, 1:09 p.m.
0
555
reply
-1" OR 2+302-302-1=0+0+0+1 -- , Jan. 24, 2023, 1:09 p.m.
0
555
reply
-1' OR 2+543-543-1=0+0+0+1 or 'DuMNhiUh'=' , Jan. 24, 2023, 1:09 p.m.
0
555
reply
-1' OR 2+104-104-1=0+0+0+1 -- , Jan. 24, 2023, 1:09 p.m.
0
555
reply
-1 OR 2+556-556-1=0+0+0+1 , Jan. 24, 2023, 1:09 p.m.
0
555
reply
-1 OR 2+569-569-1=0+0+0+1 -- , Jan. 24, 2023, 1:09 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:09 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:09 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:07 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:07 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:05 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:04 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:04 p.m.
0
I3JNaA6E')) OR 209=(SELECT 209 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 1:04 p.m.
0
5WfVozWj') OR 209=(SELECT 209 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 1:04 p.m.
0
tYHSFHhs' OR 824=(SELECT 824 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 1:03 p.m.
0
-1)) OR 367=(SELECT 367 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 1:03 p.m.
0
-5) OR 116=(SELECT 116 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 1:03 p.m.
0
-5 OR 843=(SELECT 843 FROM PG_SLEEP(12))--
reply
tGhYxqFm , Jan. 24, 2023, 1:03 p.m.
0
T378Ib94'; waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 1:03 p.m.
0
1 waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 1:02 p.m.
0
-1); waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 1:02 p.m.
0
-1; waitfor delay '0:0:12' --
reply
tGhYxqFm , Jan. 24, 2023, 1:02 p.m.
0
(select(0)from(select(sleep(12)))v)/*'+(select(0)from(select(sleep(12)))v)+'"+(select(0)from(select(sleep(12)))v)+"*/
reply
tGhYxqFm , Jan. 24, 2023, 1:02 p.m.
0
0"XOR(if(now()=sysdate(),sleep(12),0))XOR"Z
reply
tGhYxqFm , Jan. 24, 2023, 1:02 p.m.
0
0'XOR(if(now()=sysdate(),sleep(12),0))XOR'Z
reply
tGhYxqFm , Jan. 24, 2023, 1:02 p.m.
0
if(now()=sysdate(),sleep(12),0)
reply
tGhYxqFm , Jan. 24, 2023, 1:02 p.m.
0
611'
reply
tGhYxqFm , Jan. 24, 2023, 1:01 p.m.
0
-1" OR 2+368-368-1=0+0+0+1 --
reply
tGhYxqFm , Jan. 24, 2023, 1:01 p.m.
0
-1' OR 2+849-849-1=0+0+0+1 or 'X8nlleYk'='
reply
tGhYxqFm , Jan. 24, 2023, 1:01 p.m.
0
-1' OR 2+152-152-1=0+0+0+1 --
reply
tGhYxqFm , Jan. 24, 2023, 1:01 p.m.
0
-1 OR 2+161-161-1=0+0+0+1
reply
tGhYxqFm , Jan. 24, 2023, 1:01 p.m.
0
-1 OR 2+789-789-1=0+0+0+1 --
reply
tGhYxqFm , Jan. 24, 2023, 1:01 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 1:01 p.m.
0
555
reply
�''�"" , Jan. 24, 2023, 12:54 p.m.
0
555
reply
�'�" , Jan. 24, 2023, 12:54 p.m.
0
555
reply
JyI= , Jan. 24, 2023, 12:54 p.m.
0
555
reply
@@lb4Wc , Jan. 24, 2023, 12:54 p.m.
0
555
reply
\ , Jan. 24, 2023, 12:54 p.m.
0
555
reply
1'" , Jan. 24, 2023, 12:54 p.m.
0
555
reply
tGhYxqFm , Jan. 24, 2023, 12:54 p.m.
0
�''�""
reply
tGhYxqFm , Jan. 24, 2023, 12:54 p.m.
0
�'�"
reply
tGhYxqFm , Jan. 24, 2023, 12:54 p.m.
0
JyI=
reply
tGhYxqFm , Jan. 24, 2023, 12:54 p.m.
0
@@pTumI
reply
tGhYxqFm , Jan. 24, 2023, 12:54 p.m.
0
\
reply
tGhYxqFm , Jan. 24, 2023, 12:54 p.m.
0
1'"
reply
tGhYxqFm , Jan. 24, 2023, 12:52 p.m.
0
555
reply