2

When displaying multiple products that are basically the same, let's call them Product A with different sizes, 30, 40 and 50, I choose to create only one page per product and avoid duplicates, since the size would really be the only difference.

So in this page, I'm displaying the different product codes based on their size, ie: A30, A40 and A50.

On a different page, for example, where Product B is listed, I would like to display related products, in this case, Product A (only a list with sizes and codes, no pictures).

I can either display Product A by itself (which I don't want to, since a Product B30 would fit a product A30, for example), or display Product A30, A40 and A50.

Using schema.org, itemprop="url", I would like to link to this product's page.

The question here is, product A30, A40 and A50 are all listed in the same URL. Would linking these 3 products to the same URL pose a problem?

| improve this question | |
  • Just to clarify things: you want to list different versions of product A on product B's page, and provide itemprop="url" for each version of product A there back to the product A page? – dan♦ Feb 15 '14 at 16:01
  • Yes, using "isAccessoryOrSparePartFor" – riseagainst Feb 16 '14 at 0:52
1

If Product A is an accessory or spare part for Product B, this shouldn't be a problem since you're using the isAccessoryOrSparePartFor property, which is:

A pointer to another product (or multiple products) for which this product is an accessory or spare part.

It's natural to list accessories on the same page as the corresponding product, and provide a link to another page for more details on them. And as previously covered here, several products can be listed on a single page.

This is akin to having a page for a printer (Product B), and then listing various printer cartridges (Product A) there as accessories, which point to a cartridges page that contains content like pictures of the cartridges, compatibility, specs, etc...

It's doubtful that a search engine would view this as a form of manipulation or otherwise since you're indicating the accessory/product relationship, and this type of structuring is common.

| improve this answer | |
  • Hi Dan, and thank you for your answer. My question is solely about the links. One would think if there's the "isAccessoryOrSparePartFor" property available, listing more than one product per page wouldn't be a problem and so shouldn't linking. Problem is there's no documentation anywhere about it. I just want to make sure as you said that this is not treated as a form manipulation or something that would hurt this website in any way. Is there anything you found that would support your answer? – riseagainst Feb 17 '14 at 12:35
  • No problem. Yes, I was discussing links in regards to multiple ones pointing back to the same product page, from a page where multiple products are listed as accessories. Since you're using the right property, and schema.org was created by the major search engines, there really isn't any cause for concern since this doesn't fall under any of the black hat techniques that search engines penalize for (i.e., it's natural). – dan♦ Feb 17 '14 at 17:04
  • You're not always going to find documentation for every specific situation, unless there's cause for it :-) – dan♦ Feb 17 '14 at 17:04
  • I tend to agree with you on that one. Thank for the answer. =] – riseagainst Feb 19 '14 at 12:41
  • No problem. Good luck :-) – dan♦ Feb 19 '14 at 15:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.