stajer
msg:3066113 | 4:47 pm on Aug 30, 2006 (gmt 0) |
This type of cloaking is common and not a problem for seo purposes. What you want to avoid is showing one version of your site to search engines but another version to real visitors who use a web browser to access. For example, googlebot and an engineer at google using his desktop computer should see the same thing.
|
Brett_Tabke
msg:3066124 | 4:52 pm on Aug 30, 2006 (gmt 0) |
Agent and device cloaking is extremely common. Just robots.txt off the pda/wap stuff.
|
Fr4n
msg:3066241 | 6:11 pm on Aug 30, 2006 (gmt 0) |
Thanks!
So, would you keep the wap.domain.com access?
|
bird
msg:3066330 | 7:17 pm on Aug 30, 2006 (gmt 0) |
Why not redirect wap devices to the subdomain?
|
stajer
msg:3066342 | 7:29 pm on Aug 30, 2006 (gmt 0) |
I wouldn't keep wap.domain.com - just show different content. More user friendly - your visitors don't have to remember multiple domains for your site. Think about it this way: Your user is sitting on the toilet (where I think 90% of mobile surfing is done) and painfully types your domain into their browser with some horrible t9 interface. Make it simple for them - just let them type in your standard domain. Don't make them guess what the mobile domain might be. On a related note - is anyone coding in WAP anymore? Most phones can display html - I would think a stripped down html page is fine for most mobile users. You may even just be able to change stylesheets and have all your content mobile friendly.
|
Brett_Tabke
msg:3066398 | 8:15 pm on Aug 30, 2006 (gmt 0) |
> I wouldn't keep wap.domain.com - just show different content or prep for the absurd .mobi tld coming in...
|
|
