On Sep 17, 10:17 pm, Joseph Letness <[email protected]> wrote: > I'm no SEO expert but I've always considered it Best Practice to use > semantically meaningful URLs for the both "src" and "alt" attributes > in my HTML. However, using get_serving_url() takes away any SEO > relevance in the "src" attribute. But after testing performance with > get_serving_url(), I think the improved user-experience is worth the > loss in SEO. > > Although, I think that a possible work-around for this would be to > append the URL in the markup with a GET parameter containing > meaningful data. For example: > > http://lh5.ggpht.com/V53SofI9tmIdjz28H7=s160?filename=keyword-friendl... > > I've tested this and it seems to work just fine. However, I am > **assuming** that Googles image server is just ignoring the GET > parameter. Does anybody know if this is the case or could I be > negatively affecting performance with the extra parameter? > > Also, if there are any SEO experts in this group, does this sound like > a worthwhile approach? > > Thanks! > > --Joe Also when image was created and updated is more meaningful than a hash value. Usecase I posted relies on semantic image information "How to recognize (in)appropriate images?" (http://stackoverflow.com/ questions/1257933/starting-semantic-image-recognition) Since implemented a solution combining semantic and id combined since semantic is not unique simply /<id>/<slugify(title)> Image recognition gets more advanced to create semantically meaningsful information extracted from an RGB image histogram or likewise for what information belongs to same set. An online image editor may edit the image and keeping old semantics when working towards that meaningful semantics are found from the image blob or file. Best wishes Nick Rosencrantz
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
