How to solve WAP without Cloaking?

Forum Moderators: open

Message Too Old, No Replies

How to solve WAP without Cloaking?

You can have the need to cloak if there´s wap users visiting www.domain.com

Fr4n

3:28 pm on Aug 30, 2006 (gmt 0)

I can tell my users that if they want wap content they should go to wap.domain.com but what if they don´t remember this and they access www.domain.com? The logical thing would be to try to convert those guys into sales serving them wap content through cloaking. And, of course, cloaking is something I still want to avoid.
So, could someone tell me how you solve this issue?

stajer

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

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

6:11 pm on Aug 30, 2006 (gmt 0)

Thanks!
So, would you keep the wap.domain.com access?

bird

7:17 pm on Aug 30, 2006 (gmt 0)

Why not redirect wap devices to the subdomain?

stajer

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

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...