MerlinoxHow does Google interpret JS redirects?
👉🏻 It indexes the start page
👉🏻 It doesn't index the destination page
👉🏻 It sees redirect as a DOM update and uses the content of the destination page
🇺🇦 Optimisey 🇺🇦@merlinox Interesting.
I wonder if Googlebot would behave differently if the original/start page was not blank?
I still think Googlebot crawls a lot *without* javascript (like a 'forward scout bot') so if the page the scout found wasn't empty - would it behave differently? 🤔
Dave Smart 
@optimisey @merlinox my experience is that they are treated much like 302 redirect, so rather than seeing as a DOM update, it's more a case of the first url being treated as the canonical of the second's content for a while. This normally changes given time.
@dwsmart @optimisey When 302 was treated by Google as 302 the destination content was temporarily ignored. In that case, the destination content is the only content Google considers.
ps: now Google treats 302 as 301!
There's still a difference between 302 and 301, (see: https://developers.google.com/search/docs/crawling-indexing/http-network-errors) and canonicalisation still applies, so it can go both ways. 302 hijacking was a thing for a reason until they tightened this up, mainly now same origin stuff.
302 eventually becomes 301, once they decide that's what you mean, and from a very practical level, you are right, long term they do.
@dwsmart @optimisey about that topic there are a lot of tweets:
https://twitter.com/search?q=from%3Ajohnmu%20302&src=typed_query&f=live
The summary is that a 302 will become a 301 in an unknown x time!