ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

SEO: Cloaking Can Be Ethical

Updated on December 9, 2017
jondiscipulo profile image

Jon is a Technical Visionary at Rich Media Manila. He improves relentlessly considering Information Technology for more than 20 years.

Short Recap

Search Engine Optimization is a practice that exists as it maintains its evolution with the internet. "Cloaking" is one practice in SEO that has been debatable for some time until now. Perhaps there should be another term for "cloaking" as the current leaves a negative impression. Cloaking is simply displaying data with a different presentation and it should not be considered as being a bad habit. The said practice is simply to optimize your information for whatever device that reads the actual content. Examples of these devices are standard browsers, text-only browsers, WAP browsers, other deprecated browsers, hand-held devices, generic APIs, custom data-listening protocols, screen readers, scrape bots, data crawlers, and spiders from the search engine itself. Now, SEO is becoming a broader technology and topic to deal. It may combine itself or totally separate from SMO or Social Media Optimization, which emerged after some social platforms become relevant to the internet due to the large number of users.

Optimized Versus Another Content

Cloaking is mostly used in a web page that expects itself to be read by a vast number of unique devices concerning its purpose. If you optimize your web page accordingly, for example, by removing layout tags or some images to comply with a specific device user-agent but you tend to produce the same content, it should not be referred to as cloaking. Since cloaking has its negative connotation and is practically a black hat method since it is also being used to present a totally different content rather than the real content. Displaying optimized content is different from displaying another content. As of this writing, I am aware of the practice of hiding content from users but not from spiders or crawlers. As an example, a module for a popular forum software has been created to do such work where a bot, can be spider or crawler, is considered a registered member of the forums and is automatically logged in once the module detects it is reading some of its web pages. This way, the bot, even unregistered, can enter, view and scrape the forums, articles, posts, profiles and comments that a non-registered user is not capable of doing. But since the content is hidden from non-registered users, it should not be referred to as "cloaking" because of the fact that the page is just optimized and should be available for registered and logged in members. Again, to push my point, content is not hidden. You just need to register and log in so you can view the content reserved for registered users.

Conclusion

My conclusion is that you can ethically present an optimized page version to each user-agent and devices that you care about. By actually providing the same content, it should not matter. This would remain right as long as you do not present another content in another device as it may pose confusion to some readers. This is true as it might contain a different data or a totally different point of view. Optimization or cloaking, for as long as you do not confuse your readers, then you are doing a great job.

© 2017 Jonathan Discipulo

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)