How to handle .mobi and normal website for mobile search and regular search
-
Hi,
we have our regular website at jameda.de and a mobile only page at jameda.mobi
Users on mobile devices will be automatically redirected to .mobi if they click on a link to jameda.de in the SERPs.
What is the best practice to ensure, that Googlebot is indexing jameda.de and Googlebot Mobile is indexing jameda.mobi without duplicate content issues and having Link-Juice benefits on mobile search at the same time?
Thanks a lot
-
If you are using PHP, then you can include as is explained in the URL below:
http://detectmobilebrowsers.mobi/
Yu can use a javascript based useragent redirection as well:here is the URL:
http://www.quirksmode.org/js/detect.html
You can also use the Yahoo Library API to detect browsers (mobiles have different browsers as compared to desktop computers and laptops.
http://developer.yahoo.com/yui/examples/yahoo/yahoo_ua_detection.html
For apache level redirection:
http://stackoverflow.com/questions/1005153/auto-detect-mobile-browser-via-user-agent
Hope these resources help you.
-
This post is deleted! -
Thanks, but you missed the point.
We ARE already redirecting users according to their user agents, but what's about Google-Bot?
How to ensure, that both pages are indexed and ranking, one (.de) in Google regular search and the other (.mobi) ranking in Google mobile search?
-
add a mobile sitemap to your GWT.
Here is a link that will help you.
http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=34648
-
Create a regular and mobile site map, then remove the redirect for the googlebot (authentication google bot that is not just the googlebot useragent as that is easily spoofed).
As a side note, anyone looking for mobile device redirection, detectmobilebrowsers.mobi should only be used if you are a small business within the US or Europe only. If you are a medium to large business and/or care about global visitors and covering all mobile device not just top of the range "smartphones" its simply not good enough and you should look into using WURFL or "DeviceAtlas".