Skip to main content

Disable Right-Click

I periodically get requests from Y! Store merchants to disable right-clicking on their Yahoo! Store. They typipically want this so that their competitors cannot steal their photos. While disabling right-clicking is easy to do, it's not a very hot idea. Here are a few reasons why:

  1. It's does not give you 100% protection. Disabling right-clicking is a JavaScript solution, so the easiest way to circumvent it is to disable JavaScript while viewing the page. Disabling JavaScript is very easy to do. In Internet Explorer, you can go to Tools > Internet Options > Advanced, and disable "Active Scripting". In Firefox, you can download the Developer Tools extension, and you can disable JavaScript right off the toolbar (there may be other ways, I'm just used to using the Developer Tools extension for this.)
    Another way is to view source on the page, find the image location, then bring it up in your browser and save the image.
    Or, look inside your web browser cache. By the very nature of Internet browsing, every page you visit with all of its images and other pieces is downloaded into your computer, and you can find these pieces in your browser cache.

  2. It's limiting. You are disabling a function your visitors may be used to. Many users are used to right-clicking on images and web pages to do certain tasks, such as printing a page or image, navigating back or forward, or in Firefox, for example, to use "Gestures".

  3. It's annoying. You won't realize how much you use right-clicking on a web page until you cannot do it. The right-click context menu's options are typically available through some other means (menus), but often it's quicker to just right-click and shoot.

  4. It's insulting. The vast majority of your visitors won't come to your store or site to steal your images. By reminding them that your images are copyrighted, you assume they are there to copy your images.
There are other ways to protect your copyrighted material. To start with, put up a copyright message at the bottom of your pages (you can add this in the "final-text" variable, for example.) The best way to protect your images is to watermark them. This involves a bit of work on your part, but if your images are important to you, this may be worth it. To watermark an image, simply use your favorite image editing sofware and superimpose a light text with your company name on your images. Some image editing programs such as Adobe Photoshop can also embed digital watermarks in images. These are not visible, but can be detected electronically in case you need to take legal action. By the way, Yahoo! takes copyright infringement very seriously. If you have a strong case that someone is infringing on your copyrights, you can report it to Yahoo. If the site stealing your images or contents is a Yahoo! store, Yahoo! in most cases will first notify the other party, then suspend their store until you sort this out with them.

If you still want to disable right-clicking on your web site, get a "disable right-click" javascript (here is one), and put that javascript code inside the "head-tags" variable of your store.

Comments

Popular posts from this blog

CPR for a Yahoo Store on Google's Supplemental Index

Recently a client of mine came to me and said that most of his store pages disappeared from Google, and he did not do anything to make this happen. I was a bit skeptical, so I went to Google, did a search on his store, and sure enough, there were only two pages indexed, his home page and his site map (ind.html) page. The rest were in the supplemental results, which means that Google thought the rest of the pages were not much different than these two pages. When I looked at the supplemental results, the little excerpts under each link were exactly the same, and I also noticed that what Google showed under each result was actually text from the ALT tags of the header image. I looked at some of these pages in my client's store, and they were actually different. This was a bit puzzling, but then I thought perhaps Google saw that the header and left navigation was the same throughout the site (which is pretty normal), but that the text that made each page different was too far down ins

What to expect when your redesign goes live

At Y-Times we roll out new designs, redesigns and other major upgrades to Yahoo stores on a fairly regular basis. Some of the main questions our clients ask are how to prepare for a roll-out and what to expect in terms of SEO and conversions when the changes go live? For any functional Yahoo store how well the site ranks and how well it converts are probably the two most important metrics. Since pretty much ANY change you make to any page can potentially alter either or both of these metrics, merchants may understandably feel nervous about far reaching alterations to their sites. However, when those functionality and design changes and additions are done right, there is really very little to fear. First off, what does it mean for a design or redesign to be "done right?" From the technical stand point, search engines look at the underlying structure of your site (the HTML, and increasingly also the CSS and JavaScript code) to try to extract information and meaning from i

Smaller is Better

You often hear the phrase "bigger is better". Sometimes it's true but not when it comes to JavaScript or CSS code in your Yahoo! Store pages. If you include JavaScript code or CSS either as linked files (the preferred method) or embedded inside your pages (obviously not preferred), making these files as small as possible should be your goal. Why? This is no rocket science: smaller files mean faster page loads = happy customers. Ok, so what bloats JavaScript code? In general, white space (tabs, carriage returns, non-used spaces), comments, and the actual code, such as variable and function names. You have control over all of these, however, if you don't use white spaces, carriage returns or comments, it will be immensely difficult to understand and modify your code. And not just for others, you too. There are many commercial JavaScript compression tools around, but I've been using this handy and free utility: http://www.andrewkesper.com/jscrush/ This little utilit