Salla schema markup: what actually helps
Which schema types a Salla theme already outputs, which are worth adding yourself, and how to check the markup matches what a buyer actually sees.
Most Salla themes already output basic Product schema, so the work is usually validation rather than a build: confirm the price, currency, availability and name in the markup match the page, add BreadcrumbList on category pages, and only add Review schema when you have genuine, on-site reviews to mark up.
That is one slice of the wider Salla SEO guide, which covers everything else the platform leaves in your hands. This post is just the structured-data part of it.
On this page
What does Salla already add to your product schema?
Usually the basics. Most Salla themes generate Product markup automatically from the fields you already fill in on the product page — name, price, currency and, on many themes, availability — because the theme template renders that data into the page and into a JSON-LD block at the same time.
What varies is completeness and accuracy, not presence. Some themes stop at name and price and leave out availability entirely. Others emit availability but do not update it reliably when stock changes on the backend, which produces a markup that says "in stock" on a page that says "sold out." Google's own documentation on Product markup lists the properties it looks for and treats missing or mismatched ones as reasons to ignore the block rather than reasons to guess [1].
So the first job on any Salla store is not writing schema. It is opening a handful of product pages, viewing the page source, and reading what is already there against what Google actually asks for.
| Property | Usually present | Worth checking |
|---|---|---|
| Product name | Yes | Matches the visible H1, not a shortened version |
| Price and currency | Usually | Updates when you run a sale, not just on load |
| Availability | Sometimes | Reflects real stock, not a default value |
| Images | Usually | Points at the actual product image, not a placeholder |
| Reviews / rating | Rarely | Only add if reviews genuinely exist on the page |
| Breadcrumb | Rarely | Worth adding on every category and product page |
Which schema types are worth adding yourself?
Mainly one: BreadcrumbList. It is the type most hosted stores leave out entirely, and it is also the cheapest to add correctly, because the data it needs — the category path from the home page to the current page — already exists in your navigation.
Google's structured data guidance treats breadcrumbs as a way of describing a page's position in your site, and a search result that can show that position instead of a raw URL is a small but real improvement in how a listing reads [4]. On a store with several category levels, that is the difference between a URL string and a path a shopper can actually parse.
Review and AggregateRating schema are worth adding only when the underlying reviews are real and live on the page you are marking up. Google's general structured data guidelines are explicit that markup has to reflect content a user can actually see on the page, and review data is one of the categories it checks most carefully, because it is also one of the most abused [2]. If your store does not yet collect on-site reviews, the honest move is to skip this type entirely rather than mark up a rating you cannot back up.
Everything past those two — FAQ-style markup, how-to markup, organization markup on the homepage — is worth less on a product catalogue than getting Product and BreadcrumbList right on every page, because those two run at catalogue scale and the rest do not.
How do you check the markup is actually correct?
By reading it against the live page, not by trusting that a green checkmark in a testing tool means the data is true. A validator can confirm the JSON-LD is well-formed and confirm which properties are present; it cannot confirm that the price it sees matches the price a buyer sees, because it has no idea what the page is supposed to say.
View the page source on five real product pages
Not a demo product — five ordinary ones, including one that is currently out of stock and one that is on sale, because those are where mismatches show up first.
Read the JSON-LD block against the page
Name, price, currency and availability should match exactly what a visitor sees, not a cached or default value.
Repeat for a category page
Check whether BreadcrumbList is present at all, since on most Salla themes it is not unless something has been added deliberately.
Recheck after every theme update
A theme update can quietly change the template that generates this data. Treat schema as something you verify on a schedule, not something you set once.
What commonly breaks schema on a Salla theme?
The same filtered and duplicated URLs that cause other problems on hosted stores. When a theme generates a distinct, indexable URL for every filter or sort combination, each of those URL variants often inherits — or fails to inherit — schema in inconsistent ways, and the same duplicate content problem that costs you crawl budget tends to produce inconsistent or missing markup on the very variants a crawler is most likely to land on.
Stale availability is the other common failure, and it is worth naming as its own category rather than folding it into "check everything." A product that sells out at 11pm and stays marked "in stock" in its schema until the next scheduled sync is not a rare event on a busy store; it is a routine one, and it is the single most common reason a schema audit finds a mismatch on a Salla catalogue.
A third, quieter cause is an app. Stores that install a third-party reviews widget, a loyalty plugin or a bundling app sometimes end up with two schema blocks on one page — the theme's own and one injected by the app — describing the same product slightly differently. Search engines are not obliged to pick the correct one, and a page carrying contradictory markup is worse off than a page carrying none at all. Checking for duplicate JSON-LD blocks in the page source is worth doing once you have ruled out the theme itself.
None of this is about page speed directly, but the discipline is the same one that applies to Salla store speed: verify against the real, current state of the page rather than assuming a setting you configured once is still true.
Does schema markup change your rankings?
Not directly, and it is worth being blunt about that before anyone spends a week on it expecting a ranking jump. Structured data makes a page eligible for a richer search result — a price, a rating, a breadcrumb trail shown directly in the listing — and Google is explicit that eligibility is not a promise of appearance, and that markup contradicting the page can be ignored outright [2][3].
What it does change is the click a listing gets once it appears, because a result showing a price and a rating gives a shopper more reason to click than a bare blue link. On a catalogue with hundreds of product pages, that difference compounds even though no individual page's ranking moved.
The order of operations that makes sense here: get Product and BreadcrumbList correct everywhere first, because that is catalogue-wide leverage, and treat anything more exotic as optional polish rather than a priority.
What should you fix first?
Availability accuracy, then BreadcrumbList, then everything else. A wrong price or stock status in your markup is the kind of error a search engine treats as a trust signal about the whole domain, not just the one page, so it is worth fixing before anything additive. BreadcrumbList is next because it is missing on most stores and costs almost nothing to add once the navigation data exists.
If you also run a blog on the store, the same discipline — check what the platform already outputs before you add anything by hand — applies there too; see blogging inside Salla for what that looks like on articles rather than products. And if schema is one item on a longer list of things you suspect are wrong with the store, our ecommerce SEO service runs the fuller audit this post only covers one slice of.
Nobody loses rankings over missing schema. They lose trust in their listings over schema that says something the page doesn't, which is a much easier mistake to make on a hosted store than people expect.
Whether your schema even renders correctly can depend on which apps are running on the same pages — Salla SEO apps worth installing covers which categories touch markup and which just add unrelated scripts.
Questions people also ask
Does Salla add schema markup by itself?
Most Salla themes output basic Product markup on their own, generated from the same fields you already fill in for the product page. The quality varies by theme, which is why checking it is worth an afternoon before you assume it is correct.
Do I need to write JSON-LD by hand on Salla?
Rarely. The more common job is validating what the theme already emits and adding the one or two types it leaves out, such as BreadcrumbList. Hand-written JSON-LD is usually only needed for something a theme genuinely cannot produce.
Should I add Review schema if I don't have on-site reviews?
No. Review and AggregateRating markup must reflect reviews collected on your own site under Google's guidelines. Marking up review data you do not actually have is the fastest way to draw a manual action, not a rich result.
Does correct schema markup guarantee a rich result?
No. Structured data makes a page eligible for a richer listing; it does not guarantee one appears, and Google can and does ignore markup that does not match the page. Treat it as a prerequisite, not a lever you can pull for a specific outcome.
How often should I re-check schema on a Salla store?
After every theme update and every price or stock change process, at minimum. A theme update can silently change what it outputs, and stale availability in your markup is the single most common schema problem on hosted stores.
Sources
- Product structured data — Google Search Central (checked 22 September 2026)
- Structured data general guidelines — Google Search Central (checked 22 September 2026)
- Intro to how structured data markup works — Google Search Central (checked 22 September 2026)
- Breadcrumb (BreadcrumbList) structured data — Google Search Central (checked 22 September 2026)
Find out what your Salla theme is actually outputting
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Salla SEO: the complete guideHow to rank a Salla store: what the platform controls, what you control, Arabic product pages, duplicate theme URLs, and the order to fix things in.
- Salla vs Zid vs Shopify for SEOThree store platforms compared on what they let you control: URLs, templates, sitemaps, Arabic handling and speed, and which differences change rankings.
- Salla blog SEO: is it worth using?Whether Salla's built-in blog is worth using for SEO, what it can't do, and how to structure posts so they support products instead of competing with them.
- How to audit a Salla store's SEOA practical order for auditing a Salla store: what to check first, which tools to use, and how to turn the findings into a fixing sequence rather than a list.