Difference between revisions of "How to add Structured data for rich snippets"
| Line 17: | Line 17: | ||
Check the [http://schema.org/docs/full.html list of all available Schema.org objects]. Choose the most accurate object type that describes your listing (what is being reviewed). Don't add the "Rating" or "Aggregate Rating" objects because they are included in JReviews by default as sub-objects of the main object. | Check the [http://schema.org/docs/full.html list of all available Schema.org objects]. Choose the most accurate object type that describes your listing (what is being reviewed). Don't add the "Rating" or "Aggregate Rating" objects because they are included in JReviews by default as sub-objects of the main object. | ||
| + | Most Schema.org objects have many properties that describe the listing. For example, the '''Product''' object type has a ''brand'' property. If your product listing has a custom field that outputs the name of the product brand, you can add the property name to the field output so that Google will know which part of the product page is a brand name. This can be done using the '''Output Format''' text area of individual custom fields in the Fields Manager. | ||
| + | For example, the Output Format of a field looks like this: | ||
| + | <pre> | ||
| + | {fieldtext} | ||
| + | </pre> | ||
| + | |||
| + | To add the "brand" property, change it like this: | ||
| + | <pre> | ||
| + | <span itemprop="brand">{fieldtext}</span> | ||
| + | </pre> | ||
| + | |||
| + | After making the changes, check the listing in the [https://search.google.com/structured-data/testing-tool Rich Snippets Testing Tool] again to see if the changes are valid and if the new property is included: | ||
| + | |||
| + | [[File:Rich-snippets-test-results.png]] | ||
Revision as of 16:11, 15 July 2016
JReviews adds Structured data markup so Google can use that data to index your content better and present it more prominently in search results. Here is an example of Google search results with breadcrumbs and rating rich snippets:
The code required for this is included in JReviews by default, but keep in mind that Google doesn't automatically include rich snippets in search results for every site just because the site contains the required code, other factors like site popularity are considered as well. If Google detects fake reviews or reviews copied from other sites, that can also be a reason why rich snippets aren't included in search results.
To improve your chances of rich snippets being included in search results, you can:
1. Test your listing detail pages with the Rich Snippets Testing Tool to check if there are any errors. If errors exist, do what Google suggests to fix them.
2. Add additional Structured data markup provided by Schema.org
The first thing that you should do is set the main Schema.org Object Type for your listings. This is done in the Listing Types Manager for each individual listing type. For example, if you have a listing type for Products, the correct Schema.org object would be http://schema.org/Product. Edit the listing type in the Listing Types Manager and you will find the setting in the SEO Manager tab:
Check the list of all available Schema.org objects. Choose the most accurate object type that describes your listing (what is being reviewed). Don't add the "Rating" or "Aggregate Rating" objects because they are included in JReviews by default as sub-objects of the main object.
Most Schema.org objects have many properties that describe the listing. For example, the Product object type has a brand property. If your product listing has a custom field that outputs the name of the product brand, you can add the property name to the field output so that Google will know which part of the product page is a brand name. This can be done using the Output Format text area of individual custom fields in the Fields Manager.
For example, the Output Format of a field looks like this:
{fieldtext}
To add the "brand" property, change it like this:
<span itemprop="brand">{fieldtext}</span>
After making the changes, check the listing in the Rich Snippets Testing Tool again to see if the changes are valid and if the new property is included:
