Welcome to WebmasterWorld Guest from 220.127.116.11
Smartphone users are a significant and fast growing segment of Internet users, and at Google we want them to experience the full richness of the web. As part of our efforts to improve the mobile web, we published our recommendations and the most common configuration mistakes.
Avoiding these mistakes helps your smartphone users engage with your site fully and helps searchers find what they're looking for faster. To improve the search experience for smartphone users and address their pain points, we plan to roll out several ranking changes in the near future that address sites that are misconfigured for smartphone users.
Let's now look at two of the most common mistakes and how to fix them.
From SMX in last 12 hours :
Next topic: Google’s smartphone news from today with Danny Sullivan and Matt Cutts.
MC: You really need to be thinking about mobile. We’re starting to think a lot about mobile. We’ve noticed a couple common problems:
* when every URL on your site redirects to a single mobile URL
* infinite loops when Googlebot gets sent back and forth from feature phone version of a site to desktop version and back again.
* at Google I/O, there was a session on instant mobile websites – there were page speed recommendations. We’ve said that before about desktop sites, we might start doing the same thing about mobile websites.
DS: When is the smartphone thing happening?
MC: It’s been approved. I don’t know when it’ll rollout.
Some sites I watch have over 50% of traffic coming from smart phones. What are SEO's advising their clients and what are business' doing/not doing about it.
Many sites don't give smartphone users the same great experience as desktop users. That's not good for anyone involved in the mobile web: the users, the webmasters, and Google searchers on smartphones.
Let's fix that.
We've published a list of common mistakes here: [plus.google.com...]
joined:Nov 2, 2012
I hope having responsive design is enough. If not, then I am clueless.
•Server must render the response (< 200 ms)
•Number of redirects should be minimized
•Number of roundtrips to first render should be minimized
•Reserve time for browser layout and rendering (200 ms)
there will be little need to shrink down past 1000 pixels
Not much point to having a site whose content fits into 1000 pixels if half your users are reading it on a five-inch-wide screen. Seven-point type, anyone? Last time I looked, my iPad's browser still didn't have a set of preferences settings for default text size.