- Posts: 467
- Thank you received: 21
Variants URLs/@id in structured data — question triggered by Shopping/Merchant
- Reincidente
-
Topic Author
- Offline
Less
More
8 months 2 weeks ago #370602
by Reincidente
Variants URLs/@id in structured data — question triggered by Shopping/Merchant was created by Reincidente
Hi Nicolas,
I’m reaching out with an SEO-oriented question about variants and URLs, triggered by what I’m seeing in Google Shopping / Merchant listings.
I have a main product page with variants (numbers 0–9). In the structured data, each variant Offer currently points to a URL built like:
index.php?option=com_hikashop&ctrl=product&task=show&cid=...&name=...&Itemid=...
In Shopping/Merchant listings, I sometimes see Google treating variants as distinct “items”, and it made me wonder whether my current variant URLs/identifiers in the structured data are ideal, or whether I should provide more stable unique identifiers for each variant.
ChatGPT suggested generating a stable, unique identifier/URL per variant in the structured data (for example a distinct @id and/or a distinct url per variant/offer) so Google can better understand each item/variant in the ProductGroup/hasVariant context.
Before attempting anything, I want to confirm the safest approach from both a HikaShop and SEO perspective:
Is it technically possible/recommended in HikaShop to output a distinct @id and/or distinct URL per variant inside the JSON-LD, without turning variants into separate product pages?
Could outputting unique URLs/identifiers per variant create SEO risks such as:
multiple URLs being discovered/indexed for essentially the same product (cannibalization)
conflicts with canonical tags (main product canonical vs variant URLs)
the need for 301 redirects if Google starts indexing variant URLs
issues caused by Itemid/menu routing generating different URL paths for the same content
If the recommended approach is to avoid unique variant URLs, what’s the best practice in HikaShop for variant structured data (ProductGroup + hasVariant) so Google understands the variants while keeping a single canonical product URL?
If it helps, I can paste the current JSON-LD excerpt (ProductGroup + hasVariant array) and my canonical setup.
Thanks a lot,
José Ángel
I’m reaching out with an SEO-oriented question about variants and URLs, triggered by what I’m seeing in Google Shopping / Merchant listings.
I have a main product page with variants (numbers 0–9). In the structured data, each variant Offer currently points to a URL built like:
index.php?option=com_hikashop&ctrl=product&task=show&cid=...&name=...&Itemid=...
In Shopping/Merchant listings, I sometimes see Google treating variants as distinct “items”, and it made me wonder whether my current variant URLs/identifiers in the structured data are ideal, or whether I should provide more stable unique identifiers for each variant.
ChatGPT suggested generating a stable, unique identifier/URL per variant in the structured data (for example a distinct @id and/or a distinct url per variant/offer) so Google can better understand each item/variant in the ProductGroup/hasVariant context.
Before attempting anything, I want to confirm the safest approach from both a HikaShop and SEO perspective:
Is it technically possible/recommended in HikaShop to output a distinct @id and/or distinct URL per variant inside the JSON-LD, without turning variants into separate product pages?
Could outputting unique URLs/identifiers per variant create SEO risks such as:
multiple URLs being discovered/indexed for essentially the same product (cannibalization)
conflicts with canonical tags (main product canonical vs variant URLs)
the need for 301 redirects if Google starts indexing variant URLs
issues caused by Itemid/menu routing generating different URL paths for the same content
If the recommended approach is to avoid unique variant URLs, what’s the best practice in HikaShop for variant structured data (ProductGroup + hasVariant) so Google understands the variants while keeping a single canonical product URL?
If it helps, I can paste the current JSON-LD excerpt (ProductGroup + hasVariant array) and my canonical setup.
Thanks a lot,
José Ángel
Please Log in or Create an account to join the conversation.
8 months 2 weeks ago #370607
by nicolas
Replied by nicolas on topic Variants URLs/@id in structured data — question triggered by Shopping/Merchant
Hi,
Also, if you turned on the "Remove categories and products id from URLs" setting, then it's possible that the URL for each variant will be the same as the main product since the distinction between the URLs of a product page and its variants comes from the id.
HikaShop will already output distinct URLs per variant inside the JSON-LD, provided you didn't configure a canonical URL in the main product.Is it technically possible/recommended in HikaShop to output a distinct @id and/or distinct URL per variant inside the JSON-LD, without turning variants into separate product pages?
Also, if you turned on the "Remove categories and products id from URLs" setting, then it's possible that the URL for each variant will be the same as the main product since the distinction between the URLs of a product page and its variants comes from the id.
It's indeed a risk. It depends how Google handle that situation. I'm not privy to Google's SEO issue detection so I can't say. This might require some testing or looking around for information because I don't have it.Could outputting unique URLs/identifiers per variant create SEO risks such as:
multiple URLs being discovered/indexed for essentially the same product (cannibalization)
conflicts with canonical tags (main product canonical vs variant URLs)
Please Log in or Create an account to join the conversation.
Time to create page: 0.046 seconds