Welcome to the Q&A Forum

Hi all

A query has recently been raised internally with regard to the use of canonical links. Due to CMS limitations with a client who's CMS is managed by a third party agency, canonical links are currently output with the port number attributed, e.g.

example.com/page:80

...as opposed to the correct absolute URL:

example.com/page

Note port number are not attributed to the actual page URLs. We have been advised that this canonical link functionality cannot be amended at present. My personal interpretation of canonical link requirements is that such a link should exactly match the absolute URL of the intended destination page, my query is does this extend to the attribution of port number to URLs. Is the likely impact of the inclusion of such potentially incorrect URLs likely to be the same as purely incorrect canonical links.

Thanks

Hi all, I'm in discussion with a client who wishes to introduce a 'refurbished' products section to their website. This section will effectively replicate the structure of the 'brand new' products section. Unusually the key difference will be the fact that the 'refurbished' products section will feature significantly more products than the 'brand new' section, in the region of four times as many. As a guide the website currently stocks approximately 200 products across 8 core product areas. We have recommended that the two sections should be combined in order to prevent the creation of two separate product hierarchies. With 'brand new' / 'refurbished' products segmented via filter functionality. However the client is set on having two separate product hierarchies, i.e. a 'refurbished' section within a completely separate directory.

Just wanted to crowd source opinion, in additionally to gaining insight if anyone has experience of a similar request. What solution did you implement? My feeling is that there is a high likelihood over time of the 'refurbished' section growing in authority and starting to outrank the 'brand new' products section. Not to mention a key missed opportunity to group and build authority / content within one product hierarchy.

All thoughts and opinions much appreciated!