The big names in search are coming together around a common agreement on sitemap handling, including a method of autodiscovery linking to the sitemap from within the robots.txt file. Nice! I see nothing about a common understanding of how to deal with mobile content however. Not nearly as nice! Poor poor mobile web, never getting invited to the party. This must be some kind of mobile web psychological torture. Diabolical! The whole being tortured bit just drives me nuts.
Mike Rowehl
I've been working in mobile for a long time, and on internet service scalability even longer. I'm currently working on Churn Labs with some friends, hacking on a bunch of interesting mobile projects. Drop me a line if you're interested.
Miker on Twitter- miker: Chrome for Android beta (ICS only it seems): http://t.co/LJkTq9Jn Looking pretty good so far!
- miker: RT @bryanrieger: Strategies for choosing test devices - http://t.co/YRHkEr7M by @stephanierieger
- miker: RT @kwestin: Asking me to sign an NDA before having coffee to discuss your startup idea is like me asking you to buy condoms before I me ...
- miker: @erickoester There's normally a video of the events. I'll send it along once its posted.
- miker: Mobile Monday tonight in Palo Alto: http://t.co/Ypi3YDZC The business of mobile dating
- del.icio.us feed
- Announcing the FLORA, Adafruit’s wearable electronics platform and accessories « adafruit industries blog
- Enyo JavaScript Application Framework
- A Quick Guide To Investing Like Warren Buffett
- Go Green Saint Patricks Day Run
- Avenue of the Giants Marathon May 1, 2011 - Home
- Server-side device detection used by 82% of Alexa top 100 sites | mobiForge
- ..::[[~ceinig]]::..
- http://www.halfmarathonclub.com/California_Half_Marathon_Races.html
- Fabrice Grinda’s Nine Criteria For Investing In Startups | Young Upstarts
- AhNg519CEAEP5O4.jpg (589×440)
For what it’s worth, Google’s approach to mobile content is to have you submit additional sitemaps for your mobile content (http://www.google.com/support/webmasters/bin/answer.py?answer=34648). In practice, this works reasonably well. In theory, this kind of promotes the view that mobile content is something separate from other content, which may be controversial.
I am not sure whether we’re going to evolve that approach, or suggest an extension for mobile-specific info or what. The extension approach is more like what we have adopted for integrations with carrier partners, when handling their on-net content.