Updated 13 October 2026 · B2B advisory and acquisition in Tunisia
Product Schema: making your product page information reliable
A product page may show a current price while retaining an old amount in its structured data. This mismatch makes the catalogue less reliable for systems using that information.
Product Schema describes a product in a structured format. It helps search engines interpret certain characteristics and may contribute to eligibility for enhanced presentations. It guarantees neither their display nor an increase in traffic.
For a Tunisian company, the priority is to align markup with an accurate page and a real commercial journey. Here are the checks to organise before multiplying properties.
1. Which pages is Product Schema suited to?
Product markup describes an identified product. Start with individual pages presenting its characteristics and terms. A category page, article and consulting service serve other purposes.
This guide remains an editorial article: it explains markup without becoming a product offer itself. Adding Product everywhere does not make every page an eligible product result.
For a B2B catalogue, distinguish references available for purchase from those presented through a quotation request. The journey and available information determine what can be declared. An SEO audit of the website can identify the page templates involved.
2. Which presentations does Google distinguish?
| Framework | Use | Check |
|---|---|---|
| Product snippets | Enhanced information about a product | Required properties and page content |
| Merchant listings | Purchase-related experiences | A page enabling purchase and specific requirements |
Google distinguishes these two frameworks in its documentation. A page on which visitors cannot buy does not become eligible for merchant listings simply by adding an Offer property.
For product snippets, Google requires the name and at least one of offers, review or aggregateRating, with the corresponding requirements. This rule never justifies fabricating missing data. Check the conditions for the intended result, because recommendations differ between the two frameworks.
3. Which information should you check in the catalogue?
Check the product’s identity, description, images and identifiers actually available. The name should designate the reference presented, with the characteristics needed to avoid confusion between several models.
When an offer is declared, check its price, currency, URL and availability. A zero price is acceptable only for an actually free offer; it does not represent a price to request from the seller.
Reviews and ratings must correspond to real evaluations and the rules applicable to the intended result. Invented reviews or an average without verifiable data undermine the page’s reliability.
Define who corrects information: the catalogue team, sales administration or website owner. A property correct at launch may become wrong at the next update.
4. How should you handle variants and quotation requests?
A difference in size, capacity or packaging can change price and availability. Check the variant actually selected and the URL representing it. The technical model should allow a consistent description of each situation.
On a “price on request” page, do not enter a fictional amount to satisfy a test. Describe known characteristics and examine, with the technical owner, which presentations are actually available to that page.
The right choice may be to complete the journey before targeting a merchant result. A delivery condition, minimum order or commercial restriction should also be understandable to visitors.
Our website creation and development advisory service connects these constraints with catalogue operation.
5. How should you avoid duplicates and outdated data?
A theme, SEO plugin and ecommerce plugin may generate structured data simultaneously. Multiple scripts are not automatically an error, but contradictory descriptions of the same product need examination.
Identify the component responsible for markup and its data source. Check whether updating the visible price also changes the JSON-LD. Check caches and values generated for visitors who are not logged in.
Keep an inventory of templates and their exceptions. Correcting one reference does not prove that all variants, promotions or stock shortages behave the same way. Test representative cases before generalising.
6. Example: checking a professional equipment page
Fictional example. A company presents a machine in two capacities. The smaller version can be purchased, while the larger requires a consultation to specify installation.
The check starts with each version’s visible information. The team then verifies prices and generated URLs, followed by the JSON-LD actually rendered. It does not copy the purchasable version’s price onto the version offered only by quotation.
A checking table records the reference, commercial status, test performed, correction and date. After an availability change, the team re-examines the page and markup. This example illustrates a procedure, without promising an enhanced display.
7. How should you test and measure the outcome?
Use Google’s Rich Results Test to examine the technical eligibility of representative pages. Distinguish errors that block a framework from warnings about recommended properties.
Complement the test with a review of the page: syntactically accepted markup may still be commercially inaccurate. Then examine available Search Console reports and actually observed changes.
The guide Search Console: organising the SEO diagnostic helps monitor pages and their performance. A change in click-through rate may have several causes; it should not automatically be attributed to markup.
Does Product Schema guarantee a rich result?
No. Compliance contributes to eligibility, but Google chooses which presentations to display.
Should you add stars without reviews?
No. Ratings and reviews must be real and meet the documentation’s conditions.
Should a quotation-only page display a zero price?
No. Zero describes something actually free. It does not replace an unavailable price.
Make your product pages and markup reliable
Socials Analytica helps you audit page templates, define corrections and organise checks with your technical and catalogue teams.
Explore the relevant advisory service
Let’s discuss your project on WhatsApp.
To define your priorities, ask us about our B2B acquisition diagnostic, a paid service distinct from the initial conversation.
Sources and references
Documentation consulted on 13 October 2026.
