11–20 of 52 posts
"Optimizing" UI for session length and clicks is the same thing as finding the local maxima of bad, right?
Not necessarily - if I have a website that is trying to offer information to people about something, then it's better for everyone if it's more navigable/undersatandable, which session length / clicks might be a proxy for. That said, it certainly can be.
"Optimizing" UI for session length and clicks is the same thing as finding the local maxima of bad, right?
The effects of this are easiest to see with online recipes; the highest ranking recipes are all thousand word ramblings with a recipe tacked on at the end. Google sees you spent more time on the site (i.e. wasted scrolling) and thinks you were more 'engaged.'
"Optimizing" UI for session length and clicks is the same thing as finding the local maxima of bad, right?
I just hope they won't kill Experiments in Google Analytics.
Earlier quoted context omitted.
Not necessarily - if I have a website that is trying to offer information to people about something, then it's better for everyone if it's more navigable/undersatandable, which session length / clicks might be a proxy for. That said, it certainly can be.
If your users find what they need right away, session times will go down.
"Published Mar 30, 2017" (I'm not complaining–it's interesting and I'll give it a try. But it's not brand new)
"Optimizing" UI for session length and clicks is the same thing as finding the local maxima of bad, right?
I just hope they won't kill Experiments in Google Analytics.
Why? This is a straight up upgrade over content experiments.
I just hope they won't kill Experiments in Google Analytics.
We have a few thousand visitors a month and are starting to convert, but my guess is A/B testing language and buttons would be premature optimization for us. Just curious at what point that's no longer the case.