zowl

This is what google says about creating alt tag for the crawler to be able to identify what it is. The crawler cannot ID words imbeded in the pictures. If you have a heavy pictured site I think you would want it.

This is an exerpt from the Google https://bit.ly/4m8VQu

“With image search, just as with web search, Google’s goal is to provide the best and most relevant search results to our users. Following the best practices listed below (as well as our usual webmaster guidelines) will increase the likelihood that your images will be returned in those search results.
Don’t embed text inside images

Search engines can’t read text embedded in images. If you want search engines to understand your content, keep it in regular HTML.
Tell us as much as you can about the image
Give your images detailed, informative filenames

The filename can give Google clues about the subject matter of the image. Try to make your filename a good description of the subject matter of the image. For example, my-new-black-kitten.jpg is a lot more informative than IMG00023.JPG. Descriptive filenames can also be useful to users: If we’re unable to find suitable text in the page on which we found the image, we’ll use the filename as the image’s snippet in our search results.”

If you follow the link above there is a youtube video about creating great alt text.

I have a problem with ebay widgets. They don’t display the clicks impressions nothing. It is ebay’s own flash code, and when I use their tool validation it says that there is no campid in the parm or embed tag. But when I inspect it they are there? Anybody finding the same thing?

Have a woo theme at https://electricandhybridcar.com

Excuse me if I pile on here! I have a problem with ebay widget not registering with eaby when someone clicks? The tool validator says that my campid is missing in the param tag and the embed tag but if I do an inspect they are there?

Ah ite!

I also tried 1pixelout. It is only good for version 1.5 to 2.3 the beta version is good up to 2.5. I installed it and it wrote errors in my header. I had to hand delete it after that because it locked up in the plugin control panel…