What if I told you that for only a few minutes of your time, you could gain a large volume of organic traffic from visitors eagerly looking to make a purchase? Luckily, this can very easily become a reality through the use of the often-ignored Google Images search.
This is an amazing guest post by the owner of Pages that convert. For pre-made landing pages that utilize the most useful and up-to-date methods available to affiliates, be sure to check out Pages That Convert.
Why target the image search?
Think about it. Customers looking to buy a product or service online crave a detailed look at what they are about to buy. In an increasingly visual-centered culture, the visual aspect of a product is just as important as its feature list. I discovered this yesterday when I was looking to purchase a new luxury watch—after finding a few models I was interested in, the first thing I did was type the models into Google Image search and look for real (not product images) images to give me a better sense of what I was about to buy. To jump to the point, I clicked on the most attention-grabbing picture and actually ended up purchasing my watch directly from that retailer.
The best part about the image search is that there is little to no competition. My web search for these watches returned around 300,000 – 500,000 results each, while the image search results were consistently between 200-600. It should be obvious at this point that the ability to organically rank in the top-10 for any image search is as simple as a quality image, the right formatting, and a halfway decent website.
How to use images to your advantage
In order to take advantage of a high ranking in the Google Image search, we must first understand the formatting that the Google crawler looks for when indexing images. The structure that Google looks for is as follows:
Tables Based Layout:
<td>Keyword1, Keyword2, Keyword3<br>
<p><img src=”images/keyword1-keyword2-keyword3.jpg” alt=”Keyword1, Keyword2” />
Keyword1, Keyword2, Keyword3</p>
</td>
DIV Based Layout:
<div> Keyword1, Keyword2, Keyword3<br>
<p><img src=”images/keyword1-keyword2-keyword3.jpg” alt=” Keyword1, Keyword2” />
Keyword1, Keyword2, Keyword3</p>
</div>
These are the key points ranked in order of importance to keep in mind when considering how to construct the code around your image. As for sizing, small images are 150x150 and under, medium are between 150x150 and 500x500, and large images are anything larger than 500x500. Most customers doing image research on products sort by either All, Medium, or Large so size your images accordingly. It’s best to use the highest resolution image you have available and use your code to re-size accordingly.
1) Keyword should be below or above your image in the DIV, floating DIV, or table.
2) Keyword should be in the same paragraph as your image.
3) Keyword should be in the same table cell as your image.
4) Keyword presence in the image name and image meta-file summary.
5) Keyword presence ALT tag.
Bonus Content
How to automatically remove the Google “frame” at the top
<script language=”JavaScript1.1″ type=”text/JavaScript”>
if (parent.frames.length > 0) top.location.replace(document.location);</script>
How to re-direct Image Search traffic
Sometimes you may get traffic from image search that may be valuable, but not extremely targeted to the content on your site. You can still leverage this traffic with some simple .htaccess additions that will re-direct them to wherever you choose. A good example of the usefulness of this is with someone searching for pictures of a particular cruise ship. When they realize that your site isn’t actually the place to book their vacation, they may leave quickly however using this, you can re-direct them to your affiliate link for a travel booking offer or something of the sort.
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^http:\/\/images\.google\. [NC]
RewriteRule .*\.$ redirect/redirect.php [R,NC]
No related posts.
Related Posts:
No related posts.
Rate This Post:
(4 votes, average: 5 out of 5)
Loading ...
Wesley says 30th June @ 12:26
Something seriously wrong with all your code samples.