... use SEO-optimised URLs
Using the traffic servers, URLs can be transformed so that an SEO-friendly article name can be specified instead of the file name.
Here are some examples of what these URLs might look like.
Width & height defined
SSI-URL:
https://myserver.com/fsi/server?type=image&source=products/123/12345.jpg&width=1000&height=1000
SEO-optimised URL:
https://myserver.com/v2/1000x1000/products/123/12345/jpg/red-dress.jpg
v2
is the template used. If https://myserver.com/v2/1000x1000/ is specified, both width and height are given.
The normal image path is then: products/123/12345/jpg
The specification jpg
in the path does not define how the image is output, but refers to the file type in which the image is saved.
If it was saved as a png on the server, the path here would be products/123/12345/png
.
Defining width only
SSI-URL:
https://myserver.com/fsi/server?type=image&source=products/123/12345.jpg&width=720
SEO-optimised URL:
https://myserver.com/v2/720/products/123/12345/jpg/red-dress.jpg
In the example https://myserver.com/v2/720/
only the value 720
is given, in this case the image will be retrieved with a width of 720 pixels.
If you change the dimensions in the SEO URL, the image is adjusted accordingly.
Defining height only
SSI-URL:
https://myserver.com/fsi/server?type=image&source=products/123/12345.jpg&height=800
SEO-optimised URL:
https://myserver.com/v2/x800/products/123/12345/jpg/checkered-dress.jpg
If https://myserver.com/v2/x800/
is specified with x800
, only the height will be defined.
If the dimensions entered do not match the aspect ratio of the image (e.g. if a square image is retrieved with the request https://myserver.com/v2/350x500/
), the request is based on the specified width, i.e. the image would be output in 350x350.
When the image is saved, the filename is chosen as desired, analogous to the SEO-optimised image name (e.g. red-dress.jpg
).