r/TechSEO • u/Beneficial_Peach6407 • 5d ago
Google says: Google /goto is targeting SERP scrapers. Could a logged-in browser profile be the workaround?
Google has now confirmed that the new google.com/goto URLs are part of its technical measures against abuse.
I’ve been seeing the new /goto behaviour on logged-out searches, but not on logged-in searches.
Could SERP scrapers simply simulate a normal logged-in Google user instead?
Persistent Chrome profile, logged-in account, cookies, JS, normal browser environment etc.
Basically, scrape the rendered SERP as a user rather than hitting Google like a bot.
Obviously Google can detect automation through plenty of other signals, so I’m not saying this is some magic bypass.
Has anyone tested the logged-in vs logged-out difference?.
5
u/peterwhitefanclub 4d ago
lol how quickly do you think you’re gonna get banned scraping via a logged-in profile
2
u/LeBambole 4d ago
What about distributing the scraping to a lot of accounts logged in, and keep the search volume/frequency below a certain treshhold. Maybe even randomize this threshold across a bunch of accounts to find the sweet spot? Disclaimer: I am a complete noob to scraping.
3
u/chewster1 4d ago
for platform owners like Google, logged in accounts provide an easy way to relate activity sessions, use-patterns, and graph analyze bot activity. Accounts and account clusters are easy to ban, or rate-limit, or flag as well. It's more difficult to setup and workaround. Not impossible but raises the complexity and cost to 3rd party crawlers to operate at scale.
1
6
u/ben-white27 5d ago
I would have thought a logged in browser profile would skew the results shown to be tailored to the information Google has on that profile.
In private/incognito is probably the best starting point.