How 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
How 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
@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? π€
Test!
I'm building a test now anyway. :)
Ok - test set up - https://www.simoncox.com/seotests/jsredirect1/
Page 1 indexed with content and is findable with "Javascripted redirected page" as a query.
Page 2 not crawled and indexed yet.
@merlinox @optimisey
More info...
Title of page 1 is: "Javascripting a redirect"
and description: "This is a javascripted redirecting page to see what happens when it is indexed."
The title of page 2 is: "Javascripted a redirect"
and description: "This is a javascripted and redirected page to see what happens when it is indexed."
And we can see the SERP is showing the 1st page URL, The title and description from the 2nd page - even though it is not indexed.
My conclusion so far is that if I come across this with any clients it might be good practice to change the redirect page's title and description to match the landing page.
@optimisey @merlinox
Not yet there is more testing to be done!
Kind of does make sense though if you think about what Google crawls, how and when.