How to Add Reviews to PrestaShop: Hooks Decide Everything

PrestaShop builds a page by calling hooks, which are named points in the template where modules get a chance to render. Nothing appears on a storefront because it exists; it appears because something attached it to a hook that the page calls. That single fact explains the most common PrestaShop frustration, which is a block that is saved, correct, visible in the admin, and nowhere at all on the site.

The Custom HTML Block

Create a custom HTML block in the admin and paste the widget embed into its content. Use the source or code view if the field offers one, since a visual field will escape the markup.

Give it a name that says what it is. On a store with a dozen modules, a block called Block 3 is a mystery in six months.

Save it. At this point the block exists and renders nowhere, which is normal and is the next step rather than a fault.

Attach It to a Hook

PrestaShop templates call hooks at defined points: after the product description, in a column, above the footer. A module or block renders when it is attached to one of those and the page being viewed calls it.

Choose the hook by where you want the reviews to appear and on which pages. A product-page hook puts the block on product pages, a home hook puts it on the home page, and they are separate decisions.

This is the step that is missing when a block is saved and invisible. Nothing is broken; the block simply has no invitation to render.

Then Clear the Cache

PrestaShop compiles templates and caches them, and a newly hooked block frequently does not appear until that cache is cleared. This is the second half of the same frustration.

Clear the cache from the admin and reload the storefront. If the store also sits behind a page cache or a CDN, that layer needs purging too.

Doing both steps by habit after any structural change saves a lot of time diagnosing things that were never wrong.

The Theme Decides Which Hooks Exist

Available hooks come from the theme as much as from PrestaShop. A custom or purchased theme may add hooks, may not call some defaults, and may position them differently from what their names suggest.

So if a hook that sounds right produces nothing visible, try a neighbouring one before concluding the block is broken. The names are a guide rather than a guarantee on a customised theme.

On a heavily modified store, the fastest route is often to ask whoever built the theme which hook renders where, if that person is reachable.

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 theme.

A compact layout is easier to hook successfully, because column hooks are narrow and a wide grid placed in one will look wrong even when it technically works.

The header rating comes from the platform aggregate rather than from the cards on screen. Free plan, unlimited widget views.

Where Should the Reviews Go?

On the product page, hooked after the product information and before or beside the add to cart area. That is where a first-time buyer hesitates on a store they do not know.

The home page is a reasonable second placement for a compact badge, particularly on a store where the home page is the main entry point.

Keep it off the cart and the checkout. Those pages have one job each and a block offering a link away costs more than it adds.