Skip to main content

Shopadvizor widgets — France

FranceThis guide

Ratings widget and reviews carousel, from the French Shopadvizor catalogue.

Spain

Ratings widget, from the Spanish Shopadvizor catalogue.

Shopadvizor widgets show your product's ratings and reviews in your page's HTML, not in JavaScript. Search engines and AI crawlers read them without executing anything, and each widget comes with the structured data (schema.org JSON-LD) they need to consider showing a rich result.

That is the whole point. A widget that only appears after JavaScript runs is invisible to them, which is exactly the problem this replaces.

Available widgets​

Both widgets are served by the same endpoint, /v1/fragment. The variant parameter picks which one you get:

WidgetvariantWhat it shows
Ratings widgetcompact (default)Stars, decimal average and review count
Reviews carouselreviewsThe average and count on top, then up to 12 featured reviews as cards

How it works​

  1. Your server requests the fragment for a product (by EAN) and prints the response into your HTML, exactly as it comes. This is the step that matters for SEO.
  2. Optionally, you load hydrate.js once per page. It adds the carousel's arrows, dots and automatic advance; the ratings widget looks the same without it. The widget is fully indexable without it, and fully functional too — except on pages that insert it with JavaScript: see Step 2.
One URL for everything: saz-ssr-server.public.shopadvizor.com

It serves both the fragment/JSON endpoints and the optional browser bundle. Shopadvizor deploys and versions it — you don't host it.

How these docs are organised​

Both widgets share the same integration — the same decision, the same credential, the same parameters and the same checks. That lives in the General guide, with tabs wherever a widget behaves differently:

  1. Before you start — the one decision you have to make
  2. Step 1 — Print the fragment from your server
  3. Step 2 — The JavaScript enhancement (optional)
  4. Parameters
  5. Verify your integration
  6. What not to do
  7. Troubleshooting

Each widget's own page covers only what is specific to it: what it looks like, the structured data it emits, its extra styling hooks and its own troubleshooting.