Joost de Valk

Sounds smart indeed. We could add support to [Yoast WooCommerce SEO](https://yoast.com/wordpress/plugins/yoast-woocommerce-seo/) for this easily and quickly.

@danbri unfortunately, we/Yoast can't add support for ASIN until this gets merged, as the Schema validator will throw errors for it, causing a barrage of emails to our support team...

This would be a good change, for many things indeed. I’m wondering if adding a `colloquialName` property as well might help with disambiguation for consumers. Maybe… `Name` should be a...

FWIW, I fully agree with @jonoalderson that this is not a good idea. We already have standards for this... I feel we should just tell people that need this, that...

What if we created a type `alternateURL`, which in itself would have the properties `URL`, a property for MIME type and something to classify it, either `rel` or `role` or...

> However I couldn't make out if alternateURL was a type or a property here. I was thinking of a property at the time I think. Reading your doc -...

@alex-jansen I keep coming back to the fact that having a version of `mobileUrl` means we'll need a `metaverseUrl` at some point too, or another device type / context /...

One more vote here to get this in, seems there's quite a bit of consensus already...

If we could do site level data at the homepage only, that'd be simple to implement. Then you also use the method @jvandriel linked above, specifically for the homepage, to...

Note that I'm more than happy to experiment with the implementation I have on joost.blog, and if we need a bigger data set, I could easily push this feature into...