How to Add Reviews to Ecwid: Two Places, One Right Answer

Almost every other builder in this series owns the whole page, so there is only one place a snippet can go. Ecwid is different by design. It is a store that installs into a website you already have, which means a page with an Ecwid store on it has two owners: the host platform owns the page, and Ecwid owns a region inside it. Work out which of those you are pasting into and the rest is ordinary. Get it wrong and the widget will appear to work until the store re-renders and takes it away.

Your Store Lives Inside Another Site

Ecwid documents several ways to add commerce to an existing website: the full catalogue embedded on a page, a single category on its own page, Buy Button widgets for individual products, or Instant Site as a hosted storefront on a subdomain. The first three all put the store inside a page that something else built.

That host might be WordPress, Wix, Squarespace, a hand-built site or anything else with somewhere to put code. Ecwid arrives either through a plugin for that platform or through integration code that varies depending on the platform, and the host site keeps its own theme, header, footer and page structure around the store region.

So when you ask where the review widget goes, the honest answer is a question back: is the page a host page with a store in it, or is it Instant Site? Those are different products with different answers, and most confusion about Ecwid embeds comes from guides that assume one and are read by someone using the other.

On a Host Site, Paste Into the Host

If the store is embedded, use the host platform’s own code element. A Custom HTML block in WordPress, an Embed element in Wix, a Code Block in Squarespace. The widget then sits in the page alongside the store region rather than inside it, which is what you want.

The reason is that the store region is managed. Ecwid renders and re-renders it as the shopper moves between the catalogue, a category and a product, and anything you have injected into that area is at the mercy of that lifecycle. Content in the host page is not.

This also gives you the placement you actually want. A reviews section above the catalogue or below it is a statement about the business, and it should be as stable as the header and the footer are. Putting it in the host page makes it exactly that.

The Instant Site Exception

If Ecwid is the whole storefront, the picture simplifies. Open the Instant Site editor, add a section and choose custom code, or edit the code slot on an existing section, then paste the widget embed and publish. The reviews render on the live Instant Site.

The About section is the natural home, directly above the store section. Instant Site pages are short and ordered, so a visitor scrolling to the products passes the reviews on the way, which is the sequence you want rather than the reverse.

Ecwid also offers Instant Site as the fallback when a host site is iframe-based or otherwise awkward to integrate with. If you have ended up there for that reason, the same advice applies: it is now the whole page, so the custom code section is the right slot.

Plugin Installs Versus Integration Code

Which route the store arrived by changes where to look for a code element, though not the principle. If a platform plugin installed the store, the plugin usually owns a shortcode or a block and the rest of the page is edited normally, so the host platform’s code element is right there in the editor.

If the store arrived as integration code pasted into a page, you already know where the host code element is, because you used it. The review widget goes in the same kind of element, in the same page, above or below the store code rather than inside it.

Either way, do not put the widget inside the same block as the store snippet. Keeping them in separate elements means one can be moved, edited or removed without disturbing the other, which matters the first time you restyle the page.

When It Does Not Render, Work Out Which Layer

The most common symptom is a widget that shows on first load and disappears after the shopper clicks into a product. That is the store re-rendering its region, and it tells you the embed is inside the store area rather than in the host page. Move it and the symptom goes.

The second most common is a widget that shows on the storefront page but nowhere else. That one is usually correct behaviour being misread: the widget is in a single host page, and other pages have not had it added. Decide whether it belongs on more than one and add it there deliberately.

Third is nothing rendering at all, which is nearly always the host platform rather than Ecwid. A visual editor that escaped the script, a plan that does not include custom code, a caching layer serving the old page. Check the host first, because Ecwid is rarely the thing in the way.

How Do You Build the Widget?

Paste your Google, Trustpilot or Facebook profile URL, preview your real reviews and rating, then choose from over 100 layout styles across the slider, marquee, grid, list, masonry and badge families, and match the colours to the host site rather than to Ecwid.

Matching the host matters more here than on a single-platform build, because a shopper sees your header, your reviews and then the store region, and the store region already has its own visual language. The reviews should belong to the site around it.

The header rating comes from the platform aggregate rather than from the cards on screen, so the number stays honest against the profile. Free plan, unlimited widget views, which keeps it out of the way as the store grows.

Where Should the Reviews Go?

Above the store region on the main shopping page. A shopper arriving cold has one question before browsing, which is whether this shop is real and ships what it says, and that question is answered before the products rather than after them.

Add a compact badge near the contact or shipping information as well. That is where a hesitant buyer goes looking for reassurance, and a rating in that spot is doing work that a review wall higher up the page has already stopped doing.

Keep it off the cart and the checkout. Those pages have one job, and anything that invites a click away from them costs more than the reassurance it adds.