Re:What's Going on at Google? Massive Search Engine Spam Attack
by bhartzer on Friday December 22, 2023 @04:49PM
(#38739074)
You can actually get a manual action (penalty) from Google if you do IP cloaking/redirects. It's still mentioned prominently in Google's Webmaster Guidelines: https://support.google.com/webmasters/answer/9044175?hl=en#z...
[ Parent
| on HN ]
Re:What's Going on at Google? Massive Search Engine Spam Attack
by franze on Friday December 22, 2023 @07:21PM
(#38740373)
And then there is Dynamic Rendering which OKed cloaking
https://developers.google.com/search/docs/crawling-indexing/...
and the there are AMP pages which is Google Enforced cloaking...
Re:What's Going on at Google? Massive Search Engine Spam Attack
by londons_explore on Friday December 22, 2023 @11:27PM
(#38741629)
I think by now all search engines run JavaScript and index the rendered page...
Re:What's Going on at Google? Massive Search Engine Spam Attack
by gildas on Saturday December 23, 2023 @06:11AM
(#38743333)
As the founder of SEO4Ajax, I can assure you that this is far from the case. Googlebot, for example, still has great difficulty indexing dynamically generated JavaScript content on the client side.
Re:What's Going on at Google? Massive Search Engine Spam Attack
by charrondev on Saturday December 23, 2023 @11:19AM
(#38745345)
This isn’t about JavaScript vs no JavaScript.
It’s about serving different pages based on User Agent.