Required elements

The elements that must remain visible however the review section is customised, and their legal basis.

You decide how the review section looks; some elements, however, are not design choices but obligations that the regulations place on how reviews are displayed.

In the default component, Sayproof displays these elements. They can be styled with CSS variables and CSS rules; hiding them is contrary to the terms of use.
In headless use, you must display these elements yourself. All of them are included as data in the review list and SSR responses.

On this page, Regulation refers to the Turkish Ministry of Trade’s Regulation on Commercial Advertising and Unfair Commercial Practices, and Guideline refers to the Turkish Advertising Board’s Guideline on Consumer Reviews (12 September 2023).

Elements

Element	Where it is in the data	Basis
Method statement link	`core.method_statement.url` and `label`	Guideline, Art. 6/3: explaining the verification process, the rules for publishing reviews, how the average rating is calculated and how sorting works
Only permitted sort orders; date by default	`sorts`, `core.sort.allowed`, `core.sort.default`	Regulation, Art. 28/B-4: sorting reviews by objective criteria
A single combined review stream	All reviews come in a single list	Regulation, Art. 28/B-3: publishing product, delivery and seller reviews in the same area, clearly and in an easily accessible way
Seller response and resolution shown in the same place as the review	`seller_response` and `resolution` on the review row	Regulation, Art. 28/B-7: publishing a complaint reported as resolved in the same place as the original review
Source label	`origin` on the review row (for values other than `own`)	Guideline, Art. 5/5-c: stating the source of a review shared from another source
Process experience label	`experience` on the review row (value `process`) and `words.experience_process`	Guideline, Art. 5/4: after a cancellation or return, a review is limited to the experience up to that stage. Showing the label is a Sayproof rule; the method statement explains that these reviews are marked separately.
Structured data matching the screen	`json_ld`, `aggregate`	Google Search’s structured data guidelines for review snippets

Verification badge

Guideline, Art. 6/4 makes the “verified buyer” wording mandatory for intermediary service providers (marketplaces). If you sell the product yourself on your own site, this wording is not mandatory for you. We still recommend displaying it: it is the mark that shows visitors the reviews are based on purchases. The default component displays the “Verified buyer” badge on every verified review. A review imported from a marketplace has no badge; a source label is shown instead.

Page check

The Page check tab on the Channels screen checks a product page rendered on your server (SSR) or with your own design for the required elements. You choose a channel and enter the https address of a product page on one of your verified domains; Sayproof reads the HTML the page’s server returns and does not run the page as a browser would. In the component drawn by the script these elements already come from the script.

If the page as it first loads has no review section (no data-review-root or data-review-item), no findings are given and the message “No review section was found in the page as it first loads.” is shown. If the review section loads after the page opens (by the Sayproof code or your site’s own code), the check can’t see it; open the page in a browser and check it yourself. When a review section is found, these findings are looked for:

Finding	Condition
Reviews are shown but the verified buyer badge is missing.	The channel’s market requires proof of purchase, and the page has a `data-review-item` other than imported marketplace reviews but no `data-review-verified`
More than one sort order is allowed but the page has no sort control.	More than one sort order is allowed in the channel’s market and the page has no `data-review-sort`
The method statement link is missing from the page.	The address of the channel’s method statement in the channel’s language does not appear on the page

If there are no findings, “All required elements were found on the page.” is shown. If the channel’s market rule does not allow sorting by date, this is not counted as a page finding; it is shown in a separate A note from this market’s rule box, because the rule comes from the Market rules screen, not from your page. If the address cannot be read, the answer is 400 invalid / url_invalid; if it is not on your verified domains, 400 invalid / host_unverified; if the page cannot be read, 502 page_unreadable. The check can only be run in a panel session with the “Can manage users and channels” permission; every check is recorded in the Activity history.

Additional rules for headless use

The “Write a review” button must only call the Sayproof.write method. Do not open your own form, and do not add a general button that invites visitors who have not bought the product to write a review. Guideline, Art. 8/4 prohibits steering people who have not bought the product towards writing a review; Sayproof.write verifies the purchase before opening the form.
Do not filter the list by rating by default. Filters the visitor chooses are permitted; however, showing only high-rated reviews when the page first opens amounts to hiding negative reviews and is a manipulative practice under Guideline, Art. 8/5.
Do not add options outside the permitted list to the sort menu. The server refuses sort requests that are not on the list in any case.
Do not calculate the average rating yourself. Use the aggregate.average and aggregate.stars_filled values; the value on screen and the value in the structured data must be the same.

Using reviews in other channels

If you use reviews in advertising, email or social media, use only reviews backed by proof of purchase, and a selection that reflects the general nature of the reviews. Selecting only the most positive reviews may be misleading (Regulation, Art. 28/B-6).