Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Google mobile algo to be bigger than Panda / Penguin as deadline looms

         

Whitey

8:54 am on Mar 19, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Gary Illyes retweeted
Aleyda Solis @aleyda Mar 17
Zineb from Google at #smx Munich about the mobile ranking update: is going to have a bigger effect than penguin and panda! [twitter.com...] .
In case you know someone who hasn't heard, you might want to forewarn them of the impending intensity of this.

I wonder if the algorithm will allow a quicker reprieve for those that go under, but are mobile friendly afterwards, or, if it makes those who are putting in late changes more vulnerable, as the algorithm might be baking already, as the deadline looms.

Anyone you know not heard / caring ; other thoughts ?

Dugger

9:42 pm on Mar 20, 2015 (gmt 0)

10+ Year Member



By the way, Webmasterworld only gets a 58/100 for user experience on Mobile. Still lots of work would need to be done to appease Google.

lizardx

9:59 pm on Mar 20, 2015 (gmt 0)

10+ Year Member



Exactly, there is something PROFOUNDLY wrong with google's concept of mobile vs desktop, and I fear it's caused by that idiotic pattern of young developers who don't have a clue about life outside their brains but who live and interact primarily on their expensive large screen mobile devices. I've seen this before, for example, Firefox devs, who all ran huge ram systems, for years ignored active and valid bug reports about firefox memory leaks, because they couldn't be bothered to actually use a normal user desktop with finite ram, where you'd actually see the bug.

Even the statement to design for mobile first, which is the thing I really noticed in their webmaster mobile advice link, is downright idiotic, that's BAD design, there is no benefit to it at all, though it does certainly today pay to design concurrently with mobile in mind, this is very simple actually, all you have to do is avoid placing structures into primary containers (think left or right nav type bars) and simply allow things to float, for example, rather than have a contained right bar, with sub components, just have the sub components floated, and have the content cell have a width, so they appear to be two columns. Sure it breaks existing and very good new html5 like using <section> for logical sectioning of html, but that doesn't matter that much, but then you can easily handle what you do with the column data for mobile.

webmasterworld is fine on mobile, always has been, the problem here is the google mobile team, and that's what worries me, they are clearly young idiots with no real experience, that's crystal clear, probably with the same asbergers issues that are so increasingly common in silicon valley. This is however one of the most extreme manifestations of that problem I've seen to date, and the one that impacts me as a dev and user the worst.

This is not to say that mobile shouldn't be handled, it should be, but not the way google says, if they want to not be evil, which is by this stage a total joke for anyone who has seen first hand their mafia like extortion known as 'adwords', they need to not allow stupid kids to make up rules that impact grownups.

Robert Charlton

10:36 pm on Mar 20, 2015 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



By the way, Webmasterworld only gets a 58/100 for user experience on Mobile.

Actually, a responsive, mobile-friendly version of WebmasterWorld has been in the works for some time. As you might imagine with a site of this size, it's been a massive undertaking.

The beta version is now available to all members to try out and give feedback. See details under "announcements" in the menu up at the top of your page. Here's a link...

New WebmasterWorld Beta
Mar 15, 2015
[webmasterworld.com...]

Note that the Beta is very much a work in progress, and there are links provided in the announcement to enable you to switch back and forth between WebmasterWorld "Classic" and the mobile-friendly "Beta" version, which is getting friendlier every day. The announcement tells you where you can provide feedback, which we very much encourage.

Still lots of work would need to be done to appease Google.

I think you might consider this a step toward making our site user-friendly for a large percentage of users. For users who don't use mobile, desktop rankings, as I understand, should remain unchanged, at least for the current time.

Again, "mobile" as defined by Google is smart phone searches.

vphoner

11:19 pm on Mar 20, 2015 (gmt 0)

10+ Year Member Top Contributors Of The Month



Someone made a good point, what if you make your site mobile friendly and it makes your site less attractive, and loses something in the translation, and your bounce rate goes way up and time on site decreases. These factors might lower your ranking, even though you are mobile friendly.

Maybe a better way of ranking is to look at time on the site, pages read, and bounce rate as a true rank of how mobile users feel about your site. If they don't like your site, they leave fast. This would save people from making changes that are detrimental, where they really should leave it as is.

I think this whole thing will cause a big mess for webmasters and Google.

And the fact that bigger smartphones are now the norm, they should render full sites better than the older ones. Maybe remove big smartphones from the mobile friendly penalty. Google should take into account how the site looks in landscape and not just portrait mode. I don't hold my tablet in portrait mode, why should I hold a smartphone in portrait mode when on the web. Totally illogical.

Selen

11:37 pm on Mar 20, 2015 (gmt 0)

10+ Year Member Top Contributors Of The Month



These days I come across a lot of 'appealing' sites but - besides nice looks - they have little to offer. It seems the packaging is more important than content. But it's just a short-term value - some websites with valuable content and 'unappealing' design continue to gain active users.

fathom

11:47 pm on Mar 20, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The chance of harming yourself is next to impossible.

A mobile site is the same content without massively large images, graphics or icons. Font sizes are scaled appropriately and commonly a longer screen vice wider screen as viewports for smart phones are thin & tall.

ken_b

12:04 am on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



For what it's worth....

"Too wide for the window"

That has had me wondering a bit. A little experimenting leads me to believe it means about 420 pixels. Any wide brings the notice in the G Mobile Friendly test.

.

blend27

12:41 am on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I read the comments by @lizardx and ....why did I put @ sign before lizardx? I don't know, we get used to what seems to be normal.

What lizardx wrote makes a lot of sense to me. I am Developer & SMB and so on and so on, so I get the point.

Where is the standard? where does it say that we can not or should not use none responsive CSS for an image when we get resolution less than 361px? Guidelines, where are those.

The only thing Goog will do is end up with an algorithm in mobile that will make regular users to stop using their "search engine", as we used to call it. The only reason for that is that every-at-most "site master" - yes Dorothy You, will loose their mind when apocalypse date is here, or even before that.

Then I read @fantom's(that pesky @ is here again) post and it all makes sense, cause I am a Dev, I know where 361 breaks, I just know. I know people that know. And I know, at least that I could see that there are lot of WM(web masters or smb's) that made a choice to go with the latest prepackaged crap on their site when this fiasco was announced.

I then think of what lizardx said, and it all makes sense. My Widget H1 takes too much space on the screen on a mobile device, so does the image for it.

Planting of uncertainty in your potential customers minds is what drives Capitalism. With almost monopoly in Search in several regions of the Globe GOOG could do this. They have Android, they know what users have seen before you do. Your turn to use Adwords is almost there.

HAHA.

p.s. Oh wait, there is another update coming up at the end of October so they could suck more money out of You.

EditorialGuy

1:01 am on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The only thing Goog will do is end up with an algorithm in mobile that will make regular users to stop using their "search engine", as we used to call it.


Think of the mobile algorithm 1.0 as a typical Google public beta that will be monitored in the wild and refined over time. Google has a reputation for being a data-driven company, and if users don't behave as expected (and as they've presumably behaved during pre-launch testing), the people who run the mobile-search project will find out soon enough.

Also, Google's mobile search inevitably will evolve as mobile devices and usage evolve. Three years from now, how many Google users (or mobile users in general) will still be searching on smartphones with 320-pixel viewports?

adamxcl

1:24 am on Mar 21, 2015 (gmt 0)

10+ Year Member



My few cents. I think the benefits of responsive are mostly a positive for a site but the subject does matter. Certain topics are just not things that people will do on mobile. The experience may not be better for traditional desktop users but it is better than having multiple versions of a site. I have tried that and it's a lot of work and a big pain. As my mobile users usage went up, bounce rates went up a bit with time on site going down a bit. People spend less time on a site on their mobile device where as desktop users do more deep diving.

Apps and websites are very different things and if your site or company supports quality versions, meaning that the app is not made just to have a lousy app, you should do so.

Imagine the search results for "blue widgets" and you have a mobile friendly website, a Apple iOS app and Android app all on the first page or two. That is more real estate with your company. Same goes for company name and reputation. You have more high quality listings at the top and it looks better.

chrisv1963

7:59 am on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Maybe a better way of ranking is to look at time on the site, pages read, and bounce rate as a true rank of how mobile users feel about your site.


I agree 100%!

When I look at my stats I see the following percentages for RETURNING visitors on one of my websites that is "not mobile friendly" according to Google. (In reality the website looks good on a mobile phone)

Mobile: 21%
Tablet: 30%
Desktop: 14%

I did a few tests with a design that is "mobile friendly" according to Google. Users no longer have a good overview of the content, have to do a lot more scrolling ... it simply is less user friendly.

mcneely

2:13 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Somewhere in the back of my head, there's this nagging that says all of this will eventually affect more than just mobile ... Google can't seem to do any one targeted thing these days without mucking up everything else around it -- We've done default RWD for the past few years so I'm not seeing where there would be a problem directly, but there are those that might be conned into the gentle bliss of thinking it's mobile -- and then wake up one day to find that this isn't necessarily the case. (as is with most things Google these days)

EditorialGuy

2:30 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Somewhere in the back of my head, there's this nagging that says all of this will eventually affect more than just mobile.


Sure, why not? If mobile results are going to be optimized for the "mobile experience," why shouldn't desktop, laptop, and tablet results be optimized for the "non-mobile experience"?

For example, we often hear that mobile users have shorter attention spans, want less text, etc. than desktop users do. If that's true--and I'm not sure that it is--wouldn't it make sense for Google to serve up meatier results for desktop searchers while skewing more in the direction of Cliff's Notes results for the mobile audience?

RedBar

2:57 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Google can't seem to do any one targeted thing these days without mucking up everything else around it


Without a doubt you are correct, whether that is by by accident or design they'll never admit however they certainly do not seem to comprehend testing like I do!

mcneely

3:48 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



we often hear that mobile users have shorter attention spans, want less text, etc


Sure .. We hear that .. but that's not the problem with mobile.

There isn't anything that's wrong with the attention span that removing data caps couldn't fix.

Case in point:

A while back, Twitter decided that it would be a great deal of fun to allow rich interactive experiences -- Their traffic tanked ... the percentage of lost traffic was in the double digits -- Why? -- Well because everybody started stressing over their data plans, that's why.

People who use phones to cruise the net are just as thoughtful and precise as those who cruise the net on their P.C.'s ... It's not the people --- It's the data plans, data caps, and carriers that are the problem.

Now here we are with Google bally-hooing all about mobile -- Why? -- RWD can be and is most often times even heavier than most other standard writes. Mobile users are still going to be mindful of their data no matter which side of the burger one chooses to put his cheese on.

Bottom line here is that it's not "to mobile" or "not to mobile" -- the bottom line here is the money -- It's not the site that affects the total overall mobile experience - It's the money. Your mobile experience is going to be greatly degraded if you don't have the money to cover your data expenses.

So far, and according to what I see folks doing in order to effect change with regard to the so-called requirements of Google, guys are simply writing in viewport and other configs just to satisfy what they think Google wants .. the sites are still just as clunky and heavy as before ... in the end, nothing changes to garner a positive end user experience for mobile .. It's still going to be about the data/money, regardless of whether it's a first position ranking in mobile or not ...

[edited by: mcneely at 4:40 pm (utc) on Mar 21, 2015]

Dugger

4:29 pm on Mar 21, 2015 (gmt 0)

10+ Year Member



I believe people don't "search" on their mobile devices but instead "look stuff up". Depending on what your site is about stressing over mobile may be a complete waste of time.

It could just be because of the data caps / cost or it could also be because the small screen size is really not all that pleasing of an experience regardless of whether a site is deemed mobile friendly.

EditorialGuy

5:37 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Re data caps: According to press reports, one of the goals of Google's forthcoming wireless network is to make it easier for users to switch between cellular and Wi-Fi networks. (Supposedly it's going to be a kind of demonstration project to nudge cellular carriers in the right direction.)

If you were able to switch automatically between, say, Verizon or AT&T and the Wi-Fi networks in the places that you frequent (home, office, neighborhood coffee shop, municipality, etc.), your cellular data allowance would stretch further, and page weight wouldn't be as much of a factor in "mobile-friendliness" or user behavior as it is now.

lizardx

6:00 pm on Mar 21, 2015 (gmt 0)

10+ Year Member



mcneely, those are also good points. In the sports site - a news site, basically, where before you could scan about, oh, maybe 30 to 40 items on one desktop screen, now forces you to scroll endlessly to access only a fraction of what they showed before. How this can be considered 'friendly' to anything is beyond me frankly.

Somewhere in the back of my head, there's this nagging that says all of this will eventually affect more than just mobile ...


Somewhere in the front of my head is the nagging suspicion that last week's weird traffic drops may be related to this somehow, in ways as of yet unclear. We can at this point find no causes for it.

It's also of course worth noting that oine of the vast gaping holes in mobile 'design' is the lack of real navigation. Just as with per screen content shrinking, you likewise lose the ability to have usable menuing systems, which to my mind points towards the only way you access mobile content really on a site is either through clunky blocks that are clickable OR search, either site or google. All mobile oriented sites I've seen suffer from this, from hulu to netflix to almost anything else that removed real navigation menus. This is of course a HUGE usability fail, because it means as the end user, you have to know what you are looking for in order to find or see it. It's very unfortunate that usability has been tossed out the window in the quest to service inferior platforms in this way in my opinion, when really what is going to happen longer term is that the inferiority will get so irksome that, as you already see, the interfaces will expand in size, the tools used to browse will get more advanced than a clumsy large finger tip, and this will all look in the future exactly like what it is, a stupid short term misguided web fad, which we will then in that future hopefully put in its web fad box, unless it sticks, which means the internet stops being a powerful tool and becomes just another dumbed down access point to commercial interests. Which is possible, no doubt about that. But trends seem to be pointing away from it, keyboard addons for tablets come to mind as an admission of the inferiority of touch keyboards.


But in the meantime we are left with google promoting seriously bad technology when clean simple solutions that work well for most mobile users are the clear path forward in my opinion, but these will not make the random decisions of the google system happy. Usually there is some faint sense to google's thinking but I think we also have to admit to ourselves that every large computer corporation hits a point where something goes wrong in the internal culture and it begins to stagnate and stop evolving, there are certain signs to me that this could be such a moment in google, but it's hard to know, it could just be a mistake they are making, they've made them before, hard to know.

From what I'm seeing, while google is sort of jumping on the heavy badly coded responsive bandwagon, equally to blame are those legions of horrible wordpress cookie cutter sites loaded to the brim with drop in jquery modules, totally non upgradeable due to absurdly complex templating systems designed to try to make wordpress, a fine blogging platform, into a very bad cms. Then ontop of that mess, they drop on these pre made 'responsive' packages.

I know when I've watched companies go this route, without any intention on my part, merely because they made it hard to access data, clumsy, and clunky, my 'stickiness' plummets, and I often have stopped reading or using the sites, I know I stopped using hulu for example shortly after they switched to their terrible mobile first responsive layout.

I remember people used to be good at mobile, but it was clearly too hard for script kiddies tasked with implementing a site's 'mobile' strategy, so now we are burdened with a responsive 'technology' that actually has grown out of date before it really even became mature (because of the expansion of pixel density in mobile screens).

Dugger, you have it, that's what they do, I think a lot of 'apps' are really just a bookmark to a mobile-ized site interface, I know that's what our app, should we make one, will be. You in fact really only can 'look stuff up' because it takes too long to try to browse though a crippled navigation system, if there is even one left to look at, depends on the design. Even if a top highest level navigation fits onto the screen, that will just land you on more clunky endlessly scrolling pages, so it's pretty clear most mobile users probably do in fact just look stuff up, whether its google traffic, probably a top destination, or a quick restaurant review. So what you are in the end giving a mobile user is basically just one page, if that.

Why any site then takes that fact and reality and destroys the desktop experience is beyond me, I have to also suspect we're looking at the same fads we've always seen here on WebmasterWorld, junior web designers/devs fall into the fad (you know how it works, tables are bad, so put tabular data into a complicated ul/li set which is totally wrong technically but fits the fad). I see this stuff in my own work all the time, stupid use of code to fit a narrow grasp of what is good or right, a grasp that usually in fact is wrong and bad.

I mention tabular data being presented not in tables because it's such a typical example of young clueless web designers following fads they don't even understand, and it's something I see all the time in my own work, I have to deal with that nonsense, though of course we don't do anything that stupid ourselves, but it always makes me think, and realize just how technically bad web designers as a group are, particularly the ones who do the plug and play wordpress modular sites.

unless 'repsonsive design' gets access to actual screen display inches/cm, it's a dead end in my opinion, now if it could access the more accurate information, it could actually be very interesting.

I haven't followed WebmasterWorld css forums for ages, but I'm sure if how they used to be is how they are now, WebmasterWorld has been directly responsible for the responsive fad spreading out to clueless web designers, along with other key sites, but that's just how css goes I think, too complicated for most users but great for fads, and now it's even more complicated, but the device technology left it behind before it really even started I think, which is kind of funny if you think about it.

blend27

7:08 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I find the entire thing sort of pathetic, a terrible user experience being pushed by Google

When it is done in none-complete matter, e.g copy code snippets from Web, It is called a Feature Reach Syndrome. I observed this being mentioned by one of Senior Dev Managers in response of a large corporation hiring cheap UI/UX devs from overseas a few month ago.

The sad part is it is spreading, not good for users.

EditorialGuy

7:09 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Sure, responsive design is a kludge, but you can have a "mobile-friendly" site without using it. Separate mobile-optimized pages can work well, both for the site owner and users. The "two URLs" approach is worth considering if:

1) You don't have a massive number of pages, and...

2) You don't mind if some of your pages (such as low-traffic legacy or archived pages) rank poorly in mobile search.

chrisv1963

7:20 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



But in the meantime we are left with google promoting seriously bad technology when clean simple solutions that work well for most mobile users are the clear path forward in my opinion, but these will not make the random decisions of the google system happy.


And again this demonstrates how bad Google's monopoly is. We have to do what Google dictates (even when it makes our website visitors' user experience worse) or our website might not rank any longer and lose a lot of visitors and income.

mcneely

9:31 pm on Mar 21, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



We have to do what Google dictates


Well ... we really don't have to ..

Back in the day, I wrote the mobi separate and wrote redirects in for mobile thru .htacces and it all worked out pretty well at the time. Nothing fancy - just mostly info and readily available buttons pointing to maybe 3 different mobi pages - that's it.

My guess would be that you could go ahead and jump thru the Google hoops like some kind of circus animal, while at the same time, write your mobi separate with redirects that would exclude 8x10 and up for screen size - then supply separate content (so you don't get dinged dupe content) complete with a contact form for more info if they want it ...

You already know that the mobi user isn't going to stick around for very long due to possible data constraints, so you'll write it for ease of use and speed, all the while saving them from their precious data transfer concerns while you deliver your important message ..

Bottom line is that you can only do so much to satisfy the end user experience on mobile -

Google may or may not list you accordingly, but at least you'll have your bases covered if your niche will support those kinds of bases.

frankbomarito

2:51 am on Mar 22, 2015 (gmt 0)

10+ Year Member



Google was very specific with me. They listed the shortcomings as 'viewport not set' and 'links to close to each other'.

born2run

2:53 am on Mar 22, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



When is this update being rolled out?

EditorialGuy

4:16 am on Mar 22, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



When is this update being rolled out?

April 21.

jimh009

1:29 pm on Mar 22, 2015 (gmt 0)

10+ Year Member



lizardx...

Why any site then takes that fact and reality and destroys the desktop experience is beyond me...


You don't have to "destroy" the desktop/tablet usability of a website to also make the site "mobile friendly." Do various sites do that? Of course. But just because some sites do that doesn't mean that all responsive sites have have to destroy the user experience. Yes, you can have usability for both mobile and desktop/tablet users with planning and effort.


I find the entire thing sort of pathetic, a terrible usaer experience being pushed by google, who have the audacity to tell us via their mobile information to 'build for mobile first'...


I have to agree with you on this, at least to a degree - it depends on the sites vertical. I first attempted to design for "mobile first" for my sprawling information site, but didn't like the results at all when viewed on a desktop/tablet. So, I looked at my logs and saw that the tablet was by far the most popular device used to browse my site. Thus, I designed for "tablet" first, then desktop and then mobile. And I'm extremely happy with how all layouts have functioned.

Still, I can see where other sites might wish to design for mobile first. If the bulk of your visitors to the website are using mobile phones, it simply makes sense.

It's also of course worth noting that one of the vast gaping holes in mobile 'design' is the lack of real navigation. Just as with per screen content shrinking, you likewise lose the ability to have usable menuing systems, which to my mind points towards the only way you access mobile content really on a site is either through clunky blocks that are clickable OR search, either site or google.


It's hard to fit a desktop navigation system into a mobile device. It's just the nature of the beast. But it doesn't mean that a mobile site needs to have a "crippled" navigation system. Is it harder to browse a mobile site than a desktop site on a large site? Yes. But it doesn't need to be inordinately difficult, either. I agree that most responsive designs I've seen tend to ignore the ability of visitors to browse the website. But again, it doesn't need to be that way. Also, from what I've seen, responsive websites that fail in mobile navigation design frequently fail for desktop navigation, too.

My two cents.

RedBar

3:28 pm on Mar 22, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Well because everybody started stressing over their data plans, that's why.


Well, I for one am not stressing, none of my friends and business colleagues in several different countries are not stressing, just where are all these people who are suspposedly stressing and where are your figures to back it up?

Apart from unlimited texts and 1,000 mins of calls, I can also have 5GB of 4G for $27 a month, or 2,000 mins and unlimited 3G for $26 a month, that's hardly stressful.

lizardx

10:19 pm on Mar 22, 2015 (gmt 0)

10+ Year Member



The sad part is it is spreading, not good for users.


This is what is making me scratch my head, if you consider tablets a special class of desktops, and all 'phone' type devices as mobile devices, I see the main issue being to pretend that rules that are good for mobile display have any place on a desktop css stylesheet.

This is why I'm concluding that unfortunately, css 2 and 3 rules were devised just before mobile screen resolutions started to skyrocket, so the assumptions made about pixel densities are now completely out of date, so the most common methods in responsive design, except for super crude tests like <> 400 px, 800px for mobile only, there's almost no usable information you can gain about the actual viewport of the device from pixel resolutions.

Certain things were supposed to be obsoleted by these 'new' css rules, but the actual screen display advancements are now so far ahead of css rules that I believe only browser detection, very sad to say, it being something of a long term headache for particularly mobile, and in especial particular, tablets, and custom mobile/tablet/desktop stylesheets can really be used to create a decent experience for all your users. I know I have NEvER seen a good responsive design desktop. This doesn't mean it can't be done, I know I personally could do it, but it would be really hard. In my opinion for particularly information sites, they should do mobile last, not first. That's what makes the google 'recommendations' such bs, there are many types of sites, some work ok on mobile - think newsfeeds where the newstype is very slow, say, 5 10 max per day, something that's ok to scroll through with touch - anything more complicated however, that's a mistake. I actually do not understand what is happening with particularly very large companies who easily have the budgets, or should have, to do good quality mobile AND desktop/tablet development, it's not rocket science after all.

I totally agree that it's becoming very clear that UI development is being handed to completely incompetent junior level script kiddies, but why major sites do this I have to admit I find truly mystifyinig, it's not like you can't develop advanced html and css that work decently for both desktop and mobile, in the sports site in question, I did some tests using firefox site css style sheets and had a fairly workable desktop display running in about 2 hours, give or take, and with 8 hours, I would have had something about 5x better than what they were running live, with no changes to their html at all, so it's not like it can't be done or anything, it can.

I'm certainly going to see how we do with this challenge, but I want to repeat my personal fear, google is already using mobile to downgrade non mobile friendly sites, I can't say this is for sure, but I am beginning to suspect it, though I can't be sure.

vphoner

10:24 pm on Mar 22, 2015 (gmt 0)

10+ Year Member Top Contributors Of The Month



If you are ranked #1 on google for a keyword, and #1 on google on mobile using google currently, where will you be ranked after the algorithm change once it goes into place (assuming your site is mobile unfriendly according to google).

Mobile friendly/unfriendly will be weighted more (which means it already probably is weighted). And it is only one of several factors.

As I stated before google should use bounce rate, time on page, and pages viewed as the true vote by users as to whether they like the page, not an arbitrary mobile friendly/unfriendly classification.

Pages on the iphone 6 (both versions) and phablets, should be excluded from this mobile friendly restriction as they have nice large high resolution screens.

EditorialGuy

10:28 pm on Mar 22, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I want to repeat my personal fear, google is already using mobile to downgrade non mobile friendly sites...

Some of our mobile pages are already ranking higher in mobile search than their non-mobile versions are ranking in desktop search. That's just anecdotal evidence, though.
This 249 message thread spans 9 pages: 249