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 founder and CTO at Metaresolver, Inc, a tech platform for performance media buying in mobile. I have a personal blog at rowehl.com.
Miker on Twitter- del.icio.us feed
- Leveling Up on Chef Best Practices
- How to pass system properties to "maven test" task?
- OneTab extension for Google Chrome - save 95% memory and reduce tab clutter
- Solve for X
- Orwell: Politics and the English Language
- Form Factor
- opencog/opencog
- http://www.mattsilverman.com/2013/02/tools-to-generate-beautiful-api-documentation.html
- plenty-web
- Filipe Kiss : A better git log
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.