https://netsuiteprofessionals.com logo
Join Slack
Powered by
We just went live with SC on 8/12, and I'm getting...
# suitecommerce
w
We just went live with SC on 8/12, and I'm getting constant emails from Google about microdata errors, with this one being the most prevalent: Invalid enum value in field "availability". Our PDP microdata looks like this: 
<link itemprop="availability" href="<http://schema.org/InStock>" content="in stock">
Looking at Googles documentation, the 
href
shouldn't be there and the 
content
should be the schema.org URL, but looking at schema.org's docs, what we have should be correct. Is anyone else getting these errors on their Google search console?
m
Hi @wes_w we run in some similar issues with SCA and schemas, the fastest solution is to modify the templates to correct the issues.
This is the correct markup for the item availability
<link property=“availability” href=“http://schema.org/InStock” />
no need of content attribute
there you have schema example made by google
w
What's weird is that the templates show what you have, but Google shows the content tag on the page
@Martin This is the code in my template: 
<link itemprop="availability" href="{{#if isInStock}}<https://schema.org/InStock{{else}}https://schema.org/OutOfStock{{/if}}%22/>|https://schema.org/InStock{{else}}https://schema.org/OutOfStock{{/if}}"/>>
No mention of content...
Just got an email from the SuiteCommerce Success Team member at NetSuite who worked with us on implementation, and NetSuite's DX team found an SEO engine error coming from the Item Badges extension we installed. Not sure if this is part of our issue.
2 Views
Open in Slack
PreviousNext
Powered by