Wordpress is easy when it comes to SEO because the system does a lot for you, like putting links to headlines, great overall HTML semantics and RSS, SE-ping and meta data are all done for you.

With C5 you have the same possibilities but it requires you as a developer/designer to do some of the lifting. You create the theme so therefor you have to set it up to be SEO friendly. C5 gives you the tools but you have to do it right...

There is no way of protecting images you put up on the web. You can make it a little harder by disabling right-click and putting the images in a flash-based player but if someone wants the image they can get it, no matter the system.

There are other ways though, take a look at any site providing stock photos: istockphoto.com or shutterstock.com.

yeah all our sites we build with SEO in mind so no problem there. Just wanted to be sure he will not lose his ranking in Google because we move his from Wordpress blog to C5. He is quite fussy.

As for the image protection, I just thought there might be a permission option to disable right click etc. Some users as you ay will always be able to get the image if they know what they are doing but for the users who have no clue then its better than no protection for my client.

Havn't seen any function in C5 core for disabling rightclick on images but it's a simple JavaScript no? Just add it to your theme and its all right.

Regarding a transfer to C5 from WP, just make sure you 301 all pages correctly and there should be no problems. WP does have alot of URLs that Concrete doesn't support (out of the box). Like summary-pages for tags and so on... if no equivalent page exists on the new site, thees url's will be lost from the SE index.

for protecting images, try this jquery plugin

http://davidwalsh.name/image-protector-plugin-for-jquery...

One thing you ABSOLUTELY must do is redirect his old pages to your new pages. Say in the old system his photo gallery was athttp://site.com/photo.php

but now it's athttp://site.com/index.php/page/photo...

Those are not the same thing to Google. An easy to way to do it is make a file called .htaccess and add on it's own line

redirect 301 /photo.php /index.php/page/photo

You may need to do some more research on .htaccess 301 redirects via google to get it working just right.

Thanks for the advice guys. Much appreciated. ;-D

Even with all the safeguards possible you can always take a screenshot and crop the image out of the background.

Yes, I have informed my client of this. He says he would rather have some security than none.

I've been experimenting with a few ways to make images harder to copy with some of my packages. there's a few approaches you can take, including layering an transparent image over the top of your images so you can't easily just right click and download, or adding oncontextmenu="return false" to the image tag. to get around the screenshot, you could do some kind of watermark over the image. nothing's going to be a foolproof solution though... just showing the copyright next the image is probably the best way to discourage illegal usage.

Interesting approach. My client had a problem of another photographer using his images as if they were his own so he is a little paranoid.

Thanks again guys for all the advice.

thought I update this thread to mention that I've started adding digital watermark functionality to all of my image gallery / photography add-ons. This will allow you to protect your images with either text or an image, where you can choose the position, transparency, font-size (if text), and whether you also want to watermark the thumbnails. This is currently available for the ProPhoto Image Browser:http://concrete5packages.com/toolbox/prophoto/...

...and I'll be also adding it to these image add-ons over the next couple of weeks:
http://inneroptics.net/toolbox/image-file-search/...
http://inneroptics.net/toolbox/billboards/...
http://inneroptics.net/toolbox/file-image-details/...

Nice one I have that add-on for a client. The link you your site is dead by the way. Server error.

thx for the heads-up on that. looks like mysqld crashed for some reason.

Watermarking can work well. When using a Gallery that has no inherent watermarking ability, I use TechSmith's "SnagIt" to bulk watermark all of my images, then upload them.

Of course, a real-time solution is always better.