Hey Dan,

Glad I read to the end as I was about to suggest looking at this. A client of mine was also hit very recently with something similar and it was rogue code that was carried over from one version to another.

Glad all is sorted

-Andy

Sorry Becky, I forgot to say that without some level of testing, it is almost impossible to say with any degree of certainty just what you would get from this as a site-wide task. Depending on the products, searches conducted and how Google ranks the images, you may find a good deal of additional traffic or you may find very little.

Perhaps take a control group to test and monitor the products over the course of a month to see if sales / traffic has increased.

-Andy

Hi Becky,

You aren't likely to be penalised for this, but the benefit you can derive from ALT text will be lessened. If the picture is of a floor fan, and the ALT tag says this, there is no problem.

However, I would be saying something like "Metal Blizzard Floor Fan 12" 55W with tilt". It will help because you have more of a chance of it turning up in image searches = more traffic.

-Andy

Definitely a great idea is there is a dev on hand to do this

-Andy

Hi Becky,

What you need to be careful of, is over optimising with ALT tags. This can lead to issues, but what you suggest is correct. John Mueller from Google had this to say about ALT tags...

"alt attribute should be used to describe the image. So if you have an image of a big blue pineapple chair you should use the alt tag that best describes it, which is alt=”big blue pineapple chair.”** title attribute** should be used when the image is a hyperlink to a specific page. The title attribute should contain information about what will happen when you click on the image. For example, if the image will get larger, it should read something like, title=”View a larger version of the big blue pineapple chair image.”

If the image someone can click on is the rear view of a cupboard, then say this in the ALT tag. However, it is worthwhile remembering that you need to be descriptive with these.

Here is a great article on the subject.

-Andy

I  put an end to that, mostly because it was absolutely pointless and not user friendly.

This..

Hi,

I have never heard of any issues with this in either case. Google can see past a right click block with ease, but why do you think this might be hurting his traffic? Because of scraping tools and copying content? It isn't something I would really suggest doing unless there is an exceptionally good reason.

In fact, here is John Mueller endorsing an answer over on Google's forums.

-Andy

Hi Bejan,

Your chosen language should be sat at the primary domain.

For example, if your are a Saudi based site that wants Arabic as the primary language, this shouldn't be sat in an identifier. Ideally, you want to have a primary site language as this is how most will do it.

www.example.com (Arabic Language)
www.example.com/en/ (English Version)

Or...

www.example.com (English Language)
www.example.com/ae/ (Arabic Version)

You need to also remember to set these correctly by using HREFLANG. This is what will tell Google which languages should be associated to which pages. Moz have a couple of very useful pages on this here and here.

I hope this helps a little.

-Andy

Hi Yiannis,

I tend to add these in as an advisory to my clients because for the most part, and unless I see something specific, the results have absolutely no effect on SEO. If they wish to act on them, it is for their developers to handle.

I don't argue my corner really - never had to. I just tell them like it is - the site is rendering fine in everything and with no issues, so fix errors if you have the time and resources.

As I said, unless I spot something that is an actual problem, then it tends to just get bypassed.

-Andy