Hi, First thanks for this great module.
For me as SEO-specialist this is the first step to friendly product urls!

I am testing your module, and it is working great for node/99?id=171 (ID's).

An enhancement could be that the node/[nid] url would be overridden immediately by this url. I use globalredirect to not have duplicate content.
I do not know a solution yet for your module related to duplicate content..
It would be great to have the url /node/[nid]?id=[PID] be changed to the alliased node /node_alias?term_reference=blabla.

This way it can work with globalredirect and have solely the url /node_alias?term_reference1=blabla?termreference2=blablo
Hopefully this is doable.

Now I have node/[nid] aliased to node_alias and node/[nid]?id=[pid] pointing to the same content..

Thanks for considering in advance.
Greetings, Martijn

Comments

Summit’s picture

Category: bug » feature

Sorry this is not a bugreport. Greetings, Martijn

maciej.zgadzaj’s picture

Well, to be honest I am not sure if there really is a problem here.

Note that for commerce products you have a canonical META tag in the page head, pointing to main product display URL, therefore, as I understand it, and as it was suggested by carl.brown in the original Implement unique URLs for particular products on product displays issue, there should be no duplicate content issue here. (See also both links in Carl's comment.)

This essentially means that:

  • all /node-alias?[param]=[value] pages (whatever the param would be, either id or sku or any other attribute field) define canonical meta tag pointing to /node-alias,
  • all /node/[nid]?[param]=[value] pages define canonical meta tag pointing to /node/[nid],
  • finally, /node/[nid] gets redirected to /node-alias by your Global Redirect module,

so at the end of it all, /node-alias is the only URL given to search engines to index.

Will keep the issue open for some time if you/anyone has a different point of view.

Summit’s picture

Title: Duplicate content? » Duplicate content and best content

Hi, Thanks for your explanation. I would very much have the url what would be indexed be the:

/node-alias?[term-alias1 for ?[param]=[value]?[term-alias2 for ?[param]=[value] etc..
and not the node-alias.

So my urls reads like:

/mp4 player deluxe/black/musicplayers
/mp4 player deluxe/blue/musicplayers
etc..

This way I can get the best url's possible indexed. And not only

/mp4 player deluxe

Thanks for considering this.
Greetings, Martijn

maciej.zgadzaj’s picture

Status: Active » Closed (won't fix)

Well, what you've described is not a request for this module - it's your pretty specific use case, which is not generic enough to consider it here I am afraid.

To have aliases like /mp4 player deluxe/black/musicplayers (with spaces?) you just need to create them somehow (manually, or write a custom function/module that is going to take care of that).

To have those aliases indexed by search engines (and assuming you have quite a big part of content different between different product variations, to avoid duplicate content penalty) you need to get rid of that meta canonical tag from the header - which also has nothing to do with this module.

Therefore, sorry, but there is nothing that could be done here.

Summit’s picture

Hi,
The node alias is already there. The term alias is already there. The only thing is I would like to be able to combine those to get to a product-page.
Is that such a specific use case?

For SEO and Shops it would be great to be able to use those already available aliases combined!
Could you please reconsider. Perhaps I didn't explain the generic part of this solution. It is absolutely not a specific on considering the thread which this functionality came from.

greetings, Martijn