You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 13, 2020. It is now read-only.
AFAIK both URLs are not the best considering a SEO perspective, where the image name has a quite strong weight in SERP.
Both are not the best indeed - though that's not what the statement says.
Why not something like $imagename_$width_$height_$otherparameters.... ?
The image path already has the image name in it, so all your are adding is params of width & height, given the mount of variables (width/height/cropping/cropping options/watermarking options/any 3rd party addons) the filename would be come too long. The URLs that WP Thumb outputs is just as good as the standard WordPress file uploads, the phpthumb.php? example is not about seo, it's about exposing more information that necessarily and getts very messy image paths when it comes to query params.
I understand your point, but most of the literature about image SEO declares keywords in the image name as one important positioning factor, so what about swapping the image name with encoded parameters?
‘uploads/cache/h456d6/foo-bar.jpg’
instead of
‘uploads/cache/foo-bar-jpg/h456d6.jpg’
AFAIK both URLs are not the best considering a SEO perspective, where the image name has a quite strong weight in SERP.
Why not something like $imagename_$width_$height_$otherparameters.... ?
The text was updated successfully, but these errors were encountered: