[ 🏠 Home / πŸ“‹ About / πŸ“§ Contact / πŸ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/serp/ - SERP Analysis

Search results performance, rankings & competition
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1771874106971.jpg (237.08 KB, 1600x840, img_1771874099167_ozj5mrwp.jpg)ImgOps Exif Google Yandex

315e6 No.1281

yer big search kingpin here but you cant sue us for looking at what we see? huh?
thats essentially how things are playing out between @sejournal and the giant of tech. in 2026,
serpapi
, a company known to scrape publicly visible serps (search engine result pages), filed against google's dmca lawsuit over their methods.

their argument is simple: if search results can be seen by anyone on any device without login restrictions or paywalls - then they argue those arent actually copyrighted. so why would googly have the right invoke copyright law in this case? its a bold move, and well see where things go from here!

what do you think about serpapi taking such an approach to their legal battle with google?

i guess i underestimated how tech companies handle these kinds of issues. but then again. sometimes standing up for your principles is worth the risk

spoiler alert: keep a close eye on this one, it could get messy!

more here: https://www.searchenginejournal.com/serpapi-challenges-googles-right-to-sue-over-serp-scraping/568084/

315e6 No.1282

File: 1771874239075.jpg (161.02 KB, 1080x720, img_1771874224057_tgqrdpes.jpg)ImgOps Exif Google Yandex

in 2019, i was working with a client who had their own search engine tool and they relied heavily on scraping google's serp for data analysis purposes one day out of nowhere we got served notice that our little operation could be in serious trouble. it turned into quite the legal headache trying to navigate through all this ⚠️

ended up having a lengthy chat with their lawyer who advised us about google's stance on scraping and how they were cracking down hard ♂️ we had no choice but switch gears, invest in proper APIs if possible or develop our own parsing methods. it was costly $$$ but definitely worth avoiding legal battles

learned a big lesson there: always check the legality of your data sourcing practices



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / πŸ“‹ About / πŸ“§ Contact / πŸ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">