Jewelry schema is structured data, usually written in JSON-LD, that describes a jewelry website’s products, offers, reviews, business and store locations in a format search engines read directly. A jewelry store needs Product markup with an Offer on every product page, Organization and WebSite markup on the home page, BreadcrumbList on collections and products, and JewelryStore markup on each showroom location page if it has physical stores.
Schema doesn’t raise rankings on its own. What it does is make pages eligible for product snippets, merchant listings and other search features, help Google match your products to shopping searches and keep your business details consistent across search and AI-assisted answers. It only works when it’s accurate: the markup has to describe what’s visible on the page, and Google’s rules on reviews and FAQs have tightened in recent years.
This guide sets out which types to use where, the properties that matter for jewelry, and the rules that decide whether markup helps or gets ignored. Property tables stand in for full code samples; your developer or platform turns them into JSON-LD.
Which schema types a jewelry site needs
Most jewelry websites need five or six types. Each belongs on a specific page type.
| Schema type | Where it goes | What it supports |
|---|---|---|
| Product with Offer | Every product page | Product snippets, merchant listings, Shopping data |
| ProductGroup | Products with variants | Variant understanding (size, color, material) |
| Organization | Home or about page | Brand details, logo, contact and policies |
| WebSite | Home page | Site name shown in results |
| BreadcrumbList | Collections, products, guides | Page position in the site hierarchy |
| JewelryStore | Each showroom location page | Store address, hours, phone |
| Article with Person | Guides and blog posts | Author and publication details |
Google recommends JSON-LD as the format, and it’s what Shopify themes and WordPress SEO plugins output. Keep one block per type per page. Two Product blocks for the same item, one from the theme and one from an app, is a common source of errors.
What is jewelry schema?
Jewelry schema is structured data, usually in JSON-LD, that describes a jewelry site’s products, prices, availability, reviews, business details and store locations so search engines can read them precisely and show them in product and local search features.
Product and Offer on product pages
Google describes two experiences that Product markup supports. Product snippets add details such as price, availability and ratings to a standard result. Merchant listing experiences cover shopping surfaces for pages where a buyer can purchase the product. A jewelry product page with a working buy button should be marked up for both.
Core Product properties
| Property | What to put in it | Notes |
|---|---|---|
| name | The product title | Match the H1 |
| image | Several high-quality image URLs | Include main and alternate views |
| description | The product description | Your written copy, not supplier text |
| brand | A Brand with a name | Your brand or the designer’s |
| sku | Your SKU | Match the feed |
| gtin or mpn | Barcode or manufacturer part number | Where the piece has one |
| offers | An Offer (see below) | Required for merchant listings |
| aggregateRating, review | Customer ratings and reviews | Only when visible on the page |
Offer properties
| Property | Value | Notes |
|---|---|---|
| price | Numeric price, such as 2450.00 | Must match the visible price |
| priceCurrency | Three-letter code, such as USD | Required with price |
| availability | InStock, OutOfStock, PreOrder, BackOrder | Update when stock changes |
| itemCondition | NewCondition or UsedCondition | Use UsedCondition for estate and pre-owned |
| url | The canonical product URL | Not a collection path |
| shippingDetails | Shipping rate and delivery time | Recommended for merchant listings |
| hasMerchantReturnPolicy | Return window and method | Recommended; must match your policy page |
Price accuracy matters more for jewelry than most categories. Gold pieces priced against the metal market can change price often. If the page, the markup and the Merchant Center feed disagree, Shopping listings can be disapproved and snippets show the wrong price. Generate the markup from the same data that renders the page, never from hardcoded values.
Jewelry attributes in Product markup
Jewelry buyers search by attributes, and markup can carry them. Schema.org gives Product some direct properties and a general additionalProperty field for everything else.
| Attribute | Property | Example value |
|---|---|---|
| Metal | material | 14k white gold |
| Metal color | color | White |
| Weight | weight (QuantitativeValue) | 4.2 grams |
| Carat weight | additionalProperty (PropertyValue) | Carat total weight: 1.50 |
| Diamond grades | additionalProperty | Color: F; Clarity: VS1; Cut: Excellent |
| Diamond origin | additionalProperty | Origin: Laboratory-grown |
| Certificate | additionalProperty | Grading report: IGI, followed by the report number |
| Chain length | additionalProperty or size | 20 inches |
Google doesn’t promise to use every additionalProperty value in search features, so treat these as clarifying context rather than a route to a visible enhancement. The visible specification block on the page matters more; markup should mirror it, not replace it. Our jewelry product page guide covers what that specification block should contain.
Ratings and reviews: the rules that keep you eligible
Star ratings in search results draw attention to a listing, which is why review markup is the most abused schema on ecommerce sites. Google’s review snippet guidelines are strict, and breaking them can cost you rich results across the site.
Ratings must come from customers and be visible on the page. If a product page shows 4.8 stars from 23 reviews in markup, a visitor must be able to see those reviews on that page.
Don’t aggregate reviews from other websites. Google’s guidelines say review markup shouldn’t aggregate ratings collected on other sites. Reviews collected by your own store or by a review app on your product pages are fine.
Self-serving reviews don’t get stars. Since 2019, Google doesn’t show review rich results for LocalBusiness and Organization markup when the business displays reviews about itself on its own site. Putting your Google review average into your home page Organization markup won’t produce stars.
Don’t mark up collections with product ratings. AggregateRating belongs on the product it describes. A collection page with an aggregate rating across many products is misleading markup.
Never invent or seed reviews. Fake reviews are a policy violation under Google’s rules and a consumer protection problem under the FTC’s rule on fake reviews.
Variants with ProductGroup
Most jewelry products have variants: ring sizes, chain lengths, metals, carat weights. Google supports product variant structured data through ProductGroup.
| Property | Where | Example |
|---|---|---|
| productGroupID | ProductGroup | The parent product’s ID |
| variesBy | ProductGroup | size, color, material |
| hasVariant | ProductGroup | A list of the variant Products |
| inProductGroupWithID | Each variant Product | The parent’s productGroupID |
| sku, offers | Each variant Product | Variant-level SKU, price and availability |
Use it when variants differ in price or availability, such as a ring offered in 1, 1.5 and 2 carat center stones at different prices. Each variant Product carries its own Offer. For variants that only differ by ring size at the same price, a single Product with one Offer is often enough. Whichever you use, the variant prices in markup must match what the buyer sees when they select that option.
Organization and WebSite on the home page
Organization markup tells Google who runs the site. It supports the logo and business details Google may show, and it gives AI-assisted search tools a clean, consistent description of the business.
| Property | Value for a jewelry business |
|---|---|
| name | Your trading name, exactly as on the site and Business Profile |
| url | Home page URL |
| logo | A square or rectangular logo image URL |
| sameAs | Official profiles: Instagram, Pinterest, Facebook, YouTube |
| contactPoint or telephone, email | Customer service contact |
| address | Head office or registered address |
| hasMerchantReturnPolicy | Store-wide return policy, if it applies to all products |
Google has documented store-wide return policy markup under Organization, which helps when the same policy covers every product. Product-level return policies override it where they differ, for example final-sale custom pieces.
WebSite markup on the home page, with name and url, helps Google show your preferred site name in results. Google retired the sitelinks search box in late 2024, so search action markup no longer produces a visible feature.
LocalBusiness and JewelryStore for showrooms
Schema.org includes a JewelryStore type, a subtype of Store under LocalBusiness. A jeweler with physical showrooms should use it on each location page.
| Property | Value |
|---|---|
| @type | JewelryStore |
| name | Store name as it appears on the Business Profile |
| address | Full street address (PostalAddress) |
| telephone | The location’s phone number |
| geo | Latitude and longitude |
| openingHoursSpecification | Days and hours, including special hours |
| url | The location page URL |
| image | Photos of the storefront and interior |
| parentOrganization | The Organization, for multi-store groups |
Google uses Business Profile data as its main source for local panels and the map pack, so markup doesn’t replace the profile. Its value is consistency: when the location page, the markup and the Business Profile carry identical name, address, phone and hours, Google and AI search tools have fewer conflicting signals. For multi-store jewelers, give each store its own location page and its own JewelryStore block. Don’t put every store’s address in one block on the home page. Our local SEO for jewelers service covers the profile side of this work.
FAQ, HowTo and markup that no longer shows
Some schema types still circulate in old SEO advice but no longer produce visible results for jewelry sites.
FAQPage. In August 2023, Google limited FAQ rich results to well-known, authoritative government and health websites. A jewelry store’s FAQ markup won’t create expandable questions under its result. Visible FAQs on collections and product pages are still worth writing for buyers and for AI-assisted search; the markup is optional and harmless when it matches the visible questions.
HowTo. Google deprecated HowTo rich results in 2023. Ring sizing or jewelry cleaning guides won’t get step-based results from markup.
Sitelinks search box. Retired in late 2024, as noted above.
Plan schema around Product, Organization, local and breadcrumb markup, which still support active features.
Breadcrumbs, articles and authors
BreadcrumbList belongs on every collection, product and guide page, matching the visible breadcrumb. Each ListItem has a position, a name and the item URL. On Shopify, products can belong to many collections, so set one primary path per product and use it in both the visible breadcrumb and the markup.
Article or BlogPosting belongs on guides and blog posts, with headline, image, datePublished, dateModified and an author marked up as a Person with a name and a URL to their author page. For jewelry buying guides, a named author with genuine jewelry or gemology experience gives buyers and search engines a clear source.
Implementing and validating on Shopify and WordPress
Shopify
Most current Shopify themes output Product JSON-LD on product pages and basic Organization data. Before adding an app, view the page source or run the Rich Results Test to see what the theme already provides. The common problems are a review app or SEO app adding a second Product block, markup that ignores variant prices, and missing shipping and return details. Fix the theme template or configure the app so only one complete block remains. The Shopify setup guide for jewelry stores covers where this sits in a full store setup.
WordPress and WooCommerce
WooCommerce outputs product structured data, and SEO plugins add Organization, WebSite, BreadcrumbList and Article markup. Check that the plugin and WooCommerce don’t both output Product, and that the plugin’s Organization settings use your exact business name and logo.
Validate every template
- 01
Step 1
Test each template type
Run one product, one variant product, one collection, the home page and one location page through Google’s Rich Results Test.
- 02
Step 2
Check the full vocabulary
Use the Schema Markup Validator to catch property errors that the Rich Results Test ignores.
- 03
Step 3
Compare with the page and feed
Confirm price, availability, name and images in the markup match the visible page and the Merchant Center feed.
- 04
Step 4
Monitor in Search Console
Review the product snippets, merchant listings and breadcrumb reports monthly and fix new errors after theme or app changes.
Schema is part of the technical foundation our technical SEO for jewelry work covers, alongside crawling, canonicals and speed.
Jewelry schema FAQs
What schema should a jewelry store use?
Product with an Offer on every product page, ProductGroup for variants with different prices, Organization and WebSite on the home page, BreadcrumbList on collections and products, Article on guides, and JewelryStore on each showroom location page.
Does schema markup improve jewelry rankings?
Not directly. It makes pages eligible for product snippets, merchant listings and other features, and helps Google understand products and business details precisely. Those features can improve click-through rate, and accurate data supports Shopping and AI-assisted search.
Can I show my Google review stars on my home page through schema?
No. Google doesn’t show review rich results for Organization or LocalBusiness markup when a business displays reviews about itself on its own site. Product review stars are possible when customer reviews for that product are visible on the product page.
Is FAQ schema still worth adding?
Since August 2023, FAQ rich results only appear for well-known government and health sites, so FAQ markup won’t change a jewelry store’s search listing. Visible FAQ content still helps buyers and AI-assisted search. Adding the markup is optional.
Should I use LocalBusiness or JewelryStore?
Use JewelryStore, the more specific schema.org type for jewelry shops. It inherits all LocalBusiness properties. Put it on each location page, with the same name, address, phone and hours as that store’s Business Profile.
Why does Search Console show schema errors after installing a review app?
Many review apps add their own Product or rating markup, creating a second block that conflicts with the theme’s markup. Check the page source, then configure the app or edit the theme so only one complete Product block remains.
How should I mark up lab-grown diamonds?
State the origin clearly in the product name and visible description, and mirror it in the markup, for example as an additionalProperty for origin. The markup must describe exactly what the page discloses.
Written by
Muhammad Sufyan
AI Search Head, TechUp Solutions
Muhammad Sufyan leads AI search and technical SEO delivery at TechUp Solutions: entity and structured-data work, crawl and indexing audits, Search Console diagnostics and the content patterns that AI assistants quote. He checks every SEO For Jewelry guide in his area for technical accuracy before it is published and again when it is updated.
Meet the teamHow we review guides
Reviewed by
Muhammad Arslan
Technical & Paid Search Head, TechUp Solutions
Muhammad Arslan leads technical SEO implementation and paid search at TechUp Solutions: Shopify and WooCommerce indexing fixes, site migrations, GA4 and Google Tag Manager tracking, Merchant Center feeds and Search and Shopping campaigns for jewelry clients.