Announcement

**brucet** · 30-Nov-2017, 05:28 PM

Sellerdeck 2018 will support schema tags out of the box, using the same method and similar code.

**Buzby** · 01-Dec-2017, 09:30 AM

Any idea when this will be available to play with in Beta?

**brucet** · 01-Dec-2017, 09:46 AM

We hope to have a Beta in January

**Mantra** · 10-Jan-2018, 01:29 PM

This is my current schema/rich snippets code I use in Sellerdeck sites. To use it in Design Library find the group Meta Tags,

Your schema/rich snippets code looks useful and I should like to try this out with microdata code addition only.
The first 83 lines of code I think are the same as that which already exists in the Standard Meta Tags layout, so would you be able to list the code lines needed just for the microdata bit (no Feefo etc.)?
I already have the microdata code lines within the product layout and this is working fine at the moment although the Standard Meta Tags layout would seem to be the right place for this code to be.
I tried adding just the microdata code to the Standard Meta Tag layout but this resulted in errors concerning incorrrect placement of variables so I guess some more code lines (<script>) are needed in addition that you have incorporated within your code.
Martin
Mantra Audio

**graphicz** · 10-Jan-2018, 03:16 PM

Copy your meta tags into Notepad++ and then mine into another document and compare. It will be easy then to remove from mine what you don't want.
(https://notepad-plus-plus.org/
https://sourceforge.net/projects/npp-compare/)

If errors are generated it would be handy to post them here. I don't have errors here so I may have variables you don't. Any you don't have can be created in Design Library or you can hard code values.

The ones I posted are in use on live sites and the site owners and their SEOs seem reasonably happy with them.

You may need to flesh them out a bit for Pinterest rich pins,

Code:

<meta property="og:site_name" content="The Name of the Company" />
<meta property="product:price:amount" content="<actinic:block php="true">echo preg_replace('/[^\d\.]/', '', '<actinic:block type="pricelist"><actinic:block if="%3cactinic%3avariable%20name%3d%22ListIndex%22%20%2f%3e%20%3d%3d%201"><actinic:variable name="TaxInclusivePrice" selectable="false" /></actinic:block></actinic:block>');</actinic:block>"  />
<meta property="product:price:currency" content="GBP" />
<meta property="og:availability" content="instock" />

whilst Facebook Pixels go elsewhere, below the <body> tag..

**Mantra** · 11-Jan-2018, 03:16 PM

Thank you for your response on this.

Copy your meta tags into Notepad++ and then mine into another document and compare.

I have pasted the Microdata code that presently works fo me below:

Code:

 <!-- microdata BEGIN -->
<div class="product-text notabber" itemscope itemtype="http://schema.org/Product">
<meta itemprop="sku" content="<actinic:variable name="ProductID" />" />
<meta itemprop="name" content="<actinic:variable encoding="actinic" name="ProductName" />" />
<meta itemprop="description" content="<actinic:variable name="ProductPageMetaDescription" />" />
<meta itemprop="image" content="<actinic:variable name="CatalogURL" /><actinic:variable name="ProductImageFileName" />" />
<meta itemprop="brand" content="<actinic:variable name="brand" />" />
<meta itemprop="mpn" content="<actinic:variable name="mpn" />" />
<meta itemprop="gtin13" content="<actinic:variable name="ean" />" />
<meta itemprop="gtin12" content="<actinic:variable name="upc" />" />
<meta itemprop="category" content="<actinic:variable name="google_product_category" />" />
<div class="purchase_data" itemprop="offerDetails" itemscope itemtype="http://schema.org/Offer">
<meta itemprop="priceCurrency" content="GBP" />
<meta itemprop="price" content="<actinic:block php="true">echo preg_replace('/[^\d\.]/', '', '<actinic:block type="pricelist"><actinic:block if="%3cactinic%3avariable%20name%3d%22ListIndex%22%20%2f%3e%20%3d%3d%201"><actinic:variable name="TaxInclusivePrice" selectable="false" /></actinic:block></actinic:block>');</actinic:block>" />
<meta itemprop="availability" content="<actinic:variable name="availability" />" />
<meta itemprop="itemCondition" itemtype="http://schema.org/OfferItemCondition" content="http://schema.org/NewCondition" />
<meta itemprop="seller" content="<actinic:variable name="CompanyName" />"/>
</div>
</div>
<!-- microdata END -->

If errors are generated it would be handy to post them here

When I add the above microdata code at the end of the Standard Meta Tags layout code and upload I get the error codes displayed attached.
Some of the micro data code lines are different to yours, however some of my variables pass through whist the others shown in the listed errors do not.
I use ProductPageMetaDescription instead of ProductDescription variable because some products have tabs and table coding embedded in descriptions that do not display well in Google Data Feed.
Any advice on solution to remove these errors when microdata is added to Standard Meta Tags layout code would be appreciated.
The final error on the list concerning the ProductEmbedVideo layout is a latent error I have after upgrading to SellerDeck 2016 and does not concern the microdata code. Not sure why this should be but it clears when I restore the layout back to default but keeps re-appearing. It is not a big problem though - just a niggle.

Martin
Mantra Audio

Attached Files

MetaTagsLayoutCodingErrors.jpg (217.7 KB, 276 views)

**graphicz** · 11-Jan-2018, 03:43 PM

You can use encoding = strip html to remove html (right click on the variable and 'appearance')

I am not getting those errors, all product related stuff should be in a blockif <actinic:variable name="PageType" /> == 'Product Page'

SD does like to throw up errors.

Closing and openoing sometimes does the trick.

Sometimes they are just spurious. If you do Design Check Coding Errors that will show any 'real' errors. Also if the error message is there but grey and you cannot click on it I would not worry too much.

If your variables are within a block of php the will need to be encoding perl selectable false.

**Mantra** · 15-Jan-2018, 02:44 PM

Originally posted by graphicz View Post

You can use encoding = strip html to remove html (right click on the variable and 'appearance')

Thank you for the tip - very helpful.

I am not getting those errors, all product related stuff should be in a blockif <actinic:variable name="PageType" /> == 'Product Page'

If your variables are within a block of php the will need to be encoding perl selectable false.

I superimposed my code over your code including the the product related stuff within blockif's and this cleared the errors that through up within SD.

However, after uploading I started to get the "missing microdata for condition" notifications again in Google Merchant Centre. Checking some sample products using Google Structure Data Testing Tool flagged up 2 errors - 'itemCondition' and 'mpn' not recognised by Google for an object of type offer.

I remembered this one cropped up before because the Offer group is not separate to the Product group and needs to be a sub-part (child) of the Product group within the Procuct <div> </div>.

After correcting the above another error was presented using the Google Structured Data Test tool - offerDetails - the property offerDetails is not recognised by Google for an object of type Product.
I got this one resolved by removing part code "class="purchase_data"" and renaming "itemprop="offerDetails"" to "itemprop="offers"" on the same code line.

I have included below the microdata code using schema vocabularly that works for me at the end of your suggested update of the Standard Meta Tag Layout.

Code:

<!-- microdata BEGIN -->
<div class="product-text notabber" itemscope itemtype="http://schema.org/Product">
<actinic:block if="true">
<meta itemprop="sku" content="<actinic:variable name="ProductID" />" />
</actinic:block>
<meta itemprop="name" content="<actinic:variable encoding="actinic" name="ProductName" />" />
<meta itemprop="description" content="<actinic:variable name="ProductPageMetaDescription" />" />
<meta itemprop="image" content="<actinic:variable name="CatalogURL" /><actinic:variable name="ProductImageFileName" />" />
<actinic:block if="true">
<meta itemprop="brand" content="<actinic:variable name="brand" />" />
</actinic:block>
<actinic:block if="true">
<meta itemprop="mpn" content="<actinic:variable name="mpn" />" />	
</actinic:block>
<actinic:block if="true">
<meta itemprop="gtin13" content="<actinic:variable name="ean" />" />	
</actinic:block>
<actinic:block if="true">
<meta itemprop="gtin12" content="<actinic:variable name="upc" />" />	
</actinic:block>
<actinic:block if="true">
<meta itemprop="category" content="<actinic:variable name="google_product_category" />" />	
</actinic:block>
<div itemprop="offers" itemscope itemtype="http://schema.org/Offer">
<meta itemprop="priceCurrency" content="GBP" />
<meta itemprop="price" content="<actinic:block php="true">echo preg_replace('/[^\d\.]/', '', '<actinic:block type="pricelist"><actinic:block if="%3cactinic%3avariable%20name%3d%22ListIndex%22%20%2f%3e%20%3d%3d%201"><actinic:variable name="TaxInclusivePrice" selectable="false" /></actinic:block></actinic:block>');</actinic:block>" />
<meta itemprop="availability" content="<actinic:variable name="availability" />" />
<meta itemprop="itemCondition" itemtype="http://schema.org/OfferItemCondition" content="http://schema.org/NewCondition" />
<meta itemprop="seller" content="<actinic:variable name="CompanyName" />"/>
</div>
</div>
<!-- microdata END -->

I have substituted the variable "availability" in place of hard code "In stock" for consistency with my Google Product Feed layout "availability" variable for "in stock" (default), out of stock" and "preorder" options.

Finally I note that although my products now pass through the Google Structured Data Test with no errors there are 2 entries for each product - see screenshot sample attached.

The items covered in the second listing correspond to those incorporated within the microdata code entries and I think possibly some of those included in the first entry may come from code entries before the microdata code so there appears that there could be some unnecessary duplication within the code that needs to be removed.

Hope this helps.

Martin
Mantra Audio

Attached Files

GoogleStructuredDataTestProduct(2).jpg (714.9 KB, 173 views)

**brucet** · 24-Feb-2018, 09:10 PM

The v18 Beta version is now available, incorporating rich snippets and other useful new features. See https://community.sellerdeck.com/showthread.php?t=57501

**orcahouse** · 05-Mar-2018, 02:56 PM

Hi Mantra,
Sorry to bother you but I'm trying to get microdata working on my site. I've got the code passing the checker but Google seems to have trouble finding it!! Where exactly have you placed it? Many thanks, Tom

**graphicz** · 06-Mar-2018, 01:29 PM

Mine goes in the Standard Meta Tags but anywhere in the <head></head> area should be fine.

**Mantra** · 06-Mar-2018, 05:20 PM

Originally posted by orcahouse View Post

Sorry to bother you but I'm trying to get microdata working on my site. I've got the code passing the checker but Google seems to have trouble finding it!! Where exactly have you placed it? Many thanks, Tom

I placed my code at the end of the Standard Meta Tags Layout after considering Jonathan's original post and it is working fine.

Martin Nichols
Mantra Audio

**Mantra** · 19-Jul-2019, 11:01 AM

Originally posted by brucet View Post

Sellerdeck 2018 will support schema tags out of the box, using the same method and similar code.

Google Search Console URL crawl has been identifying coverage issues randomly on some of selected products on our site variously for a few months so I decided to try a few sample product URL tests using Google Structured Data Test tool:
https://search.google.com/structured-data/testing-tool
This now flags up
1 Error - Availability
"availability"
It appears that the markup for "availability" Valid Values has been changed from "in stock", "out of stock" and "preorder" that I intially set up as a product property variable to a revised set of values comprising "Discontinued", "InStock", "InStore", "OnlineOnly", "OutOfStock", "PreSale" and "SoldOut".
I can expand the variable:availabilty that is incorporated in the Standard Meta Tag Layout to cover the additional values but the question is how could I change the existing variable values from "in stock" to "InStock" and "out of stock" to "OutOfStock" without compromising the existing data values?
Is there a way to display product "availabilty" value text with spaces that is different to the variable value i.e "InStock" as "In Stock", "OutOfStock" as "Out Of Stock"

The test tool also flags up 4 Warnings - field values recommended (optional) for:
"priceValidUntil"
"url"
"aggregateRating"
"review"
Although these are optional any guidance or suggestions on code lines that could be incorporated into the Standard V16 Meta Tag layout to cover would be appreciated.
Does Sellerdeck V18 address these availabilty values and optional field value recommentations?

**graphicz** · 19-Jul-2019, 12:47 PM

This is my valid until:

Code:

"priceValidUntil": "<actinic:block php="true">
            $date = new DateTime();
            $date->add(new DateInterval('P6M'));
            echo $date->format('d M Y');
        </actinic:block>"

Aggregate offer is where there is a high and a low price:

Code:

"offers": {
    <actinic:block php="true" selectable="false" >
    if ($ProductPrice > 0)
    {
        if ($MaxPrice == $MinPrice)
        {
            echo "\"@type\": \"Offer\",", chr(13) , chr(10), "\t\t", "\"price\": ", number_format($ProductPrice,2, '.', ''), ",";
        }
    }
    if ($MaxPrice > $MinPrice)
    {
        echo "\"@type\": \"AggregateOffer\",", chr(13) , chr(10), "\t\t", "\"highPrice\":", number_format($MaxPrice,2, '.', ''), ",", chr(13) , chr(10), "\t\t", "\"lowPrice\":", number_format($MinPrice,2, '.', ''), ",";
        echo "\"offerCount\": \"10\",";
    }</actinic:block>

This is what I did for a soapbox customer, hopefully you can adapt it:

Code:

"@type": "Product",
        "aggregateRating": {
        "@type":  "AggregateRating",
        "ratingValue": "<actinic:block php="true">echo <actinic:variable encoding="perl" name="SoapboxRating" selectable="false" /> /2;</actinic:block>",
        "reviewCount": "<actinic:block if="%3cactinic%3avariable%20name%3d%22SoapboxReviewCount%22%20%2f%3e%20%3d%3d%200">1</actinic:block><actinic:block if="%3cactinic%3avariable%20name%3d%22SoapboxReviewCount%22%20%2f%3e%20%3e%200"><actinic:variable name="SoapboxReviewCount" /></actinic:block>",
        "bestRating"  : "<actinic:block php="true">echo <actinic:variable encoding="perl" name="SoapboxRating" selectable="false" /> /2;</actinic:block>",
        "worstRating" : "<actinic:block php="true">echo <actinic:variable encoding="perl" name="SoapboxRating" selectable="false" /> /2;</actinic:block>"
    },
    "review": {
    "@type": "Review",
    "reviewRating": {
      "@type": "Rating",
      "ratingValue": "<actinic:block php="true">echo <actinic:variable encoding="perl" name="SoapboxRating" selectable="false" /> /2;</actinic:block>",
      "bestRating": "<actinic:block php="true">echo <actinic:variable encoding="perl" name="SoapboxRating" selectable="false" /> /2;</actinic:block>",      
        "worstRating" : "<actinic:block php="true">echo <actinic:variable encoding="perl" name="SoapboxRating" selectable="false" /> /2;</actinic:block>",
      "description": "<actinic:variable encoding="Strip and Encode" name="SoapboxEmbeddedReviewContent" selectable="false" />"
    },
    "author": {
      "@type": "Person",
      "name": "Valued Customer"
    }

  },

Soapbox ratings are 1-10 hence dividing by two for google's 1-5

Announcement

Google Schema - Rich snippets

Google Schema - Rich snippets

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment